Hello guys,

I am able to archiving data  in my service that use Export-CsArchivingData powershell cmdlet, but I found out a defect.

For example:

We start a conversation at 11:00;

My service start archving at 11:02 before conversation archived. My service execute cmdlet as below: 

Export-CsArchingData -startdate "7/17/10:00:00"  -enddate "7/17/11:02:00" -dbinstance ...

It is no data can be exported, cause this conversation has not be archived.

At next, this conversation has been archived at 11:03(user close the chart window or it archived automaticlly);

My service start archiving again at 11:05, the executed cmdlet as below:

Export-CsArchingData -startdate "7/17/11:02:00"  -enddate "7/17/11:05:00" -dbinstance ...

Also we can not got data from this cmdlet, cause THE CONVERSATION ARCHIVING TIME IS CONVERSATION START TIME 11:00, My service will ignore archive this conversation.

I think this is a defect from lync cmdlet of Export-CsArchivingData. Can you help me how to figure out it in Lync server?

• Edited by EinsteinSu Friday, July 17, 2015 4:45 AM

Hi,

It seems that the export-csarchivingdata will export the archive data which need to include both the chat start time and the archiving time.

As the auto save time happen about several minutes after the chat start, the workaround is to set the time interval a little big. Such as you want to archive the conversation from 11:00 to 11:03, you can run the command

Export-CsArchivingData -startdate "7/17/11:00:00"  -enddate "7/17/11:10:00"

Best Regards,

Eason Huang