Has anyone seen the following situation: Once or twice a day our MS-SQL SP3 database server stops responding. All jobs on it hang and it is unresponsive to enterprise manager. WiTango locks up waiting on queries to return. The database log shows several occurences of the following error:
Process 69:0 (6b0) UMS Context 0x0D37A8B0 appears to be non-yielding on Scheduler 2. Error: 17883, Severity: 1, State: 0 We've installed a recommended hotfix from Microsoft to no avail. When we kill the WiTango service the database comes back. Since we can't connect to the database during this time, I can't tell what the process ID mentioned in the error is - by the time we can get back in it's gone. Since killing WiTango seems to fix it, I'm assuming it's a WiTango query of some kind. We're running: W2K SP4, WiTango .065 with SQL Server ODBC driver version 2000.85.1022.00. Database is W2K SP3, MS-SQL SP3. Any help would be appreciated... Dave Machin ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
