Lync shows ‘The address book is preparing to synchronize. Search result might not be current.’

Error

When user try to search one Lync user from Lync client user gets a message that ‘The address book is preparing to synchronize. Search result might not be current.’

Solution

1. From the client system, logoff from Lync client and close it.
2. Open registry editor [Use regedit] .
3. From Registry Editor browse through and go to ‘HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator’
   
4. Create a DWORD value by name ‘GalDownloadInitialDelay’ with value ‘0’
5. Go to ‘%userprofile%\AppData\Local\Microsoft\Communicator’ and open the folder by user’s sip-address.
6. Delete ‘GalContacts.db.idx’ and ‘GalContacts.db’
   
7. Start Lync client and wait for some time the error message should be gone.

Update-CsAddressBook fails with below Error="Retrieving the COM ….

 

Description

Update-CsAddressBook fails with below error.

Update-CsAddressBook : Error="Retrieving the COM class factory for remote component with CLSID {2766B7D8-C4FA-4617-9718 -31198883538A} from machine 10.33.243.20 failed due to the following error: 80070005.", Possible causes="Make sure that the Lync Server Front-End service is correctly installed and is running on the computer: "10.33.243.20"."
At line:1 char:21
+ Update-CsAddressBook <<<<
+ CategoryInfo          : NotSpecified: (:) [Update-CsAddressBook], DcomException
+ FullyQualifiedErrorId : DCOM_TYPE_CREATION,Microsoft.Rtc.Management.AddressBook.Cmdlet.UpdateAddressBookCmdlet

Solution

1. Add the ‘RTCUniversalServerAdmins into local admin group from where the command fails.
2. Log off and login and run the command again. It should work

‘Unable to connect to the remote server’ error when try to open SQL reporting link

 

You may get an error while configuring the reporting service and opening the reporting service URL stating that ‘Unable to connect to the remote server’. This error normally visible when you change the default reporting DB name or reporting URL.

Solution

From the SQL server where you have reporting DBs configured,

1. Go to the ReportServer folder [By default its C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer]

2. Locate the file ‘rSreportServer.config’
   
3. Open ‘rSreportServer.config’ in notepad and search for ‘SecureConnectionLevel’ and set the value to “0”
   
4. Save the file and close it.
5. Now try opening the URL it will be opening without any issue.

A timeout was reached (30000 milliseconds) while waiting for the SQL Server Reporting Services (Sql Instance name) service to connect.

 

Error

A timeout was reached (30000 milliseconds) while waiting for the SQL Server Reporting Services (SQLDB04) service to connect.

Reason

A timeout was reached (30000 milliseconds) while waiting for the SQL Server Reporting Services (MSSQLSERVER) service to connect.

Solution

To solve this issue you have add registry key with higher value than 30000 milliseconds.

Here are the steps to do so,

1. Click Start, click Run, type regedit, and then click OK.

2. Browse through the registry and then click the following registry sub key,
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

3. Right-click on Control, point to New, and then click on DWORD Value.

4. In the New Value #1 box, type ServicesPipeTimeout, and then press ENTER.

5. Right-click ServicesPipeTimeout, and then click Modify.

6.  Click Decimal, type the number of milliseconds that you want to wait until the service times out, and then click OK.

In this example its 60 seconds and for the same you
For example, to wait 60 seconds [60000 milliseconds] 

Quit Registry Editor, and then restart the computer. Once you are rebooted you can see the service is getting started or at least the value mentioned in the error is different. 

How to check SRV records by using ‘nslookup’

Even though the nslookup is very familiar to lot people its a so confusing tool to always Yesterday I had spent lot of time to see whether the srv record which i have created for Lync 2010 is correct or not.

Oops! I didn't mention why I wanted to verify from the client side, I did setup lync 2010 for my client but auto-login for the client was not working. When setup the client to use the server name manually it worked. You all know that, when client starts it always search for _sipinternaltls SRV records its configured to auto-login.

Lets come back to the point how we can check SRV records from nslookup, here is the steps.

1. Open cmd and type nslookup and press enter key
2. Inside nalookup type ‘set type=all’ and press enter.
   
3. Type ‘_sipinternal._tcp.domainname.com’ and press enter
   
4. You will be able to see the SRV record details of _sipinternaltls record. The same way can be followed for any other records like _ladp.