Mutex timeout of 30000 ms / null object reference error.

[Cat]

I've seen these two errors mentioned in the forum, but I haven't found any resolution.

Repro steps:
Log in with both a VS2008 instance and a standalone client.
Put computer to sleep.
Resume from sleep on a different WiFi network.

The only way to fix things is to close all Vault connections (VS and standalone.)

I'm forced to kill the VS process if I get the mutex error, or work offline. A 'quit' option here would be nice.

[Beth]

on a different WiFi network

I think that is the root of the issue. That is a large change to make in the middle of an already existing connection.

Does it happen if don't switch networks?

I can put in a feature request for a quit button.

[Cat]

I'll try to see what happens if I don't switch networks.

Why can't there be an option to re-establish the connection? I frequently put my laptop to sleep at home, drive to work, then bring it out of sleep at my desk. Surely many people do this?

[Beth]

This wouldn't really be a re-establishing of a connection due to the network changing I think. It doesn't mean we couldn't see if there's a nice way to change how it works with this though. I can put in a feature request.

[jeremy_sg]

One option you have is to go to the File->Change Vault Bindings dialog. From there, you can uncheck the Online checkbox to enter offline mode. Hit Ok on the Bindings dialog. Then you should be able to click the File->Vault Source Control->Go Online menu item to reconnect to the server.

[Cat]

Working offline is not an option, because most of the time I'm presented with a modal dialog box. Dismissing the box only makes it pop back up immediately. I have to terminate the devenv.exe process.

All Vault-related connections must be closed before I can successfully use Visual Studio. This means closing 3 to 4 instances, some of which must be terminated, potentially losing data.

[Cat]

This is also now happening in without any hibernation/sleep. It's usually preceded by a Namespace Conflict or other out-of-the-ordinary state that has to be resolved.

[ian_sg]

The mutex timeouts when there are namespace conflicts was a known issue that was resolved in either 4.1.2 or 4.1.3. Can you upgrade your client to the latest version, 4.1.4? (It will work with any 4.1.x server, so you can upgrade the server whenever it's convenient.) If the behavior persists after upgrading, let us know.

[Cat]

I'll upgrade today; thanks!

[Beth]

Thanks. If you have any further questions just let us know.