Article Number: 2541
Reviewed: 16/7/2012 (dd/mm/yyyy)
OS: Windows
Problem Description:
When attempting to start a iBUS related Windows services, the
following error message is received:
Could not start the %{Service} service on local computer.
Error 193:0xc1
Upon further investigation, the following entry is found in the
Application logs in Event Viewer:
Event ID: 7000
Source: Service Control Manager
Type: Error
Description: The "Online Backup Scheduler (iBUSOBM)" service failed
to start due to the following error: "Online Backup Scheduler
(iBUSOBM)" is not a valid Win32 application.
Note:
The issue can also occurs for other Windows services, such as the
Online Backup Scheduler (iBUSACB) service, AutoUpdateAgent
(iBUSACB) service or iBUS Offsite Backup Server and Replication
Server ... etc.
Cause:
This issue occurs when one or both of the following conditions is
true:
There is a file named 'Program' in your SystemDrive folder.
There is a file named 'Common' in your ProgramFiles folder.
When Windows Service Control Manager (Services.exe) tries to start
the Server service, the program verifies the following paths:
SystemDrive\Program
Program Files\Common
If the Program or Common paths exist as files, the Service Control
Manager cannot locate the required folders, you will receive the
error messages and event ID messages that are listed in the Problem
Description section of this article. This issue can also occurs if the path of the executable file for
the service contains spaces.
When a service is started by Windows, the operating system first
parses the path of the service from left to right. If both of the
following conditions are true, Windows may locate and try to run
the file or folder before it locates and runs the executable file
for the service: The path of a service’s executable file contains spaces.
There is a file or folder on your computer’s hard disk that has the
same name as a file or folder in the path to the service's
executable file.
For example, if the path of the executable file for a service is
'C:\Program Files\iBUSOBM\bin\Scheduler.exe', and if a folder that
is named 'C:\Program' also exists on your hard disk, Windows
locates the 'C:\Program' folder on your hard disk before the
'C:\Program Files\iBUSOBM\bin\Scheduler.exe' file, and then tries
to run it. For more details, please refer to the following article from
Microsoft. http://support.microsoft.com/kb/812486
Resolution:
To resolve the problem, rename, move, or delete the respective
files or folder listed below from the SystemDrive folder and/or the
ProgramFiles folder.
Common
Program
Alternatively, please refer to the Microsoft knowledge base article
for adding quotation marks around the corresponding entry in the
Windows registry.http://support.microsoft.com/kb/812486