Sharepoint 2010 Convert classic to claim based authentication

You already have a Web application created using Classic Mode Authentication and you want to convert Web application from Classic Mode authentication to Claims based Authentication.

You don’t have to delete that web application. You can convert that web application from classic mode authentication to claims based authentication. However this can only be done using PowerShell and it’s an irreversible process. Follow PowerShell commands to convert the web application from Classic Mode Authentication to Claims based Authentication:

$App = get-spwebapplication “URL”

$app.useclaimsauthentication = “True”



$App = get-spwebapplication “http://webapp:1907”

$app.useclaimsauthentication = “True”


Warning!: This is an irreversable process.


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.