SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I had a clean environment prior to installing service pack 1 and the June CUs. User Profile Sync is up and running, and synchronizing, but all web applications are throwing a SharePoint error. Digging into the logs, we're getting "Exception occurred while connecting to WCF endpoint" claiming the connection request to ProfilePropertyService.svc exceeded the allotted timeout of 00:00:20. If I hit ProfilePropertyService.svc manually I get "The server was unable to process the request due to an internal error."

I have tried blowing away UPS, rebooting, rebuilding UPS and rebooting, and that did not resolve the issue. All services are started, and all application pools are online.

Any thoughts?

share|improve this question
Update - Looks like it is unique to a single web front end. Removed it from the load balancing and the farm functions normally. – Mike Oryszak Sep 9 '11 at 1:59

We've run into a couple of problems with the User Profiles after SP1 and June CU. While they may not be exactly the problem you are encountering, they are something to check to ensure there are no problems from these as well.

1st: FIM's configuration file is changed to use .net 4.0. This doesn't work, details are in this article by Todd Carter.

2nd: User Profile photos can only be updated by the user themselves -- NOT User profile Admins. Details in this article by Trevor Seward.

I hope one (or both) of those articles will save you from the late nights my co-worker went thru before finding them.

share|improve this answer
up vote 1 down vote accepted

It looks like this wasn't a UPS specific issue; one of the web front ends essentially bricked itself as part of the upgrade. Detaching it from the farm and re-adding it didn't solve the issue; we actually ended up rebuilding the box.

share|improve this answer

This is most likely due to a change in the service accounts. Is it possible that there was a manual change to the service accounts through IIS Manager that was reset to the configured account when the configuration manager was run after the service pack installation?

Please refer to Spencer Harbar's User Profile Sync Guide for the proper service account roles and permissions if you haven't already.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.