Propagation Status - Waiting for Initialization

i had a customer with 19,000 users and 5 server farm with 2 x WFE.

The problem had to do with search. After applying the cumulative patch from Feb, things did not really good.

In the search administration site, under search setting, the Propogation Status showed "Propagation Status - Waiting for Initialization ().

Event ID: 6482 was logged in the event log of the query server with the reason being something like this "Object 66a9ed68-c956-4bb3-af4f-3b9eb257a64e not found".

The waiting for initialization error points to the process of of propogation in a stuck state. So got to restarting the Windows SharePoint Administration services on both the query servers (WFE) and the propogration kick started. This services is found in the Services applet in the Administration tools of the WFE servers.

Before doing anything drastic, understand how search works in a SharePoint farm. Know the services involved, know the process involved and the flow of this services from index to propogation.

March 27, 2010

Cannot connect to the server at this time error SOLVED

One of my clients have had this persistent issue bugging them.

Problem.

When trying to export a list from SharePoint Teamsites to Excel (Office 2007 on Vista), this error always pops up. Sometimes it works once and then the error shows up again on subsequent attempts.

After weeks of trying out different scenarios, the solution is pretty simple.

Solution
Turn off the setting for checking server certification revocation list. :)

How
Using network analysis tools to see the communication between client and sharepoint server.

The evaluation version of Microsoft Office SharePoint Server 2007 for this server has expired

Here is a fix for the above problem from my buddy Murthy, as we work on a SharePoint migration/implementation.
--

This issue happened when I try to access the Mysite (web application) pages or any pages in the SSP admin web application.
There is no issue in accessing the Team sites, it is working fine.

Hmm, Strange Error made me to explore
The windows event log
Sharepoint log
SQL server log
Etc etc…

Many articles suggests different solution and one is as below

http://blogs.msdn.com/joelo/archive/2008/01/02/evaluation-version-expired-but-not-really.aspx
http://mosschampions.com/blogs/moss/archive/2006/11/02/False-Expiry-messages-in-SharePoint.aspx


RESOLUTION: We gave group WSS_WPG Read permissions to following registry key HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Office Server\12.0 We gave group WSS_ADMIN_WPG Full permissions to the same registry key HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Office Server\12.0 We added application pool Account ("dcomcnfg.exe") to the Distributed users We rebooted the server

No Use with all those solutions.

Then I did Uninstall MOSS, and reconfigured the whole farm again, still got the issue.

Spent the whole day, finally I got one article says peculiar solution to this problem, it worked for me too.

Here is the link to the article https://blogs.pointbridge.com/Blogs/ayyapusetty_raja/Pages/Post.aspx?_ID=10

Here is the solution, Believe it


The evaluation version of Microsoft Office SharePoint Server 2007 for this server has expired
By: Raja Ayyapusetty Posted: November 22, 2007 at 1:24 PM
Add Comment Share It Category: SharePoint Server

Definitely not the message you want to see after paying a whole lot of bucks. This happened to a colleague of mine when he tried to setup "My Sites". In fact, same error message was thrown whenever he tried to use any feature of "MOSS Enterprise".
After opening MS ticket and much debugging, here is the solution:
Open the associated web.config
Make any change and undo it
Save the web.config
Believe it or not that is your solution. Hope this helps to somebody.


Regards
Murthy

Sharepoint Orphans Explained

A very good explanation of SharePoint Orphans.
http://blogs.technet.com/corybu/archive/2007/05/31/sharepoint-orphans-explained.aspx