Last post Oct 18, 2007 12:00 AM by dr. qaak
Nov 12, 2005 12:03 PM|lucamauri|LINK
Aug 09, 2007 06:27 AM|csi|LINK
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.
Oct 18, 2007 12:00 AM|dr. qaak|LINK
I have been getting the same error. I am using ASP.NET web matrix webserver which is free and can be run with arguments:
DRIVE:\Program Files\Microsoft ASP.NET Web Matrix\v0.6.812\WebServer.exe /port:PORTNUMBER /path:"PATH"
As you can see it's fairly easy to configure to run. I sometimes have several webservers running on different ports. I use the webserver to do some maintenance on my web site for me. A file called cleanup.aspx is run once with the querystring = cleanup.aspx?dir=links to
check for broken links in the links directory on my site.
It's scheduled to run again after two hours with a different querystring to check for broken links in another directory.
The MUTEX problem occurs only when trying to run cleanup.aspx as the second scheduled task. It doesn't matter if I've stopped the first scheduled task already and closed the webbrowser on all other ports and closed all browser windows. That simply doesn't
have anything to do with the error.
The temporary fix for me:
After the first scheduled task of starting the webserver and opening up cleanup.aspx?dir=links then I can use the web browser address bar to modify the querystring and proceed to check for broken links in another directory. This however requires some manual
typing which I really hate to have to do
The scheduled tasks are all run under a limitted account. They used to be run under a full control account until I read that it is more secure to use a limitted account for most things but maybe I need to be running these under a full control account.
Also, I used to have no problem doing this with XP but now I've upgraded to VISTA and installed all the latest updates.