cancel
Showing results for 
Search instead for 
Did you mean: 

Pushing Windows client upgrade fails

Dan_Giberson
Level 5

We are standing up a new Netbackup 7.5.0.3 evironment to replace our old NBU 7.0.1 environment. We are having issues doing remote installs to multiple (or even one) client.  Local install of client works fine with the same credentials used in the remote push (Domain Admin). I have also tried with the local Administrator account (also fails). The install fails going from client to client as well as from Master to client. Below is the log file:

 


1:(06/19/12 13:43:34)->Log Started: ID:1
1:(06/19/12 13:43:51)->Creating destination connection: computername, Administrator
1:(06/19/12 13:43:51)->Connecting to remote WMI service: computername, computername\Administrator
1:(06/19/12 13:43:51)->Connecting: root\cimv2, computername, computername\Administrator
1:(06/19/12 13:43:54)->Connecting to remote registry: computername, computername\Administrator
1:(06/19/12 13:43:54)->Connecting: root\default, computername, computername\Administrator
1:(06/19/12 13:43:58)->Querying remote drives...
1:(06/19/12 13:43:58)->Creating remote install directory...
1:(06/19/12 13:43:58)->Creating folder: C:\BEW-6E004B53783842F68158922A14A9E83C
1:(06/19/12 13:43:58)->Creating process: cmd.exe /c md C:\BEW-6E004B53783842F68158922A14A9E83C
1:(06/19/12 13:44:00)->Creating share: BEW-6E004B53783842F68158922A14A9E83C, C:\BEW-6E004B53783842F68158922A14A9E83C, BEWPush Temporary Directory
1:(06/19/12 13:44:00)->Creating security descriptor...
1:(06/19/12 13:44:00)->Creating security DACL...
1:(06/19/12 13:44:01)->Establishing connection to network resource: \\computername\BEW-6E004B53783842F68158922A14A9E83C, computername\Administrator
1:(06/19/12 13:44:01)->Connection has been established: \\computername\BEW-6E004B53783842F68158922A14A9E83C, computername\Administrator
1:(06/19/12 13:44:53)->Getting server information...
1:(06/19/12 13:44:53)->ERROR: Code(-2147417848): executing query: select * from Win32_OperatingSystem
1:(06/19/12 13:44:53)->Pushing files: C:\Users\danbert\AppData\Local\Temp\NBStaging\PC_Clnt\x64\NBUPush_computername_computername.lst
1:(06/19/12 13:44:53)->Reading push files: C:\Users\danbert\AppData\Local\Temp\NBStaging\PC_Clnt\x64\NBUPush_computername_computername.lst
1:(06/19/12 13:44:53)->Adding push file: \NBStaging\PC_Clnt\x64\Bkupinst.xsl, \temp\nbusetup\Bkupinst.xsl, 1
1:(06/19/12 13:44:53)->Adding push file: \NBStaging\PC_Clnt\x64\data1.cab, \temp\nbuSetup\data1.cab, 1
1:(06/19/12 13:44:53)->Adding push file: \NBStaging\PC_Clnt\x64\data2.cab, \temp\nbuSetup\data2.cab, 1
1:(06/19/12 13:44:53)->Adding push file: \NBStaging\PC_Clnt\x64\data3.cab, \temp\nbuSetup\data3.cab, 1
1:(06/19/12 13:44:53)->Adding push file: \NBStaging\PC_Clnt\x64\data4.cab, \temp\nbuSetup\data4.cab, 1
1:(06/19/12 13:44:53)->Adding push file: \NBStaging\PC_Clnt\x64\NBUPush_computername_computername.resp, \temp\nbuSetup\NBUPush_computername_computername.resp, 1
1:(06/19/12 13:44:53)->Adding push file: \NBStaging\PC_Clnt\x64\setup.exe, \temp\nbuSetup\setup.exe, 1
1:(06/19/12 13:44:53)->Adding push file: \NBStaging\PC_Clnt\x64\strpimon.exe, \temp\nbuSetup\strpimon.exe, 1
1:(06/19/12 13:44:53)->Adding push file: \NBStaging\PC_Clnt\x64\VxLogServer.exe, \temp\nbuSetup\VxLogServer.exe, 1
1:(06/19/12 13:44:53)->Adding push file: \NBStaging\PC_Clnt\x64\VxSetup.ini, \temp\nbuSetup\VxSetup.ini, 1
1:(06/19/12 13:44:53)->Adding push file: \NBStaging\PC_Clnt\x64\Symantec NetBackup Client.msi, \temp\nbuSetup\Symantec NetBackup Client.msi, 1
1:(06/19/12 13:44:53)->Pushing files...
1:(06/19/12 13:44:53)->Disconnecting from network resource: \\computername\BEW-6E004B53783842F68158922A14A9E83C
1:(06/19/12 13:44:53)->Disconnected from network resource: \\computername\BEW-6E004B53783842F68158922A14A9E83C
1:(06/19/12 13:44:53)->Deleting remote share...
1:(06/19/12 13:44:53)->Connecting to remote WMI service: computername, computername\Administrator
1:(06/19/12 13:44:53)->Connecting: root\cimv2, computername, computername\Administrator
1:(06/19/12 13:44:55)->Connecting to remote registry: computername, computername\Administrator
1:(06/19/12 13:44:55)->Connecting: root\default, computername, computername\Administrator
1:(06/19/12 13:44:59)->Deleting remote share...
1:(06/19/12 13:44:59)->Deleting entire folder: C:\BEW-6E004B53783842F68158922A14A9E83C
1:(06/19/12 13:44:59)->Deleting entire folder by api: C:\BEW-6E004B53783842F68158922A14A9E83C
1:(06/19/12 13:44:59)->Deleting folder files: C:\BEW-6E004B53783842F68158922A14A9E83C
1:(06/19/12 13:44:59)->Getting sub folders: C:\BEW-6E004B53783842F68158922A14A9E83C
1:(06/19/12 13:44:59)->Deleting folder: C:\BEW-6E004B53783842F68158922A14A9E83C
1:(06/19/12 13:44:59)->Querying remote drives...
1:(06/19/12 13:44:59)->Creating remote install directory...
1:(06/19/12 13:44:59)->Creating folder: C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:44:59)->Creating process: cmd.exe /c md C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:45:01)->Creating share: BEW-B58FB0FBC3514D3A8B0FBCD95D747635, C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635, BEWPush Temporary Directory
1:(06/19/12 13:45:01)->Creating security descriptor...
1:(06/19/12 13:45:01)->Creating security DACL...
1:(06/19/12 13:45:01)->Establishing connection to network resource: \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635, computername\Administrator
1:(06/19/12 13:45:01)->Connection has been established: \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635, computername\Administrator
1:(06/19/12 13:45:01)->Copying files to machine: computername
1:(06/19/12 13:45:01)->Creating directory: \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635\temp
1:(06/19/12 13:45:01)->Creating directory: \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635\temp\nbusetup
1:(06/19/12 13:45:01)->Copying file: C:\Users\danbert\AppData\Local\Temp\\NBStaging\PC_Clnt\x64\Bkupinst.xsl, \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635\temp\nbusetup\Bkupinst.xsl, 1
1:(06/19/12 13:45:01)->Copying file: C:\Users\danbert\AppData\Local\Temp\\NBStaging\PC_Clnt\x64\data1.cab, \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635\temp\nbuSetup\data1.cab, 1
1:(06/19/12 13:45:03)->Copying file: C:\Users\danbert\AppData\Local\Temp\\NBStaging\PC_Clnt\x64\data2.cab, \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635\temp\nbuSetup\data2.cab, 1
1:(06/19/12 13:45:04)->Copying file: C:\Users\danbert\AppData\Local\Temp\\NBStaging\PC_Clnt\x64\data3.cab, \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635\temp\nbuSetup\data3.cab, 1
1:(06/19/12 13:45:05)->Copying file: C:\Users\danbert\AppData\Local\Temp\\NBStaging\PC_Clnt\x64\data4.cab, \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635\temp\nbuSetup\data4.cab, 1
1:(06/19/12 13:45:05)->Copying file: C:\Users\danbert\AppData\Local\Temp\\NBStaging\PC_Clnt\x64\NBUPush_computername_computername.resp, \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635\temp\nbuSetup\NBUPush_computername_computername...., 1
1:(06/19/12 13:45:05)->Copying file: C:\Users\danbert\AppData\Local\Temp\\NBStaging\PC_Clnt\x64\setup.exe, \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635\temp\nbuSetup\setup.exe, 1
1:(06/19/12 13:45:05)->Copying file: C:\Users\danbert\AppData\Local\Temp\\NBStaging\PC_Clnt\x64\strpimon.exe, \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635\temp\nbuSetup\strpimon.exe, 1
1:(06/19/12 13:45:05)->Copying file: C:\Users\danbert\AppData\Local\Temp\\NBStaging\PC_Clnt\x64\VxLogServer.exe, \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635\temp\nbuSetup\VxLogServer.exe, 1
1:(06/19/12 13:45:05)->Copying file: C:\Users\danbert\AppData\Local\Temp\\NBStaging\PC_Clnt\x64\VxSetup.ini, \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635\temp\nbuSetup\VxSetup.ini, 1
1:(06/19/12 13:45:05)->Copying file: C:\Users\danbert\AppData\Local\Temp\\NBStaging\PC_Clnt\x64\Symantec NetBackup Client.msi, \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635\temp\nbuSetup\Symantec NetBackup Client.msi, 1
1:(06/19/12 13:45:06)->Starting Install: \temp\NBUSetup\strpimon.exe /k SOFTWARE\Veritas\BU\STATUS /i "setup.exe -s /RESPFILE:'NBUPush_computername_computername.resp'"
1:(06/19/12 13:45:06)->Connecting to remote WMI service: computername, computername\Administrator
1:(06/19/12 13:45:06)->Connecting: root\cimv2, computername, computername\Administrator
1:(06/19/12 13:45:06)->Connecting to remote registry: computername, computername\Administrator
1:(06/19/12 13:45:06)->Connecting: root\default, computername, computername\Administrator
1:(06/19/12 13:45:09)->Creating process: C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635\temp\NBUSetup\strpimon.exe /k SOFTWARE\Veritas\BU\STATUS /i "setup.exe -s /RESPFILE:'NBUPush_computername_computername.resp'"
1:(06/19/12 13:47:02)->Cleaning up push install...
1:(06/19/12 13:47:02)->Deleting registry key: -2147483646, SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Install\PushStatus
1:(06/19/12 13:47:02)->ERROR: Code(-2147417848): getting parameter object: StdRegProv, DeleteKey
1:(06/19/12 13:47:02)->Disconnecting from network resource: \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:47:02)->Disconnected from network resource: \\computername\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:47:02)->Deleting remote share...
1:(06/19/12 13:47:02)->Connecting to remote WMI service: computername, computername\Administrator
1:(06/19/12 13:47:02)->Connecting: root\cimv2, computername, computername\Administrator
1:(06/19/12 13:47:04)->Connecting to remote registry: computername, computername\Administrator
1:(06/19/12 13:47:04)->Connecting: root\default, computername, computername\Administrator
1:(06/19/12 13:47:07)->Deleting remote share...
1:(06/19/12 13:47:07)->Deleting entire folder: C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:47:07)->Deleting entire folder by api: C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:47:07)->Deleting folder files: C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:47:07)->Getting sub folders: C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:47:07)->Deleting entire folder by api: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp
1:(06/19/12 13:47:07)->Deleting folder files: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp
1:(06/19/12 13:47:08)->Getting sub folders: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp
1:(06/19/12 13:47:08)->Deleting entire folder by api: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup
1:(06/19/12 13:47:08)->Deleting folder files: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup
1:(06/19/12 13:47:09)->Deleting file: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup\bkupinst.xsl
1:(06/19/12 13:47:09)->Deleting file: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup\data1.cab
1:(06/19/12 13:47:09)->Deleting file: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup\data2.cab
1:(06/19/12 13:47:09)->Deleting file: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup\data3.cab
1:(06/19/12 13:47:09)->Deleting file: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup\data4.cab
1:(06/19/12 13:47:09)->Deleting file: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup\nbupush_computername_computername.resp
1:(06/19/12 13:47:09)->Deleting file: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup\setup.exe
1:(06/19/12 13:47:09)->ERROR: Code(2): deleting file: CIM_Datafile::Delete
1:(06/19/12 13:47:09)->Deleting file: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup\strpimon.exe
1:(06/19/12 13:47:09)->ERROR: Code(2): deleting file: CIM_Datafile::Delete
1:(06/19/12 13:47:09)->Deleting file: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup\symantec netbackup client.msi
1:(06/19/12 13:47:09)->ERROR: Code(15): deleting file: CIM_Datafile::Delete
1:(06/19/12 13:47:09)->Deleting file: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup\vxlogserver.exe
1:(06/19/12 13:47:09)->Deleting file: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup\vxsetup.ini
1:(06/19/12 13:47:09)->Getting sub folders: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup
1:(06/19/12 13:47:09)->Deleting folder: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup
1:(06/19/12 13:47:09)->ERROR: Code(2): deleting folder: Win32_Directory::Delete
1:(06/19/12 13:47:09)->Deleting entire folder by process: C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:47:09)->Creating process: cmd.exe /c rmdir /S /Q C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:47:09)->Deleting remote share...
1:(06/19/12 13:47:09)->Connecting to remote WMI service: computername, computername\Administrator
1:(06/19/12 13:47:09)->Connecting: root\cimv2, computername, computername\Administrator
1:(06/19/12 13:47:09)->Connecting to remote registry: computername, computername\Administrator
1:(06/19/12 13:47:09)->Connecting: root\default, computername, computername\Administrator
1:(06/19/12 13:47:12)->Deleting remote share...
1:(06/19/12 13:47:12)->ERROR: Code(-1): cleaning push install: could not delete folder share
1:(06/19/12 13:47:12)->Deleting entire folder: C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:47:12)->Deleting entire folder by api: C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:47:12)->Deleting folder files: C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:47:12)->Getting sub folders: C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:47:12)->Deleting entire folder by api: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp
1:(06/19/12 13:47:12)->Deleting folder files: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp
1:(06/19/12 13:47:12)->Getting sub folders: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp
1:(06/19/12 13:47:12)->Deleting entire folder by api: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup
1:(06/19/12 13:47:12)->Deleting folder files: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup
1:(06/19/12 13:47:13)->Deleting file: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup\setup.exe
1:(06/19/12 13:47:13)->ERROR: Code(2): deleting file: CIM_Datafile::Delete
1:(06/19/12 13:47:13)->Deleting file: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup\strpimon.exe
1:(06/19/12 13:47:13)->ERROR: Code(2): deleting file: CIM_Datafile::Delete
1:(06/19/12 13:47:13)->Deleting file: c:\bew-b58fb0fbc3514d3a8b0fbcd95d747635\temp\nbusetup\symantec netbackup client.msi
1:(06/19/12 13:47:13)->ERROR: Code(15): deleting file: CIM_Datafile::Delete
1:(06/19/12 13:47:13)->Deleting entire folder by process: C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:47:13)->Creating process: cmd.exe /c rmdir /S /Q C:\BEW-B58FB0FBC3514D3A8B0FBCD95D747635
1:(06/19/12 13:47:13)->Push install cleaned.
 

1 ACCEPTED SOLUTION

Accepted Solutions

Mark_Solutions
Level 6
Partner Accredited Certified

I do see these two lines in your log file in the first post:

ERROR: Code(-2147417848): executing query: select * from Win32_OperatingSystem
Adding push file: \NBStaging\PC_Clnt\x64\Bkupinst.xsl, \temp\nbusetup\Bkupinst.xsl, 1

This indicates you are trying to push from a 32 bit to a 64 bit server and that won't work

Do make sure that they really are like for like - 2003 32bit to 2003 32bit, 2008 64bit to 2008 64 bit etc.

It may be easier for you to do then using the silentclient.cmd files rather than push them out.

View solution in original post

11 REPLIES 11

Yogesh9881
Level 6
Accredited

Is that affected Client is part of cluster ?

Dan_Giberson
Level 5

Hi Yogesh,

No these are straight file servers. Nothing special about them.

Yogesh9881
Level 6
Accredited

As u told us " new Netbackup 7.5.0.3 evironment to replace our old NBU 7.0.1 environment"

Is it fresh installation or upgrade existing NBU infrastructure from 7.0.1 to 7.5.0.3 ??

Dan_Giberson
Level 5

It will be a new install (all new hardware). The exisitng 7.0.1 catalog will not be migrated to the new environment. Instead, we will be re-creating the policies and maintaining the old environment until the images have expired. As such, we are upgrading the clients to 7.5.0.3 and pointing them to the new Master as we create the policies.

Bmitche
Level 5

I have experienced similar issues. The problem I have is pusing from win2008 and trying to import a list of clients....the import just doesn't work. It works fine when I import a client list on a win2003 server. Until a true "fix" is found....this is the work around that I use.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

You need to upgrade to 7.5 first, then 7.5.0.3.

Also should be same bit level?

We have seen in previous forum posts that 32-bit clients can be pushed from another 32-bit machine and same for 64-bit.  Some experience has been that OS should also be the same.

Please see this post for more remote install requirements : https://www-secure.symantec.com/connect/forums/remote-installation-netbackup-75-client-failing-windows-platform#comment-7196471

 

Dan_Giberson
Level 5

Hi Marianne,

I am doing it in a stepped approach and installing to "like" systems. It seems to be very hit or miss on whether the install will work or not.....For now, we are just muscling through and doing them individually.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Have you had a chance to look at the post mentioned above?

It lists actual requirements for remote installations. With all requirements in place, there should be little or no 'misses'...

Mark_Solutions
Level 6
Partner Accredited Certified

I do see these two lines in your log file in the first post:

ERROR: Code(-2147417848): executing query: select * from Win32_OperatingSystem
Adding push file: \NBStaging\PC_Clnt\x64\Bkupinst.xsl, \temp\nbusetup\Bkupinst.xsl, 1

This indicates you are trying to push from a 32 bit to a 64 bit server and that won't work

Do make sure that they really are like for like - 2003 32bit to 2003 32bit, 2008 64bit to 2008 64 bit etc.

It may be easier for you to do then using the silentclient.cmd files rather than push them out.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Update to post mentioned above:  https://www-secure.symantec.com/connect/forums/remote-installation-netbackup-75-client-failing-windows-platform#comment-7303931 

Upon further investigation, we were able to recreate this issue internally, and we recognize the need to directly register the "logon as a service" privilege with a custom service account during Windows remote/push installations.  We've modified our Windows installers to address this.  You should see this change reflected in our future releases.  If you would like us to provide this functionality for past releases, please work with your support contacts to open an official request and we will work to provide the packages.

Let us know if there are questions.

Thank you,
Dan

 

Bmitche
Level 5

I opened a support case and was sent the EEB's to fix it. Looks like step 1 below is also a good workaround.

 

There is two ways to fix this

 

1:  The first option would be to copy/move the import file to the same location from
    which the installer is launched.  This would be the same location where
    setup.exe resides.  I found that doing this resolved the issue for me on Windows
    2008. 


2: This EEB resolves an issue with the 7.5 NetBackup Windows installers being
   unable to import hosts from a list on Windows 2008 and later.  To use the
   EEB, copy the 7.5 GA media to a writeable location.  Overwrite
   "<ROOT>\PC_Clnt\<PLATFORM>\Symantec NetBackup.msi" with the MSI file included
   in this EEB.  Restart the install, and the import hosts from list operation
   will work as desired.


This  EEB 2750798 fix will be in the 7.5.0.4 release