The Namespace CAS Health — Connection Status check tests client access protocol connectivity against a configured Exchange namespace, rather than against an individual server. When it reports a warning or error, the underlying evidence is on the ENow web server in the log and results files listed below.
Log file
Namespace monitoring writes to a single log:
C:\Program Files (x86)\ENow\MailscapeWeb\MailscapeData\LogFiles\ENowNamespaceMonitor.log
Start here to confirm the check ran, and to see the error text returned by the failing protocol.
Results files
Each protocol writes its own results file. They are stored per namespace, in a subfolder named for the namespace you configured:
C:\Program Files (x86)\ENow\MailscapeWeb\MailscapeData\Database\NamespaceMonitor\<namespace>\
| Protocol tested | Results file |
|---|---|
| ActiveSync | ActiveSyncResults-ActiveSync.xml |
| Autodiscover | EWSResults-Autodiscover.xml |
| Exchange Web Services | EWSResults-EWS.xml |
| MAPI | MAPIResults-MAPI.xml |
| Outlook Anywhere | OLAResults-Outlook Anywhere.xml |
| Exchange Control Panel | OWAResults-ECP.xml |
| Outlook Web App | OWAResults-OWA.xml |
How to use them
- Identify which protocol the dashboard is reporting on.
- Open that protocol's results file from the namespace subfolder and read the recorded status and response.
- Cross-check the same timestamp in
ENowNamespaceMonitor.logfor the full error returned by the endpoint. - If the results file shows a success but the dashboard disagrees, the gap is usually collection or permissions rather than the endpoint itself.
A protocol that fails here but succeeds when tested by hand from the ENow web server generally points at the monitoring service account's rights, or at a namespace URL that resolves differently from the web server than from a client.
Comments
0 comments
Article is closed for comments.