I am trying to get the backup exec agent installed and working on a domain controller to back it up with Backup Exec 2010 R3 SP4. The Media server (we will call it Server1) and the remote server (we will call it Server2) are both running Windows Server 2008 R2 Standard and they both happen to be AD domain controllers. Server2 used to be a Backup Exec 2010 R3 media server, but I have uninstalled the software (using Control Panel > Uninstall a Program). After uninstalling it, I pushed the RAWS agent from Server1 to Server2 using the server name (we will say that is Server2.DOMAIN.COM). The install is successful and the service is running. On Server1, the new Server2 entry shows up in my selection list under favorites, but any interaction with it will lock up the Backup Exec program no matter how long I wait. After 15 seconds or so, an error is generated in Server1's Event Log under Application. The Error is: Event ID 1002 "Application Hang" -
The program BkupExec.exe version 13.0.5204.1270 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 1418
Start Time: 01cffdc6d2e9bdc3
Termination Time: 6
Application Path: D:\ProgramFiles\BackupExec\BkupExec.exe
Report Id: 93364944-69ba-11e4-be7f-f01fafe1ccadThis error is generated every time I try to expand Server2 in the selection list.
Things I have already checked:
I have already checked for the trusted relationship entry in Server2's Agent Utility. It is present and appears correct.
I have also turned off the firewalls on both servers to rule those out. Both servers are on the same subnet, same switch even. Server1's IP is 192.168.1.52, Server2's IP is 192.168.1.51.
I also verified DNS is resolving correctly between the servers. I even put the IP of Server2 in Server1's HOSTS file to be sure.
I did reboot the servers after uninstalling BE2010 on Server2 as well as another reboot after installing the RAWS agent.
After some research, it seems useful to have SGMON output to see where the breakdown in communication is. Here is the output I get from the Media Server, with all boxes checked in SGMON. The capture starts just before I click to expand Server2's selection list entry.
***************************************************************************
***** SGMon log for \\\\Server1 *****
***** Local Offset =05:00 *****
***************************************************************************
BEREMOTE: [11/11/14 10:49:56] [7712] [fsys\shared] - FS_ResolveDevName: [\\Server2.DOMAIN.COM]
BEREMOTE: [11/11/14 10:49:56] [7712] [fsys\mb2] - MB2-Resolve returned 1
BEREMOTE: [11/11/14 10:49:56] [7712] [fsys\notes2] - Notes Agent:CLNFileSystem::ResolveDeviceName
BEREMOTE: [11/11/14 10:49:56] [7712] [fsys\adc] - ADC_ResolveDeviceName: pid = 6240, checking \\Server2.DOMAIN.COM
BEREMOTE: [11/11/14 10:49:56] [7712] [beutil] - ApplyRegExp(): Invalid input (\\Server2.DOMAIN.COM). Parsing Failed.
BEREMOTE: [11/11/14 10:49:56] [7712] [beutil] - GoodEvName(): Invalid EV device (\\Server2.DOMAIN.COM).
BEREMOTE: [11/11/14 10:49:56] [7712] [beutil] - ApplyRegExp(): Invalid input (\\Server2.DOMAIN.COM). Parsing Failed.
BEREMOTE: [11/11/14 10:49:56] [7712] [beutil] - GoodEvName(): Invalid EV device (\\Server2.DOMAIN.COM).
BEREMOTE: [11/11/14 10:49:56] [7712] [beutil] - Input Error (e000fe23) for Type: (43)
BEREMOTE: [11/11/14 10:49:56] [7712] [fsys\ev] - EVM_ResolveDeviceName: Function Enter
BEREMOTE: [11/11/14 10:49:56] [7712] [beutil] - ApplyRegExp(): Invalid input (\\Server2.DOMAIN.COM). Parsing Failed.
BEREMOTE: [11/11/14 10:49:56] [7712] [fsys\ev] - EVM_ResolveDeviceName: Invalid device name (\\Server2.DOMAIN.COM). Parsing Failed.
BEREMOTE: [11/11/14 10:49:56] [7712] [fsys\ev] - EVM_ResolveDeviceName: Function Exit
BEREMOTE: [11/11/14 10:49:56] [7712] [fsys\ntfs] - Not valid device name : \\Server2.DOMAIN.COM
BEREMOTE: [11/11/14 10:49:56] [7712] [dsss\rpc] - RPCDsSession::GetLoginCredentials: Connecting to BEM API as user: DOMAIN\administrator
BESERVER: [11/11/14 10:49:56] [3928] -1 Client requested key (1415721161).
BESERVER: [11/11/14 10:49:56] [3928] "Cluster" key does not appear to be present in the registry
BESERVER: [11/11/14 10:49:56] [3928] Failed to open Microsoft cluster ()
BESERVER: [11/11/14 10:49:56] [3928] VCS cluster keys do not appear to be present in the registry
BESERVER: [11/11/14 10:49:56] [3928] Failed to open VCS cluster ()
BESERVER: [11/11/14 10:49:56] [3928] 01 Server Configuration: Client added: 9
BESERVER: [11/11/14 10:49:56] [3928] -1 Client 'Server1' connected('','DOMAIN\administrator'): 0xd844570
BESERVER: [11/11/14 10:49:56] [3928] 01 Server Configuration: Client removed: 8
BESERVER: [11/11/14 10:49:56] [3928] -1 Client 'Server1' Disconnected:0xd844570
BEREMOTE: [11/11/14 10:49:56] [7712] [ndmp\ndmpcomm] - Could not resolve the "bews-ndmp" or the "ndmp" service, error code: 10109, using port 10000
BEREMOTE: [11/11/14 10:49:56] [7712] "Cluster" key does not appear to be present in the registry
BEREMOTE: [11/11/14 10:49:56] [7712] Failed to open Microsoft cluster ()
BEREMOTE: [11/11/14 10:49:56] [7712] VCS cluster keys do not appear to be present in the registry
BEREMOTE: [11/11/14 10:49:56] [7712] Failed to open VCS cluster ()
BEREMOTE: [11/11/14 10:49:56] [7712] [ndmp\ndmpcomm] - ndmpConnectEx: Querying the neighbour advertisement cache to discover information on 'Server2.DOMAIN.COM' ...
BENETNS: [11/11/14 10:49:56] [2148] NRDS API - client connected.
BENETNS: [11/11/14 10:49:56] [2148] Connecting to BE Database.
BESERVER: [11/11/14 10:49:56] [3928] -1 Client requested key (1415721161).
BESERVER: [11/11/14 10:49:56] [3928] 01 Server Configuration: Client added: 9
BESERVER: [11/11/14 10:49:56] [3928] -1 Client 'Server1' connected('','DOMAIN\BackupAdmin'): 0xd844570
BENETNS: [11/11/14 10:49:56] [2148] Successfully connected to BE Database.
BENETNS: [11/11/14 10:49:56] [2148] Reading agent database record for Server2.DOMAIN.COM.
BENETNS: [11/11/14 10:49:56] [2148] Found agent record 2 for Server2.DOMAIN.COM.
BESERVER: [11/11/14 10:49:56] [3928] 01 Server Configuration: Client removed: 8
BESERVER: [11/11/14 10:49:56] [3928] -1 Client 'Server1' Disconnected:0xd844570
BENETNS: [11/11/14 10:49:56] [2148] Disconnected from BE Database.
BENETNS: [11/11/14 10:49:56] [2148] NRDS API - client disconnected.
BEREMOTE: [11/11/14 10:49:56] [7712] [ndmp\ndmpcomm] - ndmpConnectEx : Control Connection information: A connection was established between end-points 192.168.1.52:50229 and 192.168.1.51:10000.
BEREMOTE: [11/11/14 10:51:02] [6544] [ndmp\ndmpsrvr] - Freeing unsued COM libraries
I have worked with Backup Exec alot and have never had this problem, even when dealing with these Server OS's and having BE2010 previously installed on a machine I want the agent setup on.