Posted by Tom Fulton on January 31, 2006 at 10:13:25:
Yesterday, an end-user demonstrated why "a little knowledge is a dangerous thing". He decided he needed to Uninstall Comet on a workstation and wound up Uninstalling it off the server, making Comet
unavailable to all users. My network guy re-installed Comet2005 367,
I believe they were running 359 prior to the Uninstall. We have our
document-imaging system installed at this account - so all forms programs open the ODBC Gateway to a MySQL database, print a hard copy pass and then closes the printer and runs a pass that sends records to MySQL tables for later retrieval. This was all working
smooth as silk up till yesterday. Now, when they try to run their
forms programs it will sometimes run and sometimes it will get an
Excp 29, Communications error. Inspecting the ODBC window I see the following on the successful runs:
Up and Running
ODBC CMD 002fb3b0
ODBC DONE 002fb3b0
Link Established
All the File maps, etc. show up here
On the unsuccessful runs, I see the following:
Up and Running
ODBC CMD 002fb328
ODBC DONE 002fb328
Those two commands continually repeat until some kind of timeout is
reached and the EXCP 29 is generated.
We backgraded to Comet2005 359, same results. We sent over the ODBC
DLL and Drv.exe that we're running here, same results. Sometimes it
works, sometimes it doesn't, running about 50 - 50. I really don't know where to go from here. Tom.