While testing with an external DLL in an external C_ESQL32 environment on SA 18.104.22.1683 (GA), the above error (SQLCODE -675) was raised a few times - mainly when the same external function were called from different connections in parallel.
AFAIK, the error was only raised by events that called these functions (before doing backups and the like), not when calling these functions directly from a DBISQLC session.
As each event is always run on its own connection, it will always get its own external environment process. Therefore I don't know what kind of "main thread" might be missing.
Any hints are highly appreciated:)
Yes, I'm still testing the same DLL that has already triggered other questions as well...
The error is a bad one and currently being "fixed". The main problem is that the external environment's main connection thread did not establish a connection with the server within the 15 second timeout. The problem can arise if the server is very busy or if a large number of external environments are being started at the same time. Doing a backup could also cause the error while the backup starts up. If that is the case, try delaying the backup until the extenv call is complete.
answered 14 Jul '10, 15:55