All,

I am getting the following error - when I drop a webpart into my page using SharePoint 2013 on a server running Windows Server 2012 R2 - Note: I do not have access to the code. I have run a sfc /scanner command to try and remedy any items that maybe missing or corrupt.

Could not load file or assembly 'Microsoft.SharePoint.Client.UserProfiles, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.

At first glance, this looks like a permissions issue. Question:

1. Did you use an account that is a local administrator on the boxes hosting the WFEs, or is a site collection administrator or is configured with Design level or Full Control for the site hosting the page you are trying to edit?

I'm hoping it's an easy permission issue - so in regard to the permission question - when I added the webpart to the page I was logged into a PC as myself and - I'm a SharePoint Administrator whose group is in the local admin group. I'm also the site collection admin. Also - when I installed the webparts - they were installed while logged in as the core SharePoint farm user which I previously also added as a site collection admin.

• What do you mean by "installed" the web parts - you don't need to perform any manual installation of the suite of web parts that come with SharePoint Server 2013.  Please clarify.
• What type of webpart are you trying to add?
• Have you tried logging into the site collection as the same account that you used to install the web parts?

These are webparts purchased - they are Qumu webparts -> http://webfiles.qumu.com/images/datasheets/SharePoint2013/SharePoint2013-TIM-DS040-EN-0215.pdf?1423157935

I have logged into the site collection with the same account.

However - you got me thinking - it appears that the account I utilized for the install as well as the app pool account which the webparts are running under - neither account has a profile which is being pulled into the profile service. 

I'm going to test this out a little bit more tomorrow but that could be it - likely from the error the accounts need to have profiles in SharePoint and they don't - or the profile accounts aren't being synced in from AD.