Doug Deitterick's Blog

Information about Skype for Business, Lync, OCS, and Exchange UM.

Sample OCS Archiving Report Available

Sample OCS Archiving Report Available

  • Comments 49
  • Likes

Update 6/2/13 - Sample Lync Server Archiving Report is now available!  Click here for more information.
Update 5/29/13 - Updated report download link and moved report to TechNet Gallery.

Update 11/26/10 - OCSArchivingReport - 0.6 is available.  Fixed an issue with RTF text not displaying in the results.
Update 8/26/10 - This blog post will serve as the official home of the OCSArchivingReport.  Please post any questions/feedback in the comments.
Update 8/9/10 - OCSArchivingReport - 0.5 is available.  Fixed an issue with multiparty IMs displaying incorrect results.  Fixed the form automatically pulling data when loaded.

An easy way to get information out of the archiving database has been a common request from customers, but unfortunately a canned report wasn't inculded out of the box.  That is why I have created this SQL report as an easy way to query the database. 

It builds on the functionality provided by the Archiving PowerShell script that was written ( and adds a GUI interface, the ability to filter by date, and message formatting.  It has been tested against OCS 2007 R2 and SQL Reporting Services 2005.  You will need to have a functioning SQL Reporting Services server before trying to deploy this report.


  1. Download the latest version of the OCSArchivingReport.
  2. Open Report Manager – http(s)://<SRS Server>/Reports
  3. Click on New Folder
  4. Give the folder a name – i.e. OCSArchivingReport
  5. Click OK
  6. Click on the folder you just created
  7. Click on Upload File
  8. Browse to the location where you downloaded OCSArchivingReport.rdl and select the file
  9. Click OK to upload the report
  10. Click on New Data Source
  11. Enter LcsLog for the Data Source name
  12. Enter Data Source=<SQL Servername>;Initial Catalog=LcsLogfor the Connection String
    1. Replace <SQL Servername> with your SQL server\instance
  13. Select the Windows integrated security radio button
  14. Click OK
  15. Click on OCSArchivingReport
    1. You will see the following error: The report server cannot process this report. The data source connection information has been deleted. (rsInvalidDataSourceReference).  This is normal, since we haven’t linked the report to the data source we just created.
  16. Click on the Properties tab
  17. Click on Data Sources in the left-hand column
  18. Make sure A shared data source radio button is selected
  19. Click the Browse button
  20. Expand OCSArchivingReport and click on LcsLog
  21. Click OK
  22. Click Apply

The report is now linked to the data source and ready to be used.

Using the Report

The report allows you to enter the SIP URI of any 2 users that you want to view archived messages from.  If you enter “Any User” (case sensitive) for either of the user input boxes, you are able to view any message from any user to a specific user as well as any user to any other user.  You can use the Start Date and End Date to narrow down the search to a specific date range.  Once you have entered all of the inputs, click on View Report.
The results of the search are shown.  The First User column represents the sender of the message and the Second User column represents the recipient of the message.  The Message column shows the message that was sent as well any formatting on the message.  Changing Show Toast to Yes will show the toast messages as well as the Toast column.


Click here to download the latest version of the report.

A big Thank You to Rich Thorp for helping me put together this report!


* This is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of Use (

  • Setup and working but only see message text for toast messages, so looks like not converting correctly to text for the Rich Text items.  Data I can see is in the table, also if I remove the conversion call in your code I see the raw data, so with all the formatting codes.  Not sure if related - but using SQL 2008 SP1 Reporting Services host, with database instance on another SQL 2008 SP1 host, both using Windows 2008 R2.

  • I was hoping to use this for OCS 2007, but not R2.  can this be tweaked for that? or do you know where I can find another one?

  • @Zac

    Unfortunately the database schema changed between versions, so you will need to change the queries.  You can find information on the R1 Archiving database schema here:

  • Hi

    Will this work on lynch 2010?



  • @Ecl

    Yes, in it's current form, the report does pull data from a Lync Server 2010 archiving database. The database schema is similar enough that the report will pull the information needed. There are additional tables in the database that might be interesting to include in the report. Once Lync Server 2010 RTMs, we'll look at updating the report. There is also a PowerShell command for pulling information from the archiving database. You can run "Get-Help Export-CsArchivingData -Examples" for more information on what is possible.

  • @BrITman

    I reproed it on SQL 2005 as well.  I'm looking into it.  Thanks!

  • I'm getting an error... An error occurred during client rendering.

    An error has occurred during report processing.

    Cannot create a connection to data source 'DataSource1'.

    For more information about this error navigate to the report server on the local server machine, or enable remote errors

    I can connect to the FE sql database from another sql server just fine. I remember the first time i set this up with the older rdl file it worked. Not sure if any updates would cause this error. Any suggestions? Where else should i be looking at for errors? TIA.

  • Well if there is anyone out there willing to help me get this working on OCS 2007 (Non R2) i would greatly appreciate the assistance. my email address is if you can help

  • @Yves

    Did you follow the steps above to create the Data Source and change the report to use it?

  • Hello,

    I have the similar issue reported by Yves. I managed to run the report on the SQL Report Servicesc server. However running the report from any other remote computer will fail with the same error than Yves.


  • @peter

    Make sure you have permissions set properly and are logged in with the correct account. Also, I didn't need to use the instance name in the data source name, so you could try leaving it out.

  • I'm seeing the same issue that BrItman did - only the toast messages are showing up. Also using Server 2008 R2 and SQL 2008 Version 10.0.2531.0. I've disabled RTF and HTML locally and verified group policy either matches or is not defined for these settings. Any ideas as to why the messages are missing in the report?

  • @OCSguy

    Do the messages show up in the database?  I know of an issue with the way the report is parsing RTF formatted messages from the database, which might be your issue.  If so, we're working on a fix.

  • Yes, the messages are in the database. I can see them when I run the powershell script.

    I look forward to the next version of your report, do you think it might be available before the Holidays?

  • Hello,

    I managed to resolve my issue by not using the "Windows integrated security" radio button. In used instead: "Credentials stored secyrely in the report server" radio button and check the "User as Windows credentials when connecting to the data store".

    The user used there should have the read permission to the LcsLog database.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment