Hi ,

We are getting a following error when we are browsing the web site which was build and published on to the local machine (which is having Windows XP Sp2 and Visual Studio 2005 RTM.)

Server Error in '/Ea' Application. -------------------------------------------------------------------------------- Mutex could not be created.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: Mutex could not be created.
Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [InvalidOperationException: Mutex could not be created.] System.Web.Compilation.CompilationMutex..ctor(String name, String comment) +3464673 System.Web.Compilation.CompilationLock..cctor() +158 [TypeInitializationException: The type initializer for 'System.Web.Compilation.CompilationLock' threw an exception.] System.Web.Compilation.CompilationLock.GetLock(Boolean& gotLock) +32 System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +114 [HttpException (0x80004005): The type initializer for 'System.Web.Compilation.CompilationLock' threw an exception.] System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +3426855 System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +88 System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +149 -------------------------------------------------------------------------------- Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

Please kindly provide us a solution / workaround in order to resolve this issue.

Thanks in advance.
MDeevi.

Having the same issue here.  On Server 2003, fresh install with all critical updates, SP1, .NET 2.0.  Installed SQL Express 2005, VWD 2005, then ran through tutorial for creating a web site on a local IIS server.  Received an error about NT AUTHORITY/NETWORK SERVICE not having permissions to the .NET 2.0 temporary folder, set the NETWORK SERVICE account to full control for that folder.  Next time the app was run, generated the Mutex error above.

Jeff

Hi All

I have got the same issue. It seems like Visual studio 2005 and the web application pool running ASP.NET 2.0 are having a conflict over the temporary folder.
The workaround I have got for now is:
- If you have visual studio 2005 is open, close it
- Go tot the ASP.NET temporary folder for v2.0 of the framework
    <Windows dir>\Microsoft.Net\Framework\v2.0<extra numbers>\Temporary ASpNET pages
- Remove the folder for your application (or all of them)
- Reset IIS (on a command line window, >iisreset) [not always needed, but I had to use it sometimes]
- First Browse your page from IE (http://localhost/your app)
- Then reopen Visual studio

And it should work now

I hope it will work for you as he does for me.

Joao Morais (joao.morais@free.fr)

This fixed my problem - and I would have never guessed the solution.

Thanks

Jim Harris

Thanks, its realy works.

 

Arthur

I had the same problem when I transferred my 2.0 project from my work computer to my home computer.  I was able to get rid of the "Mutex" error using the solution suggested here.

However, when I try to run it from Visual Studio, I get a compilation error:  "the type initializer for 'System.Web.Compilation.CompilationLock' threw an exception."

If I tell it to run in spite of the error, it runs and there does not seem to be any problem, but it's a little disturbing.  Why would I be getting this on my home computer and not on my work computer?  Both computers have the same version of Visual Studio.

Has anyone else run into this error?

Many Thanks ..  Mikell

Many Many thanks for the answer to this question.

I have been surfing for about an hour before I found this out.

Now does anyone know if my 1.1 projects will still work?

I have not been brave enough to try yet.

Now that I have this site converted its off to do another.

bob

Well, I have the same problem as CynthiaD... Even if I create a new project I have this error: "The type initializer for 'System.Web.Compilation.CompilationLock' threw an exception."

and realy do not have an idea how to solve that...

CynthiaD - are you logged in to windows with administrator permissions? I am not.

No, I am not administrator either, but now my project works. To tell the truth, I can't remember what I did exactly!

However, as I recall it worked OK if I opened it in file mode and used the development server instead of IIS.  It was when I ran it in IIS that it had the problem.

However, now I CAN run it in IIS and it also works there .. so I am afraid I am not much use because I can't remember what I did.  But I would try opening the project in file mode and seeing what happens.

hm... what do you mean by the 'file mode'?

Well, if you pick "Open Web Site" (not "Open Project") from the File menu, it comes up with a dialog box with five icons down the left side:  File System, Local IIS, FTP Site, Remote Site, and Source Control.  If you select "File System" you can browse to your site and open it, and then it does not run using IIS, it runs using the special Developer Web Server that comes with ASP.NET 2.0.

If you try that, you MAY not get the Mutex error ... hard to remember, but I think that's how I got around it.

I have the same problem. The solution above allows me to browse to the site through IE, but I now get the error in Visual Studio. I tried opening the site from the file system instead of IIS and this does not fix the problem.

with the file system it works, but when i came back to IIS it didn't.

I logged in as an Administrator, and everything works fine! but the problem is that i cannot be logged in as an adm normally... but i guess this is a problem of some settings in permissions... but which?... that is a question :)

if someone knows... it would be great if you share the news :)

Thanks a Million it worked for me too !!,

But Guys we need to know exactly what happened any idea ?