Error MEssage after Upgrade

[CaseyMeraz]

I just tried to upgrade my CRM to the latest version and recieved an error message. Now when I go into the CRM I get the following error message : "Sugar CRM 4.5.0a Files May Only Be Used With A Sugar CRM 4.5.0 Database.".

Does anyon know how I can fix this?

[Zucker Fan]

I am experiencing the same problem.

I started the upgrade, then had to recompile PHP to enable MBstrings. I restarted the upgrade, and after click on commit, I get the following error:

Sugar CRM 4.5.0a Files May Only Be Used With A Sugar CRM 4.5.0 Database.

I used the following upgrade patch that was downloaded today.

SugarSuite-Upgrade-4.2.1-to-4.5.0a.zip

How can I recover?

--
Marc

[cartagon]

Same problem. Seems to be something related with the mySQL version installed on the server, and a check that the installer doesn't perform correctly before upgrading.

I tried this: http://www.sugarcrm.com/forums/showt...4&page=3&pp=10, but nothing.

Can anyone help?

Is upgrading to mySQL 4.2.1 the solution?
Any way of restoring older files to get back to 4.2.0b?

I'm using Windows Server 2003. I installed sugar originally with BitRock Installer for version 4.1.0 and upgraded twice without problems, until today (upgrade to 4.5.0).

Thanks in advance!

[Zucker Fan]

When the upgrade process started, the 'pre-check' was fine with my files and the database.

I'm running Linux, but can't recall the exact version of MySQL - 4.x

I second the motion - if we can't get this fixed quickly, how can we rollback?!?

--
Marc

[cartagon]

Can anyone help there?

Thank you!

[cartagon]

I've been able to recover everything.

I've set up another server with Sugar 4.2.1b with BitRock over SuSe 9.0. after that, I've manually uploaded all the files from the database "sugarcrm" that I had in the origin server.

After that I've reviewed permissions, rebooted the server and sugar working again.

Good luck!

[lenardw]

i dont know how to start a new thread.I need help with the ff error:
CGI Error
The specified CGI application misbehaved by not returning a complete set of HTTP headers

[jorgex]

I started the upgrade, then had to recompile PHP to enable MBstrings. I restarted the upgrade, and after click on commit, I get the following error:

Sugar CRM 4.5.0a Files May Only Be Used With A Sugar CRM 4.5.0 Database.

I used the following upgrade patch that was downloaded today.

SugarSuite-Upgrade-4.2.1-to-4.5.0a.zip

--
Marc

Hello, I have same problem.

For pass "the Sugar upgrade Wizard pre-check", I upgraded mySQL and recompile PHP with MBstrings option.
My actually plataform: Linux Slackware, Apache2, mySQL 5.0.24, PHP 5.1.6

When I continued the process for upgrade my "Sugar-Suite 4.2.1b" to "4.5.0" using "SugarSuite-Upgrade-4.2.1-to-4.5.0a.zip" patch, and after click on "commit button", I got 2 lines something like this:
/path_to_sugar/xxxxx.php
/path_to_sugar/post_install.php

Now, when ever I load my Sugar-Suite for logon, I get the following message:

"Sugar CRM 4.5.0a Files May Only Be Used With A Sugar CRM 4.5.0 Database."

I need help

[tdp]

Sugar CRM 4.5.0a Files May Only Be Used With A Sugar CRM 4.5.0 Database.

This error almost always means that the upgrade bombed out at some point and didn't finish. Unfortunately, the only way I've found to recover from this is to restore the site from backups of both the site and the database. What I do know is that this isn't really related to versions of Apache, PHP or MySQL, unless you are running a version that is not in Sugar's supported version requirements. The best place to look for clues as to what is going wrong is in your server/system logs. PHP does complain about what is happening if you have logging enabled properly.

The other unfortunate bit is that I've found upgrade errors happen a LOT, so I've gone to testing all upgrades on a duplicate Sugar install and not touching my production site until I know what can go wrong and how to recover from it.

[rlbyrd]

Re: database version

I *do* remember reading somewhere on the forum earlier in the week that 4.5.0+ requires a minimum of MySQL 4.2.1, and that the upgrader mechanism was *not* doing a database pre-check. I can't find that post now, but I don't think I imagined it. Hopefully a Sugar Team resource can chime in on this to check my memory.