Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

EVOM not updating from all EV Servers

Created: 14 Mar 2013 • Updated: 19 Mar 2013 | 8 comments
Scott _Hastings's picture
This issue has been solved. See solution.

When I look at my EVOM Console, some servers have metrics that are regularly updated and others have metrics that are about 4 days old.

Any guidance on what would cause this?

TY!!

Operating Systems:

Comments 8 CommentsJump to latest comment

JesusWept3's picture

Do you know whether the MonitoringAgent.exe and MonitoringMiddleTier is running ok?
Maybe worth getting a dtrace on both of them and see if they're updating the monitoring database ok
Also check the application event logs and make sure they're not crashing (ID 1000)
Other than that, its possible that its SQL Statistics but unlikely

Also  check the registry for anything that may be disabling monitoring
Only thing i can think of off the top of my head is NoMonitor, but im pretty sure that is simply Admin Service not monitoring memory/disk threshholds and bears no relevance to how the MA and MMT work

Scott _Hastings's picture

JW... MonitoringAgent.exe and MonitoringMiddleTier are running in task manager. There are no 1000 events in the application event log that reference montoring.

Here is a part of the dtrace that could be the issue.

154 14:47:47.138  [5804] (MonitoringAgent) <3800> EV-H {MonitoringDataManager} UpdateTaskData - Error updating TaskMonitoring table
2155 14:47:47.138  [5804] (MonitoringAgent) <3800> EV-H {Logger.LogError} Exception::Symantec.EnterpriseVault.OperationsManager.DataAccessLayer.MonitoringAccessDBException ---> System.Data.SqlClient.SqlException: Violation of PRIMARY KEY constraint 'PK_ServiceMonitoring'. Cannot insert duplicate key in object 'dbo.ServiceMonitoring'.|The statement has been terminated.| 

I poked around and can't find 'dbo.ServiceMonitoring'

any ideas?

Rob.Wilcox's picture

That table is in the EnterpriseVaultMonitoring database....

Scott _Hastings's picture

Thanks Rob... I looked at the table and as you would expect the entry time matches what the monitoringwebapp displays. Any Idea on how to make it update? I already reconfigured EV Monitoing the the servers that are not updating.

Scott _Hastings's picture

Rob... it looks like it ran successfully, but the last update didn't change. Would that be your expectation?

D:\Program Files (x86)\Enterprise Vault>ForceMonitoringUtil.exe
ForceMonitoringUtility::Main method begins
 

Looking for file MonitoringAgent.exe.config at D:\Program Files (x86)\Enterprise
Vault\MonitoringAgent.exe.config
 

Trying to get monitor object at URI = tcp://localhost:7777/Symantec.EnterpriseVa
ult.OperationsManager.Monitor
 

Found Monitor object, calling PerformMonitoring() to force monitoring to happen
SUCCESS - Forced Monitoring to happen
 

ForceMonitoringUtility::Main method ends
 

Rob.Wilcox's picture

Sorry, I'm not sure, and my environments at the moment don't use EVOM.

Scott _Hastings's picture

Just to close out and inform...

Last week I lost DNS in the envronment. To resolve this, I modified the ComputerEntry table to the EV Hosts. Not very wise when I could have just updated the hosts file on each EV Server.

Anyway... I changed the ComputerEntry table back to the dns aliases. but during that time, Monitoring put some entries into the ServiceMonitoring table in the Monitoring database that weren't right.

I removed the entries that related to the servers that didn't update and then re-configured EVOM on those to 2 severs and ran a forced update.

Just thought somone might want to know.

scott