Beremote keeps crashing on 11D 7170 with Application Error (msdatl3.dll)

[Edward_Cetron]

I had been running 11d 6235 with no problems for months on a SBS 2003 box.  About a week ago, beremote started crashing anytime BE started a backup.  The event viewer error (and the pop-up on the console -- which if remote is quite a pain) was:

Event Type:      Information
Event Source:   Application Popup
Event Category:            None
Event ID:          26
Date:                7/17/2007
Time:                11:48:31 PM
User:                N/A
Computer:         SERVER2
Description:

Application popup: beremote.exe - Application Error : The instruction at "0x6120f6f1" referenced memory at "0x00000010". The memory could not be "read".

Click on OK to terminate the program
Click on CANCEL to debug the program

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

So I searched the threads at the knowledge base and the general response to similar support requests was to "upgrade to 7170".  Ok, fair enough.

Now I've upgraded.  And in the process the "Job Migration" step failed, so I've lost all my jobs and job history.  But I can live with that if only I could do backups....

The 7170.6 version of beremote does the exact same thing, but it has better debugging since not only do I get the pop-up on the console, and the event log entry, I also get this entry:

Event Type:      Error
Event Source:   Application Error
Event Category:            (100)
Event ID:          1000
Date:                7/17/2007
Time:                11:48:31 PM
User:                N/A
Computer:         SERVER2
Description:
Faulting application beremote.exe, version 11.0.7170.6, faulting module msdatl3.dll, version 2.82.3959.0, fault address 0x0000f6f1.

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 36 20 69 6e   170.6 in
0030: 20 6d 73 64 61 74 6c 33    msdatl3
0038: 2e 64 6c 6c 20 32 2e 38   .dll 2.8
0040: 32 2e 33 39 35 39 2e 30   2.3959.0
0048: 20 61 74 20 6f 66 66 73    at offs
0050: 65 74 20 30 30 30 30 66   et 0000f
0058: 36 66 31                  6f1 

Finally some debugging information.  but it still tells me nothing.  Since I have no jobs to run, it doesn't happen when a job starts, but it DOES happen as soon as I try to select a SQL Server database in the "backup selections" screen. 

Since the single most critical piece of this SBS server is the SQL Server database, we are in pretty bad shape right now.... Any help or suggestions will be greatly appreciated.  (BTW, I have disabled encryption as well)

-ed cetron

ecetron@tili.com

[harmstrong]

Hi Edward,

You can try installing win debug to try to get more information on the crash .

Install DebugDiag v1.1  http://www.microsoft.com/downloads/details.aspx?FamilyID=28BD5941-C458-46F1-B24D-F60151D875A3&displa...

  Run DebugDiag ("Start | Programs | Debug Diagnostics Tools 1.1 | DebugDiag 1.1"

 Select "Crash" and "Next"

 Select "A specific process" and "Next"

  In Selected Process type     BEREMOTE.EXE    and select "Next"

 Select "Full User Dump" in "Action type for unconfigured first chance exceptions" and select "Next"

  You can change the name of the rule and/or where the userdump file will be located, and select "Next"

  Make sure "Activate the rule now" is selected, and select "Finish".

Have you try running a repair on BE 11 7170 , ensure you are selecting the SQL only via the SQL Agent icon on the backup selections.  You may need to open a case to obtain further debugs.

Regards,

Harmstrong

Symantec

[Edward_Cetron]

Repair -- it is a brand-new fresh install.  And I tried it before any hotfixes and between each one.  This installation has hotfix 1, 3, 4,6,7,8,9, and 10.  Definately clicking on the Sql Agent Icon -- indeed that is what causes beremote to crash.  I have a bunch of crash dump files know... where do I send them?

-ed cetron

ecetron@tili.com