A forum for technical support discussion related to Fogbugz.
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.
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...
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.
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.
This topic is archived. No further replies will be accepted.Other recent topics