1 - Standard Server 2 - No, it's SP4 (so I suppose SP2 is included)
3 - Dual Intel Xeon 2.8G hyperthreading, but WiTango only uses one processor. 4 - Yes, nothing obvious, just the restart. 5 - Mostly .tafs, there are two common tcfs that include common functions that each .taf loads. 6 - no 7 - don't think so, not sure how I'd tell if one was happening by mistake though. 8 - Neither What is auditing - is it just a higher level logging? Dave ----- Original Message ----- From: "Rick Sanders" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Friday, January 14, 2005 6:35 AM Subject: Re: Witango-Talk: Any Help Appreciated - WiTango Stops Responding > > Hello Dave, > > 1. What version of W2K server are you running? Small business, standard, or > Enterprise? > 2. Do you have SP2 installed on the server? > 3. What processor are you running on your server? > 4. Did you check the application log in your events log? > 5. Are you running mostly taf's, tcf's, or combo of both. > 6. Do you have any cron jobs running from your WiTango server? > 7. Do you have any continuous loops running that may be causing you a > problem? > 8. Are you running a software firewall, or the Windows firewall? > > Sorry for all the questions, but this will help identify the problem. > > You might also want to turn auditing on the WiTango server. > > Rick > > > > We're having intermittent problems, usually once per day, sometimes more > > often. > > > > Witango (.065, running on W2K SP3) just suddenly stops responding. The > > connections to our IIS web server start climbing and Witango never > > responds > > until killed and restarted. > > > > We thought it might have something to do with our database (MS SQL 2000 > > SP3) > > but we've examined the SQL profiler traces and stepped through the IIS > > logs > > and WiTango does not appear to be issuing any queries at the time it > > stops. > > In fact, all open WiTango connections eventually go away if we leave > > Witango > > unresponsive long enough. > > > > There are no events in the witango events log, related events on the > > system, > > or witango log messages written after Witango stops responding. IIS > > starts > > writing 500 errors about a minute after Witango stops responding to it. > > When Witango stops responding we see a build up of "dllhost" port > > connections (that we normally see come and go) that never go away. I > > assume > > these are attempted connections between IIS and Witango that get stuck. > > > > We so far can see no common events prior to Witango's demise - the > > immediately prior application requests and queries are always different. > > The last event we had happened between a form being displayed and it being > > submitted (in other words, the form was successfully requested and then a > > few seconds later the form is submitted but WiTango is no longer > > responding). > > > > The only other clue is that it seems to be related to system load since > > the > > outages only happen during the day and only on week days. But, it doesn't > > seem to be a particular application causing the problem. > > > > We're getting desperate on this one - we'd be willing to discus paying > > someone to help us solve this problem. > > > > Dave Machin > > > > > > ________________________________________________________________________ > > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > > > > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
