NetTalk as a service and ODBC drivers

[Devan]

Hey all,

We've got a web service here written in NetTalk that uses a combination of TPS file and CONNX ODBC drivers to get data from a legacy system.

Client wants this web app to run as a service on their main server so that it is still available after reboots etc.  All fine except that when running as a service, the ODBC links just do not work at all.  No data found.  Running the app standalone works absolutely fine.  I set up the service with the same credentials as I use on the server (when testing standalone OK) but still no dice.  I've made sure the ODBC DSN is a System DSN and not a User DSN.  TPS file access works fine.  Just the ODBC ones that break.

Any tips for getting service based NetTalk sites to communicate nicely via ODBC ?

Thanks,
Devan

[Bruce]

My guess is that you need to add a dependancy - so that your service is "dependent" on the ODBC service.
If your program ran _before_ the ODBC service got going then I guess you'd see something like this effect.

One quick test of this theory is to stop the service, and then start it again. If it then works, then it's likely it's dependent on some other service.

[Larry Sand]

Another thing that happens is the account the service runs under does not have sufficient rights.  If you create a user just for the service and ensure it has logon as service rights and set the service to use it to logon, then you can control the permissions.

Larry Sand

[terryd]

Hi Bruce
I have a service which is dependant on MSSQL and the effect is as you describe, it starts but is not available but if I stop and start the service it's fine.
My question is what is the best way to establish what dependancies a service has and how do I advise the system of  the dependancy?

[Bruce]

open the services manager (services.msc), find your service, select "properties" and navigate from there.