When I run the following command:
Export-CsArchivingData -DBInstance archive\LYNCARCHIVE -StartDate 12/06/2010 -OutputFolder c:\12062010archive
I get nothing in the output, and receive the following output:
Total number of sessions: 0 Successfully exported sessions: 0 Failed sessions:
there is nothing located in the folder path, its blank. However, if I open the Messages table through SQL Management, I can see the messages located in there.
I have made sure the account is a member of the necessary groups to run the command.
Anyone offer any suggestions?
Are you sure you are using the correct DB Instance?
Technical Specialist Microsoft OCS & UC Voice Specialisation - http://www.uwictpartner.be
If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it.
I have the same problem. Both in my production deployment and my previous test deployment. I have only had my production archiving server set up for a day so I haven't been able play around with exporting much. In my test deployment the export command wouldn't grab IM's until a day or two after they appeared in the SQL table. Still looking for a solution.
Since my current deployment uses the default sql instance I am using the following switch -DBInstance sqlservername
I am having the same issue.
I turned on Archiving today (enabled archiving server in topology, did the install on the archiving server + MSMQ install, and started services)
Ran some test chats with archived users through and I can see the conversations in the messages table using a "SELECT * FROM Messages" query against the LcsLog database.
Our database is running the default instance (MSSQLSERVER) and is named sql2, so I am running the following cmdlet:
Export-CsArchivingData -DBInstance sql2 -StartDate 1/1/2011 -EndDate 2/16/2011 -OutputFolder "C:\ArchivingExports"
It wouldn't take for the longest time (several hours, even though there were messages in the database) but now as I type this post, it does seem to be working, so maybe there is some logic in there that requires a minimum amount of time to go by.
When issuing Export-CSArchivingData without an -EndDate parameter the returned data will only run up to the midnight (it's import to consider time zones) on the previous day. Given this you will not see any records for the current day. If you want to see records for the current day the best option is to manually specify an end date in the future (tomorrow).