Auto-refresh error

snapjeff · Post by **snapjeff** » Tue Jul 08, 2008 1:59 pm

For some users, we are getting entries in the server log when a background auto-refresh is executed. The server log entry has the following:

System.InvalidCastException: Unable to cast object of type 'VaultServiceBase.VaultFile' to type 'VaultServiceBase.VaultFolder'.

The user has no idea that this error happened as the Vault client does not display any error. This is not a consistent error and I cannot determine anything in common with the users that generate this error. There can be a couple dozen of these in a day.

Is this something we should be concerned about?

Vault version: 4.1.2.18185

- Jeff

Beth · Post by **Beth** » Tue Jul 08, 2008 2:43 pm

Are there any other errors listed there as well?

Did your users set working folders in Vault as well as VS? If so, have them unset their working folders in Vault, or go into their Clear Client Side Cache and delete cachemember_workingfolderassignments. Make sure Vault and VS are both closed if and when you remove that cache member.

Do you have any sharing or branching going on?

What version of VS are you using and do you have it set to use the Vault Enhanced or Classic client?

snapjeff · Post by **snapjeff** » Fri Jul 18, 2008 5:03 pm

Sorry it took so long to reply.

Are there any other errors listed there as well?

Nope.

Did your users set working folders in Vault as well as VS?

No, they used the GUI client to set their working folders.

Do you have any sharing or branching going on?

Yes.

What version of VS are you using and do you have it set to use the Vault Enhanced or Classic client?

The users that are generating this error are using VS2005, Enhanced client.

Jeff

Beth · Post by **Beth** » Mon Jul 21, 2008 12:27 pm

The users that are generating this error are using VS2005, Enhanced client.

Using IDE integration and then using the GUI client to set working folders leaves open the possibility of having the working folders set differently in each location. When you are first binding a project to source control, what VS has as the location for the solution is the working folder. If the working folders for VS and Vault don't match, then confusion usually results and one doesn't know which is being used or updated.

Can you make a copy of your working folder assignments and then remove it from the cache area (close Vault and VS before starting)? Then try to open the solution in VS and work with it.