Good point, sorry I don't know how I overlooked that detail. If the other
clients are successfully connecting you may just try to change/repair the
Vault client and see if that does the trick. I think I saw that error
message and ran with it, bad assumption on my part, because I've seen it a
handful of times. Usually, that is a reference to something not being right
with .NET framework. If the change/repair on the client doesn't do the
trick, you might take a look at your vlog files (which are located in yourn
default filestore folder on the Vault server - even if the file store has
been moved elsewhere). The vlog files and maybe the VaultManager logs in the
same location can yield clues about where the problem lies.
Let me know how it goes..
Thanks,
Bob Henry
MSD Support Specialist
Autodesk, Inc
---------------------
wrote in message news:4894599@discussion.autodesk.com...
Thanks a lot Bob. I will try. Do you mean repair Vault 3 Server or Client?
The server is communicating fine with the other clients.