install cluster server error 2147417842

[shafei]

Hi

Install of cluster server stop and i found that error

ERROR: Code(-2147417842): getting parameter object: StdRegProv

Please support

[Anshu_Pathak]

You need to check install logs along with <install_path>\netbackup\logs\cluster on node where you have started installation. These logs will provide detail information on failure.

Install only on one node at a time. Do not select both nodes during installation.

[Tousif]

Hello,

The error is very (-2147417842) generic and the failure must have occurred before this error.

Please share the install log located on the node. 

Log Location:

Default: <Install_path>/veritas/cluster/log

You can also find the log location, in a third or fourth page of the installation wizard.

Regards,

[shafei]

error log

1:(08/12/18 09:20:18)->Starting Install: \temp\NBUSetup\setup.exe "-s /RESPFILE:'NBUPush_ALY_NB-ONE.resp'"
1:(08/12/18 09:20:19)->Connecting to local WMI service...
1:(08/12/18 09:20:19)->Connecting: \\.\root\cimv2, (null), (null)
1:(08/12/18 09:20:19)->Connecting to local registry...
1:(08/12/18 09:20:19)->Connecting: \\.\root\default, (null), (null)
1:(08/12/18 09:20:22)->Creating process: C:\BEW-D7F0B153CA774C26B1A48EDA364ACD94\temp\NBUSetup\setup.exe "-s /RESPFILE:'NBUPush_ALY_NB-ONE.resp'"
1:(08/12/18 09:22:27)->Cleaning up push install...
1:(08/12/18 09:22:27)->Deleting registry key: -2147483646, SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Install\PushStatus
1:(08/12/18 09:22:27)->ERROR: Code(-2147417842): getting parameter object: StdRegProv, DeleteKey
1:(08/12/18 09:22:27)->Disconnecting from network resource: \\NB-ONE\BEW-D7F0B153CA774C26B1A48EDA364ACD94
1:(08/12/18 09:22:27)->Disconnected from network resource: \\NB-ONE\BEW-D7F0B153CA774C26B1A48EDA364ACD94
1:(08/12/18 09:22:27)->Deleting remote share...
1:(08/12/18 09:22:27)->Connecting to local WMI service...
1:(08/12/18 09:22:27)->Connecting: \\.\root\cimv2, (null), (null)
1:(08/12/18 09:22:27)->Connecting to local registry...
1:(08/12/18 09:22:27)->Connecting: \\.\root\default, (null), (null)
1:(08/12/18 09:22:30)->Deleting remote share...
1:(08/12/18 09:22:33)->Deleting entire folder: C:\BEW-D7F0B153CA774C26B1A48EDA364ACD94
1:(08/12/18 09:22:33)->Deleting entire folder by api: C:\BEW-D7F0B153CA774C26B1A48EDA364ACD94
1:(08/12/18 09:22:33)->Deleting folder files: C:\BEW-D7F0B153CA774C26B1A48EDA364ACD94
1:(08/12/18 09:22:33)->Getting sub folders: C:\BEW-D7F0B153CA774C26B1A48EDA364ACD94
1:(08/12/18 09:22:33)->Deleting entire folder by api: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp
1:(08/12/18 09:22:33)->Deleting folder files: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp
1:(08/12/18 09:22:33)->Getting sub folders: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp
1:(08/12/18 09:22:33)->Deleting entire folder by api: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup
1:(08/12/18 09:22:33)->Deleting folder files: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup
1:(08/12/18 09:22:41)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\bkupinst.xsl
1:(08/12/18 09:22:41)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\data1.cab
1:(08/12/18 09:22:41)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\data2.cab
1:(08/12/18 09:22:41)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\data3.cab
1:(08/12/18 09:22:41)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\data4.cab
1:(08/12/18 09:22:41)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\data5.cab
1:(08/12/18 09:22:41)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\data6.cab
1:(08/12/18 09:22:41)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\data7.cab
1:(08/12/18 09:22:41)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\data8.cab
1:(08/12/18 09:22:41)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\nbupush_aly_nb-one.resp
1:(08/12/18 09:22:41)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\setup.exe
1:(08/12/18 09:22:41)->ERROR: Code(2): deleting file: CIM_Datafile::Delete
1:(08/12/18 09:22:41)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\strpimon.exe
1:(08/12/18 09:22:41)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\veritas netbackup server.msi
1:(08/12/18 09:22:41)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\vxlogserver.exe
1:(08/12/18 09:22:41)->Getting sub folders: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup
1:(08/12/18 09:22:41)->Deleting folder: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup
1:(08/12/18 09:22:41)->ERROR: Code(2): deleting folder: Win32_Directory::Delete
1:(08/12/18 09:22:41)->Deleting entire folder by process: C:\BEW-D7F0B153CA774C26B1A48EDA364ACD94
1:(08/12/18 09:22:41)->Creating process: cmd.exe /c rmdir /S /Q C:\BEW-D7F0B153CA774C26B1A48EDA364ACD94
1:(08/12/18 09:22:41)->Deleting remote share...
1:(08/12/18 09:22:41)->Connecting to local WMI service...
1:(08/12/18 09:22:41)->Connecting: \\.\root\cimv2, (null), (null)
1:(08/12/18 09:22:41)->Connecting to local registry...
1:(08/12/18 09:22:41)->Connecting: \\.\root\default, (null), (null)
1:(08/12/18 09:22:44)->Deleting remote share...
1:(08/12/18 09:22:44)->ERROR: Code(-1): cleaning push install: could not delete folder share
1:(08/12/18 09:22:44)->Deleting entire folder: C:\BEW-D7F0B153CA774C26B1A48EDA364ACD94
1:(08/12/18 09:22:44)->Deleting entire folder by api: C:\BEW-D7F0B153CA774C26B1A48EDA364ACD94
1:(08/12/18 09:22:44)->Deleting folder files: C:\BEW-D7F0B153CA774C26B1A48EDA364ACD94
1:(08/12/18 09:22:45)->Getting sub folders: C:\BEW-D7F0B153CA774C26B1A48EDA364ACD94
1:(08/12/18 09:22:45)->Deleting entire folder by api: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp
1:(08/12/18 09:22:45)->Deleting folder files: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp
1:(08/12/18 09:22:45)->Getting sub folders: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp
1:(08/12/18 09:22:45)->Deleting entire folder by api: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup
1:(08/12/18 09:22:45)->Deleting folder files: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup
1:(08/12/18 09:22:45)->Deleting file: c:\bew-d7f0b153ca774c26b1a48eda364acd94\temp\nbusetup\setup.exe
1:(08/12/18 09:22:45)->ERROR: Code(2): deleting file: CIM_Datafile::Delete
1:(08/12/18 09:22:45)->Deleting entire folder by process: C:\BEW-D7F0B153CA774C26B1A48EDA364ACD94
1:(08/12/18 09:22:45)->Creating process: cmd.exe /c rmdir /S /Q C:\BEW-D7F0B153CA774C26B1A48EDA364ACD94
1:(08/12/18 09:22:45)->Push install cleaned.

[Marianne]

What is this reference to Backup Exec?

Deleting registry key: -2147483646, SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Install\PushStatus

Is BE installed on one or more nodes?

Maybe we should take a step back and ask if you have read through NBU Installation Guide and Clustered Master server manual and if you have double checked and ensured that all pre-reqs are in place?

I have shared links to manuals in one of your previous posts. Also in the link in my signature.

[Marianne]

@shafei

In addition to my previous post - reading the documentation and proper preparation is a must for successful installation.

Rather spend a day or 2 reading, preparing, and another double-check before you start with installion. 
Ensure ALL traces of previous installation attempts have been removed, and that ALL other backup software (such as Backup Exec) have been removed.

NBU Installation Guide is the 1st manual to go through - Chapter 4:
Installing server software on Windows systems
This chapter includes the following topics:
■ Installation and upgrade requirements for Windows and Windows clusters
■ About the NetBackup preinstallation Environment Checker
■ Running the preinstallation Environment Checker
■ Requirements for Windows cluster installations and upgrades
■ Performing local, remote, or clustered server installation on Windows systems
■ Post-installation tasks for NetBackup cluster environments
■ Verifying Windows cluster installations or upgrades

NetBackup Clustered Master server manual: Chapter 2:
NetBackup in a Windows Server Failover Clustering
This chapter includes the following topics:
■ About NetBackup on Windows Server Failover Clustering
■ Installation prerequisites for NetBackup on WSFC cluster
■ Installing a NetBackup failover server on WSFC cluster
■ Configuring a NetBackup server on WSFC cluster

[Tousif]

Hello,

Kindly share the latest install log file in text format.

Location: C:\ProgramData\Symantec\NetBackup\InstallLogs

Example File Name:  NetBackup Install.20170220

Regards,

[shafei]

Dear

Please check attached file

[Marianne]

I see this error in the installation log:

08-12-2018,09:22:19 : The web service user account password supplied is invalid. Please confirm that the account exists, and that the password was specified correctly.
08-12-2018,09:22:19 : CustomAction Immediate_CorrectWebsvcAccountCreds returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
08-12-2018,09:22:19 : Action ended 9:22:19: Immediate_CorrectWebsvcAccountCreds. Return value 3.

[shafei]

The istallation like that

2 nodes each node 8G ram

user for installation is nbwebsvc  ,ngwebgrp i have created these on my ADC

Shall i create that user on local account not on ADC

shall at  installation use local account or domain

[Tousif]

Hello,

In a cluster, the user should be a domain user for windows node.

Kindly refer the below article for more information.

https://www.veritas.com/support/en_US/article.000081350 

Thanks for the log. Found the user permission issue in log.

I agree with Marianne Please follow the above mentioned article to fulfill the user requirement.

Regards,

[shafei]

Hello

First thanks for your support

User Domain  has to be nbwebsvc or the administrator of the domain becuase when i use Administrator account i got  error the web server can not run with administrator privilage

also there is no link

please check last error

Thanks

[Marianne · Accepted solution]

I don't understand why you say 'there is no link'. This URL is also mentioned in the list of requirements in NBU Installation Guide:
https://www.veritas.com/support/en_US/article.000081350

Please check user account requirements carefully. You need to get this right for installation to succeed.

You can also use the pre-installation check utility to check requirements.

[Tousif · Accepted solution]

Hello,

Kindly refer the below article for user privileges in more detail.

https://www.veritas.com/support/en_US/article.000125384

In log it showing pbx having an issue "MSCS was not configured".  Could be two possibilities 1) pbx packages already installed 2) cluster not detected by NBU.

1) pbx packages already :

To fix:

A) check if any pbx package installed if not change the  

B) delete the folder if exist C:\Program Files\Veritas\NetBackup\Logs\user_ops

2) cluster not detected by NBU:

A) Make sure that cluster configuration page getting pop up during the installation.

Error :

08-13-2018,13:41:50 : Action start 13:41:50: InstallExecute.
08-13-2018,13:42:06 : Action 13:42:06: uninstallMSCSConfigure.B2D5B6C9_4698_42F7_AC9D_955789A69556. Unconfiguring MSCS configuration of VxPBX exchange
08-13-2018,13:42:06 : An unexpected error occured while installing Veritas Private Branch Exchange. The error desfcription follows:Error Number : -2147024894Error Description : Invalid root in registry key "HKLM\SOFTWARE\VERITAS\VxPBX\MSCSConfigured".Source : WshShell.RegReadMethod Name : unconfigureMSCSOperation : MSCS was not configured.
08-13-2018,13:42:06 : Action 13:42:06: MMTerminateProcess.B2D5B6C9_4698_42F7_AC9D_955789A69556. Terminating VxPBX exchange process
08-13-2018,13:42:06 : Action 13:42:06: UndoBackupMM.B2D5B6C9_4698_42F7_AC9D_955789A69556.

Regards,

[shafei]

Hello

TOUSIF  , Realy thanks for your support

Instllation done :)

Regards

[shafei]

HI

Marianne   , Realy thanks for your support

 done :)

Regards

[Marianne]

This is awesome news! 

Thanks for the feedback. 

I can honestly not stress enough how important it is to take some extra time to go through all the documentation when preparing for a new installation - especially with a clustered master server where the documentation is spread across 2 manuals. Even a third doc with webuser requirements... 
I used to sit with both manuals and compile my own step-by-step checklist and task list, then get a colleague to double-check for me.
The checklist and task list is then ticked off as each step is checked and completed.