Dear Friends,
I am also having this problem when I am trying to upgrade from 7.10.4 to 7.10.5.
First, when I am going to Upgrade WIZARD it is starting from upload the package, not from checking the permissions etc.
Two, When I select the file and upload the package, it returns with the error message:
I have the following settings in PHP.ini:
And the suitecrm.log show the bare message only:
There is nothing in the php/apache error logs too.
I also have cleaned the Upload directory and removed all the contents/files from its subdirectories.
Kindly suggest what to do.
With thanks,
RK
What is the effective max_upload_size you see in Admin / Diagnostics / phpinfo
Note: get it from that menu, not from the command-line, please.
Dear pgr,
I think the problem is mismatch between post_max-size = 8M & upload_max_filesize = 32M is the reason.
What is your take?
With thanks,
RK
If increasing post_max_size solves the problem, then I would say you are right 
Try it, I think it will work!
Dear pgr,
You were right. Once the changes made in PHP.ini reflected after hostgator restarted the webserver, I could successfully complete the upgrade process.
However, when I run the diagnost tools and checked for bean files, I observed the followings:
This information tells us whether or not the beanFiles specified in the beanList actually exists. This can be an issue with an improperly defined module loaded extension.
Green means the file does exist.
Orange means there is no indexed file, so we cannot look it up.
Red means the file does not exist.
NO! --- DynamicField is not an index in $beanFiles
NO! --- Connectors is not an index in $beanFiles
NO! --- Version is not an index in $beanFiles
NO! --- CustomFields is not an index in $beanFiles
NO! --- Audit is not an index in $beanFiles
Kindly enlighten me on these and suggest the solutions.
Also when I do run the Diagnostic Tools with all default options ‘selected’, it remains stuck at 0% for. What is the problem?
With thanks,
RK
I think the diagnostics section is quite old, and hasn’t been kept properly. I tried the BeanList diagnostic on the Softaculous live demo, and I get the same results as you. I would say you don’t need to worry about that.
To see why it’s hanging you can try running each diagnostic individually to see which one is hanging.