cancel
Showing results for 
Search instead for 
Did you mean: 

can't install be 12.5 agent on a w2k8 R2 server

jbroedel
Level 3
version 12.5, SP4

For some reason I cannot push the agent from my media server to a w2k8 r2 server.  Fails with the message:

"attemp to connect to server failed with the following error: no network provider accepted the given network path"

I can see the temp. directory being created on the server but its empty.  Here's the bepushes.log, any ideas?



1:(09/09/10 16:40:38)->Log Started: ID:1
1:(09/09/10 16:40:45)->Creating destination connection: w2k8-1, administrator
1:(09/09/10 16:40:45)->Connecting to remote WMI service: w2k8-1, domain\administrator
1:(09/09/10 16:40:45)->Connecting: root\cimv2, w2k8-1, domain\administrator
1:(09/09/10 16:40:45)->Connecting to remote registry: w2k8-1, domain\administrator
1:(09/09/10 16:40:45)->Connecting: root\default, w2k8-1, domain\administrator
1:(09/09/10 16:40:48)->Querying remote drives...
1:(09/09/10 16:40:48)->Creating remote install directory...
1:(09/09/10 16:40:48)->Creating folder: C:\BEW-3E4015A4351445028BD9EE86F73096EB
1:(09/09/10 16:40:48)->Creating process: cmd.exe /c md C:\BEW-3E4015A4351445028BD9EE86F73096EB
1:(09/09/10 16:40:51)->Creating share: BEW-3E4015A4351445028BD9EE86F73096EB, C:\BEW-3E4015A4351445028BD9EE86F73096EB, BEWPush Temporary Directory
1:(09/09/10 16:40:51)->Creating security descriptor...
1:(09/09/10 16:40:51)->Creating security DACL...
1:(09/09/10 16:40:51)->Establishing connection to network resource: \\w2k8-1\BEW-3E4015A4351445028BD9EE86F73096EB, domain\administrator
1:(09/09/10 16:41:12)->ERROR: Code(1203): Failed to establish connection: \\w2k8-1\BEW-3E4015A4351445028BD9EE86F73096EB, domain\administrator, 0
1:(09/09/10 16:42:34)->Creating destination connection: w2k8-1, administrator
1:(09/09/10 16:42:34)->Connecting to remote WMI service: w2k8-1, w2k8-1\administrator
1:(09/09/10 16:42:34)->Connecting: root\cimv2, w2k8-1, w2k8-1\administrator
1:(09/09/10 16:42:36)->Connecting to remote registry: w2k8-1, w2k8-1\administrator
1:(09/09/10 16:42:36)->Connecting: root\default, w2k8-1, w2k8-1\administrator
1:(09/09/10 16:42:39)->Creating remote install directory...
1:(09/09/10 16:42:39)->Establishing connection to network resource: \\w2k8-1\BEW-3E4015A4351445028BD9EE86F73096EB, w2k8-1\administrator
1:(09/09/10 16:43:00)->ERROR: Code(1203): Failed to establish connection: \\w2k8-1\BEW-3E4015A4351445028BD9EE86F73096EB, w2k8-1\administrator, 0
1:(09/09/10 16:43:37)->Creating destination connection: w2k8-1, administrator
1:(09/09/10 16:43:37)->Connecting to remote WMI service: w2k8-1, domain\administrator
1:(09/09/10 16:43:37)->Connecting: root\cimv2, w2k8-1, domain\administrator
1:(09/09/10 16:43:37)->Connecting to remote registry: w2k8-1, domain\administrator
1:(09/09/10 16:43:37)->Connecting: root\default, w2k8-1, domain\administrator
1:(09/09/10 16:43:40)->Creating remote install directory...
1:(09/09/10 16:43:40)->Establishing connection to network resource: \\w2k8-1\BEW-3E4015A4351445028BD9EE86F73096EB, domain\administrator
1:(09/09/10 16:44:01)->ERROR: Code(1203): Failed to establish connection: \\w2k8-1\BEW-3E4015A4351445028BD9EE86F73096EB, domain\administrator, 0
1:(09/09/10 16:48:28)->Creating destination connection: w2k8-1, administrator
1:(09/09/10 16:48:28)->Connecting to remote WMI service: w2k8-1, domain\administrator
1:(09/09/10 16:48:28)->Connecting: root\cimv2, w2k8-1, domain\administrator
1:(09/09/10 16:48:28)->Connecting to remote registry: w2k8-1, domain\administrator
1:(09/09/10 16:48:28)->Connecting: root\default, w2k8-1, domain\administrator
1:(09/09/10 16:48:31)->Creating remote install directory...
1:(09/09/10 16:48:31)->Establishing connection to network resource: \\w2k8-1\BEW-3E4015A4351445028BD9EE86F73096EB, domain\administrator
1:(09/09/10 16:48:52)->ERROR: Code(1203): Failed to establish connection: \\w2k8-1\BEW-3E4015A4351445028BD9EE86F73096EB, domain\administrator, 0
1:(09/09/10 16:49:05)->Creating destination connection: w2k8-1, administrator
1:(09/09/10 16:49:05)->Connecting to remote WMI service: w2k8-1, w2k8-1\administrator
1:(09/09/10 16:49:05)->Connecting: root\cimv2, w2k8-1, w2k8-1\administrator
1:(09/09/10 16:49:07)->Connecting to remote registry: w2k8-1, w2k8-1\administrator
1:(09/09/10 16:49:07)->Connecting: root\default, w2k8-1, w2k8-1\administrator
1:(09/09/10 16:49:10)->Creating remote install directory...
1:(09/09/10 16:49:10)->Establishing connection to network resource: \\w2k8-1\BEW-3E4015A4351445028BD9EE86F73096EB, w2k8-1\administrator
1:(09/09/10 16:49:31)->ERROR: Code(1203): Failed to establish connection: \\w2k8-1\BEW-3E4015A4351445028BD9EE86F73096EB, w2k8-1\administrator, 0
1:(09/09/10 16:49:40)->Cleaning up push install...
1:(09/09/10 16:49:40)->Deleting registry key: -2147483646, SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Install\PushStatus
1:(09/09/10 16:49:40)->ERROR: Code(-2147417848): getting parameter object: StdRegProv, DeleteKey
1:(09/09/10 16:49:40)->Disconnecting from network resource: \\w2k8-1\BEW-3E4015A4351445028BD9EE86F73096EB
1:(09/09/10 16:49:40)->Disconnected from network resource: \\w2k8-1\BEW-3E4015A4351445028BD9EE86F73096EB
1:(09/09/10 16:49:40)->Deleting remote share...
1:(09/09/10 16:49:40)->Connecting to remote WMI service: w2k8-1, w2k8-1\administrator
1:(09/09/10 16:49:40)->Connecting: root\cimv2, w2k8-1, w2k8-1\administrator
1:(09/09/10 16:49:40)->ERROR: Code(-2147221008): creating locator
1:(09/09/10 16:49:40)->Push install cleaned.
1:(09/09/10 16:51:28)->Log Started: ID:1
1:(09/09/10 16:51:40)->Creating destination connection: 10.10.10.13, administrator
1:(09/09/10 16:51:40)->Connecting to remote WMI service: 10.10.10.13, w2k8-1\administrator
1:(09/09/10 16:51:40)->Connecting: root\cimv2, 10.10.10.13, w2k8-1\administrator
1:(09/09/10 16:51:42)->Connecting to remote registry: 10.10.10.13, w2k8-1\administrator
1:(09/09/10 16:51:42)->Connecting: root\default, 10.10.10.13, w2k8-1\administrator
1:(09/09/10 16:51:45)->Querying remote drives...
1:(09/09/10 16:51:45)->Creating remote install directory...
1:(09/09/10 16:51:45)->Creating folder: C:\BEW-2A86519253E84A4C95A7CFE56EAD71C7
1:(09/09/10 16:51:45)->Creating process: cmd.exe /c md C:\BEW-2A86519253E84A4C95A7CFE56EAD71C7
1:(09/09/10 16:51:48)->Creating share: BEW-2A86519253E84A4C95A7CFE56EAD71C7, C:\BEW-2A86519253E84A4C95A7CFE56EAD71C7, BEWPush Temporary Directory
1:(09/09/10 16:51:48)->Creating security descriptor...
1:(09/09/10 16:51:48)->Creating security DACL...
1:(09/09/10 16:51:48)->Establishing connection to network resource: \\10.10.10.13\BEW-2A86519253E84A4C95A7CFE56EAD71C7, w2k8-1\administrator
1:(09/09/10 16:52:09)->ERROR: Code(1203): Failed to establish connection: \\10.10.10.13\BEW-2A86519253E84A4C95A7CFE56EAD71C7, w2k8-1\administrator, 0
1:(09/09/10 16:55:48)->Creating destination connection: 10.10.10.13, administrator
1:(09/09/10 16:55:48)->Connecting to remote WMI service: 10.10.10.13, w2k8-1\administrator
1:(09/09/10 16:55:48)->Connecting: root\cimv2, 10.10.10.13, w2k8-1\administrator
1:(09/09/10 16:55:50)->Connecting to remote registry: 10.10.10.13, w2k8-1\administrator
1:(09/09/10 16:55:50)->Connecting: root\default, 10.10.10.13, w2k8-1\administrator
1:(09/09/10 16:55:53)->Creating remote install directory...
1:(09/09/10 16:55:53)->Establishing connection to network resource: \\10.10.10.13\BEW-2A86519253E84A4C95A7CFE56EAD71C7, w2k8-1\administrator
1:(09/09/10 16:56:14)->ERROR: Code(1203): Failed to establish connection: \\10.10.10.13\BEW-2A86519253E84A4C95A7CFE56EAD71C7, w2k8-1\administrator, 0
1:(09/09/10 17:02:26)->Cleaning up push install...
1:(09/09/10 17:02:26)->Deleting registry key: -2147483646, SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Install\PushStatus
1:(09/09/10 17:02:26)->ERROR: Code(-2147417848): getting parameter object: StdRegProv, DeleteKey
1:(09/09/10 17:02:26)->Disconnecting from network resource: \\10.10.10.13\BEW-2A86519253E84A4C95A7CFE56EAD71C7
1:(09/09/10 17:02:26)->Disconnected from network resource: \\10.10.10.13\BEW-2A86519253E84A4C95A7CFE56EAD71C7
1:(09/09/10 17:02:26)->Deleting remote share...
1:(09/09/10 17:02:26)->Connecting to remote WMI service: 10.10.10.13, w2k8-1\administrator
1:(09/09/10 17:02:26)->Connecting: root\cimv2, 10.10.10.13, w2k8-1\administrator
1:(09/09/10 17:02:29)->Connecting to remote registry: 10.10.10.13, w2k8-1\administrator
1:(09/09/10 17:02:29)->Connecting: root\default, 10.10.10.13, w2k8-1\administrator
1:(09/09/10 17:02:32)->Deleting remote share...
1:(09/09/10 17:02:32)->Deleting entire folder: C:\BEW-2A86519253E84A4C95A7CFE56EAD71C7
1:(09/09/10 17:02:32)->Deleting entire folder by api: C:\BEW-2A86519253E84A4C95A7CFE56EAD71C7
1:(09/09/10 17:02:32)->Deleting folder files: C:\BEW-2A86519253E84A4C95A7CFE56EAD71C7
1:(09/09/10 17:02:32)->Getting sub folders: C:\BEW-2A86519253E84A4C95A7CFE56EAD71C7
1:(09/09/10 17:02:32)->Deleting folder: C:\BEW-2A86519253E84A4C95A7CFE56EAD71C7
1:(09/09/10 17:02:32)->Deleting remote share...
1:(09/09/10 17:02:33)->Connecting to remote WMI service: 10.10.10.13, w2k8-1\administrator
1:(09/09/10 17:02:33)->Connecting: root\cimv2, 10.10.10.13, w2k8-1\administrator
1:(09/09/10 17:02:33)->Connecting to remote registry: 10.10.10.13, w2k8-1\administrator
1:(09/09/10 17:02:33)->Connecting: root\default, 10.10.10.13, w2k8-1\administrator
1:(09/09/10 17:02:36)->Deleting remote share...
1:(09/09/10 17:02:36)->ERROR: Code(-1): cleaning push install: could not delete folder share
1:(09/09/10 17:02:36)->Deleting entire folder: C:\BEW-2A86519253E84A4C95A7CFE56EAD71C7
1:(09/09/10 17:02:36)->Deleting entire folder by api: C:\BEW-2A86519253E84A4C95A7CFE56EAD71C7
1:(09/09/10 17:02:36)->Deleting folder files: C:\BEW-2A86519253E84A4C95A7CFE56EAD71C7
1:(09/09/10 17:02:36)->ERROR: Code(-2147217406): executing query: ASSOCIATORS OF {Win32_Directory.Name='C:\BEW-2A86519253E84A4C95A7CFE56EAD71C7'} Where ResultClass = CIM_DataFile
1:(09/09/10 17:02:36)->Deleting entire folder by process: C:\BEW-2A86519253E84A4C95A7CFE56EAD71C7
1:(09/09/10 17:02:36)->Creating process: cmd.exe /c rmdir /S /Q C:\BEW-2A86519253E84A4C95A7CFE56EAD71C7
1:(09/09/10 17:02:36)->Push install cleaned.
1:(09/09/10 17:09:31)->Log Started: ID:1
1:(09/09/10 17:09:41)->Creating destination connection: 10.10.10.13, administrator
1:(09/09/10 17:09:41)->Connecting to remote WMI service: 10.10.10.13, w2k8-1\administrator
1:(09/09/10 17:09:41)->Connecting: root\cimv2, 10.10.10.13, w2k8-1\administrator
1:(09/09/10 17:09:43)->Connecting to remote registry: 10.10.10.13, w2k8-1\administrator
1:(09/09/10 17:09:43)->Connecting: root\default, 10.10.10.13, w2k8-1\administrator
1:(09/09/10 17:09:46)->Querying remote drives...
1:(09/09/10 17:09:46)->Creating remote install directory...
1:(09/09/10 17:09:46)->Creating folder: C:\BEW-C32567E04C154495928C44E361021868
1:(09/09/10 17:09:46)->Creating process: cmd.exe /c md C:\BEW-C32567E04C154495928C44E361021868
1:(09/09/10 17:09:48)->Creating share: BEW-C32567E04C154495928C44E361021868, C:\BEW-C32567E04C154495928C44E361021868, BEWPush Temporary Directory
1:(09/09/10 17:09:48)->Creating security descriptor...
1:(09/09/10 17:09:48)->Creating security DACL...
1:(09/09/10 17:09:48)->Establishing connection to network resource: \\10.10.10.13\BEW-C32567E04C154495928C44E361021868, w2k8-1\administrator
1:(09/09/10 17:10:09)->ERROR: Code(1203): Failed to establish connection: \\10.10.10.13\BEW-C32567E04C154495928C44E361021868, w2k8-1\administrator, 0

2:(09/09/10 16:18:17)->Log Started: ID:2
2:(09/09/10 16:18:24)->Creating destination connection: w2k8-1, administrator
2:(09/09/10 16:18:24)->Connecting to remote WMI service: w2k8-1, domain\administrator
2:(09/09/10 16:18:24)->Connecting: root\cimv2, w2k8-1, domain\administrator
2:(09/09/10 16:18:24)->Connecting to remote registry: w2k8-1, domain\administrator
2:(09/09/10 16:18:24)->Connecting: root\default, w2k8-1, domain\administrator
2:(09/09/10 16:18:27)->Querying remote drives...
2:(09/09/10 16:18:27)->Creating remote install directory...
2:(09/09/10 16:18:27)->Creating folder: C:\BEW-CC53EABDA80E4E9889AACD3158858D08
2:(09/09/10 16:18:27)->Creating process: cmd.exe /c md C:\BEW-CC53EABDA80E4E9889AACD3158858D08
2:(09/09/10 16:18:29)->Creating share: BEW-CC53EABDA80E4E9889AACD3158858D08, C:\BEW-CC53EABDA80E4E9889AACD3158858D08, BEWPush Temporary Directory
2:(09/09/10 16:18:29)->Creating security descriptor...
2:(09/09/10 16:18:29)->Creating security DACL...
2:(09/09/10 16:18:29)->Establishing connection to network resource: \\w2k8-1\BEW-CC53EABDA80E4E9889AACD3158858D08, domain\administrator
2:(09/09/10 16:18:50)->ERROR: Code(1203): Failed to establish connection: \\w2k8-1\BEW-CC53EABDA80E4E9889AACD3158858D08, domain\administrator, 0
2:(09/09/10 16:27:31)->Cleaning up push install...
2:(09/09/10 16:27:31)->Deleting registry key: -2147483646, SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Install\PushStatus
2:(09/09/10 16:27:31)->ERROR: Code(-2147417848): getting parameter object: StdRegProv, DeleteKey
2:(09/09/10 16:27:31)->Disconnecting from network resource: \\w2k8-1\BEW-CC53EABDA80E4E9889AACD3158858D08
2:(09/09/10 16:27:31)->Disconnected from network resource: \\w2k8-1\BEW-CC53EABDA80E4E9889AACD3158858D08
2:(09/09/10 16:27:31)->Deleting remote share...
2:(09/09/10 16:27:31)->Connecting to remote WMI service: w2k8-1, domain\administrator
2:(09/09/10 16:27:31)->Connecting: root\cimv2, w2k8-1, domain\administrator
2:(09/09/10 16:27:31)->Connecting to remote registry: w2k8-1, domain\administrator
2:(09/09/10 16:27:31)->Connecting: root\default, w2k8-1, domain\administrator
2:(09/09/10 16:27:34)->Deleting remote share...
2:(09/09/10 16:27:34)->Deleting entire folder: C:\BEW-CC53EABDA80E4E9889AACD3158858D08
2:(09/09/10 16:27:34)->Deleting entire folder by api: C:\BEW-CC53EABDA80E4E9889AACD3158858D08
2:(09/09/10 16:27:34)->Deleting folder files: C:\BEW-CC53EABDA80E4E9889AACD3158858D08
2:(09/09/10 16:27:34)->Getting sub folders: C:\BEW-CC53EABDA80E4E9889AACD3158858D08
2:(09/09/10 16:27:34)->Deleting folder: C:\BEW-CC53EABDA80E4E9889AACD3158858D08
2:(09/09/10 16:27:34)->Deleting remote share...
2:(09/09/10 16:27:34)->Connecting to remote WMI service: w2k8-1, domain\administrator
2:(09/09/10 16:27:34)->Connecting: root\cimv2, w2k8-1, domain\administrator
2:(09/09/10 16:27:34)->Connecting to remote registry: w2k8-1, domain\administrator
2:(09/09/10 16:27:34)->Connecting: root\default, w2k8-1, domain\administrator
2:(09/09/10 16:27:37)->Deleting remote share...
2:(09/09/10 16:27:37)->ERROR: Code(-1): cleaning push install: could not delete folder share
2:(09/09/10 16:27:37)->Deleting entire folder: C:\BEW-CC53EABDA80E4E9889AACD3158858D08
2:(09/09/10 16:27:37)->Deleting entire folder by api: C:\BEW-CC53EABDA80E4E9889AACD3158858D08
2:(09/09/10 16:27:37)->Deleting folder files: C:\BEW-CC53EABDA80E4E9889AACD3158858D08
2:(09/09/10 16:27:37)->ERROR: Code(-2147217406): executing query: ASSOCIATORS OF {Win32_Directory.Name='C:\BEW-CC53EABDA80E4E9889AACD3158858D08'} Where ResultClass = CIM_DataFile
2:(09/09/10 16:27:37)->Deleting entire folder by process: C:\BEW-CC53EABDA80E4E9889AACD3158858D08
2:(09/09/10 16:27:37)->Creating process: cmd.exe /c rmdir /S /Q C:\BEW-CC53EABDA80E4E9889AACD3158858D08
2:(09/09/10 16:27:38)->Push install cleaned.

 
1 ACCEPTED SOLUTION

Accepted Solutions

Ken_Putnam
Level 6
Have you applied the required HotFix or SP on the media server?

See  http://seer.entsupport.symantec.com/docs/331998.htm

Have you tried a local install on the problem machine?

See http://seer.entsupport.symantec.com/docs/265736.htm

View solution in original post

3 REPLIES 3

Ken_Putnam
Level 6
Have you applied the required HotFix or SP on the media server?

See  http://seer.entsupport.symantec.com/docs/331998.htm

Have you tried a local install on the problem machine?

See http://seer.entsupport.symantec.com/docs/265736.htm

Sush---
Level 6
Employee Accredited Certified
Try to perform the local install of Remote Agent on the Windows 2008 R2 machine. Also ensure that when you copy the RAWSx64 folder it has the UPDATES folder in it which should contain MSP  files of SP4.

Thanks,
-Sush...

jbroedel
Level 3

Have you applied the required HotFix or SP on the media server?

See  http://seer.entsupport.symantec.com/docs/331998.htm    DID NOT WORK

Have you tried a local install on the problem machine?

See http://seer.entsupport.symantec.com/docs/265736.htm     WORKED!!!

 

 

Nice to see SP4 doesnt fix this problem