Archiving Troubleshooting

The Archiving Server 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 if you find your Archiving Server deployment not going smoothly.

Because a lot of server-to-server connections are involved in an Archiving 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 Archiving Server. Also, ensure that the accounts aren’t subject to password expiration in Active Directory.

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

One common cause for Archiving to fail is that the Front End Server isn’t able to install the Archiving agent properly due to a problem with the Message Queuing Service. You might see event ID 30517 in the Lync Server logs or you might see event ID 30509. Although the FE role requires Message Queuing Service, it doesn’t require Message Queuing Directory Integration. However, the Archiving agent does require this. The fix is to simply install the additional feature on the FE servers that are targets for Archiving.