cancel
Showing results for 
Search instead for 
Did you mean: 

Upgraded NBU 7.0 server fails to run with a 193 error

Tom_Grimes
Level 3
I could not find an article on the issue I encountered so I'll post up my experience for the benefit of others.

I upgraded my NBU Master server from 6.5.4 to 7.0 only to find that the console would not launch due to the following services failing to start -
NetBackup Client Service
NetBackup Database Manager
NetBackup Device Manager
NetBackup Request Daemon

When I tried to manually start them most of the services produce a 'failed dependencies' error but the Client Service produced a 193 error. Looking in the event log I saw coresponding 7000 events which is a ".... is not a valid win32 application" error.

Researching this led me to the MS article below which finally resolved my issue, I suspect that you are more likely to encounter this error if you are running NBU on Windows x64 as you will probably have 2 paths containing application installations "Program Files" and "Program Files (x86)"

The annoying thing is that most of the NBU services have their registry 'imagepath' values correctly enclosed in quotes but the four services that failed to start did not, this is something that Symantec probably needs to fix in their NBU v7.0 installation package.


http://support.microsoft.com/kb/812486
One or more of the services that are installed on your computer do not start, and one of the following issues occurs:

  • You receive the following error message:
    Error 193: %1 is not a valid Win32 application.
    -and-
  • The following event is logged in the System event log for each service that does not start:

    Event ID: 7000
    Source: Service Control Manager
    Type: Error
    Description:
    The ServiceName service failed to start due to the following error: %1 is not a valid Win32 application.

This issue may occur if the path of the executable file for the service contains...

This issue may occur if the path of the executable file for the service contains spaces.

When Windows starts a service, it 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\MyProgram\MyService.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\MyProgram\My Service.exe file, and then tries to run it.


RESOLUTION

This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756  (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows


To resolve this issue, add quotation marks around the following entry in the Windows registry, where <ServiceName> is the name of the service:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<ServiceName>\ImagePath
The ImagePath entry contains the path of the executable file for the service. To add quotation marks around the ImagePath entry for a service:
  1. Click Start, and then click Run.
  2. In the Open box, type regedit, and then click OK.
  3. Locate, and then click the following registry entry, where <ServiceName> is the name of the service:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<ServiceName>.
    For example, if the service is named MyService, locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MyService key.
  4. In the right pane, double-click ImagePath.
  5. In the Value data box, add quotation marks around the complete path of the executable file for the service.

    For example, if the path of the MyService service is C:\Program Files\MyProgram\MyService.exe, change the entry in the Value data box for the MyService service to the following
    "C:\Program Files\MyProgram\MyService.exe"
  6. Click OK, and then quit Registry Editor.
Regards,
Tom
1 ACCEPTED SOLUTION

Accepted Solutions

Tom_Grimes
Level 3
Yeah, I thought I'd give everyone thinking of a v7.0 upgrade a heads-up on this just incase they fall foul. I did log a case and they were not aware of the issue so now it has been referred to the backline.

View solution in original post

4 REPLIES 4

Marianne
Level 6
Partner    VIP    Accredited Certified
Thanks for the info Tom! I hope that you've logged a call with Symantec Support?

Tom_Grimes
Level 3
Yeah, I thought I'd give everyone thinking of a v7.0 upgrade a heads-up on this just incase they fall foul. I did log a case and they were not aware of the issue so now it has been referred to the backline.

Bill_Burditzman
Level 3
Sorry- but you never install a first release of any enterprise system product.
Wait until a product patch or two appears before you upgrade anything- unless there is some shiny new feature you absolutely must have today?

Tom_Grimes
Level 3
Why wouldn't I want to evaluate it before putting it into my production environment? I do not want 'some shiny new feature' but I do have some issues with my current set-up for which there are fixes in v7.0 so it makes sense to start my investigation into that version's performance and stability. If I satisfy my criteria then it makes sense to install it, first release or not.

I am merely posting here to let other users know of a previously undocumented issue.