Tuesday, March 23, 2010

Event: 2423

I recently had this Warning in my Event Log:

Event Type: Warning
Event Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 2423
Date: 2010/03/23
Time: 09:09:04 AM
User: N/A
Computer: xxxxxxxxxxxxxx
Description:
The update cannot be started because all of the content sources were excluded by crawl rules,
or removed from the index configuration.

Context: Application 'Search index file on the search server', Catalog 'Search'

Details:
Unspecified error
(0x80004005)



I checked the Search Administration, and found that all my content sources were "indexing" but no indexing were taking place. I could not pause the crawling, and nothing was being added to the Crawl Logs.

I then restarted the "Windows Services SharePoint Search" service, and the "Office SharePoint Server Search".

I could then pause the various Content Sources, and Indexing started.

Thats it!

Monday, March 15, 2010

Deleting a Site Collection Administrator

I searched every where (almost) on the Net for an answer to this. Adding a secondary site collection administrator is very easy:

stsadm -o siteowner -url http://xxxx/sites/sitename -ownerlogin someuser -secondarylogin someuser2

Walla second site collection administrator added. If you have more than two site collection administrators you can add another by using this command:

stsadm -o adduser -url http://xxxx/sites/sitename -userlogin someuser3 -useremail someuser3@email.com -role "Full Control" -username "someuser3Name Surname" -siteadmin

Now what do you do when you want to remove Someuser3 from the Site Collection Administrators?

Quite easy:

1. Make a note of the user for the SecondaryLogin of the site collection
2. Add the someuser3 to the secondarylogin for the site. This will remove the previous secondarylogin for the site, and add someuser3 as the secondarylogin.
3. Add the user from step 2 (previous secondarylogin) back to the site.

This will remove someruser3 from the site collection administrators for the site collection.

Wednesday, January 20, 2010

Error Restoring a Folder from the Recycle Bin

Trying to restore a folder that was deleted gives this error in SharePoint:

File Not Found. at Microsoft.SharePoint.Library.SPRequestInternalClass.RestoreRecycleBinItem(String bstrWebUrl, Guid gItem)
at Microsoft.SharePoint.Library.SPRequest.RestoreRecycleBinItem(String bstrWebUrl, Guid gItem)
at Microsoft.SharePoint.SPRecycleBinItemCollection.RestoreCore(Guid[] ids)
at Microsoft.SharePoint.SPRecycleBinItemCollection.Restore(Guid[] ids)
at Microsoft.SharePoint.ApplicationPages.RecycleBinPage.ProcessAction(String action, String guidString)
at Microsoft.SharePoint.ApplicationPages.RecycleBinPage.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)


Actually it is a simple error to fix. The Folder that has to be restored was nested inside a "Parent" folder. The "Parent" Folder was then renamed or deleted. To restore the Folder, create the "Parent" folder as per the "Original Location" displayed in the Recycle Bin.

And Restore... Done...

Friday, January 15, 2010

Method 'post' of object 'IOWSPostData' failed

I came across this curious error today. This error pops up when a user (Office 2007) wants to import a spread sheet into a custom list (SharePoint 2007).

Further investigation (Google) revealed that it is a macro inside Office 2007 that is causing the problem. Exactly why, I don't know. But here is my work around, use at your own risk ;-).

Make a backup of the file and edit the file in "C:\Program Files\Microsoft Office\Office12\1033\EXPTOOWS.XLA" (with Excel):

1. Open the file with Excel
2. Press F11
3. Locate the following code:
....
aTarget(iPublishDesc) = Title
lVer = Application.SharePointVersion(URL)
End Sub
....
4. Insert right after: lVer = Application.SharePointVersion(URL)
the following line: lVer = 3
5. Save the file EXPTOOWS.XLA

Make sure you overwrite the file.

That's it! Anyone welcome to leave a comment as to why this happens, or what the consequences would be if you edit the EXPTOOWS.XLA file.