Hi guys, I have some user profile pictures returning 404s. I can't seem to pinpoint the reason. Perhaps someone can give some insight. The playback:
1. Either a user uploads a picture when editing their profile or I do it for them via Central Admin.
2. All 3 pictures (large, medium, small) shows up properly in the picture profile store in the root site collection of the My Site Host.
3. When I click into the image all the way to the physical address of the large image, it returns a 404.
Bits are at December 2011 CU. Any ideas or tips? Note: this doesn't happen for all images. I haven't figured out what images cause this yet though.
Thanks for your post.
According to the images, I found that the url for the image(“http://server/User%20Phontos/Profile%20Pictures/_w/Prod_cchen1_LThumb_jpg.jpg”) is different from the url, which you type in the ie address.(“ http://server/User%20Phontos/Profile%20Pictures/Prod_cchen1_LThumb_jpg.jpg”)
So please check whether you have type the correct url.
Then, you can also delete the user image at first, and then upload it in the User Properties.
Share your result.
TechNet Community Support
Hi Wayne, thank you for your response. The URLs are correct. The URL with the _w is used by the DispForm.aspx page. Most of the images will return an image found when clicking on it from the DispForm.aspx page. Some pictures are returning a 404. I've also tried deleting and re-uploading the images to no avail.
This seems like a bug with photos of CMYK format as discussed below:
Is this something that is one the SharePoint team's fix list?
My current workaround is to manually identify these bad pictures and replace the large thumbnails with a copy of the medium thumbnails, which works.
- Edited by Henry Ong Saturday, March 03, 2012 2:03 AM
Thank you for your post on these errors. I just started getting them the other day, http://blog.henryong.com/2012/03/02/case-study-on-troubleshooting-a-failed-sharepoint-user-profilefim-synchronization-bad-cmyk-user-photos-and-disappearing-user-profiles/.
Have you found a workaround to manually identify these bad pictures?