Can't upload upgrade file to Upgrade Wizard

[Lvis Enrique]

When upgrading to the next Sugar release, you may find that your default PHP and Apache settings don't allow you to upload large files. The Sugar upgrade files may be too large for the default settings. As of Sugar 6.2, you should configure your system to accept files up to 30MB in size.

You will see this problem manifest itself when uploading the upgrade file into the Sugar Upgrade Wizard. The upgrade utility will return to the Sugar home screen without moving forward in the upgrade process.

To increase the file upload size, you will need to update the following configurations below before you begin the upgrade process:

• In your SugarCRM config.php file:
  
  • Ensure the upload_maxsize is set to more than 31500000.
  
  
• In your PHP php.ini file:

• Ensure upload_max_filesize is set to more than 30MB.
• Ensure post_max_size is set to more than 30MB.
• If you have set max_input_time in the php.ini file, then ensure that is set to a value greater than 600 or use the default value of -1.
• Restart your Web server and then begin the upgrade process.

• If you are using an Apache Web Server and if you have set LimitRequestBody in the httpd.conf file (note these settings are not required and may not be present), then ensure that you set it to a large number or use the default value of 2GB. Restart Apache and then begin the upgrade process.

Clint

By meas of the present message I would like to request your advice to the following problem that I´m having upgrading from 5.2.0I to 5.5.0:

+ The problem is that after searching in this forum about I realize that need to set up the php.ini file in the way that you indicate above... I did... and after restart my pc I can´t login anymore... it just not work (i have not any errors messages), so I´m not sure what to do

The only things that I tried are:
- Change the register_long_arrays to "on"
- Check out the session dir but Im not sure how to set up

I´m using Sugar as localhost with MS SQL (using the MSSQL wizard from the support page), so I will be very appreciatte if you can tell me any advice that could be used to solve this type of issues.

Thanks in advance for your time and attention.

Regards

Lvis Enrique

[mclee]

Hi,

Just to share my experience “upgrading” from beta to GA. I have tried using the upgrade wizard with various “upgrade path” to upgrade from 6.2.0 Beta 4 to 6.3.0 GA without success. And I later found out that there is not automated upgrade path from beta -> GA from the forum.

Nevertheless, I managed to "upgrade" to 6.3.0 GA via Installatron in cpanel. Here are the steps (Important Note: please try at your own risk!!!).

1. logon to Cpanel and check if the latest sugar crm is avail.
2. Add your sugar instance to the Installatron application (for my case: I have installed the 6.2.0 Beta manually, should have done through installatron in the first place )
3. Once added the application to the installatron, update the version indicated to the actual version if it is incorrect (for my case: it shown as “6.3.0” after i added my 6.2.0 Beta 4 instance to the application list, so i modify the version number to the actual).
4. Once the actual version is lower than the available version in Installatron, the “Upgrade” button in Installatron became available...
5. During the upgrade process, Installatron will prompt (or automatically) create a backup.
6. Once the upgrade process is completed, as usual, you need to change the read-write-execute access in order for the rendering to work correctly. (for directory such as Cache, Data, Modules etc, 775 for directories, 664 for files if i remember correctly)
7. Goto “About” on the upper right corner to check your sugar crm version.

Good luck!

Important Note 1: I’ve only tried this for upgrade from 6.2.0 Beta 4 to 6.3.0 GA, and try at your own risk
Important Note 2: Again, I’ve only tried this for upgrade from 6.2.0 Beta 4 to 6.3.0 GA, and try at your own risk

Cheers!

MC

[john9797]

Yes, I've seen those instructions also. Rather than changing server settings to allow a single upload (which will not work anyway)..I hacked the upload.php .. you will still get the error message but just click 'OK' and it will then let you proceed to the next step, which is clicking the button that is no longer grayed out.

Go to:

modules/upgradewizard,
change from: document.getElementById("upload_button").disabled= 'disabled';
to: document.getElementById("upload_button").disabled= '';


It is in the codeblock below.
document.getElementById("upload_button").disabled= 'disabled';
}
else{
document.getElementById("upload_button").disabled= '';
}
}
}

[brianhildebrandt]

To determine the location of the php.ini file create a simple phpinfo page. I create a file in doc root on the server named phpInfo.php containing the following...
<?php
phpinfo();
?>

Make sure it is accessible to the web server (file permissions).
Then point your browser to it http://my.server.com/phpInfo.php
You will see in the top most section the location of the config file.

LimitRequestBody in the httpd.conf

Thanks for the tips Clint, but I've done all of this except for the "LimitRequestBody in the httpd.conf " part. Where is this file located? In the original Upgrading Sugar file it stated that the LimitRequestBody variable was in php.ini. I take it that that is not the case?

Thanks in advance for you help.

------ EDIT ------------
Ok, I've found the file, but LimitRequestBody was not set in it. So what next?

Thanks,

Tim

[webdecoder]

I am trying to upload the upgrade file for 6.3.1 to 6.4 and getting the error below.

ZIP Error(5): 0

any ideas, thanks for your help

[paoron]

Yes, I've seen those instructions also. Rather than changing server settings to allow a single upload (which will not work anyway)..I hacked the upload.php .. you will still get the error message but just click 'OK' and it will then let you proceed to the next step, which is clicking the button that is no longer grayed out.

Go to:

modules/upgradewizard,
change from: document.getElementById("upload_button").disabled= 'disabled';
to: document.getElementById("upload_button").disabled= '';


It is in the codeblock below.
document.getElementById("upload_button").disabled= 'disabled';
}
else{
document.getElementById("upload_button").disabled= '';
}
}
}

Thank you john9797, I've just followed your suggestion and succesfully completed my upgrade from 6.3.4 to 6.4.3. But now I can't load upgrade wizard anymore because of "Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending any data".... bad news for me....

[williams22]

Showing code error ex888, and unable to paste. php.ini file is in the /php folder