Jaa

June CU Breaks UPA - If you patch the child farm and not the federated farm

  • Artikkeli

In Microsoft IT we encountered an issue with patching our child farm that was federated to a UPA farm that was the RTM build (without the June CU). UPA service failed until we patched the UPA Federated farm to the June CU.

Here is a Matrix of what scenario works:

Child farm RTM

Child farm June CU

UPA farm RTM

Works

Broken

UPA farm June CU

Works

Works

Error thrown when our farm was changed from consuming from JuneCU UPA to an RTM UPA:

User Profile Application Proxy failed to retrieve partitions from User Profile Application: Microsoft.Office.Server.UserProfiles.UserProfileApplicationNotAvailableException: No User Profile Application available to service the request. Contact your farm administrator.

 at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_ApplicationProperties()

 at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_PartitionIDs()

 at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.IsAvailable(SPServiceContext serviceContext)

The SharePoint developer Team is aware of the bug and will be fixed in the August CU. Beware and plan accordingly for this scenario. Thanks!

Comments

  • Anonymous
    January 01, 2003
    Which version of SharePoint are you running on your farms now?

  • Anonymous
    November 08, 2010
    We are getting this same error without installing the June CU. We get this error when trying to access the properties page on the User Service Application. Verified that the farm account has the necessary permissions as stated by S. Harbars excellent post. Any ideas? Thanks

  • Anonymous
    September 18, 2011
    Hi all,         I also facing this problem that is "   Microsoft.office.server.Administration.UserProfileApplicationProxy.get_ApplicationProperties()  +134 Microsoft.office.server.Administration.UserProfileApplicationProxy.get_PartitionIDs() +44 Microsoft.office.server.Administration.UserProfileApplicationProxy.IsAvailable(SPServiceContext ServiceContext) +134" How to solve this