Very Computer

This is a strange interaction problem and I'd appreciate any ideas on
how to fix it:

We have an NT Service that starts and runs OK until we rebuild it to
include a module that has SOCKETs. We don't need to call the socket
code -- we just include the socket code in the executable service, which
presumably causes the wsock32.dll to be loaded.

We get this error when we try to start the NT service with socket code
included:
"Initialization of the DLL D:\orant\bin\ociw32.dll failed. The process
is terminating abnormally."

How could the presence of the wsock32.dll cause the ociw32.dll to not
initialize?

Thanks, Sal James

Quote:>This is a strange interaction problem and I'd appreciate any ideas on
>how to fix it:

>We have an NT Service that starts and runs OK until we rebuild it to
>include a module that has SOCKETs. We don't need to call the socket
>code -- we just include the socket code in the executable service, which
>presumably causes the wsock32.dll to be loaded.

>We get this error when we try to start the NT service with socket code
>included:
>"Initialization of the DLL D:\orant\bin\ociw32.dll failed. The process
>is terminating abnormally."

>How could the presence of the wsock32.dll cause the ociw32.dll to not
>initialize?

>Thanks, Sal James

That fixed my problem.

Hope it helps!