Exception: There is an error in XML document (1, 600371).

[Perry]

(Posting failed again, with the same error I reported before, I think -- "the forum you selected does not exist" -- why does it keep selecting a non-existent forum, instead of the one I'm trying to post to?)

(But, back to the error I intended to report.)


I just got the following error from the 3.1.6 Vault client:

[01/23/2006 14:09:01] An exception was encountered during the get latest operation. Exception: There is an error in XML document (1, 600371).
InnerException: The operation has timed-out.


Has this error caused any serious damage? What does it require to address?

[Perry]

Retrying to fetch the files -- as I don't know how far it got before that error -- failed entirely this time, apparently:


[01/23/2006 14:14:43] An exception was encountered during the get latest operation. Exception: 2100 : FailExistingDownload

[Perry]

[2006-01-23 14:15:47] Version Check: This Vault client is version 3.1.6.3658
[2006-01-23 14:15:49] Version Check: Your Vault server is version 3.1.6.3658

[Perry]

Closed Vault client down entirely and restarted it and tried again to fetch latest in that directory, and got the original error (I think) again:

[2006-01-23 14:22:09] An exception was encountered during the get latest operation. Exception: There is an error in XML document (1, 355229).
InnerException: The operation has timed-out.

[Perry]

I rebooted the client workstation, and that
- a) caused a new error logging in to this forum:
> "You must select a topic to reply to"
(when I tried to reply to this thread)
- b) fixed the problem

So one fix appears to be to close all applications and reboot.

[Perry]

(I just got the forum error again, replying to this: "You must select a topic to reply to").

Bump, as I think you may have a couple of bugs here (the forum errors, and the bug I was actually reporting above.

[Perry]

Bump as I've never had any responses to this

(Are you all waiting for me to supply some more information of some kind? If so, could you let me know what kind?)

(Should I just keep bumping this every couple days in hopes that someday someone will read it and respond?)

(BTW, I got that forum error again -- You must select a topic to reply to -- so apparently the forums still have that bug.)

[dan]

After searching through some forum history, it looks like this generally happens because of some kind of configuration error on the specific machine being used. I'm not sure we've managed to isolate which package needs re-installed (XML, .Net framework, etc), but people report that it goes away after a machine has been rebuilt.

Can you verify it is a machine issue by logging in on another machine and verifying you don't have the issue?

[Perry]

How could I verify whether this issue is present on any particular machine?

(I don't know what the circumstances are that produce this, so I don't know how to test it.)

[dan]

There appears to be something messed up in the configuration of the machine, but since we can't reproduce it here, there isn't much we can do to isolate it.

Let us know if you can reproduce it in a reliable way, or on a different machine.

[Perry]

There also appears to be a serious problem with the forums, no? Yet again, I got that annoying "You must select a topic to reply to" trying to post this. I am getting kind of tired of that error, I must admit.

But back to the bug of this topic, re: there isn't much we can do

I'd think that you could maybe fix that error message to have some type of useful content -- ie, saying what document is malformed, and how.

[jclausius]

Perry:

Issue 1 - XML error. Have you had a look at your Vault Server Log. Is there any indication that something is wrong? If not, also check your Windows Event View (both application / system logs) of the Vault Server. Finally take a look at the IIS (%windir%\system32\logfiles\W3SVC1) logs.

I think the only other time we've seen something like this, someone had a bad .Net installation. Uninstalling / Reinstalling the .Net framework solved their problem.

Issue 2 - Forum error. Did you see the other post where I had asked about the cookies? Try removing ALL support.sourcegear.com cookies, shutting down the browser, and retry the support site. This is a one time operation to make sure your browser's cookies are refreshed.

[Perry]

re: Vault Server logs

I'll have to ask about them; I'm not an administrator on the server machine.

re: cookies

I just replied in (I think) great detail on the other thread. It appears like it is just a bug in the Reply To button forwarding to the login button -- the forum always forgets what you were doing when it sends you to the login page. The workaround suggested there -- try to remember to go login first before trying to reply -- is probably the best workaround.