Monitoring Troubleshooting

The Monitoring role is fairly straightforward; however, there are a few things that commonly go wrong during deployment. This section covers the common issues and areas to check should you find your Monitoring Server deployment not going smoothly.

Because a lot of server-to-server connections are involved in a Monitoring Server deployment, the most obvious problem area is in ensuring proper permissions. Also, ensure that usernames and passwords are typed correctly. When in doubt, reenter the usernames and passwords used for database access for the Monitoring Server and the Reporting Server. Also, ensure that the accounts aren’t subject to password expiration in Active Directory. There’s no “doh” feeling like having a service account’s password expire 30 or 90 days into your deployment.

If you’ve chosen to use SSL for your Reporting Services URLs, ensure that the subject name (SN) of the certificate matches the site name you’ve chosen. Note that this might or might not be the same as the FQDN of your server, depending on your reporting server configuration.

The Lync Server event log is also a good place to check for errors. From the Start menu select Administrative Tools and then Event Viewer. Expand the Applications and Services Logs item and select Lync Server. All events related to Lync Server functions reside here. Often the error description is enough to identify the problem and determine the resolution.