BE 12.0 setup e-mail notification immediately creates "systemaccessviolationexception"
Updated: 21 May 2010 | 2 comments
Trying to configure e-mail notifications for BE 12.0 1364 (Windows server 2003 R2 x64). Selecting "E-mail & Pager Notification" from the "Tools" option immediately causes "systemaccessviolationexception" (see attached) and B.E. to close. All available (per Symatec tools) hotfixes have been applied (300287 and 300290).
A severe application error has occurred.
Exception: System.AccessViolationException
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack Trace: at BackupExec.UI.BEDlgs.ConfigureEmailAndPagerNotification()
at BackupExec.UI.MainForm.a6(Command A_0)
at BackupExec.UIFramework.CommandManager.a(Object A_0, EventArgs A_1)
at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at BackupExec.UI.MainForm.a(String[] A_0)
at BackupExec.UI.MainForm.b(String[] A_0)
at BackupExec.UI.MainForm.a6(Command A_0)
at BackupExec.UIFramework.CommandManager.a(Object A_0, EventArgs A_1)
at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at BackupExec.UI.MainForm.a(String[] A_0)
at BackupExec.UI.MainForm.b(String[] A_0)
New installation / high priority
Discussion Filed Under:
Comments
Would you like to reply?
Login or Register to post your comment.