Sharepoint 2007 unable to remove orphane content database

 If you realized content database still remain at the Manage Content Databases section in Central Administration. When try to delete this database you received “Object reference not set to an instance of an object.” or by using stsadm getting belowed errors.

C:\>stsadm -o removecontentdb -url  -databasename “Sharepoint_blog_db” -databaseserver DBBLOG

Database “Sharepoint_blog_db” is not associated with this web application

C:\>stsadm -o addcontentdb -url  -databasename “Sharepoint_blog_db” -databaseserver DBBLOG

An update conflict has occurred, and you must re-try this action. The object SPWebApplication Parent=SPWebService is being updated by POSTMAN\bugra, in the w3wp process, on machine BLOGSERVER.  View the tracing log for more information about the conflict.

This issue occurs if the contents of the file system cache on the front-end servers are newer than the contents of the configuration database. After you perform a system recovery, you may have to manually clear the file system cache on the local server.

Solution :
Clear the file system cache on all servers

end of article 🙂


Unexpected error in “content sources” when try to crawl in SSP


Exception Details: System.IndexOutOfRangeException: DisplayInAdminUI


Could not find stored procedure ‘dbo.proc_MSS_GetCrawlHistory’.   at Microsoft.SharePoint.Portal.Search.Admin.Pages.SearchAdminPageBase.ErrorHandler(Object sender, EventArgs e)
at Microsoft.SharePoint.Portal.Search.Admin.Pages.SearchSSPAdminPageBase.OnError(EventArgs e)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at ASP._layouts_listcontentsources_aspx.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


SharePoint database is not on the same version as the farm’s configuration database. If you open up SQL Server and looked at the rows on the dbo.Version tables in both the configuration database and the database associated with the failed SSP, and check that they are not in sync; the updates for the farm had been applied to the configuration database but not the SSP databases.


  1. On a SharePoint server in your farm (I’d suggest the one hosting the Central Admin site), open a command prompt and navigate to the directory containing the SharePoint Products and Technologies Configuration Wizard (psconfig.exe)
  2. Execute the following command:
    psconfig -cmd upgrade -inplace b2b -wait -force
  3. Review the PSconfig and Update logs to see if any errors were reported.
  4. Check the versioning data in the dbo.Version table in both of the SSP’s databases to confirm that they now matched the config database’s version.
  5. Open the SSP Admin site and tried to administer the farm’s Search configuration


Sharepoint 2007 Error in HtmlEditor.js Line:5740


A single user with Full Control permissions is having trouble using certain page-editing functions. And getting javascript error with HtmlEditor.js

Here is the error:

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 1.1.4322; .NET CLR 3.0.04506.648; InfoPath.2; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; MS-RTC LM 8; MS-RTC LM 8)
Timestamp: Mon, 24 May 2010 16:13:42 UTC

Message: Invalid argument.
Line: 5740
Char: 2
Code: 0
URI: http://www.[TheSiteURL].com/_layouts/1033/HtmlEditor.js


Add your site to your local intranet zone in your browser.

IE -> Tools -> Internet Options -> Security -> Local Intranet -> Sites

Thats all.


Sharepoint 2007 Language Pack & service pack order

Language packs enable site owners and site collection administrators to create SharePoint sites and site collections in multiple languages without requiring separate installations of Microsoft Office SharePoint Server 2007

You must install the Windows SharePoint Services 3.0 language packs before you install the Office SharePoint Server 2007 language packs.
You must install the language packs in the correct order. The correct order is as follows:

1.Windows SharePoint Services 3.0 language pack
2.Windows SharePoint Services 3.0 SP1 or SP2 language pack
3.Office SharePoint Server 2007 language pack
4.Office SharePoint Server 2007 SP1 or SP2 language pack


Important Notes:

  • You must be a member of the Administrators group on the front-end Web server to install these language files. After the language files are installed, the languages are available to all users of the computer.
  • If you are uninstalling a Microsoft Office Server product, you must uninstall all language packs before you uninstall the product.
  • If you are running Service Pack 2 (SP2) of Office SharePoint Server 2007 you only have to download the SP2 language packs. The SP2 language packs include all materials that are in the SP1 language packs.
  • You must download both the Windows SharePoint Services 3.0 language packs and the Office SharePoint Server 2007 language packs.

For each Service Pack do the following :

1. Disconnect users from the server farm by stopping the World Wide Web Publishing service (w3svc) on all Web servers.

2. Begin the software installation on the server hosting the central admin web site

3. At the end of the software update installation, the SharePoint Products and Technologies Configuration Wizard start Note:  If the wizard does not start automatically, click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard.

4. On the SharePoint Products and Technologies Configuration Wizard Welcome page, click Next.

5. In the dialog box that notifies you that some services might need to be restarted during configuration, click Yes.

6. On the Completing the SharePoint Products and Technologies Configuration Wizard page, click Next.

7. When the dialog box about installation in a server farm appears, do not click OK. Instead, leave each server with the following dialog box displayed: – THIS IS CRITICAL TO THE SUCCESSFUL INSTALL.
You must run Setup to install new binary files for every server in your server farm. If you have multiple servers in your server farm, run Setup and the configuration wizard on the other servers now, and then return to this server and click OK to continue.

8. When the dialog box from the previous step is displayed on all Web servers in the server farm, use one Web server that hosts the Central Administration Web site to finalize the installation.

9. On the server you selected in the previous step (Step 2), click OK.

10. On the Configuration Successful page, click Finish. 11. Continue updating the remaining computers in the server farm, one at a time, by clicking OK in the dialog box.




For  More Information and Resources: