FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at http://help.fogcreek.com/fogbugz.

Posts by Fog Creek Employees are marked:

Documentation
Release Notes
Network Status

IIS Keeps Crashing

After our upgrade to FogBugz 4.0, we have to restart IIS every few days.  We keep getting this message:

The page cannot be displayed
There are too many people accessing the Web site at this time.

Any idea what is causing this?
Brian Hardeman Send private email
Wednesday, March 23, 2005
 
 
Are you on XP?  I think IIS has a user limit on XP (it's around 10 simultaneous accesses).

Look in your EVENT log (application) and see if there is anything interesting.
Michael H. Pryor Send private email
Thursday, March 24, 2005
 
 
Yes, this is an XP pro box.  However, we only have 6 FogBugz licenses, and only 3 of us are actively using this web server.  We never saw this problem under the 3.0 version of FogBugz.  We usually see the error first thing in the morning when the first user tries to log on -- so it seems unlikely that there are actually too many connections.

I checked the event log, but didn't see anything that looked relevant to either FogBugz or IIS.
Brian Hardeman Send private email
Monday, March 28, 2005
 
 
If the event log doesn't display anything, I'm not sure where else to look (maybe the IIS logs?). FB is definitely not displaying that error message.  It is coming directly from IIS...

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q262635&gssnb=1

There is a heartbeat service that runs and accesses the web server every 15 seconds, but I'm not sure how that equates to ten simultaneous logins.
Michael H. Pryor Send private email
Monday, March 28, 2005
 
 
I saw that KB article also.  I did as suggested and disabled keep-alives in the IIS properties, and have not seen that message since.  Too early to tell for sure, but that may have alleviated the problem.

Is the heartbeat service new in FB 4.0?  That could be why I started seeing this only after the upgrade.  If disabling keep-alives in IIS fixes it, I suppose it's not really a FB problem, just probably a quirk in IIS.
Brian Hardeman Send private email
Wednesday, March 30, 2005
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz Bug Tracking and Evidence-Based Scheduling.