It means that the database is unavailable. Stop your SQL server while Witango is running and you'll see this error. It is misleading. In fact it's probably getting confused about the reason why it couldn't open a new connection. Problems might occur with network connectivity or the ODBC driver as well as database issues (crashed, restarting, etc.)
Oh, and if you are having trouble killing your Witango service, look for an old cmd called KILL. It was part of the NT 4 Resource Kit, I think. Robert Tronics -----Original Message----- From: Bill Downall [mailto:[EMAIL PROTECTED] Sent: Thursday, September 18, 2003 10:06 PM To: [EMAIL PROTECTED] Subject: Witango-Talk: Max connections: 0??? [ 648] 2003-09-18 11:00:46 RUNTIME WARNING Unable to open to odbc.DBName due to an error during connection [ 648] 2003-09-18 11:00:46 RUNTIME INFO Max connections: 0 Current connections: 0 Does anyone have any experience or knowledge about the above lines in the witangoevents.log? What leads to "Max connections: 0" and what does it mean? Thanks. Bill ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
