Installation problems
Moderator: SourceGear
Installation problems
I've tried to install the evaluation server version on Win2K SP2 with SQL Server 2000 with Windows authentication on the same machine and cannot get the admin program to log in.
When using windows authentication, I get the following error:
"A database error has occured (FailDbReader)"
When changing the web.config file to use the sql server "sa" username with appropriate password I get the following error:
"No server was found at the specified URL"
I realize that the requirements are Win2K SP3 and we're on SP2, but our network admninistrator does not currently want to go to SP3. Could this be related to a subtle change betw SP2 and SP3? I've looked at all the user and role settings inside SQL server and it looks fine. My guess is that it is a security related problem.
Any help appreciated.
When using windows authentication, I get the following error:
"A database error has occured (FailDbReader)"
When changing the web.config file to use the sql server "sa" username with appropriate password I get the following error:
"No server was found at the specified URL"
I realize that the requirements are Win2K SP3 and we're on SP2, but our network admninistrator does not currently want to go to SP3. Could this be related to a subtle change betw SP2 and SP3? I've looked at all the user and role settings inside SQL server and it looks fine. My guess is that it is a security related problem.
Any help appreciated.
I've tried the install on my local PC (WinXP Pro, SP1, SQL server 2000 SP3) and I get the exact same problems. I've repeated the server install to use SQL Server authentication but then I get an error returned that it cannot log into the database. I must be missing something simple, yet fundamental here. I've checked the machine.config file and it has the processMode username set to "machine", which is what I choose during the install process (which is also the default).
This does sound like some sort of permissions problem.
Verify that the ASP.Net process account (the default account is ASPNET for IIS 5 and Network Service for IIS 6) has the following NTFS permissions:
- full access to vaultservice directory (eg. c:\inetpub\wwwroot\vaultservice)
- read/write access to %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys
-full access to vaultshadowfolder directory. note - this should be inherited by default from the vaultservice directory.
-full access to the folder locations specified in vault.config for both WorkingDirectory and LogFilePath.
The installer usually sets these up correctly, but maybe something weird happened during the install.
Also if have any other software running in IIS that may be causing a permissions conflict (like SharePoint) add the following line to the system.web section of the web.config file (located in your VaultService directory).
<trust level="Full" originUrl="" />
Verify that the ASP.Net process account (the default account is ASPNET for IIS 5 and Network Service for IIS 6) has the following NTFS permissions:
- full access to vaultservice directory (eg. c:\inetpub\wwwroot\vaultservice)
- read/write access to %ALLUSERSPROFILE%\Application Data\Microsoft\Crypto\RSA\MachineKeys
-full access to vaultshadowfolder directory. note - this should be inherited by default from the vaultservice directory.
-full access to the folder locations specified in vault.config for both WorkingDirectory and LogFilePath.
The installer usually sets these up correctly, but maybe something weird happened during the install.
Also if have any other software running in IIS that may be causing a permissions conflict (like SharePoint) add the following line to the system.web section of the web.config file (located in your VaultService directory).
<trust level="Full" originUrl="" />
Mary Jo Skrobul
SourceGear
SourceGear
Sorry, I think I misunderstood your email message. I thought you were getting the server not found error. What type of authentication are you using now, Windows or SQL?
If you are using windows authentication, verify that the Aspnet process account is a user in SQL and has a role of db_owner for the sgvault database. You can verify which process user is running aspnet by looking at the aspnet_wp.exe process in Windows Task Manager.
If you installed as windows anthentication and wish to use SQL auth instead, I would recommend re-installing the server and choosing SQL authentication so the sgvaultuser password is ecrypted correctly in the web.config file.
If you continue to have difficulties, email me your vault_install.log file (located in your temp (%temp%) directory) along with a phone number where you can be reached. This may be easier to troubleshoot over the phone. You can email me using the link at the bottom of this message.
If you are using windows authentication, verify that the Aspnet process account is a user in SQL and has a role of db_owner for the sgvault database. You can verify which process user is running aspnet by looking at the aspnet_wp.exe process in Windows Task Manager.
If you installed as windows anthentication and wish to use SQL auth instead, I would recommend re-installing the server and choosing SQL authentication so the sgvaultuser password is ecrypted correctly in the web.config file.
If you continue to have difficulties, email me your vault_install.log file (located in your temp (%temp%) directory) along with a phone number where you can be reached. This may be easier to troubleshoot over the phone. You can email me using the link at the bottom of this message.
Mary Jo Skrobul
SourceGear
SourceGear
I've settled on Windows authentication for the moment. The aspnet_wp.exe process runs under ASPNET user and that user does have the db_owner role in the sgvault database. The installation also went fine without any problems and there are no errors in the installation log file - it also states "you vault server has been successfully configured" at the end of the log file.