profile user db blunder webpart
edit: run-down due total update.
update:
we longer trust 64bit vs 32bit problem. have found wholly observant this, set camp slight "full control." (not behaving component account) once tested unchanging users, found zero problem. stealing "problem" users camp slight adding back, bound nonetheless user(a associate dev:)).
we started out the camp 2 32bit wfe's 32bit concentration server. have solid supplement 64bit front ends the farm, many part, roughly all worked fine. difference tradition web biased accesses user form database. works glorious 32bit front end, nonetheless following blunder 64bit front end:
user found: bucket form information database.
description: an unhandled exception
occurred during execution the
tide web request. greatfully hearing the
smoke-stack snippet some-more information about
blunder where originated in
code.
exception details:
microsoft.office.server.userprofiles.usernotfoundexception:
user found: bucket profile
information database.
source error:
an unhandled difference generated
during execution current
web request. information per the
start plcae exception
identified controlling exception
smoke-stack snippet below.
stack trace:
[usernotfoundexception: user not
found: bucket form data
database.]
microsoft.office.server.userprofiles.userprofile.load(sqldatareader
myreader, boolean bfirstread, boolean
bwssid) +930
microsoft.office.server.userprofiles.userprofile.load(sqldatareader
myreader) +64
microsoft.office.server.userprofiles.userprofile.retrieveuser(string
stracct, guid gacct, byte[] bsid,
nullable`1 recordid, boolean
donotresolvetomasteraccount) +1507
microsoft.office.server.userprofiles.userprofile..ctor(userprofilemanager
objmanager, twine stracct, boolean
donotresolvetomasteraccount, boolean
forceuserisself) +584
microsoft.office.server.userprofiles.userprofile..ctor(userprofilemanager
objmanager, twine stracct) +80
microsoft.office.server.userprofiles.userprofilemanager.getuserprofile(string
straccountname) +205
since wfe same farm, should looking during same database.
let me know any some-more info needed.
any ideas appreciated!
thanks.
Comments
Post a Comment