Troubleshooting server error in '/ProcessManager' Application
Last Updated April 22, 2009
When loading ProcessManager for the first time, seeing the following error from the browser:
Server Error in '/ProcessManager' Application.
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.
Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
This is a generic error message that is caused by an error while loading the application from the server. You will need to modify the web.config and change the customErrors mode to "Off" or "RemoteOnly". Once this setting has been changed, you will see the error message the server returned when the page is reloaded.
If this is a default installation of Workflow Solution on a Domain Member server, you will see this error message when ProcessManager is first loaded. ProcessManager uses the default ASP.NET of Network Service, which does not have rights to the .NET temp directory by default. The following error message is returned after changing the customErrors mode in the web.config file:
The current identity (NT AUTHORITY\NETWORK SERVICE) does not have write access to 'c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files'.
Grant the Network Service account
write permissions for the following directories:
'C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files' 'C:\WINDOWS\temp'
For additional troubleshooting information about this error, also refer to the following related article: