>Dear all,
>Having a problem with a backend process with terminal services clients.
>I've written a backend standalone exe (olepublic) that runs upon startup of the server.
>Clients login via terminal services to do their operation and as part of the operation, the individual sessions will send in processing jobs to a table (as a new record) and the processing will then be done by the backend process. A temporary table containing the result will be created with a filename that is given by the client process. On top of this, records are updated to databases in other directories.
>The problem that I have is that this model works fine from local network clients. However, for clients accessing via terminal services, each session needs to startup the backend standalone exe (even though one has already been started under the administrator logon) in order for the client to have access to the backend process.
>Is there a solution to this ?
>Thanks in advance.
>Yau

under the dcomfig setting for that standalone.exe check the access permissions, you can custom set them to be allow all and for authentcaton to be none, if it then works, then increase the security til you find what was preventing it.

it's nearly always the settings under dcomcnfg for these situations.

hope that helps.