SnapManager 7 & Exchange 2013 erroring on backups

CR — Thu, 05 Jun 2025 05:27:05 GMT

We have a Server 2008 R2 virtual machine with Exchange 2013 CAS with SnapManager 7 running twice a day as a scheduled task to activated the back up.

The issue we have is out of 14 back ups running in a week, at least 3 or 4 of them wont backup and send the email because SnapMgrService.exe crashes. Normally the SnapManagerService has stopped so a restart of that and then starting the schedule task aagin will then get the backup working, but obviosuly this isnt ideal. There seems to be no patern to when it will fail, sometimes its the early morning backup some times its the lunch time backup.

We do get the below errors come up in the event application log regarding SnapMgrService.exe, i was just wondering if anyone else has had this issue and has fixed it?

Log Name:      Application
Source:        MSExchange Common
Event ID:      4999
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Description:
Watson report about to be sent for process id: 604, with parameters: E12N, c-rtl-AMD64, 15.00.0847.032, SnapMgrService.exe, KERNELBASE.dll, 940d, c0f00000, dfb4, 6.1.7601.18015 (win7sp1_gdr.121129-1432).
ErrorReportingEnabled: True
%14

Log Name:      Application
Source:        Application Error
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Description:
Faulting application name: SnapMgrService.exe, version: 7.0.0.1331, time stamp: 0x52381d10
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x5315a05a
Exception code: 0xc0f00000
Fault offset: 0x000000000000940d
Faulting process id: 0x25c
Faulting application start time: 0x01cfea03d31f1fb3
Faulting application path: D:\Program Files\NetApp\SnapManager for Exchange\SnapMgrService.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 402f809f-5789-11e4-bed8-005056847e14

Thanks

Re: SnapManager 7 & Exchange 2013 erroring on backups

vienna1220 — Thu, 04 Dec 2014 10:25:16 GMT

We got the same problem on Windows Server 2012 R2 with Exchange 2013 SP1 CU6, Snapdrive 7.1 and SME 7.0. I tried SME 7.1 before but this didn't work at all (could not even list the LUNs in the backup configuration wizard)...

NetApp FAS2240-2, 7-mode, OnTAP 8.1.4P1

Setup:

1 volume containing 4 LUNs (1x Logs and 3x Mailbox store). Snapinfo dir is on the Logs LUN.

3 errors in the application event log during the verification of the log files for the second exchange store. The snapshot on the volume is present, all preceding tasks finished successful. The backup is not listed in the "Restore" menu in SME.

ERROR 1:

Watson report about to be sent for process id: 2256, with parameters: E12N, c-rtl-AMD64, 15.00.0995.029, SnapMgrService.exe, KERNELBASE.dll, 606c, c0f00000, ad56, 6.3.9600.17031 (winblue_gdr.140221-1952).
ErrorReportingEnabled: False
%14

ERROR 2:

Application: SnapMgrService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0f00000, exception address 00007FFA10B8606C
Stack:
at <Module>.CSmeCheckSgVerifyJob.Execute(CSmeCheckSgVerifyJob*)
at <Module>.CSmeCheckSgVerify.VerifySgDatabases(CSmeCheckSgVerify*, UInt16**, UInt32, UInt16*, UInt16*, UInt32, UInt32)
at <Module>.CSmeEseVerify.CheckLogExec(CSmeEseVerify*, UInt16*, UInt16*, UInt16*, Int32, UInt16*)
at <Module>.CSmeEseVerify.LogConsistentCheck(CSmeEseVerify*, _ESEFILE_SG_INFO*, _ESEFILE_SNAPSHOT_INFO*, UInt16*, Int32, UInt16**, Int32, Int32)
at <Module>.CSmeEseVerify.RunEsefileWithSnapshotStruct(CSmeEseVerify*, _ESEFILE_SG_INFO*, _ESEFILE_SNAPSHOT_INFO*, UInt16*, Int32*, Int32, Int32, UInt16**, Int32, Int32, UInt32, Int32)
at <Module>.CSmeEseVerify.RemoteEsefileSnapShotInternal(CSmeEseVerify*, _ESEFILE_SG_INFO**, Int32, Int32*, Int32, UInt16**, Int32, Int32)
at <Module>.CSmeEseVerify.RunEsefile2(CSmeEseVerify*, UInt16*, _ESEFILE_SG_INFO**, Int32, UInt16**, INtapSnapMgr**, Int32, UInt16*, Int32, Int32, Int32)
at <Module>.CSmeEseVerify.BackupLogConsistentCheck(CSmeEseVerify*, _SME_BACKUP_INFO*, _ESEFILE_SG_INFO**, _SME_BACKUP_RESULT*, Int32*, Int32, Int32*)
at <Module>.CVSSExchBackup.DoSingleVSSBackup(CVSSExchBackup*, _SME_BACKUP_INFO*, UInt16**, Int32*, std.list<int,std::allocator<int> >*, UInt16*, UInt16*, Int32*, std.list<int,std::allocator<int> >*, _ESEFILE_SG_INFO**, Int32*, _SME_EXCHANGE_INFO*, UInt32*, UInt32, Int32*, Int32*, _SME_VLD_LIST*, Int32*, UInt64*, Int32, _SME_BACKUP_ALL_RESULTS*, SmSDBroker.BackupDataSetIn)
at <Module>.CVSSExchBackup.DoSmeVSSBackup(CVSSExchBackup*, _SME_BACKUP_INFO*, UInt16**, Int32*, std.list<int,std::allocator<int> >*, UInt16*, UInt16*, Int32*, std.list<int,std::allocator<int> >*, _ESEFILE_SG_INFO**, _SME_EXCHANGE_INFO*, UInt32*, Int32*, Int32*, _SME_VLD_LIST*, Int32*, _SME_BACKUP_RESULT*, Int32, _SME_BACKUP_ALL_RESULTS*, SmSDBroker.BackupDataSetIn)
at <Module>.CSmeBackup.DoVSSBasedBackup(CSmeBackup*, _SME_BACKUP_INFO*, _SME_BACKUP_RESULT**, SME_CO_BACKUPS*, _SME_EXCHANGE_INFO*, _SME_VLD_LIST**, SmSDBroker.BackupDataSetIn, Int32, UInt16*, _SME_BACKUP_RESULT**)
at <Module>.CSmeBackup.SmeBackup2SingleGroup(CSmeBackup*, _SME_BACKUP_INFO*, _SME_BACKUP_RESULT**, SME_CO_BACKUPS*, _SME_EXCHANGE_INFO*, _SME_VLD_LIST**, SmSDBroker.BackupDataSetIn, UInt16*, _SME_BACKUP_RESULT**)
at <Module>.CSmeBackup.SmeBackup3Internal(CSmeBackup*, _SME_BACKUP_INFO*, _SME_EXCHANGE_INFO*, _SME_BACKUP_ALL_RESULTS**, Int32)
at <Module>.CSmeBackup.SmeBackup4Internal(CSmeBackup*, _SME_BACKUP_INFO*, _SME_EXCHANGE_INFO*, _SME_BACKUP_ALL_RESULTS**)
at <Module>.CNtapSnapMgr.SmeBackup4(CNtapSnapMgr*, _SME_BACKUP_INFO*, _SME_EXCHANGE_INFO*, _SME_BACKUP_ALL_RESULTS**)
at <Module>.CNtapSnapMgr.SmeBackup4(CNtapSnapMgr*, _SME_BACKUP_INFO*, _SME_EXCHANGE_INFO*, _SME_BACKUP_ALL_RESULTS**)
at <Module>.CNtapSnapMgr.SmeBackup4(CNtapSnapMgr*, _SME_BACKUP_INFO*, _SME_EXCHANGE_INFO*, _SME_BACKUP_ALL_RESULTS**)
at NetApp.SnapManager.SMEServices.SMEService.BackupWithGroups(NetApp.SnapManager.SMEServices.SmeBackupInfo, NetApp.SnapManager.SMEServices.SmeExchangeInfo, NetApp.SnapManager.SMEServices.SmeBackupAllResults ByRef)
at DynamicClass.SyncInvokeBackupWithGroups(System.Object, System.Object[], System.Object[])
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(System.Object, System.Object[], System.Object[] ByRef)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(System.ServiceModel.Dispatcher.MessageRpc ByRef)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(System.ServiceModel.Dispatcher.MessageRpc ByRef)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(System.ServiceModel.Dispatcher.MessageRpc ByRef)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean)
at System.ServiceModel.Dispatcher.ChannelHandler.DispatchAndReleasePump(System.ServiceModel.Channels.RequestContext, Boolean, System.ServiceModel.OperationContext)
at System.ServiceModel.Dispatcher.ChannelHandler.HandleRequest(System.ServiceModel.Channels.RequestContext, System.ServiceModel.OperationContext)
at System.ServiceModel.Dispatcher.ChannelHandler.AsyncMessagePump(System.IAsyncResult)
at System.Runtime.Fx+AsyncThunk.UnhandledExceptionFrame(System.IAsyncResult)
at System.Runtime.AsyncResult.Complete(Boolean)
at System.ServiceModel.Channels.TransportDuplexSessionChannel+TryReceiveAsyncResult.OnReceive(System.IAsyncResult)
at System.Runtime.Fx+AsyncThunk.UnhandledExceptionFrame(System.IAsyncResult)
at System.Runtime.AsyncResult.Complete(Boolean)
at System.ServiceModel.Channels.SynchronizedMessageSource+ReceiveAsyncResult.OnReceiveComplete(System.Object)
at System.ServiceModel.Channels.SessionConnectionReader.OnAsyncReadComplete(System.Object)
at System.Runtime.Fx+AsyncThunk.UnhandledExceptionFrame(System.IAsyncResult)
at System.Net.LazyAsyncResult.Complete(IntPtr)
at System.Net.Security.NegotiateStream.ProcessFrameBody(Int32, Byte[], Int32, Int32, System.Net.AsyncProtocolRequest)
at System.Net.Security.NegotiateStream.ReadCallback(System.Net.AsyncProtocolRequest)
at System.Net.FixedSizeReader.CheckCompletionBeforeNextRead(Int32)
at System.Net.FixedSizeReader.ReadCallback(System.IAsyncResult)
at System.Runtime.AsyncResult.Complete(Boolean)
at System.ServiceModel.Channels.ConnectionStream+IOAsyncResult.OnAsyncIOComplete(System.Object)
at System.ServiceModel.Channels.SocketConnection.OnReceiveAsync(System.Object, System.Net.Sockets.SocketAsyncEventArgs)
at System.Net.Sockets.SocketAsyncEventArgs.FinishOperationSuccess(System.Net.Sockets.SocketError, Int32, System.Net.Sockets.SocketFlags)
at System.Net.Sockets.SocketAsyncEventArgs.CompletionPortCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)
at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32, UInt32, System.Threading.NativeOverlapped*)

ERROR 3:

Faulting application name: SnapMgrService.exe, version: 7.0.0.1331, time stamp: 0x52381d10
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17278, time stamp: 0x53eebf2e
Exception code: 0xc0f00000
Fault offset: 0x000000000000606c
Faulting process id: 0x8d0
Faulting application start time: 0x01d00f17c60d1285
Faulting application path: C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrService.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 8d934bd4-7b2f-11e4-80d0-005056b53a98
Faulting package full name:
Faulting package-relative application ID:

Re: SnapManager 7 & Exchange 2013 erroring on backups

jmmorrell — Wed, 07 Jan 2015 20:18:20 GMT

I am also seeing this result in a very similar environment. Has there been any fix? I am about to open a case with NetApp support. We are running the following versions of software. Some backups complete and some backups fail randomly.

cDOT 8.2.2P2

SnapDrive 7.0.3

SME 7.0.0.1331

Server 2012 R2

Exchange 2013 SP1 CU6

Regards,

Jim

Re: SnapManager 7 & Exchange 2013 erroring on backups

georgevj — Thu, 08 Jan 2015 05:50:12 GMT

This is because of BUG id 825515. http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=825515

SnapManager for Exchange 6.1D1 as well as 7.1 contains a fix for this issue.

Re: SnapManager 7 & Exchange 2013 erroring on backups

CR — Thu, 08 Jan 2015 09:03:41 GMT

We are running 7.1 though so 6.1D1 is older.

So if there is a fix for 6 why does 7.1 have a problem?

topic Re: SnapManager 7 & Exchange 2013 erroring on backups in Data Protection

SnapManager 7 & Exchange 2013 erroring on backups

Re: SnapManager 7 & Exchange 2013 erroring on backups

Re: SnapManager 7 & Exchange 2013 erroring on backups

Re: SnapManager 7 & Exchange 2013 erroring on backups

Re: SnapManager 7 & Exchange 2013 erroring on backups