New Windows Service installed, fails to start: "System error 2 ... system cannot find the file specified"

Question

I have installed several other custom .Net windows services successfully. A new one I had recently written was very similar to the others and while it installed without error - on starting it with the service controller it failed to start with the error dialog: System error 2 ... system cannot find the file specified.

After time and consternation, the only thing I could think of that was significantly different about this service was that the path and executable name were at least 10 characters longer than any of my other services. On shortening both the path and .exe name and re-installing, the service ran fine: no error! I can only assume my previous path or service or .exe name was too long.

Also, It would be pertinent to mention I had used some borrowed "service driver" code built in to my exe to handle the install/uninstall of the service to the service controller via win API calls. It could be a character limit was hidden within that service driver module.

I could not find any windows related docs to confirm if there is a system bound character limit to a path or service name that I had exceeded. I will dig in to the service driver when time permits and see if that turns out to be the problem. Meanwhile I welcome any insights.

Answer 1

I experimented with some test services and found it was not the length of any property that caused my problem (“System error 2 ... system cannot find the file specified”) to begin with.

My built-in service installer uses three properties: ServiceName, ServiceTitle, ServiceDescription. On installing, I found that it writes a full-service path to the registry, but it doesn’t just take the actual exe (assembly) name, it uses the ServiceName property to build the path!

My issue was that the ServiceName and assembly name didn’t match, hence the file was not found. I used a PowerShell registry query to expose the path and finally noticed the mismatch from there.

When I first noticed the problem I had not noticed that when I shortened the service name from whatever it was – I just used the assembly name without the .exe and that is what actually fixed it, not simply shortening it.

Answer 2

I had a similar issue with a service, where I was getting the same error.

I went to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\YourServiceName\ImagePath

My 'ImagePath' was set to a virtual drive called "W:\" that exists on "C:\".
I replaced this path with the actual file location on the C:\ drive and then the service started successfully

Answer 3

In my case, I opened the Command Promt and navigated to the exe and installed it from there. So I did not enter the full path. Once I used the full path, it worked.

1. So, you need to either install the service with the full path or add the exe file's path to PATH in system environment variables.

    SC CREATE "Service-Name" binpath="D:\full-path-to-service\service.exe"
   

   or add D:\full-path-to-service\ to PATH variable and use

    SC CREATE "Service-Name" binpath="service.exe"
   

2. Also, verify that the path is correct. Because, I once installed with the wrong path and it got successfully installed, but when I tried to start it, I got the same error.

Answer 4

My Problem was, creating the Service with Powershell command added brakets like: <C:\Path\To\Service\Service.exe> to the registry.

Replacing < and > with " fixed it for me.

Answer 5

I had same issue, nothing did solve this error, then I resolved by not using the c:\Windows\System32 path to store the service executable!

Answer 6

In my case, the problem was caused by a mistake in the service start routine. DriverEntry (in my case it was a kernel-mode driver) returns a bad status value. I think this situation applies to user mode too.

Answer 7

Another possible reason that the sys file is blocked. If your driver doesn't exit clearly (for example, you forget to clean up Device, Callouts etc), the sys file may be blocked. To check that you can try removing sys file when service is not working. Normally you should be able to do so. If not, the driver may hold some resources and in turn blocks the sys file.

If your service indeed blocks the file, you should set the service start to Manual (check HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\YourServiceName\Start flag: 0 - start on boot, 3 - manual) and restart your device. This will free up the sys file and you can try again until you fix your clean-up flow.

Answer 8

Well, there is a path limit but not sure the char limit at this movement. Also the the file name should match exe name. sc create MyWinService BinPath=C:\System32\Queue\MyWinService.exe