6.0.1 not starting

[LuckiestBoy]

This is a silly thing that happens with every update.

The update hung. So, I did a reinstall and then restored database that was from version 6. Now I can't get Sugar CRM to start.

Now it reports:

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

[Angel]

This usually means the config table needs to be updated to reflect the matching version number. However, you shouldn't be mixing databases from one version with program files from another.

[LuckiestBoy]

Very sensitive. I could understand if I was trying to open higher version file in lower version of Sugarcrm but not the other way round.

I expected this to be norm because my experience is 90% windows environment.

[Angel]

Yup, it always expects them to match up. I really don't see it as a problem and actually prefer it that way. Otherwise it could open doors to all kinds of weird issues.

[brightworkcreative]

I've just done an upgrade from 5.5.0 to 6.0.1 and now I'm getting the same message. The normal upgrade wizard process screwed up and was returning a fatal error afterward, so I copied the files from the patch into my existing installation and then ran the database upgrade script that was in the patch (the 55x to 6.0.1 mysql version). But it's still giving this error. Does the upgrade wizard write a new version number into the config table or something? How can I correct this so that my upgraded installation is working?

Many thanks for any help,

Scott

[Angel]

You need to correct whatever issue it is that caused you the initial problem during the upgrade and in turn, the fatal error.

Copying files and mixing them up in the manner in which you did only exacerbates the issue. I hope that you have a backup that you can revert to as your best course of action would be to do that, then resolve the upgrade issue, as unraveling what you currently have will take some time and intimate knowledge of Sugar.

[brightworkcreative]

Copying files and mixing them up in the manner in which you did only exacerbates the issue.

Angel,

Thanks for your advice. I do have a backup, so I can revert to that if needed. Regarding copying the files, though, the upgrade patch includes the files that differ from the previous version and only those, so why would copying those to the existing installation (overwriting the old ones) cause problems?

-Scott

[Angel]

In my opinion, this is a bit of a chicken and egg situation.

Yes, your comment is accurate, however, to successfully perform a manual upgrade, you need to have some intimate knowledge of Sugar. This is because there are a lot of subtle nuances to the process, as you discovered when you received the error about the database not being the proper version.

Anyway, if one has that level of intimacy with Sugar, it would stand to reason that you wouldn't have a need to do it either, as one's environment is unlikely to present situations that would call for it as one should be able to resolve those.

[glynd]

I went from 5.5.4 to 6.1 using the silent upgrade. This worked without complaint but now I get this error when I try to start SugarCRM
Sugar CRM 6.1.0 Files May Only Be Used With A Sugar CRM 6.1.0 Database.
Any ideas?

[andopes]

I went from 5.5.4 to 6.1 using the silent upgrade. This worked without complaint but now I get this error when I try to start SugarCRM
Sugar CRM 6.1.0 Files May Only Be Used With A Sugar CRM 6.1.0 Database.
Any ideas?

Let us know the version of sugar inside script sugar_version.php, at the root of system and the version of database through query:
SELECT value FROM config WHERE category = 'info' AND name = 'sugar_version'

Cheers