Hi,
I have an Office 365 tenant with a handful of site collections within SharePoint Online 365.
I have created an Enterprise Search Center site which works ok and returns results.
My issue is this:
From the results page, when I select the 'People' result source (previously known as search scope) I can see all the users but the profile image does not appear correctly. This is how it appears:
When I view the properties of the image, the URL shows as:
https://<tenantname>.sharepoint.com/_layouts/15/userphoto.aspx?size=M&accountname=joe%40<tenantname>.com.au&url=https%3A%2F%2F<tenantname>-my.sharepoint.com%2FUser%20Photos%2FProfile%20Pictures%2Fjoe_<tenantname>_com_au_MThumb.jpg
Visiting this directly triggers an unexpected error with a correlation ID (not very helpful with SharePoint Online).
If I go to the top level site collection (which is based on SharePoint 2010 Online), the search works fine and displays the profile image perfectly. When I look at the properties of the correctly displaying image, the URL shows as:
https://<tenantname>-my.sharepoint.com/User%20Photos/Profile%20Pictures/joe_<tenantname>_com_au_MThumb.jpg
Visiting this directly goes to a web page with my profile picture on, as expected.
As you can see, the URL is the same as the URL shown in the problem URL after the &url= section so it would appear that the issue lies in the...
https://<tenantname>.sharepoint.com/_layouts/15/userphoto.aspx?size=M&accountname=joe%40<tenantname>.com.au&url=
....section. If I go directly to page https://gerardlighting.sharepoint.com/_layouts/15/userphoto.aspx, I also encounter an unexpected error so maybe there is a problem with this page.
I have created a whole new site collection to check that it wasn't a problem with this particular site collection but exactly the same thing happens . I'm hoping that someone else has seen this problem and that there is a quick resolution as currently this is a real show stopper.
Just to add that I have also forced a re-index of search and waited the 6 hours and the problem still exists.
Hope someone can help.
Thanks,
Joe