My clients cannot connect now. I get this error:
[InvalidOperationException: Mutex could not be created.]
System.Web.Compilation.CompilationMutex..ctor(Boolean initialOwner, String name, String comment) +245
System.Web.Compilation.CompilationLock..cctor() +112
[TypeInitializationException: The type initializer for "System.Web.Compilation.CompilationLock" threw an exception.]
System.Web.UI.TemplateParser.GetParserCacheItemInternal(Boolean fCreateIfNotFound) +20
System.Web.UI.TemplateParser.GetParserCacheItem() +32
System.Web.UI.ApplicationFileParser.GetCompiledApplicationType(String inputFile, HttpContext context, ApplicationFileParser& parser) +171
System.Web.HttpApplicationFactory.CompileApplication(HttpContext context) +43
System.Web.HttpApplicationFactory.Init(HttpContext context) +485
System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +170
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +414
Cannot connec to server after upgraded to 3.1.5 from 3.0.7
Moderator: SourceGear
A couple of questions:
1) What happens when you browse to http://localhost/vaultservice/vaultservice.asmx on the Vault server?
2) If Step 1 produces the Service Description page, have you tried a Vault client running on the Vault server? What about a Vault Admin Tool installed on the Vault server?
1) What happens when you browse to http://localhost/vaultservice/vaultservice.asmx on the Vault server?
2) If Step 1 produces the Service Description page, have you tried a Vault client running on the Vault server? What about a Vault Admin Tool installed on the Vault server?
Jeff Clausius
SourceGear
SourceGear
I get the same error
I've tried connecting to the .asmx page and using a local Vault client on the machine.
In both cases, I get the same error message.
In both cases, I get the same error message.
So a web browser is spitting out the error? If so, it seems like something is wrong with the IIS / ASP.Net configuration on the machine.
You can try to do a couple of different things:
1) Re try re-registering ASP.Net with IIS. This is done by running the .Net Framework's "aspnet_regiis.exe -i" from within the %WINDIR%\Microsoft.NET\Framework\v1.1.4322 directory.
2) You could also try reinstalling the .Net Framework on your Vault server.
An internet search on "System.Web.Compilation.CompilationLock" may provide other information related to this problem.
You can try to do a couple of different things:
1) Re try re-registering ASP.Net with IIS. This is done by running the .Net Framework's "aspnet_regiis.exe -i" from within the %WINDIR%\Microsoft.NET\Framework\v1.1.4322 directory.
2) You could also try reinstalling the .Net Framework on your Vault server.
An internet search on "System.Web.Compilation.CompilationLock" may provide other information related to this problem.
Jeff Clausius
SourceGear
SourceGear
This is resolved
The problem was my C drive was running out of space.