CMS PortIO service service failed to start to the following error: The system cannot find the file specified

CMS PortIO service service failed to start to the following error: The system cannot find the file specified
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

mlongohConnect With a Mentor Commented:
The file that the service is specified to use is missing.  One of a few possibilities - either the path specified for the service was changed, or the file that it is trying to use has been moved/renamed, or the file is corrupt, or it has been deleted.

I've encountered a similar problem where Norton AV thought my service's executable was infected (it was not - the AV thinking it was infected was a false positive) and it quarantined the file.

First check the service.  It depends on what version of OS you're running, but assuming XP here's what to do:
Click on Start, Run, and type Services.msc and hit enter
When services start, find the CMS PortIO service, right-click it and choose Properties.
One of the fields you'll see in properties is "Path to executable" - this is what is getting run when the service starts.  Verify that this file exists in the specified path.

If it exists, then it is possibly a permissions issue - but only if the service is NOT using the System account for logon.  You can click the Logon tab of the service properties to verify.

That's the first place to look.
Double click this service in start>run>services.msc, and you will see the "Path to Executable"

Go to that path, and replace it from a known working machine.....
Or look for it under "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services" in teh registry, for the ImagePath value.....
Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services, there is a key called PortD.  Its Display Name is CMS PortIO Service.  That's why you can't find it, since the message in Event Log is picking up Display Name instead of Key Name.
Expand PortD and change Start to 4, and you won't get the message any longer.
Someone said that key was left hanging when you deleted CMS BounceBack Pro.  That was the case for me -- I upgraded from Pro to Ultimate.
All Courses

From novice to tech pro — start learning today.