So, your program encountered an error, and the Vault Server returns error 0, which means "UnspecifiedSystemException". Here is how you deal with it.
Error 0 is our "catch all" error. It means that you did something that caused an Exception that we here at Autodesk didn't expect. So the Exception bubbled up to the top of the stack and resulted in error 0 getting passed back to your program.
Getting more information:
The best thing to do is to find the vlog file on the server. This file logs all server errors, including the error 0 you just ran into. You can find the vlog in your file store folder (ex. C:\Documents and Settings\All Users\Application Data\Autodesk\VaultServer\FileStore). There will be several vlog files, since a new one is created each day.
Open today's file and scroll down until you find your error. I will look something like this:
Error: Soap Exception ( mesg-id = 633969862478903845 )
Exception(Inner): Could not load type 'Connectivity.Core.DataAccess.IEditStatusBuilder' from assembly 'Connectivity.Platform, Version=184.108.40.206, Culture=neutral, PublicKeyToken=null'.
Exception rethrown at :
This is basically the stack trace of the Exception as it is seen on the server. Sometimes you can figure out the problem from the inner exception. For example, if it's a NullReferenceException maybe it's due to some null data you passed in. But most of the time it will just look like useless gibberish, which brings me to my next point.
Getting in touch with us:
Ideally Vault Server should be passing back something back more descriptive than 0. If you run into it, let us know. The best places are through the Autodesk Developer Network or on the Vault newsgroup. Make sure to tell us what you were doing and include the appropriate section from the vlog.