a blog by Rajesh

I have configured peoplepicker for about more than 10 domains. All works fine except for a domain. There was no error and only message is that the "No results found" in the People picker search results. How People picker works? People picker sends a dns query to the domain controller to retrieve the AD details. How did i resolve this issue? I ran network monitor in all the DCs. Search for a user in people picker Go to the nework monitor logs and search for the name you searched in the people picker. That will give some idea, what went wrong. Additionally, search for the destination DC. Repeat this if you are connecting to AD domain through multiple DCs. In my case, there was no response from the destination DC, which was caused by firewall port. After the port was opened in destination DC to the AD domain, the issue was resolved. Hope this helped someone out there. Happy trouleshooting!

Today, the following command saved my day. EXEC xp_readerrorlog My SharePoint 2010 installation cant find the DB server. I was able to ping , tracert to the db server from my windows (SharePoint). The SQL server were running perfectly fine. My first suspect was the firewall. I disabled the servers firewall in both servers. This is fine to do because these are testing systems. But , my sharepoint installation still cant find the SQL server. After googling for few hours, i tried the above command to check which port was being used by the SQL service. The SQL service was using port 56033 ( i guess this because the dynamic port was set as 0 ). After i configure the TCP Port to 1433 and removed the dynamic port value, the SQL server start listening in 1433 and my SharePoint was able to find the SQL server now. Hope this helps someone out there. Happy troubleshooting!