Occasionally, ASP.net will generate many errors on the Windows Event Viewer and many functions of the CentreStack application may cease to work (adding users, generating file previews, etc).
The errors that you may see in the Windows Event Viewer (Windows Key+R, eventvwr) Application list may say something similar to the following examples:
"Error reading resource file 'c:\Windows\Microsoft.NET\Framework64\v4.0.303119\Temporary ASP.NET Files\...' -- 'The system cannot find the file specified'"
"Could not write to output file 'c:\Windows\Microsoft.NET\Framework64\v4.0.303119\Temporary ASP.NET Files\...' -- 'Access Denied'"
These types of errors occur because:
- The system's temporary directory may not exist, or
- Internet Information Services (IIS) may not have permissions to access the system's temporary directory, or
- Both of the above
- Open the Windows Advanced settings window (Windows Key+Pause), then click on the Advanced System Settings button, and then click on the Environment Variables button. Edit the User Variables for TEMP and TMP. It is recommended that you point to a public location, such as C:\Windows\Temp as opposed to a location in the logged-in user's profile.
- Add the [SERVER NAME]\IIS_IUSRS group to the Security tab of the Temp folder. Give the group Full Permissions. It is important to note that ASP.Net will continue to use the default Temp directory under the C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files folder. The IIS_IUSRS group has to be added to the System's temporary folder (from the TEMP and TMP environment variables), not the actual Temporary ASP.NET Files folder.
After you implement the solution(s) above, you will not need to restart the server. Simply try to access the CentreStack application on a web browser and verify that the errors are not being generated anymore.
If you continue to experience issues, please open a support ticket by sending an email to firstname.lastname@example.org. Please include the CentreStack version (build number from the login page), and the server type (example: Windows Server 2012 R2).
Article is closed for comments.