4.0.1 is posted, so how do I upgrade from 4.0.0?

[dug]

We just started using sugar with 4.0.0 and have enough data that we don't want to blow away our install.
It looks like 4.0.1 was posted tonite, but my attempt at using the upgrade wizard said the file was incompatible.
How do I upgrade and keep my data.
I need to get inbound email working and I have all the right stuff installed, the cron job running sans errors and still no email in the group inbox. I hope this fixes it!

thanks,
dug

[clint]

You need to upload the Upgrade file into the Upgrade Wizard. You will find the Sugar Open Source 4.0.0 to 4.0.1 Upgrade file at:
http://www.sugarforge.org/frs/downlo...0_to_4.0.1.zip

There is a separate file for upgrading from 3.5.1 to 4.0.1 located at:
http://www.sugarforge.org/frs/downlo...1_to_4.0.1.zip

Regards,
Clint

[dug]

Awesome... Thanks!

[smellygig]

Got all excited about the 4.01 being finally available and foolishly upgraded our production server without backing up and testing on dev version.

Got an error message saying upgrade failed because .../image.php not writable and then when trying to enter the site get a simple message on plain white text background:

Not A Valid Entry Point

Now I am in a bit of a jam considering sales needs to use this in the morning or the company is shut down. Any ideas about where to start fixing this?

Not a developer but ok with good instructions. Were running 3.5.1d on apache before taking this unfortunate leap forward.

Thanks in advance,
Alex

[arnaudli]

Got all excited about the 4.01 being finally available and foolishly upgraded our production server without backing up and testing on dev version.

Got an error message saying upgrade failed because .../image.php not writable and then when trying to enter the site get a simple message on plain white text background:

Not A Valid Entry Point

Now I am in a bit of a jam considering sales needs to use this in the morning or the company is shut down. Any ideas about where to start fixing this?

Not a developer but ok with good instructions. Were running 3.5.1d on apache before taking this unfortunate leap forward.

Thanks in advance,
Alex

It may be a permission issue on the server. Check that the server has write access to the whole sugar directory and subdirectories (I know it is not very good to do this).

Then retry running the upgrade.

[smellygig]

Cannot re-run any upgrade. There is nothing there except for

This is not a valid Entry point

How screwed are we? I notice there are alot of other people with this exact same probem yet no answers how to recover except to chmod 777. Not really a solution considering the current situation..

Alex

[arnaudli]

Cannot re-run any upgrade. There is nothing there except for

This is not a valid Entry point

How screwed are we? I notice there are alot of other people with this exact same probem yet no answers how to recover except to chmod 777. Not really a solution considering the current situation..

Alex

That was just an idea

I don't know what the problem could be. Did you try calling the link index.php?action=Login&module=Users because it sounds likesugar cannot find what module to load. It may have no effect, the problem description is a bit short.

[smellygig]

Tried /index.php?action=Login&module=Users with the same results

Not A Valid Entry Point


Basically here is what happened:

Tried to upgrade sugar version from 3.5.1d to 4.01. Passed step 1 and at step 2 clicked "commit". After this was given an error warning about theme not being writable. And now we have this message on blank screen:

Not A Valid Entry Point


Alex

[clint]

Well, this is definitely going to take some work to get your system back up and going.

I'll try and recreate a similar environment on my local system now and come back and document what steps it takes to fully recover.

Before doing anything more, definitely take a backup of your database and a backup of your filesystem.

If you have no Studio customizations, this should be fairly straightforward. Simply install a clean 4.0.1 instance and modify the config.php to point to your existing database.

It sounds like you got far enough in the upgrade process that your database did get upgraded to 4.0.1. You can do a select * from config to check if the database thinks its 4.0.1.

If you do have field customizations, a little more work is needed. Again, install a fresh 4.0.1 system and point it at your existing database. Then go determine which html screens you modified to add/remove fields and copy over those DetailView.html/EditView.html/ListView.html/SearchForm.html files from your 4.0 hosed system to your new 4.0.1 system. You will then need to go into the Admin console, click on Repair and run Repair Extensions and Repair Relationships.

Like I said, I'll run through these steps today and see if I'm missing anything.

Oh yeah, make sure you have file permisssions set up so that your webserver can write to your Sugar directory space.

Regards,

[smellygig]

OK so i have verified the database did not update all the way. I tried pointing a clean install to it and received an error saying Sugar 4.01 files can only be used with 4.0.1 database. Is this a matter of changing the sugar_version in MySql to 4.0.1? Do I try to install a version of 3.5.1d again? Stuck in the water and down for 2 days now.

Alex