Solved

IIS Express Hangs

Posted on 2013-01-01
6
610 Views
Last Modified: 2013-01-08
I'm using VS2010 Express with SP1 on XP Pro SP3.  I have a web development site on a local drive that was running fine under IIS Express a few days ago.  Now when I launch under IIS Express, IIS Express goes up to 50% CPU usage and doesn't come down, eventually freezing the machine for at least several minutes (at which point I do a hard PC restart).    The site works fine under the VS Development Server (Cassini).  Under IIS Express the page call is

http://localhost:4306/mypage

I made two changes recently that might have affected things.  1) I made a copy of the site for operations testing and got it to run under IIS 5.1.  Then I pointed IIS 5.1 at the development site, and got it to run; works fine.  2)  I renamed the folder that the development site was in, and then could not figure out how to get VS2010 Express to recognize it on the start page; but I got past that.

I tried uninstalling IIS Express and reinstalling, no joy.  

I tried looking at the IISExpress folder config files xml however I can't find documentation to tell me what I might do with them.

I need IIS Express because I've got extensive javascript and REALLY don't want to go back to Cassini for JS debug.

Any suggestions on how to get IIS Express back up and running properly on my development site would be appreciated.

Thanks!
0
Comment
Question by:codequest
  • 5
6 Comments
 
LVL 7

Expert Comment

by:Lalit Chandra
ID: 38734873
I think you have not published the application in REalease mode. Some time it happens in debug mode. So, you can check you Config file (in IIS) and deploying web apps with
debug="false"
0
 
LVL 2

Author Comment

by:codequest
ID: 38734911
Thanks for the input.  I'm not sure I understand.  The problem is with IIS Express, so I'm not sure how IIS 5.1 configurations would affect IIS Express.  Also, I'm using IIS Express specifically for Debug, so I'm not sure that I want to turn debug = "false".  

New information:  I set up a new web application in VS2010 Express, nothing added to it, and it has the same problem of producing an IIS Express hang.
0
 
LVL 2

Author Comment

by:codequest
ID: 38735159
A sample TraceLog entry for the hang error is attached.
fr000014.zip
0
Master Your Team's Linux and Cloud Stack!

The average business loses $13.5M per year to ineffective training (per 1,000 employees). Keep ahead of the competition and combine in-person quality with online cost and flexibility by training with Linux Academy.

 
LVL 2

Author Comment

by:codequest
ID: 38737434
It was pointed out that the above log file had a "attempt to attach an auto-named database" error, so I modified the web.config and I may have I eliminated that, but I can't be sure because I can't get another TraceLog with the "hang";  the system apparently hangs before generating the TraceLog.

Then I ran some more tests, below, in which I changed site start page.  This initially generated a "cannot display page" error instead of the hang, so I thought the error might be more page specific.  But then it generated the hang error on both of the target pages, so that the "cannot display page" versus the hang is not consistent.

> Changed a connection string in web.config => it had two for the CTLS.mdb, a) one with a folder path, b) another with [DataDirectory]; removed b)
> Ran under VS Development Server  => Worked
> Closed VS2010 Express
> Restarted VS2010 Express
> Ran Debug for site under IIS Express => instead of hang, gave "IE cannot display page"
> Repeated Debug for site under IIS Express => again, "cannot display page"  
> In VS2010 Express, changed the start page to "SiteEntrance.aspx", repeated Debug under IIS Express => IIS Express hangs
> Rebooted PC
> Restarted VS2010, changed start page to "zTestLaunch.aspx", run Debug under IIS Express => "IE cannot display page"
> In VS2010 Express, changed the start page to "SiteEntrance.aspx", repeated Debug under IIS Express => "IE cannot display page"
> Stopped debug, restarted debug => cannot display page
> Stopped debug, restarted debug => cannot display page
> Closed VS2010 Express, noted it's pointing to IIS Express, restarted debug => cannot display page (page = SiteEntrance.aspx)
> Restarted VS2010, changed start page to "zTestLaunch.aspx", run Debug under IIS Express => IIS Express hangs

here's the TraceLog from one of the "cannot display page" events
fr000007-cannot-display.zip
0
 
LVL 2

Accepted Solution

by:
codequest earned 0 total points
ID: 38741698
Well, this problem is apparently so peculiar that nobody has heard of it or has any suggestions about it in four forums and one paid service.  Next stop $259 at Microsoft support.  EXCEPT - dumb me, I discovered don't NEED IIS Express to debug javascript in VS Studio Express( (which I thought I did - some misperception probably confused IIS Express with IE, which you do need) so, that being my driver, I don't need to work on this any further.

Finito! Thanks to anyone who read this far.
0
 
LVL 2

Author Closing Comment

by:codequest
ID: 38754104
Responses weren't actionable by me and the requirement went away.
0

Featured Post

Courses: Start Training Online With Pros, Today

Brush up on the basics or master the advanced techniques required to earn essential industry certifications, with Courses. Enroll in a course and start learning today. Training topics range from Android App Dev to the Xen Virtualization Platform.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Whether you've completed a degree in computer sciences or you're a self-taught programmer, writing your first lines of code in the real world is always a challenge. Here are some of the most common pitfalls for new programmers.
This article shows how to deploy dynamic backgrounds to computers depending on the aspect ratio of display
This Micro Tutorial will give you a basic overview how to record your screen with Microsoft Expression Encoder. This program is still free and open for the public to download. This will be demonstrated using Microsoft Expression Encoder 4.
This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel. Part 1 of this series discussed basic error handling code using VBA. http://www.experts-exchange.com/videos/1478/Excel-Error-Handlin…

776 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question