We are receiving the below error when accessing the SQLdmManagementService . i tried to restart the service twice but not worked.
Fault bucket , type 0Event Name: AppHangB1Response: Not availableCab Id: 0
Problem signature:P1: SQLdmDesktopClient.exeP2: 10.2.0.3269P3: 59314dc6P4: ba70P5: 134217984P6: P7: P8: P9: P10:
These files may be available here:C:\Users\sanjeev.koppella\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_SQLdmDesktopClie_71943c9256a6185262e72dbeada7571128050f_7a97a352_89f0fe2d
Analysis symbol: Rechecking for solution: 0Report Id: 6c00520f-38c6-11e9-80da-0050569e67afReport Status: 2048
Faulting application name: SQLdmManagementService.exe, version: 10.2.0.3270, time stamp: 0x59566ec8Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000Exception code: 0xc0000005Fault offset: 0x00007ffe2aba9ab9Faulting process id: 0x984Faulting application start time: 0x01d4ccd27fc18a6eFaulting application path: C:\Program Files\Idera\Idera SQL diagnostic manager\SQLdmManagementService.exeFaulting module path: unknownReport Id: 0c3ec044-38c6-11e9-80da-0050569e67afFaulting package full name: Faulting package-relative application ID:
Application: SQLdmManagementService.exeFramework Version: v4.0.30319Description: The process was terminated due to an unhandled exception.Exception Info: System.NullReferenceExceptionat 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
Powered by IDERA