Dear Friends

Hi.I have a strange problem.my lync archiving was enabled and I exported before via :

Export-CSArchivingdata -dbinstance MyLync.DomainName\archive2013 -startdate "9/9/2015 8:00:00" -enddate "9/9/2015 20:00:00" -outputfolder E:\lyncarchive

Now when I try to export in management shell I receive the below warning :

WARNING: The property "DBInstance" has been deprecated and may be removed in
future versions.

when I follow archiving path the folder is created but there is no message.

what is going wrong.please help me

thanks

The error you're receiving is one you can ignore, it's saying that the -dbinstance command is really for Lync 2010 only and is no longer necessary.

However, not having data is another issue.  If you connect to the MyLync.DomainName\archive2013 SQL instance with SQL Server Management studio, do you see data in the LcsLog database in the Messages table for that time period?

Hi Dear Anthony Caragol

thanks for your quick reply

I can connect tomy database (MyLync.DomainName\archive2013) when I Open LCSLog Database and then Select top 1000 rows on dbo.messages table,it is empty.also my folder in E drive Is empty

Then your archiving isn't enabled or that's the wrong database.  Double check that that's the instance used for archiving in the topology builder and run the following two commands via PowerShell to see if it's enabled.

Get-CsArchivingConfiguration
Get-CsArchivingPolicy

I ran those commands : Get-CsArchivingPolicy ArchiveInternal :True ArchiveExternal:True I open my topology builder : SQL Server Store:MyLync.DomainName\rtc Archiving SQL Server store:MyLync.DomainName\rtc Is that right ?

Is it possible you're archiving to your RTC instance instead? If you open that instance with Management Studio, do you see an LCSLog directory?

And for Get-CsArchivingConfiguration does it say EnableArchiging: True?

I checked it LCSLog Database is only visible via MyLync.DomainName\archive2013 .

When I open .\rtc I see :

Should it be Archive2013 database ? or is it true ?

No, it looks like you're archiving to the rtc database, but the actual LCSLog database isn't created. So, you don't have any data to export. 

Step 1 would be to notify whoever needed that data that the data does not exist.

Step 2 would be change your archiving SQL store to the right SQL server instance and keep an eye on that database to make sure it's receiving data and writing to the messages table.

Dear Anthony Caragol

thanks for your guide.

base on your recommendation I should change my database in Archiving SQL Server Store (New Topology ) and then export.

Did you mean it ?

I mean, change it in the topology builder to the correct location.  However there is nothing to export as there is no data.  Once some IM messages have come in, you can export those, but no IMs prior to the topology change you're about to make will exist.

Hi,

You could try to create a new SQL instance such as named "Archiving" to host the Archiving database. Then modify the location of Archiving store in Topology and publish it. Rerun step 2 on FE Server.

Best Regards