URGENT: Error generating XML document on all clients

[dmurty]

Upon opening source gear clients 3.1.9 we get an error message
"Server was unable to process request. --> There was an error generating the XML document. --> Method not found: Byte VaultLib.VaultCheckOutUser.get_LockType()."

If we run the source gear client from the server we get the following error message:
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.InvalidOperationException: There was an error generating the XML document. ---> System.MissingMethodException: Method not found: Byte VaultLib.VaultCheckOutUser.get_LockType().
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriter1.Write18_VaultCheckOutUser(String n, String ns, VaultCheckOutUser o, Boolean isNullable, Boolean needType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriter1.Write17_VaultCheckOutItem(String n, String ns, VaultCheckOutItem o, Boolean isNullable, Boolean needType)
at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationWriter1.Write116_GetCheckOutListChangesResponse(Object[] p)
at Microsoft.Xml.Serialization.GeneratedAssembly.GetCheckOutListChangesResponseSerializer.Serialize(Object objectToSerialize, XmlSerializationWriter writer)
at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle)
--- End of inner exception stack trace ---
at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces, String encodingStyle)
at System.Xml.Serialization.XmlSerializer.Serialize(XmlWriter xmlWriter, Object o, XmlSerializerNamespaces namespaces)
at System.Web.Services.Protocols.SoapServerProtocol.WriteReturns(Object[] returnValues, Stream outputStream)
at System.Web.Services.Protocols.WebServiceHandler.WriteReturns(Object[] returnValues)
at System.Web.Services.Protocols.WebServiceHandler.Invoke()
--- End of inner exception stack trace ---

We have restarted IIS but nothing seems to fix this issue. It seems to have happened all of a sudden. Thought it was related to MSXML4 so we repaired that install but that did not work either.


Please help, all of our development is on hold right now!

[jclausius]

The "method not found" message indicates something may have changed with the .Net Framework on either the client or server, or the Vault server installation itself. The Vault client is trying to make a web request which is not found on the server.

Let's try trouble shooting from the Vault Server's viewpoint. On the server, try browsing to http://localhost/vaultservice/vaultservice.asmx. Do you get a Service Description page. If so, try invoking Ping. Does that return an XML-document with return type of 1?

If that works correctly, try running the Vault client or Vault Admin Tool on the Vault server using localhost as the server name. Does that work?

If nothing works for these tests, you may want to investigate to see if the .Net Framework has been affected (or may need to be re-installed), IIS's ASP.Net configuration has been affected (then you'll need to run aspnet_regiis.exe under the .Net Framework directory), or if the Vault Server has been affected (in this case an uninstall / reinstall may resolve the problem).

[jclausius]

Also check the Vault Server Log as well as the Windows Event Viewer. There may be some kind of indication to what is wrong.

[dmurty]

Thanks for the help. After a simple reboot of the server all of the workstations are now able to connect with no issues. There was nothing in the vault log files and nothing in the event logs. No updates were applied. Support thinks it may have something to do with our SQL Server log file being so large.

[jclausius]

You may want to check your database's recovery model.

If set to SIMPLE, just make a full backup of the sgvault database through your SQL Server Backup tool of choice, and then truncate the database log file (BACKUP LOG sgvault WITH TRUNCATE_ONLY).

If set to FULL or BULK, then you'll need to take a look at cleaning up the log after backing up the database's log file. Another option would be to switch to SIMPLE, and or switching the backup mode to SIMPLE and use backup mode mentioned above.