NT Service would not start...!
-
I have a Windows Service application with 4-5 dialog boxes in it. I have good reasons to believe that it should have them, but the service would not start unless I remove them. Anybody any ideas ?
. . . Humans do it better . . .
If your running under the 'system' account you need to have "Allow service to interact with desktop" checked. This is in the Server Properties dialog that you must get to from the 'Services' control panel. "No matter where you go, there your are..." - Buckaoo Banzi <pete/>
-
If your running under the 'system' account you need to have "Allow service to interact with desktop" checked. This is in the Server Properties dialog that you must get to from the 'Services' control panel. "No matter where you go, there your are..." - Buckaoo Banzi <pete/>
Yes that is check'd but is there any restrictions on the size of the UI resources that can be put in a Service (that is causing me problems) ? or Is there any limit on the size of the service exe image loaded ? Tnx palbano
. . . Humans do it better . . .
-
I have a Windows Service application with 4-5 dialog boxes in it. I have good reasons to believe that it should have them, but the service would not start unless I remove them. Anybody any ideas ?
. . . Humans do it better . . .
Prabhakar wrote: I have a Windows Service application with 4-5 dialog boxes in it. I have good reasons to believe that it should have them, but the service would not start unless I remove them. Thumb rule: Services should not have windows or consoles that provide feedback to the user. If the service must have a user interface, it must run under the LocalSystem account. Any information from EventLog when you have those dialog boxes? Follow live World Cup Cricket scores here[^]
-
I have a Windows Service application with 4-5 dialog boxes in it. I have good reasons to believe that it should have them, but the service would not start unless I remove them. Anybody any ideas ?
. . . Humans do it better . . .
Read this: MSDN[^] lpDesktop Windows NT/2000/XP: Pointer to a null-terminated string that specifies either the name of the desktop, or the name of both the desktop and window station for this process. A backslash in the string indicates that the string includes both the desktop and window station names. For CreateProcess and CreateProcessAsUser, if this member is NULL, the new process inherits the desktop and window station of its parent process. If this member is an empty string, the process does not inherit the desktop and window station of its parent process; instead, the system determines if a new desktop and window station need to be created. If the impersonated user already has a desktop, the system uses the existing desktop. For CreateProcessWithLogonW, if this member is NULL or an empty string, the new process inherits the desktop and window station of its parent process. CreateProcessWithLogonW adds permission for the specified user account to the inherited window station and desktop. Otherwise, if this member specifies a desktop, it is the responsibility of the application to add permission for the specified user account to the specified window station and desktop. Follow live World Cup Cricket scores here[^]