Home/ Questions/Q 505457
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T06:36:02+00:00

I’m trying to start a Windows service on Windows Server 2003 from an ASP.NET

  • 0

I’m trying to start a Windows service on Windows Server 2003
from an ASP.NET page:

the code of line 35 is: 

32.    Dim controller As New ServiceController  
33.    controller.MachineName = System.Environment.MachineName    
34.    controller.ServiceName = "WindowsServiceRealName"  
35.    controller.Start()

The error code is

System.InvalidOperationException: Cannot open WindowsServiceRealName service on computer ‘DARWIN’. —> System.ComponentModel.Win32Exception: Access is denied — End of inner exception stack trace — at System.ServiceProcess.ServiceController.GetServiceHandle(Int32 desiredAccess) at System.ServiceProcess.ServiceController.Start(String[] args) at System.ServiceProcess.ServiceController.Start() at AfconParking.Import.StartService() in E:\ProjectsNet\AfconParking\AfconParking\system\Import.aspx.vb:line 35

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The account used for the identity of your ASP.NET application pool (“Network Service” by default) does not have the permissions required to start a service.

    To fix this issue, you have a few options:

    1. Re-architect your site to not require interactions between ASP.NET pages and the service control manager. I really can’t think of a good reason to require this (the service can simply be started at boot time, and remain running: if the service crashes, you should fix the cause of that, and/or use the corrective actions provided by the SCM. If a service restart is needed to kick of some kind of processing, use an IPC mechanism, such as sockets or named pipes, to communicate between your web app and the service instead).

    2. Create a service account with the appropriate permissions (basically, membership of the local Administrators group) as described in detail here. Do note that this has several security implications, none of them particularly good.

    • 0