Databases
StackOverflow2013
Postsdbo
POProfile User DB error in WebPart
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POProfile User DB error in WebPart
    primarykey
    data
    text
    <p><strong>EDIT:</strong> Modified title and added update.<br></p> <p><strong>UPDATE</strong>: <em>We no longer believe this is a 64bit vs 32bit problem. We have found that the only people that were seeing this, were people that were set in the farm policy as "full control." (Not acting as System Account) Once we tested regular users, we found none had the problem. Removing the "problem" users from the farm policy and adding them back, fixed all but one user(a fellow dev:)).</em></p> <p>We started out our Farm with 2 32bit WFE's and a 32bit Application server. We have decided to add 64bit front ends to our farm, and for the most part, almost everything worked fine. The exception is a custom web part that accesses the user profile database. Works fine on 32bit front end, but we get the following error on the 64bit front end:</p> <blockquote> <p>User Not Found: Could not load profile data from the database. </p> <p>Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. </p> <p>Exception Details: Microsoft.Office.Server.UserProfiles.UserNotFoundException: User Not Found: Could not load profile data from the database.</p> <p>Source Error: </p> <p>An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. </p> <p>Stack Trace: </p> <p>[UserNotFoundException: User Not Found: Could not load profile data from the database.]<br> Microsoft.Office.Server.UserProfiles.UserProfile.Load(SqlDataReader myReader, Boolean bFirstRead, Boolean bWssId) +930<br> Microsoft.Office.Server.UserProfiles.UserProfile.Load(SqlDataReader myReader) +64<br> Microsoft.Office.Server.UserProfiles.UserProfile.RetrieveUser(String strAcct, Guid gAcct, Byte[] bSid, Nullable`1 recordId, Boolean doNotResolveToMasterAccount) +1507<br> Microsoft.Office.Server.UserProfiles.UserProfile..ctor(UserProfileManager objManager, String strAcct, Boolean doNotResolveToMasterAccount, Boolean forceUserIsSelf) +584<br> Microsoft.Office.Server.UserProfiles.UserProfile..ctor(UserProfileManager objManager, String strAcct) +80<br> Microsoft.Office.Server.UserProfiles.UserProfileManager.GetUserProfile(String strAccountName) +205</p> </blockquote> <p>Since the WFE is on the same farm, it should be looking at the same database.</p> <p>Let me know if any more info is needed.</p> <p>Any ideas would be appreciated!</p> <p>Thanks.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAdamBT
    1. USAdamBT
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POProfile User DB error in WebPart
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POProfile User DB error in WebPart
      1. USAdamBT
      1. VTFavorite
    3. VO
      singulars
      1. POProfile User DB error in WebPart
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI would bet that the 32 vs 64 bit problem is a red herring and would look at the user profile store. But you may have done that already.
      singulars
      1. POProfile User DB error in WebPart
      1. USNat
    2. COwe are beginning to believe it is a "red herring." Looking at the code to see exactly how we are calling the user profile db.
      singulars
      1. POProfile User DB error in WebPart
      1. USAdamBT
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload