Auto Refresh Folder Tree Resets ReadOnly Flag

[ninety]

Just that really.

Vault client 3.5.1 (4786)
I have added the Status field to Windows Explorer.
Windows Explorer shows file status as RA - readonly, archive.
Check out file.
Windows Explorer shows file status as A - archive.
Vault client performs an auto folder tree refresh.
Windows Explorer shows file status as RA - readonly, archive.

This is happening on 2 clients, not all.

Your help is appreciated.

[Beth]

Did you check out the file from inside the Vault GUI client or from inside VIsual Studio?

[ninety]

The file was checked out with the vault client.

It is not necessary to actually open the checked out file for the problem to occur, though.

[Beth]

Could you have one of the clients that is having problems go to Help - Technical support and post the information from there? You don't need to add anything about the licenses. Then it would be good to see what the same area looks like for a user that doesn't have the same issue.

[ninety]

Thanks you for taking a look. The details are below:

From a client WITH the problem:
Client Information
Vault Client Version: 3.5.1.4786
.Net Framework Version: 2.0.50727.1433
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 502.07 MB
Time Zone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London

Server Information
Vault Server Version: 3.5.2.5087
.Net Framework Version: 1.1.4322.2407
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
SQL Version: Microsoft SQL Server 2000 - 8.00.2050 (Intel X86)
Mar 7 2008 21:29:56
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

License Information
2 serial number(s):
1 of 2: 5 users, permanent
2 of 2: 25 users, permanent

From a client WITHOUT the problem:
Client Information
Vault Client Version: 3.5.1.4786
.Net Framework Version: 1.1.4322.2407
Operating System: Microsoft Windows XP Professional
Service Pack: 3.0
OS Version: 5.1.2600
Total Physical Memory: 2 GB
Time Zone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London

Server Information
Vault Server Version: 3.5.2.5087
.Net Framework Version: 1.1.4322.2407
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
SQL Version: Microsoft SQL Server 2000 - 8.00.2050 (Intel X86)
Mar 7 2008 21:29:56
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

License Information
2 serial number(s):
1 of 2: 5 users, permanent
2 of 2: 25 users, permanent

[Beth]

The problem client is using the 2.0 .NET framework. Normally, that's not a problem, but sometimes the frameworks don't appear to play together well. I'd like you to have the problem client set their Vault to use the 1.1 .NET framework.

1. Go to the vaultguiclient.exe.config file in the Vault directory on your client.
2. Look at the top between <configuration> and <system.net>.
a. Add in the lines I show in between those below, but substitute the x's with the numbers for the .NET framework your server uses. For example, 2.0.50727. In your case, you will be putting in 1.1.4322.

• Code: Select all

  <configuration>
  
  <startup>
  <requiredRuntime version="vx.x.xxxxx" safemode="true"/>
  </startup>
  
  <system.net>

3. Restart your system afterwards and then try using Vault.

[ninety]

Between your advise & making changes to the vault shadow copy settings we seem to have resolved the issue.

Many thanks for you help,

N

[lbauer]

Glad things are working properly for you now. Let us know if we can be of assistance in the future.