Migrating 6.0.2to new server, ran into issues

[lobsterking]

I have 6.0.2 running and need to move it to a new box. I was able to export the entire db via phpmyadmin.

I was looking at moving the database into a 6.0.3 install since there appears to be no 6.0.2 available to download. I have tried upgrading my 6.0.2 to 6.0.3 but the wizard fails at a 500 error. Same thing with the backup via web UI, it fails out, times out or something.

So, i am looking for your expert and seasoned advice. My options that i think i have are:

- I can try the silent upgrade to 6.0.3 and cross my fingers, then export database again as a 6.0.3.
- Locate 6.0.2 to download?

I did try copying the entire directory over to my new box and editing the config file to point at the new database name and i get blank dead pages at index.php, nothing loads.

Any advice you can provide will be helpful, thanks

[tlugar]

The blank screen issue i ran into when i had not increased the upload_max_filesize in php.ini, so you may be running into an issue with the file size or the amount of memory php is currently allowing a script to use up before it stops a process.

[lobsterking]

The PHP. ini file has been edited and i can install a sugarce 6.0.3 instance and import a database. The two are not compatible though.

Ideally, i could copy the entire sugar directory over to the new machine and edit the config file to point to the relocated database and it should work correct?

thanks for the help

[Angel]

Yes, in theory, if the new server has a properly configured PHP environment, you would be able to copy it from the old server, edit config.php and away you go.

Though, the fact you are getting the blank screens and so forth would seem to indicate PHP needs some adjustments. Other settings that come to mind are memory_limit and max_execution_time. I would also temporarily remove the .htaccess file as I've seen a number of instances where similar copy operations are hindered by it.

Here is some additional thoughts on the copy process that might help you get a clearer understanding:

http://cheleguanaco.blogspot.com/201...mystified.html

[tlugar]

If you're running into a db conflict with the sugar version type you can just go into the database and run the command "update config set value='6.0.3' where name='sugar_version';"

[Angel]

That would get you past the error, but it is not generally advised that you do that because sometimes there are DB schema differences between versions and updating the config table wouldn't apply said changes to the system (as well as other changes).