Vault 2.0.6 on a Windows Server 2003 DC

[Sven Aelterman]

Hi all,

I have reviewed some previous posts about running Vault on a DC. I was able to install the Vault Server, although I had to try twice (for some reason, setting the database permissions failed the first time / I added them manually).

Now, when I try to connect to the Vault Server using the Vault Admin tool (from the same machine, the DC), it returns an error:

The server returned an unknown status code ({0}).

I suspect the {0} should be replaced with the actual status code, this is probably a minor bug in the error message?

When I try to connect using the Vault client tool:

Server was unable to process request. --> File or assembly name g5ucd-ib.dll, or one of its dependencies was not found.

When I try to connect using the Web Client:

Login failed.

I am not sure what's going on. I appreciate any input...

Thanks,

Sven.

[Sven Aelterman]

Hi,

I tried uninstalling (including DB removal) and reinstalling. The same error occurred while setting DB security, as in the following log

Code: Select all

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 '<domainname>\ASPNET' not found. Check the name again.
User or role '<domainname>\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

It seems to me that there really wasn't anything wrong: even though <domainname>\ASPNET does not exist, and cannot be added to the DB, it shouldn't be considered an error. It's a Windows Server 2003, and I selected NETWORK SERVICE as the identity that's running ASP.NET.

So why does the setup attempt to add the ASPNET account to the DB (and make the entire setup program fail after that)? Or maybe I am missing something?

Sven.

[jclausius]

There are some installation issues with the Vault server and Domain controllers.

This was discussed on a separate thread. Does the information there help - http://support.sourcegear.com/viewtopic.php?p=3099?

[Sven Aelterman]

Sorry, it doesn't provide any help. I had already checked that.

Fact is that .NET framework is operating correctly. This DC is my dev machine and runs about 5 ASP.NET sites correctly (even including debugging...)

Vault Web Client seems to run (at least, I get the login page), but then fails to log me on, just like the Admin tool and Client tool. From the error message the client gives (see first msg in this thread), it seems to me like the web service can't compile, and that's where the issue is...

[Sven Aelterman]

In my last post, I mentioned the solution to my problem... I have several other sites running, but all of them where running under a different application pool than the Vault Virtual Directories. I changed the Vault vdirs to run under the same app pool, and now, I can login, etc.

Thanks.

[jclausius]

Glad you are up and running.