Thursday, December 10, 2015

User Profile Picture bug in SharePoint 2013 CU October 2015

Recently I was working with one of my clients in their SharePoint 2013 test environment. They have a small farm on SharePoint 2013 SP1 and the july CU 2015. I had just installed the october 2015 CU and everything worked fine and smoothly until…… suddenly I noticed something was wrong? Was it a bird, a plain? No, it looked like a bug!!

Scenario: SharePoint 2013 server Enterprise Farm, installed SP2013 SP1 + CU October 2015:



This is the default User Profile Picture Library on the Mysite Host. I have some accounts. Me (Peter), test account ‘Clint’, 'Alex' and the SPSadmin (Administrator of the farm):


Logged on as the SPSadmin account:


As an administrator (spsadmin), when you go to the Central administration -> User Profile Service Application -> Manage User Profiles. Find another user like ‘Clint’ -> select ‘edit my profile’. You'll get the following:


When you (as the SPSAdmin) change the profice picture here and upload a new picture, Save and press ok. The user Clint's picture is changed to the new picture.


When you view this as the logged on user 'Clint' it will show this (correct):


But also the picture of the logged in administror (spsadmin) who just changed the picture, will be changed to the same picture of Clint. You can see this by going to the User Profile page of the SPSAdmin account and it will now also show the picture of Clint!!!:

When you go to the Mysite Host and the User Profile Pictures library, you’ll see that there are still 2 different pictures for both the ‘Clint’ account and the administrator ‘spsadmin’! And the SPSadmin account picture has changed into the Clint picture while Clint Eastwood still has it's own picture.


When you are logged on as the ‘Clint’ account, the profile picture will look like this:

While, when logged on as the SPSadmin account, the account will look also like this:


And this is the issue! Both have the same user profile picture while in the User Profile library it looks like they should have 2 different pictures:


When I ‘hoover’ over the image and look at the properties of the image for both ‘Clint’ and ‘SPSadmin’ it will look like this:
SPSadmin:


The Clint account:


And this is the issue! It has the URL to the SPSADmin account mapping! While we uploaded the picture to the Clint account! Now both accounts have a mapping to the spsadmin account. So it looks like the User Profile Administrator account gets the mapping if you change somebody’s profile picture through the User Profile Service Application.

When a logged on user changes his profile picture through the standard ‘About me’ link, the picture upload will be fine. The issue only exist when you change ANOTHER user profile picture as an User Profile Administrator through the User Profile Service Application -> Manage User Profiles -> Edit my profile. I’ve seen this happening in at least 3 environments with clients who upgraded to the October 2015 CU for SP2013.

Anyone else experienced this issue?

**Update** On december 10th I've installed the december 2015 CU and this issue is still in here.
***Update 7 april 2016*** This issue has been fixed in the March CU 2016 update

10 comments:

  1. I'm having the same issue in my 2013 envriornment where I attempt to add a new employees' pic however my account name is attached to the picture of the other user. Same happens if I use an admin account to upload a pic, the new pic has the admin's user name attached to it.
    Has anyone seen a fix for this?

    ReplyDelete
  2. I'm on the October CU.

    ReplyDelete
  3. Hi,

    Microsoft is aware and this will be fixed. The fix is currently planned for March 2016 CU.

    See also comments of: https://blogs.technet.microsoft.com/stefan_gossner/2016/01/12/january-2016-cu-for-sharepoint-2013-product-family-is-available-for-download/

    Best regards

    ReplyDelete
  4. Thx. I saw the post van Stefan and also gave a comment on it. It's a very strange procedure how Microsoft deals with bugs. In my scenario, I first test the CU before I install it on the client's environment. Then I encounter the error en advise the customer NOT to install it. I spread the news about the bug to Microsoft (through mails, because I could not find a site to post bugs) and also through Todd Klind's website. Nothing happens. Now I read that Microsoft only does bugfixing if the customers already has installed the CU and a support case has been filled. That's a strang procedure. I'm happy that someone else also encountered the bug and made a support call to Microsoft about it and that it should be resolved in the March Cu of 2016.

    ReplyDelete
  5. Hi Peter,

    Thank you very much for your post, we have hit this same issue in our on-premise SharePoint 2013 environment, it was good to know we aren't the only ones experiencing this issue!

    ReplyDelete
  6. FYI: This is fixed in March 2016 CU: https://support.microsoft.com/en-us/kb/3114817

    ReplyDelete
  7. I also facing same issue and I have October 2015 CU

    ReplyDelete
  8. Thanks Peter for this...I will installing this soon, hopefully this install did not break any existing functionality?

    ReplyDelete