02-12-2010 06:39 AM
02-19-2010 05:07 AM
02-21-2010 12:48 AM
02-26-2010 05:32 PM
03-01-2010 09:01 AM
03-08-2010 10:21 AM
03-08-2010 11:10 AM
03-08-2010 07:28 PM
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.
03-09-2010 05:49 AM
03-09-2010 05:50 AM
03-09-2010 06:16 PM
03-10-2010 07:52 AM
03-10-2010 08:29 AM
03-10-2010 09:03 AM
03-10-2010 01:45 PM
03-10-2010 01:45 PM
03-11-2010 06:35 AM
04-07-2010 05:46 AM
04-07-2010 06:56 PM
04-09-2010 09:05 AM
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
5c16dc267700d7ca65e1ffab4e2a026b bedsnt5.dll.1d19b2a0_aada_4f00_8d43_2857259b087aOf course it still crashed. Any more ideas? I'm lost here and a per-incident costs $250USD. Thanks! Matt