Vault installation fails on SBS 2003

GHurlman · Post by **GHurlman** » Fri Feb 20, 2004 9:25 pm

Installing on SBS 2003, installation is failing with this in the Configuration dialog (Hamlet is the server name):

Configuring your new Vault Installation
Checking for IIS Version...OK
Requesting Vault Admin user password...OK
Connecting to the SQL Server...OK
Verifying the SQL Server requirements...OK
Checking for an existing Vault database...Not found.
Creating a new Vault database on (local)...
	Creating the SourceGear Vault database...OK
	Upgrading SourceGear Vault database...OK
	Creating SourceGear Vault stored procedures...OK
	Adding Data to SourceGear Vault database...OK
Adding the admin user...OK
Giving NT AUTHORITY\NETWORK SERVICE access to the Vault database...Windows NT user or group 'HAMLET\ASPNET' not found. Check the name again.
User or role 'HAMLET\ASPNET' does not exist in this database.
Granted database access to 'NT AUTHORITY\NETWORK SERVICE'.
'NT AUTHORITY\NETWORK SERVICE' added to role 'db_owner'.
Vault Setup is exiting due to a failure or cancellation. Error Code = 402

Keep in mind that SBS 2003 servers are also domain controllers - there would be no local ASPNET account, only the DOMAIN\ASPNET account.

Is there a workaround, or is this just a bug?

Guest · Post by **Guest** » Sat Feb 21, 2004 8:58 am

If localhost\aspnet doesn't exist, then you would need to choose a different account in the installer when selecting the IIS process model to run Vault under. See http://www.sourcegear.com/vault/support ... torial.asp for more info.

GHurlman · Post by **GHurlman** » Sat Feb 21, 2004 12:34 pm

I had chosen the NETWORK SERVICE account, which was added successfully to the database... ASPNET shouldn't be involved at all in that process configuration.

dan · Post by **dan** » Sat Feb 21, 2004 12:52 pm

Yes, the ASPNET account shouldn't be involved, so it looks like a bug, but the workaround would be the same - choose a different account to run the Vault service under during the install. If you want to run Vault with the Network Service account, you'd have to then manually change that in IIS (and also manually allow access to the Vault folders that require them, which are listed in the installer guide URL above).