FAQ: Running Vault service on a domain controller (IIS 5.0)

A collection of information about Vault, including solutions to common problems.

Moderator: SourceGear

Post Reply
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear

FAQ: Running Vault service on a domain controller (IIS 5.0)

Post by jeremy_sg » Mon Feb 16, 2004 4:02 pm

This information applies to Vault versions prior to 3.0.2

By default, Vault will not run correctly on a Domain Controller (PDC or BDC). You will see the problem if the Vault Server was installed with the default values, by opening the following URL in a browser.
<pre>http://yourservername/VaultService/Vaul ... .asmx</pre>
If you see a page with an error “Server Application Unavailable”, it means that the .NET server application is not properly configured. Additionally, the event log may contain the following error:
<blockquote> <i>aspnet_wp.exe could not be launched because the username and/or password supplied in the processModel section of the config file are invalid.</i> </blockquote>

This problem is occurring because the account owner of the .NET runtime process does not exist on the machine where the Vault server was installed.


Vault can be configured to run on a domain controller.

1) Take a look at the following Microsoft Knowledge Base article. You will need to make sure the .Net Framework is configured correctly on the Domain Controller.
For more background information on the .Net security issues, please refer to:
<blockquote>http://msdn.microsoft.com/library/defau ... etHT01.asp</blockquote>

2) Once you have correctly configured the .Net Framework, you will need to make a deviation during the Vault Server installation. Uninstall the Vault Server, if it is currently installed. When the dialog is presented asking about the .Net Framework process model, choose Custom. Then provide the new "weak account" you created for the .Net Framework ( DOMAIN\ACCT ).

3) Proceed with the rest of the Vault Server installation.

Post Reply