After installation of the SafeGuard Enterprise 6 Server on Windows Server 2003 R2 IIS, browsing the SGNSRV website (http://localhost/SGNSRV) always fails with "Service unavailable" errormessage. As a consequence, the SGNSRV-Pool shuts down.
First seen in
SafeGuard Enterprise Server 6.0
Windows Server 2003,
Windows Server 2003 R2,
The custom service account that was used for the application pool identity was not correctly configured with the required ASP .NET permissions.
What To Do
When you use a custom service account, the account needs appropriate permissions to access the IIS metabase and the file system folders that are used by ASP.NET. ASP.NET 2.0 provides the Aspnet_regiis.exe utility, which allows you to grant appropriate permissions.
To assign ASP.NET permissions to the new account
Run the following command from a command window:
- aspnet_regiis -ga MachineName\AccountName
Where MachineName is the name of your server or the domain name if you are using a domain account, and AccountName is the name of your custom account.
Review the permissions required by your custom account. When you run Aspnet_regiis.exe with the -ga switch, the command grants the following rights to the account:
- Access to the IIS Metabase
- Permission to write to the %Windir%\Microsoft.NET\Framework\version\Temporary ASP.NET Files folder
The account is also a member of the local Users group; therefore, it has read access to the \Inetpub directory tree (these directories have an ACL that grants read access to the Users group).
Note The -ga switch makes a number of global changes. If you want to restrict access to specific folders, you need to manually adjust the ACLs on those folders.
Source: MSDN - How To: Create a Service Account for an ASP.NET 2.0 Application (http://msdn.microsoft.com/en-us/library/ms998297.aspx#paght000009_step4)