cancel
Showing results for 
Search instead for 
Did you mean: 

EV9 - Status - Severe alert - old date

GertjanA
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello all

EV90SP4 - Windows 2008R2

On 28-03-2014, some issue occurred, causing a Severe alert for Exchange Mailbox Synchronization. The alert is still there. Even when running a 'check now', that error does not disappear.

The bottom pane shows:

The monitor terminated unexpectedly.

Details:
System.Runtime.InteropServices.COMException (0x80040E21): Exception from HRESULT: 0x80040E21 at KVS.EnterpriseVault.Interop.DirectoryConnectionObjectClass.GetLongRunningMonitoringJobs(String monitoringItemEntryID, Int32 maxRecordsToReturn) at KVS.EnterpriseVault.Monitoring.JobMonitorBase.GetLongRunningMonitoringJobsXML(Int32 maxResults) at KVS.EnterpriseVault.Monitoring.ExchMbxSyncMonitor.RunNow(MonitorRunType runType) at KVS.EnterpriseVault.Monitoring.MonitoringThreadBase.ScheduleThread()

Is there anyway to remove these alerts?

Thanks.

Gertjan

Regards. Gertjan
1 ACCEPTED SOLUTION

Accepted Solutions

plaudone
Level 5
Employee Accredited Certified

You can get the MonitoringItemEntryId from the Monitoring table in the Directory database for the MonitoringItemType = 28 as this is for the sync.   Then run the following to get the history of that check.  

select * from MonitoringHistory
where MonitoringItemEntryId = 'ID_from_monitoring_table'

You should be able to delete the one that failed.

 

 

 

View solution in original post

4 REPLIES 4

JesusWept3
Level 6
Partner Accredited Certified
A similar issue was Fixed in 10 SP3 apparently Maybe there's a fix in 9 SP5 http://www.symantec.com/business/support/index?page=content&id=TECH200818 Maybe worth contacting support and quoting that ETrack number seeing if there's any workaround since no more EV9 updates are being made anymore
https://www.linkedin.com/in/alex-allen-turl-07370146

plaudone
Level 5
Employee Accredited Certified

I don't see that this is addressed in 9.0.5.  

Checking for possible workaround. 

 

plaudone
Level 5
Employee Accredited Certified

You can get the MonitoringItemEntryId from the Monitoring table in the Directory database for the MonitoringItemType = 28 as this is for the sync.   Then run the following to get the history of that check.  

select * from MonitoringHistory
where MonitoringItemEntryId = 'ID_from_monitoring_table'

You should be able to delete the one that failed.

 

 

 

GertjanA
Moderator
Moderator
Partner    VIP    Accredited Certified

Thanks plaudone,

that did the trick. FYI, we will be upgrading this environment to EV10SP4CHF2 next week.

Regards. Gertjan