If the Enterprise Monitor is not working, this troubleshooting list may help you resolve the problem:
-
If the Enterprise Monitor cannot get access from any monitored system and displays the message Not currently collecting monitor data from configured client systems - No Message Bank or Enterprise Production is running in this namespace (EMONITOR) on machine jgoldman6420:
Ensure that the production in the namespace is running. You will get this message if it is not running.
-
If the Enterprise Monitor appears to be working correctly but it is displaying the message Not currently collecting monitor data from configured client systems - No Message Bank or Enterprise Production is running in this namespace (EMONITOR) on machine jgoldman6420:
The production in the namespace must have a class that extends the Ens.Enterprise.ProductionOpens in a new tab class. If you create a new production using the InterSystems IRIS portal, it creates a production that extends Ens.ProductionOpens in a new tab. To fix this problem, edit the production in an IDE and change the class that it extends. Then compile the class and stop and restart the production.
-
If the Enterprise Monitor does not display an error message but the clients are not being polled and the data is not being updated:
Ensure that the production contains the Ens.Enterprise.MonitorServiceOpens in a new tab business service and that it is enabled.
-
If you observe an error where a non-functioning login screen appears in the Enterprise Monitor instead of an embedded graph, change your configuration to use https rather than http. In addition, set the web application’s Session Cookie Label setting to None. You can access your web application’s settings from System Administration > Security > Applications > Web Applications.
