I'm using Vault 2.0 on Windows Server 2003. I had no problems with the install, the client and admin tools work fine, and I was even able to import a large VSS 6 database into it. The problem I'm having is when I go to configure a shadow folder for one of my repositories. When I click add it displays and error and fails to add the repository. The following text is what appears in the shadow folder log file after this happens:
Initializing Client Instance... @ 3/17/2004 2:23:25 PM
Client Instance Initialized! @ 3/17/2004 2:23:26 PM
Verifying Repository... @ 3/17/2004 2:23:26 PM
Repository verified! @ 3/17/2004 2:23:26 PM
Retrieving Delta... @ 3/17/2004 2:23:26 PM
Access to the path "SourceGear\Vault_1\PluginWebService\CE9E812C-D469-4211-B1EF-F4F49502FD33\admin" is denied. @ 3/17/2004 2:23:29 PM
This problem only happens on Windows Server 2003. I installed Vault and the same database onto a Windows 2000 Server and the shadow folder creation had no problem. It obviously seems to be a permission problem of some kind, but the error message doesn't indicate to me where the permission problem is occuring.
Error Trying to Configure Shadow folder
Moderator: SourceGear
i've just posted this kb article. let me know if it helps you out.
http://support.sourcegear.com/viewtopic.php?t=536
http://support.sourcegear.com/viewtopic.php?t=536
Jeff Clausius
SourceGear
SourceGear
Another Windows 2003 Shadow Folder Problem
We just installed Vault on our Windows 2003 Server machine and received this exact same error trying to set up Shadow Folders ON THE SAME COMPUTER as Vault.
We followed the linked instructions. While Vault is running in a networked environment, it is not on a Domain Controller. Therefore we chose the option to run IIS in 5.0 Isolation Mode. After restarting IIS, we get the following error logging into the Admin tool:
"The Vault Server could not establish a connection to the database. Please chech the server's log for detailed information (FailDBConn)."
When turn off IIS 5.0 Isolation Mode, we can log in fine.
Installation Options:
- IIS Process Model - Machine - MACHINENAME\NETWORK SERVICE
- SQL Server - Windows Authentication
We have given rights to the Shadow folder tree to the MACHINENAME\NETWORK SERVICE account.
H E L P ! ! !
P.S. The web service installation part of the instllation had "issues". Do you have many Windows 2003 Server installations?
Todd Breyman
SunGard Insurance System
Todd.Breyman@sungard.com
We followed the linked instructions. While Vault is running in a networked environment, it is not on a Domain Controller. Therefore we chose the option to run IIS in 5.0 Isolation Mode. After restarting IIS, we get the following error logging into the Admin tool:
"The Vault Server could not establish a connection to the database. Please chech the server's log for detailed information (FailDBConn)."
When turn off IIS 5.0 Isolation Mode, we can log in fine.
Installation Options:
- IIS Process Model - Machine - MACHINENAME\NETWORK SERVICE
- SQL Server - Windows Authentication
We have given rights to the Shadow folder tree to the MACHINENAME\NETWORK SERVICE account.
H E L P ! ! !
P.S. The web service installation part of the instllation had "issues". Do you have many Windows 2003 Server installations?
Todd Breyman
SunGard Insurance System
Todd.Breyman@sungard.com
Todd:
Personally, I'd recommend setting up a custom account as detailed in the KB article for Shadow folders on Win 2003 server. Although it is not a requirement, something just feels "right" about running IIS 6 in IIS 6 mode.
In any case, if you still want to run in IIS 5 isolation mode, you need to make changes to the authentication within SQL Server. Check your local machine's user accounts, you should see an account named ASPNET. From within SQL Server, you will need to grant login rights to the ASPNET account, and then allow the user access to the Vault database.
Here is some sample script which may help:
HTH
Personally, I'd recommend setting up a custom account as detailed in the KB article for Shadow folders on Win 2003 server. Although it is not a requirement, something just feels "right" about running IIS 6 in IIS 6 mode.
In any case, if you still want to run in IIS 5 isolation mode, you need to make changes to the authentication within SQL Server. Check your local machine's user accounts, you should see an account named ASPNET. From within SQL Server, you will need to grant login rights to the ASPNET account, and then allow the user access to the Vault database.
Here is some sample script which may help:
Code: Select all
DECLARE @@aspnetacct [nvarchar](128)
DECLARE @@sql [nvarchar](512)
SET @@aspnetacct = RTRIM(CAST(SERVERPROPERTY(N'MachineName') AS [nvarchar](64))) + N'\ASPNET'
IF ( NOT EXISTS (SELECT sid FROM master.dbo.syslogins WHERE LOWER(name) = LOWER(@@aspnetacct)) )
BEGIN
SET @@sql = N'sp_grantlogin @loginame=''' + @@aspnetacct + N''''
EXEC sp_executesql @stmt = @@sql
END
GO
USE sgvault
GO
DECLARE @@aspnetacct [nvarchar](128)
DECLARE @@sql [nvarchar](512)
SET @@aspnetacct = RTRIM(CAST(SERVERPROPERTY(N'MachineName') AS [nvarchar](64))) + N'\ASPNET'
IF ( NOT EXISTS (SELECT sid FROM sgvault.dbo.sysusers WHERE LOWER(name) = LOWER(@@aspnetacct)) )
BEGIN
SET @@sql = N'sp_adduser @loginame=''' + @@aspnetacct + N''''
EXEC sp_executesql @stmt = @@sql
SET @@sql = N'sp_addrolemember @rolename=''db_owner'', @membername=''' + @@aspnetacct + N''''
EXEC sp_executesql @stmt = @@sql
END
GO
If you search around on this forum, you'll see quite a few numbers related to Win 2003 Server.Do you have many Windows 2003 Server installations?
HTH
Jeff Clausius
SourceGear
SourceGear