Wait timeout for mutex after 30000 milliseconds.

[BillFugina]

When i try to log in, I get the error message, "Wait timeout for mutex after 30000 milliseconds."

This only happens when i try to login as myself. If I use the admin account or another user account, I have no problems. It seems as though the server thiks I am still logged in. Indeed, if I look in the Vault Admin Tool, my user name is listed as "Logged In".

Client Information
Vault Client Version: 3.5.0.4741
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 2 GB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)

Server Information
Vault Server Version: 3.5.0.4741
.Net Framework Version: 1.1.4322.2300
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 1.0
OS Version: 5.2.3790
Timezone: (GMT-05:00) Eastern Time (US & Canada)
SQL Version: Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

[lbauer]

Try restarting IIS.

If the problem continues, check the Vault server log, sgvault.log in %windir%\temp\sgvault for more info.

[BillFugina]

Try restarting IIS.

If the problem continues, check the Vault server log, sgvault.log in %windir%\temp\sgvault for more info.

Restarting IIS didn't work.

Here's everything from the log from the restart on:

Code: Select all

	System Started
	Version 3.5.0.4741
	Cache Level = 1
	DataBase Buffer Size (KB) = 256
	LogFile Path = C:\WINDOWS\Temp\sgvault
	Log Level = Debug
	Archive Log = Weekly
	ReverseDNS Lookup = True
	Maximum HTTP Request Length = 102400
	Overwrite Log on Startup = False
	Session Timeout = 4320
	Active Directory Domain = 
	SGVault Working Directory = C:\WINDOWS\Temp
	SGVault Server URL = http://sv.colemaninsights.com/VaultService
	Identity = NT AUTHORITY\NETWORK SERVICE 
----7/26/2006 4:08:21 PM     --()--	Beginning SQL transaction 374 
----7/26/2006 4:08:21 PM     --()--	SQL transaction 374 successfully committed. 
----7/26/2006 4:08:21 PM     --()--	Beginning SQL transaction 375 
----7/26/2006 4:08:21 PM     --()--	SQL transaction 375 successfully committed. 
----7/26/2006 4:08:29 PM     --ROSCOE(192.168.103.36)--SSL Disabled	Beginning SQL transaction 373 
----7/26/2006 4:08:29 PM     --ROSCOE(192.168.103.36)--SSL Disabled	SQL transaction 373 successfully committed. 
----7/26/2006 4:09:08 PM     bfugina--ROSCOE(192.168.103.36)--SSL Disabled	Beginning SQL transaction 395 
----7/26/2006 4:09:08 PM     bfugina--ROSCOE(192.168.103.36)--SSL Disabled	SQL transaction 395 successfully committed. 
----7/26/2006 4:09:08 PM     bfugina--ROSCOE(192.168.103.36)--SSL Disabled	Login 
----7/26/2006 4:09:08 PM     bfugina--ROSCOE(192.168.103.36)--SSL Disabled	GetUserList returned: Success 
----7/26/2006 4:09:08 PM     bfugina--ROSCOE(192.168.103.36)--SSL Disabled	GetUserOptions returned: Success 
----7/26/2006 4:09:08 PM     bfugina--ROSCOE(192.168.103.36)--SSL Disabled	Success 
----7/26/2006 4:09:09 PM     bfugina--ROSCOE(192.168.103.36)--SSL Disabled	GetRepositories returned: Success 
----7/26/2006 4:09:43 PM     bfugina--ROSCOE(192.168.103.36)--SSL Disabled	Logout 
----7/26/2006 4:09:43 PM     bfugina--ROSCOE(192.168.103.36)--SSL Disabled	Beginning SQL transaction 494 
----7/26/2006 4:09:43 PM     bfugina--ROSCOE(192.168.103.36)--SSL Disabled	SQL transaction 494 successfully committed. 
----7/26/2006 4:09:43 PM     bfugina--ROSCOE(192.168.103.36)--SSL Disabled	Beginning SQL transaction 495 
----7/26/2006 4:09:43 PM     bfugina--ROSCOE(192.168.103.36)--SSL Disabled	SQL transaction 495 successfully committed. 

[lbauer]

Are you using Vault on Windows?

Did you close all the Vault clients on your machine -- Visual Studio, GUI, etc?

Look in Task manager to see if there's any other Vault client process running and end them, then re-launch the client.

[BillFugina]

Look in Task manager to see if there's any other Vault client process running and end them, then re-launch the client.

There was a devenv.exe listed as a task even though there were no visible signs of VisualStudio being open. I killed the process and everything went back to normal.

Thanks for your help.

[sswanson]

One of our users is having this problem. We shut down all instances of the vault client, restarted and got it to work again, but do you know what causes it or a more permanent solution?