cancel
Showing results for 
Search instead for 
Did you mean: 

[11d] Backing up with remote agent from Windows Storage Server 2003

mbrowndcm
Level 4
Hello,

I am getting repeated crashes of beremote.exe when attempting to backup a remote Windows Storage Server 2003.


Is this a known issue?


Thanks,

Matt
19 REPLIES 19

mbrowndcm
Level 4
Does anyone have any experience with this situation?

Any input is sincerely appreciated.

puterijawa
Level 3
Can you paste the error log, here?

Carls
Level 4
 Hi Matt,

Have you installed the latest service pack for BE11d?

http://seer.entsupport.symantec.com/docs/288171.htm

Carl

Ken_Putnam
Level 6
In addtion to being on the latest Service Pack, have you tried uninstalling the Remote Agent, booting and re-installing the Remote Agent on that computer?

mbrowndcm
Level 4
 I am on Service Pack 5.  I just ran LiveUpdate to see if there were any more updates.  I am completely up to date.

I have deployed the client after the update.

mbrowndcm
Level 4
 I have performed the uninstall, then restarted (twice, for fun), then re-installed.  The same error as listed above occurred.


Does anyone have any further ideas as to what to do to solve the issue?

Note that Storage Server 2003 is x64 (the RAWSX64 remote agent installer works).


Thanks,

Matt

pkh
Moderator
Moderator
   VIP    Certified

After the failure, did you check whether the BE remote agent service is still running on the remote Storage Server?  If it has crashed for some reason, restart it.

You might also want to change the recovery properties of the BE remote agent service to Restart the Service in the First Failure drop-down box.

mbrowndcm
Level 4
Here is the error information:


 Job ended: Monday, March 08, 2010 at 12:14:20 PM Completed status: Failed Final error: 0xe000848c - Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-33932




Backup- STORAGESERVER.DOMAIN.SUFFIX
Unable to attach to \\STORAGESERVER.DOMAIN.SUFFIX\test_backup.
V-79-57344-33932 - Unable to attach to a resource.  Make sure that all selected resources exist and are online, and then try again.
V-79-57344-65072 - The connection to target system has been lost. Backup set canceled.

Monitoring the backup exec remote agent reveals the process crashes when the job starts with the following in the Windows Event Log:

 



Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 3/8/2010
Time: 12:14:18 PM
User: N/A
Computer: STORAGESERVER.DOMAIN.SUFFIX
Description:
Faulting application beremote.exe, version 11.0.7170.32, faulting module bedsnt5.dll, version 11.0.7170.0, fault address 0x0000000000063ac1.



I feel like I'm kind of stuck without a non-"faulty" version of bedsnt5.dll

mbrowndcm
Level 4
 Yes it crashes.  Yes, it crashes repeatedly.


Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 3/8/2010
Time: 12:14:18 PM
User: N/A
Computer: STORAGESERVER.DOMAIN.SUFFIX
Description:
Faulting application beremote.exe, version 11.0.7170.32, faulting module bedsnt5.dll, version 11.0.7170.0, fault address 0x0000000000063ac1.

pkh
Moderator
Moderator
   VIP    Certified
Try this and see if it solves your problem

http://seer.entsupport.symantec.com/docs/278033.htm

mbrowndcm
Level 4
I will take a look into this (WMI) being the cause of the problem.

Here is some info in case other people come across the same or a similar issue on WMI:


Backing up WMI repo: http://msdn.microsoft.com/en-us/library/aa394525(VS.85).aspx
winmgmt /backup c:\wmibackup.bak
Connectivity: Use wbemtest.exe to investigate connectivity issues.
Basic Testing: http://blogs.technet.com/askperf/archive/2007/06/22/basic-wmi-testing.aspx
(more info on wmitest.vbs: http://blogs.technet.com/askperf/archive/2008/11/11/wmidiag-vbs-and-the-missing-wmi-files.aspx)

I'll post another reply with what I find (and mark if it solves the problem).


Thanks,

Matt

Dev_T
Level 6
Hello,

Is the Backup Exec account the member of the Local Admin Group on the remote server?

mbrowndcm
Level 4
The remote agent service (beremote.exe) is running as the NT AUTHORITY\SYSTEM user ("Local System" account).  beremote.exe is using the Local System account on a x86 machine without issue.

The user for which the backup job is running (network credentials) was/is a local administrator on the machine.

mbrowndcm
Level 4

mbrowndcm
Level 4
  There are no issues with the WMI repo.


Any other ideas?


Thanks for your input!

Matt

mbrowndcm
Level 4
It appears that the server only has one remote agent license. which is used by another server.

Would the job be failing with the above error if this is the case?


Thanks,

Matt

mbrowndcm
Level 4
Hello All,

We have now obtained a license and installed.

The problem is persistent:

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 4/5/2010
Time: 2:46:27 PM
User: N/A
Computer: STORAGESERVER
Description:
Faulting application beremote.exe, version 11.0.7170.32, faulting module bedsnt5.dll, version 11.0.7170.0, fault address 0x0000000000063ac1.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 62 65 72   ure  ber
0018: 65 6d 6f 74 65 2e 65 78   emote.ex
0020: 65 20 31 31 2e 30 2e 37   e 11.0.7
0028: 31 37 30 2e 33 32 20 69   170.32 i
0030: 6e 20 62 65 64 73 6e 74   n bedsnt
0038: 35 2e 64 6c 6c 20 31 31   5.dll 11
0040: 2e 30 2e 37 31 37 30 2e   .0.7170.
0048: 30 20 61 74 20 6f 66 66   0 at off
0050: 73 65 74 20 30 30 30 30   set 0000
0058: 30 30 30 30 30 30 30 36   00000006
0060: 33 61 63 31               3ac1    
 


Any further input is appreciated.


Thanks,

Matt

pkh
Moderator
Moderator
   VIP    Certified
After you installed the additional remote agent license, did you push our the remote agent again to the remote server?

mbrowndcm
Level 4

I have tried this.  Same issue exists.

Just to verify, I have compared the checksum of bedsnt5.dll on the X64 (crashing) system, with the bedsnt5.dll.

501779138bb547762523e544bebae44a bedsnt5.dll (on Windows Storage Server 2003 [which is x64])
aab1fd7b5e092491c16886eddf21f87d bedsnt5.dll (on Windows Server 2003 Standard [which is x86])

Good.

File version?

--a-- WAMD64 DLL ENU     11.0.7170.0 shp  1,108,560 03-07-2007 bedsnt5.dll  (on Windows Storage Server 2003 [which is x64])
----- W32i   DLL ENU     11.0.7170.0 shp    730,192 03-07-2007 bedsnt5.dll (on Windows Server 2003 Standard [which is x86])

Good... maybe. We are using a Intel Xeon process, not an AMD.

Checksum of  bedsnt5.dll.6B4548BF_CDF9_4A68_8BEB_70279BD089DF from data1.cab of the RAWSX64 installer?

501779138bb547762523e544bebae44a bedsnt5.dll.6b4548bf_cdf9_4a68_8beb_70279bd089df

Good.

Any ideas?

Thanks,

Matt



Getting creative... I also tried to simply copy the bedsnt5.dll file out
checksum of Itanium 64 compiled  bedsnt5.dll:
5c16dc267700d7ca65e1ffab4e2a026b bedsnt5.dll.1d19b2a0_aada_4f00_8d43_2857259b087a
Of course it still crashed. Any more ideas? I'm lost here and a per-incident costs $250USD. Thanks! Matt