Morning Quicky: Cant Change Page Settings

So a user of mine tried to edit a page in our massive collection of sites that document software applications and their use. When they went to (in editing mode) Page -> Page setting they got the following in their face:
Error returned: User Not Found
Source of problem:

My predecessor had a search problem after he migrated users over to the MOSS 2007 server. A few users had the same GUID as each other, even tho they are suppose to be unique. So his solution was to delete the offending user out of the database manually... And that is how i got my problem. Parts of the sharepoint sites pull from the tp_ID feild and reference that. Others reference tp_GUID. This page uses tp_ID to pull the information it needs to generate the settings page.

My hack-solution:
This is unsupported by microsoft, note that i only did this as a temporay measure.
I created, manually, a fake user in the database that used the same tp_ID as the one he deleted a while ago.. yes i had to do some annoying sql to get it to allow me to insert. But it did fix the problem, lets see what other problems my "fix" brings up.

The Proper solution V1:
The idea here is to rebuild the SID for all of the users on the site, but in order to do this you have to remove all of the currently-setup security levels and access for all users on the website. The most straight forward method to do this is to import your website and export it:
  1. stsadm -o export -url -filename -versions 2
  2. Delete the site collection.
  3. stsadm -o import -url -filename -updateversions 2 -nofilecompression
Again, the idea is to make the SID's reorder themselves, in order to accomplish this you have to NOT use -includeusersecurity in your command. You will loose all user-level security on the site(s) when you do this. In my current case this is not the best of solutions, as we have several 100 pages that have security set up on them. If and when i find another solution, i'll post it up here.

Comments

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

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

Project 2010 and Project Pro 2007

Just a FYI since no one knew this from what i can tell already: If you are enabling BCM (Backwards Compatibility Mode) for project 2007 to connect to Project Server 2010, there are a few things you should know first. Right off the bat, clients have to be updated to Service Pack 2 . Next, when your setting up your project server, Note this key fact I could not find anywhere, and did not get hint about in the technet forms when i posted about my problems: You CAN NOT use Claims based authentication on your web application that is hosting Project Server 2010. The 2007 Client will not connect to the server. The 2010 client will connect with no problems. Quick and dirty, hope that helps everyone!
Read more