Installation Problems

dkalweit · Post by **dkalweit** » Thu Dec 20, 2007 10:27 am

Hello. I've been having problems installing Vault Server. I tried about 2 months ago and had to put it on the back burner for a while, and now it's back to the fore-front. Anyways, I've tried installing the most recent version, 4.0.6.15954 today and I get the same sort of errors. Generally I get 'access is denied' and 'object reference not set to an instance of an object" errors when trying to login to the site(admin area, etc.) immediately after install. It looks like it might be something to do with System.Web.Hosting.ISAPIWorkerRequestInProc.GetServerVariable(), as that's the last thing in the callstack in sgvault.log(attached). Note that the database access denied errors at the top of this log were fixed, iisreset, etc., and the bottom few errors are the ones that are of concern. Thanks.

--
Derek

Beth · Post by **Beth** » Thu Dec 20, 2007 5:08 pm

Which IIS process model had you installed under? It looks like you may have chosen System? If so, then choose Machine instead.

There were also errors that said DEVSRV1\ASPNET could not access the database. Can you add that as a SQL user and give it db_owner rights to sgvault and sgmaster?

Did you choose Windows Authentication or SQL authentication when you connected to the SQL server?

Is the SQL server on the same machine or a different machine than the Vault server?

Are these servers members of a domain or workgroup?

dkalweit · Post by **dkalweit** » Fri Dec 21, 2007 8:25 am

Beth wrote:Which IIS process model had you installed under? It looks like you may have chosen System? If so, then choose Machine instead.

This log file was system. I tried machine many times before and got the same error messages.

There were also errors that said DEVSRV1\ASPNET could not access the database. Can you add that as a SQL user and give it db_owner rights to sgvault and sgmaster?

As I said in my original Email, I took care of this, doing exactly as you said.

Did you choose Windows Authentication or SQL authentication when you connected to the SQL server?

The default-- which I believe is windows auth. Based on the question above, I believe it confirms that.

Is the SQL server on the same machine or a different machine than the Vault server?

Same machine.

Are these servers members of a domain or workgroup?

Windows 2000 Domain. Windows XP Pro 'server' as it will be hosting for just 2 users.

--
Derek

Beth · Post by **Beth** » Fri Dec 21, 2007 8:54 am

I'm not sure off the top of my head what could be happening, but I have two ideas in mind.

1) With XP, one almost always has to install IIS. IIS though needs to be installed BEFORE the .NET framework (you can find an explanation here ). You could go to a command line, browse to the 2.0 .NET framwork and run these commands:

aspnet_regiis -u
and
aspnet_regiis -i

2) My other thought is to have you do a complete uninstall of Vault, keep the database, remove users from the SQL security that related to Vault which could be NT Authority/Network Service, DEVSRV1\ASPNET, and sgvaultuser, check the registry for any Vault references making sure that you don't accidentally delete your databases (might want to rename those temporarily), reboot, and then perform a fresh install. I almost always recommend the Machine IIS process model over System.

Why I'm suggesting this is because it sounds like multiple installs have been done and I'm unsure if some kind of settings were mixed up. By doing it this way, I know you are starting from a very clean state.

Try #1 first.

dkalweit · Post by **dkalweit** » Fri Dec 21, 2007 10:33 am

Beth wrote:I'm not sure off the top of my head what could be happening, but I have two ideas in mind.

1) With XP, one almost always has to install IIS. IIS though needs to be installed BEFORE the .NET framework (you can find an explanation here ). You could go to a command line, browse to the 2.0 .NET framwork and run these commands:
aspnet_regiis -u
and
aspnet_regiis -i
2) My other thought is to have you do a complete uninstall of Vault, keep the database, remove users from the SQL security that related to Vault which could be NT Authority/Network Service, DEVSRV1\ASPNET, and sgvaultuser, check the registry for any Vault references making sure that you don't accidentally delete your databases (might want to rename those temporarily), reboot, and then perform a fresh install. I almost always recommend the Machine IIS process model over System.

Why I'm suggesting this is because it sounds like multiple installs have been done and I'm unsure if some kind of settings were mixed up. By doing it this way, I know you are starting from a very clean state.

Try #1 first.

#1 seems to have worked! Thank you. I checked that IIS was using "asp.net 2.0" on the "asp.net" tab, but didn't think to try to re-register asp.net 2.0. Thanks.

--
Derek