Immediately after the installation, I get an error screen in the browser. Check the attachment for the screenshot.
The installation Environment is:
Windows Server 2003 R2 with the latest SP
IIS 6.0
MS SQL 2005 with SP3
I tried to search for the possible solutions on the net.
1. The application pool is running on NT Authority\NEtwork Service
2. The ASP.NET web service extension is allowed in IIS
3. NT Authority\Network Service has the permissions in the specified SQL Server
4. The Valult databases have been created on the SQL Server. So, the login details specified during installation is working.
I've spent half a day trying to get this right. I'm sure a small tweak might solve this problem, but unfortunately I'm unable tro find it.
Could not open the Vault website on the server after install
Moderator: SourceGear
-
- Posts: 3
- Joined: Mon Oct 08, 2007 2:04 am
Could not open the Vault website on the server after install
- Attachments
-
- Screenshot of the error I get immediately after installing Vault 4.0.4
- Error.JPG (217.95 KiB) Viewed 3299 times
The file that is referenced - mmsseclib - is used to set directory permissions for Vault during the installation.
Find the file mmsseclib.dll rename it to mmsseclib.old. Then try to bring up the page http://<your vault server>/vaultservice and let me know the results. If it doesn't work, then something may have prevented those rights from being set. In that case, the rights that you can set manually are:
* the local directory containing the server installation files (by default, InetPub\wwwroot\VaultService).
* the directory where the log files are written (by default, WINNT\Temp). The log file location can be changed after installation, in the Vault Admin Tool under Server Options.
* the IIS process account's %userprofile%\Application Data \Microsoft\Crypto\RSA\MachineKeys or to %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys if the IIS process account does not have a user profile.
* the Vault Shadow Folder directory.
* Windows\Microsoft.NET\Framework\<version>\Temporary ASP.NET Files.
Your NT Authority/Network Service needs read/write access.
Find the file mmsseclib.dll rename it to mmsseclib.old. Then try to bring up the page http://<your vault server>/vaultservice and let me know the results. If it doesn't work, then something may have prevented those rights from being set. In that case, the rights that you can set manually are:
* the local directory containing the server installation files (by default, InetPub\wwwroot\VaultService).
* the directory where the log files are written (by default, WINNT\Temp). The log file location can be changed after installation, in the Vault Admin Tool under Server Options.
* the IIS process account's %userprofile%\Application Data \Microsoft\Crypto\RSA\MachineKeys or to %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys if the IIS process account does not have a user profile.
* the Vault Shadow Folder directory.
* Windows\Microsoft.NET\Framework\<version>\Temporary ASP.NET Files.
Your NT Authority/Network Service needs read/write access.
-
- Posts: 3
- Joined: Mon Oct 08, 2007 2:04 am
This gave me an error related to trust level of the application. I tried everything in the web.config - right from Trust Level = Full to Trust Level = Low. Nothing worked.Find the file mmsseclib.dll rename it to mmsseclib.old. Then try to bring up the page http://<your vault server>/vaultservice and let me know the results.
When I try to browse through the IIS Manager I get the following error
I checked the link and checked every instruction on the msdn page. Nothing helped.Cannot connect to the configuration database. For tips on troubleshooting this error, search for article 823287 in the Microsoft Knowledge Base at http://support.microsoft.com.
-
- Posts: 3
- Joined: Mon Oct 08, 2007 2:04 am
That makes sense then. Special configuration is needed to work with Sharepoint. See this KB article for details and options: Installing Vault on the same server as Sharepoint
The easiest solution I found for that is to create a separate website for Vault and install to that website.
The easiest solution I found for that is to create a separate website for Vault and install to that website.