Couple of weird things with the Vault 4.1 Upgrade

tommyg · Post by **tommyg** » Wed Mar 05, 2008 6:05 pm

Some issues we found when upgrading from 4.06 to 4.10 ...
- If the install path you wish to install to includes a space character, it does not work.
- When selecting to use a domain account for the impersonation, the password is not asked for so you need to edit the config files manually
- If installing over 4.06, it deletes all files in the existing structure (this though DOES work if there was a space in the path) but does not delete the Web Site entries in IIS, so you need to manually do this

Finally, when attempting to log in to the VaultShadowService, simply keep being asked for the admin password and cannot get any further than that. Any ideas?

Cheers
Tom

lbauer · Post by **lbauer** » Thu Mar 06, 2008 7:55 am

Some issues we found when upgrading from 4.06 to 4.10 ...

- If the install path you wish to install to includes a space character, it does not work.

I was able to reproduce this. It appear the installer truncates the path at the space (C:\My Folder results in a "can't find C:\My\web.config" error. I'll log this as a bug.

When selecting to use a domain account for the impersonation, the password is not asked for so you need to edit the config files manually

This is a known issue and will be fixed in the next release.

If installing over 4.06, it deletes all files in the existing structure (this though DOES work if there was a space in the path) but does not delete the Web Site entries in IIS, so you need to manually do this.

I could use more information here. Are you saying that when the installation fails and rolls back, your existing files have been deleted? But the installer doesn't delete files if there was a space in the path?

Finally, when attempting to log in to the VaultShadowService, simply keep being asked for the admin password and cannot get any further than that. Any ideas?

We've had a couple of reports of this -- I'll need to investigate and get back to you on this one.

tommyg · Post by **tommyg** » Thu Mar 06, 2008 5:10 pm

Quote:
If installing over 4.06, it deletes all files in the existing structure (this though DOES work if there was a space in the path) but does not delete the Web Site entries in IIS, so you need to manually do this.

I could use more information here. Are you saying that when the installation fails and rolls back, your existing files have been deleted? But the installer doesn't delete files if there was a space in the path?

Sorry that wasn't very clear was it. If there is a space in the install path, it still deletes all of the files correctly, then fails and the folder is left with no files in it.

Cheers

lbauer · Post by **lbauer** » Sun Mar 09, 2008 6:08 pm

Re: the shadow folder issue:

A user reported the same problem here:

http://support.sourcegear.com/viewtopic.php?t=8233

Is any of this relevant?

tommyg · Post by **tommyg** » Tue Mar 11, 2008 12:48 am

We have an AD Account that we are Vault under, with an SQL database. I've checked both config files for both the Vault and Shadow service and they have the correct username and password entered for them

Nothing in the other thread seems to shed any light on the issue.

lbauer · Post by **lbauer** » Tue Mar 11, 2008 9:25 pm

Chech the Vault App Pool properties->Identity. Is it using the AD account that's in the Shadow Folder Web.config file or Network Service (assuming you're on Win 2003).

tommyg · Post by **tommyg** » Tue Mar 11, 2008 9:33 pm

It is set to Network service. Should I set this to the AD Account that we are using in the .config files?

lbauer · Post by **lbauer** » Tue Mar 11, 2008 9:53 pm

Yes, I'd suggest using the AD account to see if that resolves the problem.

tommyg · Post by **tommyg** » Tue Mar 11, 2008 9:53 pm

I've just looked in the VaultShadowFolderService.txt logfile and the following is appearing in it each time i click on the Shadow Folders menu option...

12/03/2008 2:19:36 PM <generic>: [<No Name>:2012] SimpleLogger finalized
12/03/2008 2:20:28 PM <generic>: [<No Name>:2772] GetEntryAssembly() returned null; not logging assembly name
12/03/2008 2:20:28 PM <generic>: [<No Name>:2772] Creating directory Sourcegear\Client
12/03/2008 2:20:28 PM <generic>: [<No Name>:2772] Creating directory Sourcegear
12/03/2008 2:20:28 PM <generic>: [<No Name>:2772] Creating directory
12/03/2008 2:20:28 PM <generic>: [<No Name>:2772] [System.ArgumentException: The path is not of a legal form.
at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)
at System.IO.Path.GetDirectoryName(String path)
at VaultClientOperationsLib.LocalSettings.VaultClientConfigReader.MakeAllDirectories(String path)
at VaultClientOperationsLib.LocalSettings.VaultClientConfigReader.MakeAllDirectories(String path)
at VaultClientOperationsLib.LocalSettings.VaultClientConfigReader.MakeAllDirectories(String path)
at VaultClientOperationsLib.LocalSettings.VaultClientConfigReader..ctor(String scope, String strDefLocation)
at VaultClientOperationsLib.LocalSettings.Init(LocalSettingsScope scope, String strDefaultConfigDir)
at VaultClientOperationsLib.ClientInstance.Init(AccessLevelType accessLevel)
at VaultShadowFolder.VaultShadowFolderService.TestServerConnection()]The path is not of a legal form.
at System.IO.Path.NormalizePathFast(String path, Boolean fullCheck)
at System.IO.Path.GetDirectoryName(String path)
at VaultClientOperationsLib.LocalSettings.VaultClientConfigReader.MakeAllDirectories(String path)
at VaultClientOperationsLib.LocalSettings.VaultClientConfigReader.MakeAllDirectories(String path)
at VaultClientOperationsLib.LocalSettings.VaultClientConfigReader.MakeAllDirectories(String path)
at VaultClientOperationsLib.LocalSettings.VaultClientConfigReader..ctor(String scope, String strDefLocation)
at VaultClientOperationsLib.LocalSettings.Init(LocalSettingsScope scope, String strDefaultConfigDir)
at VaultClientOperationsLib.ClientInstance.Init(AccessLevelType accessLevel)
at VaultShadowFolder.VaultShadowFolderService.TestServerConnection()

Hopefully this helps?

Cheers
Tom

lbauer · Post by **lbauer** » Wed Mar 12, 2008 8:09 am

This is usually a permissions error.
Other users with this error have had success with one of the following:

-- make that custom account a member of the Windows Administrators Group on the Vault server machine. Be sure to restart IIS before trying to setup up shadow folders.

--Use the custom account for the Identity used by the Vault App Pool in IIS (this setting is in the App Pool Properties.

-- Make sure the account used by the Shadow Folder service has full access to the location of the Vault Shadow folder cache (cache location can be set in the Shadow Folder web.config file.)

tommyg · Post by **tommyg** » Thu Mar 13, 2008 10:23 pm

OK, by adding the AD account to the local administrators group, I am now able to get in and put in information for shadow Folders ... next problem

Every time I check a file in, the following error occurs on the Vault Server

.NET Runtime 2.0 Error
EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.3959, P3 45d6968e, P4 mscorlib, P5 2.0.0.0, P6 461eee3d, P7 4c53, P8 6, P9 udta330idobh2roz2ayvlcelag5agtls, P10 NIL.

Then, the client comes up with an error when it attempts to do anything, which appears to restart the Vault Server site.

Any ideas?

Tom

lbauer · Post by **lbauer** » Fri Mar 14, 2008 9:32 am

This sounds like a .Net framework error, but we'd like more information. What is the error that is seen from the client?

We would like to see a copy of the Vault server log, sgvault.log in
%windir%\temp\sgvault on the server machine. You can attach it here or email copy to support at sourcegear.com ATTN Linda. Be sure to provide a link to this post.