Thread

We had some buggy issues through updating EE 2 to current releases so we performed a clean install. After the clean install, 500 errors would appear at intermittent stages of CP navigation and commands.

Examples: super admin account

change user name
no changes made - update local settings (like paths to themes folder, etc.)

I reviewed some posts and saw where it was most likely a permissions error set on the installation folders such as :

/system/expressionengine/config/config.php
/system/expressionengine/config/database.php
 
/system/expressionengine/cache/
/images/avatars/uploads/
/images/captchas/
/images/member_photos/
/images/pm_attachments/
/images/signature_attachments/
/images/uploads/

This also happens if simply trying to install MSM.

We are running a windows server with IIS7. I changed the file/folder permissions so that the user (SERVER\Users) had write permissions to these files/folders. Once I did this, The entire admin site was shut down due to 500 errors.

Obviously this frustrated my support team who now said they need to reinstall yet again because of this.

My question is this…  Why is this becoming such a difficult process just to get EE2 (latest release as of yesterday) installed and running? This doesn’t seem to be the case in other installs. Also, I understand that the 500 errors can only be researched and understood from viewing the log files and tracking from there, but any ideas on the reasoning behind this would be nice.

Hi, Dan. Which Windows hosting company were you using EE2.1.2 with? I don’t know which Windows hosts were tested with this release, but I can certainly ask the testing team.

We host everything internal.

Dan,

Also, I understand that the 500 errors can only be researched and understood from viewing the log files and tracking from there, but any ideas on the reasoning behind this would be nice.

500 errors are server generated and not EE generated so checking the server log files will give you a clearer indication of your error

We are running a windows server with IIS7. I changed the file/folder permissions so that the user (SERVER\Users) had write permissions to these files/folders. Once I did this, The entire admin site was shut down due to 500 errors.

Obviously this frustrated my support team who now said they need to reinstall yet again because of this.

Why did your team need to reinstall again? Permissions look to be the problem here so getting them correct would solve the issue.

Can you run our Server Wizard please?
Also confirm that your server meets all the requirements