System.InvalidOperationException on command line GET.

[cada0310]

Hi there,

I'm getting this error when I use the command line version of GET on some paths in our development tree. Using the IDE on the same path doesn't cause the error.

It appears that the error occurs after the get is fully completed - all the files are where I expect them to be.

There's nothing in the server side log. The version is 4.1.2.

I've restarted IIS, but the same thing keeps happening. I've also deleted the SG cache on the machine where this is occuring.

Thanks for any help you can provide, and if there's more data I can gather, I'd be glad to.

Chris

Unhandled Exception: System.InvalidOperationException: Token StartElement in state Error would result in an invalid XML document.
at System.Xml.XmlTextWriter.AutoComplete(Token token)
at System.Xml.XmlTextWriter.WriteStartElement(String prefix, String localName
, String ns)
at System.Xml.XmlWriter.WriteStartElement(String localName)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)

[Beth]

What is your OS version?
What .NET frameworks do you have loaded on the machine?

[cada0310]

Hi Beth,

Sorry for the slow reply...was on vacation last week.

The OS is 2003 R2 SP2, and .NET 2.0 is loaded on the machine.

Again, it's really weird - it's consistantly a few paths in our source tree - like, it always chokes on the same paths.

Thanks for any information,

Chris

[Beth]

Can you look in your Vault Server Log around the time that you tried those failed Gets and see if there are any different errors?

Also, check in your Event Viewer logs for any errors and post them or email them to me at support at sourcegear.com with a link to this thread.

Could you post how your command is written?

[cada0310]

Hi Beth,

Sure, I'll look around - I'm doing an automated build right now, so I should have some data for you. Can you send me the email address so it's easier to send attachments?

[jeremy_sg]

I think that this is a client side error message. There's most likely something weird in the path of the file, or it's possible that it's trying to write out an error message, but the XML formatter is rejecting it. I would suggest that you build the CLC (the project is in the ClientAPI zip) and look at the line numbers on the stack trace for the VaultCmdLineClient.Main() file. I would be happy to provide you with a debug CLC if necessary.