![]() This information told me that the incorrect number came from the old Lync 2013 server during the user migration.īelow is a script I used to check all 300+ users in SfB using the DBAnalyze.exe tool. We could also see the “LastPubTime” was in 2015. ![]() ![]() In the output we could see the incorrect number showing. The tool grabs all data from a particular user from the Skype Database and spits it out in plain text. The MS tech ran the DBAnalyze.exe tool from the SfB Reskit.Ĭ:Program FilesSkype for Business Server 2015ResKitDBAnalyze.exe /report:user /sqlserver:SFBFE01RTCLocal > c:tempSQLExportssqlexportusername.txt I opened a case with Microsoft support to help us with this issue. So clearly this number was stored someone in the FE server. This means that every time I searched for this user in my SfB client, it would send a SUBSCRIBE message to the FE, and I would get back a 200 OK containing this incorrect number. The number was then stored in the CoreContact.cache file on my client, but not in the GalContacts.db. In this file I searched for my incorrect number “+0740892387” and found it buried in a 200 OK response from the Front-End server. SKYPE PHONE NUMBER PCThis log file can be found on your PC at C:UsersusernameAppDataLocalMicrosoftOffice16.0LyncTracing I then looked in the SfB client log file called “Lync-UccApi-0.UccApilog” using Snooper. With the help of a colleague, we looked through the Exchange GAL and local Outlook address book, but found nothing. In fact, opening the GalContacts.db file with Notepad showed the correct number.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |