When trying to grant permissions for a specific user to an area in ourSPS portal, I am receiving a "user cannot be found" error. The personhas a domain account, but has had the account renamed in the past dueto getting married. I can add people into this area that have notbeen renamed without a problem.Does anyone know how to resolve this issue.
Re-import your profile database so that it picks up the name change. This is done byPortal Server > Site Settings > Manage Profile DatabaseStart Full Import or Alternatively Add User Profile.
Actually, this persons name was changedquite a while ago, and I have tried the full import (which we doevery night automatically anyway).The really odd thing is that I can add her to a WSS site without aproblem, only in a portal area does the issue occur. It seems likethis might be a known issue, as I found this posting onlinewww.sharepointwatch.com/.../~2777~__user-cannot-be-found-errors/index.aspx. I was hoping someone may have a resolution.
What about using "Add User Profile"
She does have a user profile, and it is populated perfectly. I haverun tests with other people who's names have changed, and experiencethe same problem in the Portal. All of them have profiles that arefully populated from active directory.
I am by no means an AD expert. So, I can't suggest what may bepreventing you from finding her modified account.However, this insight may provide you with some ideas:1. The WSS Add user page interfaces the local Outlook Address Booksomehow. Click on the Address Book button to see what I mean.2. The SPS Add User page is identical except it interfaces directly withActive Directory somehow. Click on the Select users and groups link tosee what I mean.I wanted Add User pages to use AD but I couldn't get the SPSWC to workon WSS even though the WSS site is running on a server with SPS. Gofigure.
Am I right in saying you are using AD 2000 and Exchange 2003/2000?The reason I ask is because I tried to replicate the problem with my currentsetup but it worked fine.Now the reason could be that im using a native AD 2003 enviornment where as Ithink you are using AD 2000.I think there may be some kind of Architectural difference and thats why yourecieve the error.
Actually, we are still using exchange 5.5 (working on upgrading aswe speak to 2003). So, you could be right, that could be the issue.Unfortunately, I still have not found a resolution to this, but itmight fix itself when we complete the upgrade.