|
code
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
What considerations must be taken for app to run as a service?Hello,
On startup my program needs and reads some customized registration data from Windows registry. Some users are running my app as a service on their machines, usually Windows Server 2003. Some of them report, that after some time (month or so) my app stops accessing that data from the registry. What can be the problem? What consideration should be taken when accessing Win registry and running as a service? Is there some limitation? Your thoughts please, Jack "Jack" <replyTo@newsgroup> wrote in message Not much info to go on there. If you know for a fact that your apps news:OGJhP0JQGHA.3272@tk2msftngp13.phx.gbl... > On startup my program needs and reads some customized > registration data from Windows registry. > Some users are running my app as a service on their machines, usually > Windows Server 2003. > Some of them report, that after some time (month or so) my app stops > accessing that data from the registry. > What can be the problem? > What consideration should be taken when accessing Win registry and running > as a service? > Is there some limitation? DEFINITELY work for A WHILE, then the only thing I can think of is that someone is screwing around with security, but who knows? I had a service that worked fine until I upgraded one of the ActiveX controls it used and it never started again. Thanks.
I know nothing about running app as a service. I wonder, can app running as a service access Windows registry all keys? Or are there some limitations involved? Jack Show quoteHide quote "Jeff Johnson [MVP: VB]" <i.get@enough.spam> wrote in message news:Oi8iq%23UQGHA.3936@TK2MSFTNGP12.phx.gbl... > > "Jack" <replyTo@newsgroup> wrote in message > news:OGJhP0JQGHA.3272@tk2msftngp13.phx.gbl... > >> On startup my program needs and reads some customized >> registration data from Windows registry. >> Some users are running my app as a service on their machines, usually >> Windows Server 2003. >> Some of them report, that after some time (month or so) my app stops >> accessing that data from the registry. >> What can be the problem? >> What consideration should be taken when accessing Win registry and >> running as a service? >> Is there some limitation? > > Not much info to go on there. If you know for a fact that your apps > DEFINITELY work for A WHILE, then the only thing I can think of is that > someone is screwing around with security, but who knows? I had a service > that worked fine until I upgraded one of the ActiveX controls it used and > it never started again. > "Jack" <replyTo@newsgroup> wrote in message All services are run under an account. By default (i.e., unless you change news:OKfECdWQGHA.1096@TK2MSFTNGP11.phx.gbl... > I know nothing about running app as a service. > I wonder, can app running as a service access Windows registry all keys? > Or are there some limitations involved? something), it is LocalSystem, an account which has full access to the local computer (and therefore the registry), although it's possible that this was changed to LocalService (a much more limited account) in Windows Server 2003. |
|||||||||||||||||||||||
Other interesting topics