Stsadm -o export ... Wow

So i have been having fun with the stsadm -o export function allllllllll wweeeeeeekkkk llooonnggg.

Reference my earlier post about how to fix search not indexing to find out why. Needless to say, trying to export the site has not been... easy, or anything close to that.

stsadm -o export -url http://mysite's_sub_site -filename d:\somefile.cmp -versions 2

Error: FatalError: There is no row at position 0.

Cause: An item, a list, some object in your site is referencing permissions of someone who simply not in your database anymore. How? Who knows, easy fix tho:

Solution: First find the next site it was about to go to, i do it this way personally:

1. stsadm -o enumsubwebs http://mysiteiamexporting
2. find the last site that it was exporting before it errored out. Your problem site is the next site.
3. Go to the site, go to the administration page.
4. Go to Advanced Permissions, Actions -> Edit Permissions, click O.K.
5. Actions -> Inherit Permissions.

Bam site is fixed now. Happy exporting!

Comments

Ricardo Irineo said…
Hey I'm facing a similar problem, and thanks to your post now I have a rough idea of what to test for, I'll post the outcome, but mine is worst since this is happening in one site and all it's subsites, all of them with unique permissions, i will either have to replicate the permissions again or pin the user causing the error, any idea how to best approach that last scenario?.
December 17, 2009 at 3:00 PM
Post a Comment

Popular posts from this blog

CI Build broke after nugit update

One of those moments where your heart drops : Your using CI on a remote hosting service (like AppHarbor) and your build fails. You look into the fail reason and find out it is because you updated the packages in your build. Wait, my update from nuGet broke everything?! Wtf?! The error looks something like this, putting it in here for search engine's : Build started 6/10/2013 12:30:20 AM. 1>Project "D:\temp\xly5bsff.qvp\input\.sln" on node 1 (default targets). 1>ValidateSolutionConfiguration: Building solution configuration "Release|Any CPU". 1>Project "D:\temp\xly5bsff.qvp\input\.sln" (1) is building "D:\temp\xly5bsff.qvp\input\\.csproj" (2) on node 1 (default targets). 2>D:\temp\xly5bsff.qvp\input\\.csproj(880,3): error MSB4019: The imported project "D:\temp\xly5bsff.qvp\input\packages\Microsoft.Bcl.Build.1.0.7\tools\Microsoft.Bcl.Build.targets" was not found. Confirm that the path in th...
Read more

My 2012 Hit List - Things to see in the next few months

Been a while since i last updated my blog -- and i know, most people hate the "I am coming back" blog posts that people put up, so sorry for that in advance :) I have had some life changes in the past year - left a job, started a new one, started consulting, moved across the nation, been to several weddings, moved in with the girlfriend, ect. Now that it has all settled down i figure it is a good time to start blogging again! Now the direction of this blog will be changing a little bit. A departure from the sharepoint side of things for a little bit and into Project Server modifications and changes and answers to questions I have had to look up or figure out myself many times over now.  In the past 6 months i jumped into a new job and hit the ground running as they were freshly deploying project server 2010, and the consulting company they brought in simply did not meet the requirements they asked for by the time they left.   I have had the pleasure of deep-div...
Read more

Sharepoint 2007 - Access Denied when you try to edit

I'v had this solution for a little while now but never wrote it down anywhere for people to see. Here is the situation: In a site collection, you make a new list/document library in any sub-site or the main website. You then add a new item/document to the folder, and then attempt to edit the item You then see something along the lines of "Access Denied" , even if you are on the system account. This happens with every new list you create on any site or subsite. Your problem is a corrupted field definition at the site collection level. Specifically the "Effective Permissions Mask" is missing an attribute in it's xml scheme - RenderXMLUsingPattern="TRUE" The fix comes in 3 steps: 1. Update your server to the most recent cumulative update package (Service pack 2 or greater). You can get more information about this from the Sharepoint team blog post on SP2 . Included in SP2 is a hotfix that prevents this from occurring ever again on any other site co...
Read more