Quantcast
Channel: SharePoint 2010 - General Discussions and Questions forum
Viewing all articles
Browse latest Browse all 17574

SharePoint 2010 User Profile Application Proxy Issue

$
0
0

We have a SharePoint 2010 farm at our head office which runs the User Profile Service to sync users from Active Directory to SharePoint. We also have a separate SharePoint 2010 farm at a branch office. We published the User Profile Service from the head office farm and the branch office farm subscribes to it. This has been set up for well over a year and was working fine until yesterday. Suddenly, whenever you try and access a site on the branch farm you get an "An unexpected error has occurred" error message. Looking in the ULS logs, it appears the branch farm is unable to connect to the SQL database back at head office which hosts the User Profile Service Databases. This message appears:

"Failure checking user access permissions for User Profile Application Proxy 'User Profile Service'. Exception: System.Data.SqlClient.SqlException: Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding."   

I can ping the SQL servers (there are two mirrored SQL servers). I can telnet to them on port 1433. The IIS application pool service account for the branch office web application has "full control" access to the User Profile Service on the head office farm. It also has "db_owner" access to the UPS Profile, Sync and Social databases on both SQL servers. I have tried failing over the databases, IISRESETs and rebooting the branch office SharePoint server. None of this has helped. The User Profile Service still works fine on the head office farm (and a third SharePoint farm which also subscribes to the head office User Profile Service). The Managed Metadata and Search services are also published from head office farm and these still work fine on the branch farm. If I take the User Profile Service Application Proxy out of the Service Connection proxy group for the web application, the SharePoint site is accessible again. If I put it back in, the problem comes back. No changes have been made to either the branch or head office farms in the past few weeks.

I'm kind of stuck for ideas. Can anyone advise what the problem might be?

Thanks!


Viewing all articles
Browse latest Browse all 17574

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>