Data Backup and Recovery Discussions

Possible Bug with SME 5.0 Frequent Recovery Point Backup

I'm trying to understand why Frequent Recovery Point backups (in SnapManager 5.0 for Exchange) throw a .NET exception. I can consistently reproduce this error. Everything else works great !!

First, here's a high-level overview of my environment:

- Windows Server 2003 SP2 w/ all current hotfixes

- Exchange Server 2007 SP1 w/ all current rollups

- Microsoft .NET Framework 3.5

- NetApp SnapDrive 6.0

- NetApp SnapManager 5.0 for Microsoft Exchange

Now, here's that .NET exception (after right-clicking on the Exchange host within SME and selecting "Frequent Recovery Point Backup") :


Unhandled Exception in Managed Code Snap-in



Exception has been thrown by the target of an invocation.

Exception type:


Exception stack trace:

at Microsoft.ManagementConsole.Internal.SnapInMessagePumpProxy.OnThreadException(Object sender, ThreadExceptionEventArgs e)

at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)

at System.Windows.Forms.Control.WndProcException(Exception e)

at System.Windows.Forms.Control.ControlNativeWindow.OnThreadException(Exception e)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

at System.Windows.Forms.SafeNativeMethods.ShowWindow(HandleRef hWnd, Int32 nCmdShow)

at System.Windows.Forms.Control.SetVisibleCore(Boolean value)

at System.Windows.Forms.Form.SetVisibleCore(Boolean value)

at System.Windows.Forms.Control.Show()

at SMEUISnapin.SMEExchNode.FRPBackup_handler(Object sender, ActionEventArgs e)

at Microsoft.ManagementConsole.Action.RaiseTriggeredEvent(Object sender, AsyncStatus status)

at Microsoft.ManagementConsole.ScopeNode.DoAction(Int32 actionId, IRequestStatus requestStatus)

at Microsoft.ManagementConsole.NodeSyncManager.ProcessRequest(NodeRequestInfo info, IRequestStatus requestStatus)

at Microsoft.ManagementConsole.NamespaceSnapInBase.ProcessRequest(Request request)

at Microsoft.ManagementConsole.SnapIn.ProcessRequest(Request request)

at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)

at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)

at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)

at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:

at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request)

at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo)

at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest()

at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)

Any thoughts?

Brian Mitchell | Senior Systems Engineer | Arrow Electronics

m: (770) 298-1171 | 1725 Windward Concourse Alpharetta, GA 30005 | |


Re: Possible Bug with SME 5.0 Frequent Recovery Point Backup

Hello Brian,

I have a lab which identically matches that configuration and was able to replicate the problem.

That said, I've filed a BURT regarding this issue, and I will be personally following this to see what it takes to get it resolved (be it setting or bug fix)

Thank you for your attention to the matter and verbose environmental details in order to replicate it.

Christopher Kusek

Re: Possible Bug with SME 5.0 Frequent Recovery Point Backup

Stupid question here:

did it work before?

I may have had a similar issue. I think I re-installed powershell, and whala, it started working.

Cloud Volumes ONTAP
Review Banner
All Community Forums