XML Errors in Vault Gui Client

Nahum · Post by **Nahum** » Mon Oct 03, 2005 9:19 pm

One of my developers gets the following messages when trying to perform a get from the Vault Gui Client. Sometimes it works, but mostly not.

* An exception was encountered during the get latest operation. Exception: Server was unable to read request. --> There is an error in XML document (1, 998). --> The XML declaration is unexpected. Line 1, position 1027.

* An exception was encountered during the get latest operation. Exception: Server was unable to read request. --> There is an error in XML document (1, 1018). --> The '<' character, hexadecimal value 0x3C, cannot be included in a name. Line 1, position 1025.

* An exception was encountered during the get latest operation. Exception: Server was unable to read request. --> There is an error in XML document (1, 999). --> The XML declaration is unexpected. Line 1, position 1027.

Version 3.1.1.3506 on Win2k Pro SP4. Auto updates are on.

This has just started happening out of the blue as he hasn't installed anything recently.

At the moment Vault is completely unusable for him.

dan · Post by **dan** » Tue Oct 04, 2005 7:47 am

Does the server log contain anything useful?

Also, which version of the .Net framework is in use (use Help-Tech Support to get the one that Vault thinks it is using).

Nahum · Post by **Nahum** » Wed Oct 05, 2005 4:59 pm

Here goes a complete dump from the help-tech support window:

Client Information
Vault Client Version: 3.1.1.3506
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft Windows 2000 Professional
Service Pack: 4.0
OS Version: 5.0.2195
Total Physical Memory: 494.73 MB
Time Zone: (GMT+12:00) Auckland, Wellington

Server Information
Vault Server Version: 3.1.1.3506
.Net Framework Version: 1.1.4322.2300
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 1.0
OS Version: 5.2.3790
Timezone: (GMT+12:00) Auckland, Wellington
SQL Version: Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

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

I don't have access to the vault IIS server machine and have to find the network admin for that, so I havn't looked in the logs yet. I've never actually looked for the logs before so what files should I be looking for and is there anything in partucilar I should look out for in them?

FYI: I've been offsite for a bit, so my tardy response isn't because it's not important for us.

Cheers,

dan · Post by **dan** » Thu Oct 06, 2005 7:19 am

The server log would be in %windir%/temp/sgvault, and might contain some useful info.

Does the user get this on any file or folder a GET is tried on?

To try to localize this:

1. Have someone else login on this user's machine and see if the same thing happens.

2. Have this user login on a different machine, and see what happens.

If it is limited to this user on this machine, clearing out the user cache may help, at %appdata%/sourcegear, but doing so will cause client working folders and file state to be lost, and will need to be recreated.

Nahum · Post by **Nahum** » Fri Oct 07, 2005 7:46 pm

Cool, I'll have a look at the log after the weekend and try points 1 and 2. We have already tried clearing out the cache and this hasn't changed anything.

Nahum · Post by **Nahum** » Sun Oct 09, 2005 9:06 pm

His account works fine on another machine and another users account dosn't work on his machine. A number of other applications such as IIS have stopped working as expected and are exhibiting strange errors also.

We are going to have his machine rebuilt, afterwhich I expect his problems to go away. If not I'll post back here.

)

Cheers for you help.

Nahum · Post by **Nahum** » Mon Oct 10, 2005 10:16 pm

Completely reinstalling the machine has fixed the problem - I do reckon that it was a machine stability problem rather than a vault problem.

Thanks,