Troubleshooting

The Monitoring Server role is straightforward, however there are a few things that commonly go wrong during deployment. This section covers the common issues and areas to check if you find your Monitoring Server deployment doesn’t go smoothly.

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

Ensure that the correct pool is assigned to send data to the Monitoring Server. A Monitoring Server can be deployed without a pool assignment, which means data is not collected for reporting.

The Lync Server event log is also a good place to check for errors. From the Start menu, select Administrative Tools, and then select Event Viewer. Expand the Applications and Services Logs item, and then 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.