vault install problems

crichardson · Post by **crichardson** » Tue Feb 22, 2005 12:09 pm

I am having problems installing Vault server on my workstation. At the start, I'm selecting the 3rd option of using impersonation as I want to using Windows authentication (hope this is right?). I get to the point where I need to connect to the SQL Server (a named instance on my workstation), enter the instance name (eg. wkstn99\sql1) and select Windows Authentication. I then get the following message...

You must use an account that is common to both machines to execute the IIS process...

If I continue from the above and try to start the admin tool, I get a message that the SQL Server named can not be parsed.

I have searched the forum and found nothing on this. This is a disappointing start to my trial of Vault.

Clive Richardson

Post by **jclausius** » Tue Feb 22, 2005 12:40 pm

Clive:

It sounds as if you're choosing identity impersonation / Custom for the ASP.Net process model. Assuming you've configured ASP.Net and IIS using the default values, you should use the default option for the process mode.

You don't need to worry about SQL Server / Windows Authentication for SQL Server until the SQL dialog is presented. Since you are requesting Vault to use Windows authentication for SQL Server, you need to make sure the account you are currently logged in as has Administrative rights to the machine as well as the database.

Unless you want to spend quite some time configuring folder permissions, database permissions, etc, my recommendation is to completely un-install and re-install. But at the point of the ASP.Net process, choose the correct model ( the default is the usual configuration ), and continue from there.

Guest · Post by **Guest** » Wed Feb 23, 2005 4:43 am

I used the defaults before with the same results. I am using an instance of sql server on my workstation and I have full sys admin rights.

However, again, I uninstalled everything and ran the vault server install leaving the defaults as you indicated. I got exactly the same behavior with the same messages as listed in my first post.

I'm confused why the first error message uses the phrase: -

'You must use an account that is common to both machines to execute the IIS process... '

when everything is installed on the same workstation.

I'm completely stuck.

Clive

Guest · Post by **Guest** » Wed Feb 23, 2005 5:41 am

I've fixed it. I had to uninstall SQL Server (MSDE) on my destkop and I re-installed it as a default instance. Therefore, instead of having to specify 'desktopname\instance_name', I could simply specify (Local) when trying to connect through the client or admin tool. This got me a stage further but I got a different error which I could actually find some help on by following the link to the archives within the error display. It turned out that I had to properly register the .net 1.1 framework.

Now I'm up and running but I would like to have it confirmed if there is a problem installing vault server to point at a named instance of SQL Server?

Clive

Post by **jclausius** » Wed Feb 23, 2005 9:19 am

Anonymous wrote:Now I'm up and running but I would like to have it confirmed if there is a problem installing vault server to point at a named instance of SQL Server?

Clive

No problem that I'm aware of. I run MSDE 2000 under the instance NEO. I've never seen a problem when installing to the ARTHUR\NEO database instance. I've also tried .\NEO and (local)\NEO and these all seem to work.

If anyone else has run into this problem, please let us know.