The process was terminated due to an unhandled exception

We are receiving the below error when accessing the SQLdmManagementService . i tried to restart the service twice but not worked.


Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: SQLdmDesktopClient.exe
P3: 59314dc6
P4: ba70
P5: 134217984

Attached files:

These files may be available here:

Analysis symbol:
Rechecking for solution: 0
Report Id: 6c00520f-38c6-11e9-80da-0050569e67af
Report Status: 2048

Faulting application name: SQLdmManagementService.exe, version:, time stamp: 0x59566ec8
Faulting module name: unknown, version:, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ffe2aba9ab9
Faulting process id: 0x984
Faulting application start time: 0x01d4ccd27fc18a6e
Faulting application path: C:\Program Files\Idera\Idera SQL diagnostic manager\SQLdmManagementService.exe
Faulting module path: unknown
Report Id: 0c3ec044-38c6-11e9-80da-0050569e67af
Faulting package full name:
Faulting package-relative application ID:

Application: SQLdmManagementService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at Idera.SQLdm.ManagementService.Notification.NotificationManager.Process(System.Collections.Generic.IList`1<Idera.SQLdm.Common.Events.IEvent>, Idera.SQLdm.Common.Snapshots.AlertableSnapshot)
at Idera.SQLdm.ManagementService.Notification.NotificationManager.Process(Idera.SQLdm.Common.Snapshots.AlertableSnapshot)
at Idera.SQLdm.ManagementService.Monitoring.AlertQueueProcessor.ProcessNotifications(ScheduledCollectionData)
at Idera.SQLdm.ManagementService.Monitoring.AlertQueueProcessor.Run()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

  • Does the service start when you try from Windows Service but crashes shortly after? If so, I would probably start off by checking your Alert Responses. The reason for this suggestion is because I see that it's regarding the processing of notifications, which is what the Alert Responses are used for. Perhaps one of the configured Alert Responses is malformed.

    I would probably try disabling the most recently created Alert Response to see if that prevents the crashes that you are seeing with the service. You can check the changelog in the SQLdm Desktop Client (Administration > Change Log) to see which alert response was most recently modified. If disabling the alert response does prevent future crashes, then you'll need to look at that particular response to identify the problem. 

  • Hi Tep Chantra,

    It makes sense to me... I have a similar problem....
    May I know, How to do that from backend table...Couldn't find a subsequent Table....NotificationRule Table doesn't has a disable\Enable column in  the table.
    Currently GUI options are unavailable to me as Management services are in stopped state