4 thoughts on “Delete the user property SPS-Local in SharePoint 2010 breaks the My Profile page

  1. to:  Greg @ Scripps
    Hi, I have sent an email to the current case owner with some more info. AFAIK, they already offered you the supported ways but seems none of them are suitable for you…
    Hope they can make it for you but I think the only way is really restore from backup or recreate the UPA as the SPS-prefixed properties are only set once on creation time of the UPA databases.
    sorry for no better news,
    kind regards, Steve


  2. Thanks for the reply Steve.   my # is 113100910849969.   I had already pasted your blog in the ticket comments when I lodged the original.  🙂    I'm so sad.  And, what is even sadder to me – is that I even tried miisclient.exe and, darn if that tool doesn't see the SPS-HireDate … i mean, it's nowhere in there.  My SPS-HireDate is in UAT, but, as I typically test and develop in PROD, my PROD is where it's missing now.  🙂   I can't even find an 'unsupported' way to get it back.  I'll re-refer tech to the blog when I speak to him/her.    From your title, i'll probably be SOL on this one.  


  3. So, tell me this – as I just opened a premier support case bacause I mapped the SPS-HireDate , populated it – and then needed it to go away.   I 'unmapped' the SPS-HireDate – and did the expected 4 full UPA syncs – and the info would not go away from the FIMS profile.   I was sipmly unable to make the SPS-Hiredate disappear, so, natually, I said "Self, just delete it and recreate it , that'll do it."   Sure did, but problem is that I can't get it back, obviously.  I am also unable to recreate the UPA because it breaks NewsGator etc.  Seriously, this is really stupid that I am allowed to delete something but I can't put it back.   In this instance, there needs to be more warning info about this limitation in the product.   Any updates?


  4. Hi Greg,  
    I'm very sorry to hear that.  AS stated above, all properties prefixed with "SPS…" are Default properties that are spwaned on creating the UPA and its databases.
    Once you delete such a property it cannot be added/recreated back again sinc our code prevents it.
    You're right that we should have a warning or so on deletion but even with the SP2 Triage, the PG did not fix it yet.
    If you have another premier Case running for the failing recreation, please point the engineer to my blog here and I'll be happy to provide all "BUG specific" Information to him internally. Maybe this will Help to get more attraction at PG side to fix it.
    So I fear you only have to follow my post if you want to have the Default SPS-prefixed property back. else ist gone forever and cannot be recreated else in a supported way.
    Please encourage your Support engineer to get in contact with me for any further info.
    Thanks and good luck,
    cheers – Steve   😉


Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s