Monday, November 22, 2010

ERROR: request not found in the TrackedRequests. We might be creating and closing webs on different threads

When users entered information in a standard MOSS Form, the values of the fields were not saved. It was empty. Even though the fields are required. Automatic workflow is kicked off, but no values in the fields.

In the ULS Logs I found this error:

ERROR: request not found in the TrackedRequests. We might be creating and closing webs on different threads. ThreadId = 26, Free call stack = at Microsoft.SharePoint.SPRequestManager.Release(SPRequest request) ....

I searched all over on the internet and could not find a solution. This Form and Workflow is standard OOB and was not created using SharePoint Designer.

To complicate it further, I have 4 Web Front Ends, and only 1 was giving this issue. So I started at the Web.Config file.

The web.config files differed on the "working" WFE's and the "broken" WFE. The solution is quite simple. In this part of the web.config:

The enableViewState and EnableViewStateMac was set to "false" (on the "broken" WFE). So I changed both values to "true". Because that was the value on the "working" WFE's.

Walla! Problem solved.

Friday, July 2, 2010

Event 7888 and 5553

I have been getting these errors in my event log:

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server General
Event ID: 7888
Date: 2010/07/02
Time: 10:01:41 AM
User: N/A
Computer: xxxxxxxxxxxxxxxx
A runtime exception was detected. Details follow.
Message: Cannot insert duplicate key row in object 'dbo.UserMemberships' with unique index 'CX_UserMemberships_RecordId_MemberGroupId_SID'.
The statement has been terminated.

Techinal Details:
System.Data.SqlClient.SqlException: Cannot insert duplicate key row in object 'dbo.UserMemberships' with unique index 'CX_UserMemberships_RecordId_MemberGroupId_SID'.
The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.Office.Server.Data.SqlSession.ExecuteNonQuery(SqlCommand command)
at Microsoft.Office.Server.UserProfiles.WSSSynchSqlSession.SynchExecuteNonQuery(SqlCommand cmd, Boolean throwOnFail)
at Microsoft.Office.Server.UserProfiles.WSSSynchSqlSession.SynchExecuteNonQuery(SqlCommand cmd)
at Microsoft.Office.Server.UserProfiles.SiteSynchronizer.WriteChangeLogConsumed()
at Microsoft.Office.Server.UserProfiles.SiteSynchronizer.Synch()
at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)


Event Type: Error
Event Source: Office SharePoint Server
Event Category: User Profiles
Event ID: 5553
Date: 2010/07/02
Time: 10:01:41 AM
User: N/A
Computer: V058MOSFFF002
failure trying to synch site ac379cbb-a2da-4637-ae11-fb511f07a1dc for ContentDB f788b294-67ca-499f-94d8-508f2946512c WebApp e971af36-c174-4c4f-9b6b-a0ee8b628274. Exception message was Cannot insert duplicate key row in object 'dbo.UserMemberships' with unique index 'CX_UserMemberships_RecordId_MemberGroupId_SID'.
The statement has been terminated..

To fix it in my case (we have MOSS SP2 installed), we ran the following commands:

stsadm -o sync -listolddatabases 5
* This will list the database giving the problem and you will be able to match the database ID with the one in the Event Log *

stsadm -o sync -listolddatabases 0
* This command list all databases that are being synchronised and the last time they were synchronised *

stsadm -o sync -synctiming M:5
* This command set the synctiming to occur every 5 minutes, so we can check our progress with the sync *

stsadm -o sync -deleteolddatabases 0
* This command will clear out the sync information for ALL the databases, don't be alarmed it will be back soon *

Give it a few hours and periodically check your event log and run this command:

stsadm -o sync -listolddatabases 0
* The command lists the databases that are sync'd *

Problem fixed....

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
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'

Unspecified error

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 -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.