Chats are no longer being archived for OCS

Instant's Archive Viewer for Microsoft OCS is a very useful tool to search, retrieve, and report on conversations and content within the Microsoft OCS system.  However, Instant's Archive Viewer does not perform the actual content storage of the OCS chat conversations.  The content capturing and storage of the OCS conversations is performed by the Microsoft OCS Archiving Server - and the conversations and captured and stored in the LCSLog database.

You may discover chats are not up to date or no archives are shown at all in the Instant Archive Viewer or LCSlog. Usually, this means that archiving is not enabled, has stopped or is not configured in the OCS system correctly. There are some very good tools to help troubleshoot archiving issues. Example: Archiving CDR Reporter Tool. This reporting tool has built-in SQL queries to retrieve and view information from the Archiving and Call Detail Records (CDR) Backend. The tool enables the user to view Office Communications Server 2007 usage reports based on the Archiving and CDR tables. The resource kit can be downloaded here: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=b9bf4f71-fb0b-4de9-962f-c56b70a8aecd&displaylang=en

Here are some other useful things you can check:

1. Check that the Archiving services on the Archiving Server are running. Ensure that MSSQL server service (MSSQL) has started before you start the Archiving service (RTCLog). Next, click Office Communications Server 2007 R2 and start the Archiving Server by right clicking and click start. http://technet.microsoft.com/en-us/library/dd425118(office.13).aspx
2. Restart of the SQL instance, followed by a reboot of the Front End http://social.microsoft.com/Forums/en-US/communicationsserverlogging/thread/75cc1db3-7586-40e3-b5df-c4bb36977d98
3. Check the SQL server and the following ports are opened TCP/49154, TCP/135, TCP/445, TCP/49010, TCP/49191, UDP/137 http://social.technet.microsoft.com/Forums/en/ocspresenceim/thread/d778033b-42ba-4921-bfae-49d6568cd8ec
4. Install and configure Message Queue. To install and configure the message queue on the Windows Server 2008 and 2003, refer to the following link: http://technet.microsoft.com/en-us/library/dd441169(office.13).aspx
5. The Message Queuing service rejects incoming messages when it is unable to check whether the sender is allowed access to the queue for sending messages. Try manually adding the computer that is running Message queueing and relevant accounts such as authenticated users to the Windows Authorization Access Group
   
   http://blogs.technet.com/b/ucspotting/archive/2010/06/16/3338668.aspx
6. Check that message Queuing is installed on all computers that participate in archiving http://technet.microsoft.com/en-us/library/bb894580(office.12).aspx