R
Raul Rodriguez
Dear all,
one of my mates has got a problem and he has been looking everywhere for a
solution. I thought I could ask for help here.
He has developed a Win32 service that should be a "watchdog" for a process
that is going to do all the work. He had to do this because in this work
process he will open connections to different databases and the OleDB
provider has got a leak. The idea is as follows: the service starts the work
process that does all the work and it monitors it. If the process is using
too much memory it will shutdown it and start it again.
Now comes the problem: he starts the child process with CreateProcess and he
cannot open any database connection from it!! If he opens the connection
from the watchdog service or starts the work process directly from the
desktop every runs. It seems as if the child process isn't getting the
rights for opening databases. I thought that the child process inherits the
rights from the parent process but this doesn't seem to be the case.
Have you got any idea?
one of my mates has got a problem and he has been looking everywhere for a
solution. I thought I could ask for help here.
He has developed a Win32 service that should be a "watchdog" for a process
that is going to do all the work. He had to do this because in this work
process he will open connections to different databases and the OleDB
provider has got a leak. The idea is as follows: the service starts the work
process that does all the work and it monitors it. If the process is using
too much memory it will shutdown it and start it again.
Now comes the problem: he starts the child process with CreateProcess and he
cannot open any database connection from it!! If he opens the connection
from the watchdog service or starts the work process directly from the
desktop every runs. It seems as if the child process isn't getting the
rights for opening databases. I thought that the child process inherits the
rights from the parent process but this doesn't seem to be the case.
Have you got any idea?