"There is an error in XML document"

[cdeck]

Hi,

"There is an error in XML document (4,88 )"

This is the exact error message displayed just after selecting the project (after authentication). What is that I have to check for to resolve this? (I am not the admin.)

Thanks.

[lbauer]

What version of Vault client and server are you using?

Is this error in Visual Studio? What version?

Were you able to select the project before?

Is this specific to your machine or login? Does it happen to other users?

Is there anything in the Vault server log file or in the Event Viewer on your machine that corresponds to this error?

[cdeck]

The project was opened before. Once the hardcopy was cleared and was tried to pull it through VisualStudio, no files came in even after authentication and selection of project. At the same time, at VaultClient the mentioned message also appeared, with all files in 'missing' status.

Both Client and Server versions 3.1.3.3538

It seemed to happen in 'one' machine for 'one' username.

Would this information suffice?

[cdeck]

Need to pull this up. Any clue as to help this?

[lbauer]

We could use more information.

If I understand this correctly, for one user on one machine, trying to open a project causes the XML error. Other users can open the project with no problem and the user can open the project from a different machine with no problem, correct?

Also, the user is unable to "Get latest" on the project using the Vault GUI Client?

Can the user open other projects?

Is the user using Visual Studio to connect to Vault and using the Open from Source Control Command?

What version of Visual Studio is it?

Is there anything in the Vault server log file or in the Event Viewer on the machine that corresponds to this error?

Has the user tried clearing their client side cache (http://support.sourcegear.com/viewtopic.php?t=6), backing the files in their working directory and doing an "Open from Source Control" into an empty working directory?

If this doesn't work, it could be that there's a configuration problem with that machine. We've had a few reports of XML errors and they seem to be related to a bad .Net installation. Uninstalling / Reinstalling the .Net framework solved the problem.