Exception from HRESULT: 0x80040E14

You may come across this error Exception from HRESULT: 0x80040E14 when ever you try to add content to the sharepoint site or execute any stsadm commands.

The sqldb server must have run out of space. clear space from the dbserver and you see the error is no longer displayed.

Event ID: 5553 and 7888

In Application logs in the SharePoint server, we may continuously find 2 different events occurring frequently.

//-----------------------------------------------------------------
Event Type: Error
Event Source: Office SharePoint Server
Event Category: User Profiles
Event ID: 5553
Date: 4/26/2012
Time: 7:09:02 PM
User: N/A
Computer: SERVER NAME
Description:
failure trying to synch site a7b12d90-7d1d-4341-8df3-a1d92eba7a47 for ContentDB db7fb0d6-7d0d-4230-8de5-e7cc00ca0db7 WebApp 55de867d-5a9d-4ac4-83d6-f3ee9ee98df2. 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..
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

//----------------------------------------------------------------
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server General
Event ID: 7888
Date: 4/26/2012
Time: 7:09:02 PM
User: N/A
Computer: SERVER NAME
Description:
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.SqlInternalConnection.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)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
//-----------------------------------------

Cause:
The likely reason for this issue is the content database which can be movied or copied or used without detaching properly.
As the synchronization runs every hour, this issue will appear frequently in the event viewer.
Resolution:
We have to track down which content db is giving the issue.
For that you can run the following queries in the config db to find out the contentdb 

SELECT *FROM [dbo].[Objects]

WHERE ID='db7fb0d6-7d0d-4230-8de5-e7cc00ca0db7'

The GUID of the content db can be obtained from the error message itself, (5553 error)

SELECT [FullUrl]
,[Id]
,[RootWebId]
FROM [WSS_Content_sitecontentdb].[dbo].[Sites]
WHERE ID='a7b12d90-7d1d-4341-8df3-a1d92eba7a47'

The site GUId also can be obtained from the error message. Which is used to execute the below command
The following command is to be executed to clear the errors.
stsadm -o preparetomove -Site "http://<sitename>/" -OldContentDB "<ContentDBGUID>"
stsadm -o sync -DeleteOldDatabases 0
Also remember that, before moving content database execute the preparetomove command.

Unable to modify table, time out expired error

When I tried to modify a table structure in  with more than 20 million records. It gave me the time out expired error. This occurred in MS SQL Server 2005
The modifications were not saved.


When I initially tried to save the modifications for the table, a warning message appeared for me. 

Later I clicked yes and again waited for the result. It finally gave me an error saying that, 'time out expired' after 30 seconds.

The error was "Errors were encountered during the save process. Some database objects were not saved" and "Unable to modify table. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding." The table structure was same as previous.


Reason for this is the time out setting in the designer option. It would be set to 30 seconds by default. If you changes take longer than that time then they would not be saved. We need to change the value of the setting.


For this, go to Tools -> Options -> Designers

There will be check box option of "Override connection time-out value for table designers updates:" and "Transaction time-out after:" change the default value of 30 secs to the a higher value. In my case I made it 1000 seconds. And then click on OK. Do remember that transaction time out setting value should be greater than 0 and it should be in the range between 1- 65535. 


Now after doing this change, I tried to modify the table and the changes got saved now. 
Note that while the table modifications are saved, the SQL Management studio would remain inaccessible till the changes to complete. 

Hide View All site content

to hide view all site content,

edit the page, add a content editor Webpart 
in source Editor, copy the below code, and save it. 


<style>
.ms-quicklaunchheader {
display:none;
}
</style>

How to move/migrate SharePoint list items/documents and preserve metadata properties

Usually, when you want to move documents or list items from a source to destination list, we follow the following methods

• Opening in windows explorer and copy pasting the documents
• Saving the source list as template including content and then recreating the list in destination using template

But both above process when we move we have the below drawbacks

• The metadata properties more importantly the Modified date stamp and created date stamp are not preserved
• For issue tracking list, where we usually dont have the option to save as template including content cannot move items.

There is an alternate method to achieve moving the items from source and destination list, same time preserving the meta data properties.

1. Create a blank list of document library/custom list etc in the destination site. No need to create the custom columns etc, the move process will take care.

2. Access the Site and Content structure  from Site Actions button or from site settings ->Site administration ->content and strcuture

3. Select the list or library in the list and go to all items view and select all the items. In toolbar, actions , click on "Move".

4. You wil receive a pop up asking to select the destination list. Just select the list you have created and ok.

Done. Now you can see all the items are moved along preserving the time stamp. 

Note: If you get any errors while moving the items, the alternate way is save the source list as template excluding content and then recreate it in destination. This will preserve the structure in source.

Also do note that, if source has versioning enabled, then destination should also have versioning.

If it has look up columns do manage to make lookup work by created the dependency lists in destination also.

You can move the dependency list using the same process first and then the actual list.

Hope it helps you!!