Topic: Changes to import limit in php.ini disabled user app login

[powerserge]

We have several PHP applications running on a Small Business Server 2003. We are about to migrate to Windows Server 2008 R2. Before taking the final snapshot before migration, we increased the database import limits in php.ini files per documentation:

“The first things to check (or ask your host provider to check) are the values of upload_max_filesize, memory_limit and post_max_size in the php.ini configuration file. All of these three settings limit the maximum size of data that can be submitted and handled by PHP. One user also said that post_max_size and memory_limit need to be larger than upload_max_filesize.”
Increased:
upload_max_filesize to 1024MB
memory_limit to 2048MB
post_max_size to 2048MB

After updating all of the php.ini files in the XAMPP directory on the server – including php4 and php5 – all of our applications failed to allow users to login. They just reset back to the login screen with a blank password field and a prefilled user name.

I did not stop the Apache or PHP services before modifying the php.ini files, but I did reboot the server after modification.

To fix the new problem, I had to stop Apache and PHP services through Computer Management of SBS 2003, put the old files with 16MB database import limits back into the proper directories, and then reboot the server.

We are back in business, but we have to have to be able to import larger databases.

Did I set the limits too high for the SBS 2003? If so, what is the recommended increase? Or is it possible that I should’ve stopped the services before modifying the *.ini.

Thank you!

[Virsacer]

Did you check the 3 config chnges with phpinfo()?

I think the problem is the letter B: http://www.php.net/manual/en/faq.using.php#faq.using.shorthandbytes