I'm trying to install the NBU client onto a Win2K server. It runs through the setup questions OK, but when I click the button to start the actual installation, the "Installation Completed Successfully" window is displayed instantly, and no files are actually written to the server.
Comparing the MSI log with a successful logfile from another server, the difference seems to begin at the "Doing action: Appsearch" part of the installation. On the "good" server, all but one property has 5 lines of data under it, such as:
AppSearch: Property: WasAdvertised, Signature: Reg_WasAdvertised
MSI (c) (40:3C): Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (40:3C): Note: 1: 2262 2: CompLocator 3: -2147287038
MSI (c) (40:3C): Note: 1: 1402 2: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion 3: 2
MSI (c) (40:3C): Note: 1: 2262 2: IniLocator 3: -2147287038
MSI (c) (40:3C): Note: 1: 2262 2: DrLocator 3: -2147287038
However, most of the property sheets on the "bad" server are missing the middle line with the registry key. The next (and possibly more relevant) deviation is a few pages further down the log. The "good" server is as follows:
MSI (c) (40:3C): Skipping action: PostDialogProcessing_Alpha (condition is false)
MSI (c) (40:3C): Doing action: SetupProgress
Action start 14:47:48: SetupProgress.
Info 2898.MSSWhiteSerif8, Tahoma, 0
DEBUG: Error 2826: Control DlgLine on dialog SetupProgress extends beyond the boundaries of the dialog to the right by 64 pixels
Internal Error 2826. SetupProgress, DlgLine, to the right
Info 2898.MSSansBold8, Tahoma, 0
Action 14:47:48: SetupProgress. Dialog created
Action ended 14:47:48: SetupProgress. Return value 1.
MSI (c) (40:3C): Doing action: ExecuteAction
Action start 14:47:48: ExecuteAction.
While the "bad" server looks like this:
MSI (c) (54:5C): Skipping action: PostDialogProcessing_Alpha (condition is false)
MSI (c) (54:5C): Skipping action: SetupProgress (condition is false)
MSI (c) (54:5C): Skipping action: ExecuteAction (condition is false)
This looks to my untrained eye as if the installer is at this point deciding not to install the software.
Has anyone come across this before, and more importantly, does anyone have any idea how to fix this?
Please help me, it's driving me crazy!
Comparing the MSI log with a successful logfile from another server, the difference seems to begin at the "Doing action: Appsearch" part of the installation. On the "good" server, all but one property has 5 lines of data under it, such as:
AppSearch: Property: WasAdvertised, Signature: Reg_WasAdvertised
MSI (c) (40:3C): Note: 1: 2262 2: Signature 3: -2147287038
MSI (c) (40:3C): Note: 1: 2262 2: CompLocator 3: -2147287038
MSI (c) (40:3C): Note: 1: 1402 2: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion 3: 2
MSI (c) (40:3C): Note: 1: 2262 2: IniLocator 3: -2147287038
MSI (c) (40:3C): Note: 1: 2262 2: DrLocator 3: -2147287038
However, most of the property sheets on the "bad" server are missing the middle line with the registry key. The next (and possibly more relevant) deviation is a few pages further down the log. The "good" server is as follows:
MSI (c) (40:3C): Skipping action: PostDialogProcessing_Alpha (condition is false)
MSI (c) (40:3C): Doing action: SetupProgress
Action start 14:47:48: SetupProgress.
Info 2898.MSSWhiteSerif8, Tahoma, 0
DEBUG: Error 2826: Control DlgLine on dialog SetupProgress extends beyond the boundaries of the dialog to the right by 64 pixels
Internal Error 2826. SetupProgress, DlgLine, to the right
Info 2898.MSSansBold8, Tahoma, 0
Action 14:47:48: SetupProgress. Dialog created
Action ended 14:47:48: SetupProgress. Return value 1.
MSI (c) (40:3C): Doing action: ExecuteAction
Action start 14:47:48: ExecuteAction.
While the "bad" server looks like this:
MSI (c) (54:5C): Skipping action: PostDialogProcessing_Alpha (condition is false)
MSI (c) (54:5C): Skipping action: SetupProgress (condition is false)
MSI (c) (54:5C): Skipping action: ExecuteAction (condition is false)
This looks to my untrained eye as if the installer is at this point deciding not to install the software.
Has anyone come across this before, and more importantly, does anyone have any idea how to fix this?
Please help me, it's driving me crazy!