Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))
We are current users of WSS 3.0 SP1 (MS SQL Server 2005 w/SQL Server Configuration Manager & SQL Server Management Studio Express) and are having issues with the following error occurring quite frequently when we visit pages on our SharePoint site.
Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))
Our research keeps brining up that the log files are getting large and are not being cleared. We are doing a Full Backup of our SharePoint Farm with BackupExec 11d so we are not understanding how to fix this. Does anyone have any suggestions...
Thanks in advance.
All Replies
- Your out of space on the drive that is holding your SQL log.
You need to truncate it or shrink it.
Probably run a query like this:
BACKUP LOG database_name WITH TRUNCATE_ONLY
You'll have to find out which DB has the big log first. Probably your content db.
You can add a sql maintenence plan via management studio (maybe not express?) to backup the log periodically.
Are there any risks involved when running the Query to TRUNCATE the SQL log?- It just pushes your log into your backup and deletes the log that is taking up the space. Really no risk, it won't truncate the log unless it is able to add it to the backup first.
Where do you run this query?
-
Management Studio
-
.dos level
-
I got the same problem. Really would like to know if theres any solution to cure this.
Also, the lists that generates this errors is impossible to delete and probabley also is the cause to that its impossible to make a full site backup with AvePoints system.
- This is really not a SharePoint issue. It is a basic SQL management issue. The SQL logs should be managed as part of a maintenance plan which is coordinated by a SQL DBA.
There is quite a bit of information above, otherwise you should be very successful on google searching for information on backing up and truncating transaction logs, as well as investigating the different recovery models available in SQL. But how do you do Db managment and log truncating running a MS SQL Express as i do?
You can download and install Management Studio for SQL server express freely available
check out the link and download it
http://msdn2.microsoft.com/en-us/express/bb410792.aspx
So you can able to manage your express database
Hi,
I got the same error in a different context I was setting the permissions on some folders.
I am running SharePoint 2007 SP1
I have enough space on the drive (about 23GB free)
I was able to capture the call stack on the exception, it randomly happened in two different locations:
Microsoft.SharePoint.SPException: Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT)) ---> System.Runtime.InteropServices.COMException (0x80004004): Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT)) at Microsoft.SharePoint.Library.SPRequestInternalClass.UpdateRoleAssignment(String bstrUrl, Guid& pguidScopeId, Int32 lPrincipalID, Object& pvarArrIdRolesToAdd, Object& pvarArrIdRolesToRemove) at Microsoft.SharePoint.Library.SPRequest.UpdateRoleAssignment(String bstrUrl, Guid& pguidScopeId, Int32 lPrincipalID, Object& pvarArrIdRolesToAdd, Object& pvarArrIdRolesToRemove) --- End of inner exception stack trace --- at Microsoft.SharePoint.Library.SPRequest.UpdateRoleAssignment(String bstrUrl, Guid& pguidScopeId, Int32 lPrincipalID, Object& pvarArrIdRolesToAdd, Object& pvarArrIdRolesToRemove) at Microsoft.SharePoint.SPRoleAssignmentCollection.UpdateAssignment(Int32 principalId, SPRoleDefinitionBindingCollection bindings, Boolean addOnly) at Microsoft.SharePoint.SPRoleAssignmentCollection.Add(SPRoleAssignment roleAssignment)
and
Microsoft.SharePoint.SPException: Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT)) ---> System.Runtime.InteropServices.COMException (0x80004004): Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT)) at Microsoft.SharePoint.Library.SPRequestInternalClass.UpdateRoleAssignment(String bstrUrl, Guid& pguidScopeId, Int32 lPrincipalID, Object& pvarArrIdRolesToAdd, Object& pvarArrIdRolesToRemove) at Microsoft.SharePoint.Library.SPRequest.UpdateRoleAssignment(String bstrUrl, Guid& pguidScopeId, Int32 lPrincipalID, Object& pvarArrIdRolesToAdd, Object& pvarArrIdRolesToRemove) --- End of inner exception stack trace --- at Microsoft.SharePoint.Library.SPRequest.UpdateRoleAssignment(String bstrUrl, Guid& pguidScopeId, Int32 lPrincipalID, Object& pvarArrIdRolesToAdd, Object& pvarArrIdRolesToRemove) at Microsoft.SharePoint.SPRoleAssignmentCollection.UpdateAssignment(Int32 principalId, SPRoleDefinitionBindingCollection bindings, Boolean addOnly) at Microsoft.SharePoint.SPRoleAssignment.Update() at Microsoft.SharePoint.SPSecurableObjectImpl.BreakRoleInheritance(Boolean CopyRoleAssignments) at Microsoft.SharePoint.SPListItem.BreakRoleInheritance(Boolean CopyRoleAssignments)
Any help is much appreciated?!
Hi ,
I had a similar problem. same exception but diferent stack.
what solvet it for me is that i become administrator of the SQL db.
maybe before i could not execute or somthing like that.
give your self as much permissions as you can regarding the SQL - see if tht helps.
I found the cause of the problm,
It was a threading issue, 2 threads 1st one created the folder and was setting its permissions, while the 2nd thread opened the folder and was uploading a file to it.
I added the proper locking and the problem disappeared.
Thanks,
We work with WSS 3.0 SP1, SQL Server 2005 and we have the problem that we can´t add new users in groups because of this error:
Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT))
We can work normally with SharePoint for example uploading files, images, working with files and so on.
But we can´t add new users in group. We only can add new users by giving manual permissions.
So to solve this problem I did follow things:
1. Backup of the whole SharePoint system with all databases
2. Download of the Microsoft Hotfix 948945 and installing this on the server system
3. Shrinking the SharePoint files in the SQL transaction log file
But all this steps couldn´t remove the error.
Have someone an idea how to solve this problem?
Thanks a lot.
My content db was set to expand up to a certain size - well I hit that size and got the error. Allocated more space to the db and now it works fine. Thanks for the tip about available space.I added the proper locking and the problem disappeared.
Sorry, can you share what you did to add locking or where you went, typed and commanded or in what menu drop downs? I'd sure like to get rid of the operation aborted or can not display the page.....
Thx
Laura
Hi Laura,
Well, I am working on a migration tool that uploads the files to SharePoint, the tool is multi-threaded.
My tool also creates folders on the fly, and what happened is one thread created the folder and was setting the folder permissions, while the other thread was trying to upload a file to the same folder.
I added a critical section around my code and the problem disappeared.
That translates to two users opening 2 sessions, one is setting permissions on a folder while the other is uploading a file to the same folder.
I hope that clears my statment.
Cheers,
- Voca -- did you figure out how to resolve this problem? I am experiencing the same exact thing.
Thanks.
- Proposed As Answer byChris Wilkins Thursday, July 02, 2009 3:39 PM
- After opening a case with Microsoft, we found the following to be true.
RESULT:
You did a new profile import and you see that your groups have been imported.
When you add a new user to the group, you get a Operation aborted (Exception from HRESULT: 0x80004004 (E_ABORT)) abort error message on your
people picker page and the user is not added to the group.
CAUSE:
If you break the role inheritance on a group you get two membership adherence lines
into the database for that group and then when you try to add new users, and you
get a SQL exception error, something like " Violation of PRIMARY KEY constraint
"Webmembers_PK". Cannot insert duplicate key in object 'dbo.members'. SharePoint
functionality is not hindered by this error message but if the "xact abort" SQL
option is enabled on the SQL server in the properties of the default instance under
connections, then the transaction is rolled back by the SQL server and this
generates a HRESULT abort error in SharePoint. This option is turned unchecked by
default
RESOLUTION:
After un-checking the 'xact abort' option on the SQL server, you are able to add
your new users to the SharePoint group as desired and system activity is normal.- Proposed As Answer byChris Wilkins Thursday, July 02, 2009 3:40 PM

