Add New Files Crash (Cleared Cache)

[Tyrsius]

Anytime I try to select "Add New Files" from the menu in vault, it crashes. I have cleared the cache, and even tried installing Vault on a fresh OS. Still happens.

Every forum post I can find seems to think clearing the client cache will resolve the issue. Am I going to need to redo the server installation?

[Beth]

What version of the Vault client did you install and on what operating system?

Are you using the Vault GUI client alone, or are you integrating it with some other software?

Is the Vault client that is crashing on the Vault server or on some other machine?

[Tyrsius]

Vault Client 5.0.4. Crash happens on Windows XP, Windows Vista, and Windows 7.

The Xp machine has vault integrated with visual studio. Crash occurs from Vault GUI, not the IDE. Vista and windows 7 were not integrated.

It is the client crashing, not the server. The server is not affected. The client will be fine if you kill and restart it, but it will crash again if you try to add files. This behavior is quite crippling, since detect new files will not add subfolders.

[Tyrsius]

May be related: Error from web service when trying to open Shadow Folders:

Shadow Folders - Initial Repository
The Shadow Folder Service has a configuration error. A valid Cache Path was not specified, and the Shadow Folder Service was unable to create the cache in the default location. Please specify a valid "shadowfolder_cachepath" in the appSettings of the Shadow Folder Service's web.config file.

[Beth]

The shadow folder error is not related to the client issue at all. If you want to set up shadow folders, then try the suggestions in this KB article: http://support.sourcegear.com/viewtopic ... 13&t=11576.

What .NET frameworks do you have installed on the client machines?

Can you install a client right on the server and run it?

[Tyrsius]

1.1, 2, 3, 3.5, and 4.

No, I can't install on the server atm. Software changes to the server require too much approval.

[Beth]

What other software do you have on all your client machines?

What anti-virus are you running?

Can you see any errors in your client's Event Viewer logs at the same time as the crash?

[Tyrsius]

I highly doubt this has anything to do with other software on the machines. A fresh install of windows 7 should not have anything that corrupts Vault. Also, no software has been added to the XP machine since before this issue was occuring.

Anti-virus is just MSE, on all. There are no errors, it isn't so much a crash as Vault becomes "Not Responding" until I kill it.

[Beth]

Are there any errors in your Event Viewer?

Are there any special group policies applied to machines on your network that could prevent Vault accessing Windows directories?

Are there any mapped drives?

Are you able to set a working folder in Vault or any other functions?

[Tyrsius]

Hanging application VaultGUIClient.exe, version 5.0.4.18845, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

--
Thats the only error.

No policies have changed since the feature worked, and none exists to my knowledge that would do that. Detect new files does not have an issue. There are several mapped drives, but they have also not changed since this feature last worked. The windows 7 fresh install had no mapped drives.

Set working folder works, this is the only feature I know of not working.

I strongly believe this is a server error. With a fresh install on a fresh OS, very few common circumstances should exist between the XP and 7 box, yet the error occurs.

[Beth]

Could I have you try logging into our Vault demo server and see if the Add Files dialog works for you then? The login information is:

• login: guest3
  password: guest3
  server: vaultdemo.sourcegear.com