Re: Problems adding users
From: Todd Klindt (usenet_at_klindt.org)
Date: 09/10/04
- Next message: jerryc: "Live Audio - WSS"
- Previous message: Colin St Rose: "Re: Adding a click-on calender"
- In reply to: Todd Klindt: "Re: Problems adding users"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 10 Sep 2004 14:53:45 -0500
Okay, I had to do some SQL surgery this afternoon that may or may not help.
First, here's the situation we were trying to fix. A domain username was
created and spelled wrong. We didn't realize this until after the user had
been added to several WSS sites. First we tried to rename the user, but WSS
wouldn't budge. Each time we added the new username, it would show up in
"User Management" as the misspelled username. We deleted the username in AD
and recreated it, spelling it correctly. Again WSS had thoughts about that
username and password and the user either could not log in, and showed up in
"user management" with the misspelled username.
When I got called in the user existed in two sites and a cross site group.
To try to alleviate the email address problem one of the other admins
changed the user's email address in AD, which showed up in one site. He
could log into one site that he was added to after the email address was
changed. His user could not be added to one site as WSS said it was already
added, but it didn't show up in User Management for the site. I went into
Enterprise Manager and queried the "UserInfo" table in the content database.
I searched for his username using a line like this:
where tp_Login = 'domain\username'
The records that returned showed the sites he was associated with. The
records have the GUID of the sites. I had to search for that GUID in the
"sites" table to get the URL. Once I knew which of the user's records were
for the site I wanted, I removed that record in SQL. I then searched the
"UserInfo" table for occurrences of his correct email address. There were
none. I went into AD and fixed his email address and added him back to the
site. It all seems to work correctly.
I learned one valuable lesson through all this. WSS doesn't handle username
issues very well.
I hope that was all coherent and helps someone. Of course before you
following some schmuck on Usenet's suggestions, back your SQL databases up,
and maybe even restore them once or twice to make sure it all works. I may
well have no idea what I'm talking about here. :)
tk
"Todd Klindt" <usenet@klindt.org> wrote in message
news:%23got2l0lEHA.3520@TK2MSFTNGP11.phx.gbl...
> I've found some user information in the content database. Look in the
> "userinfo" table. You can search by login with "tp_Login" or by email
> address as "tp_Email." I would imagine you could do any editing or
> removing of information that way. I'd back that database up twice before
> I did it though. :D I'm a SQL moron, so I'm not smart enough to know
> when I'm in over my head.
>
> tk
> "Clayton@EvolveIT" <Clayton@EvolveIT@discussions.microsoft.com> wrote in
> message news:09BDA94F-06AA-4F61-B852-CC34E7248386@microsoft.com...
>> Hi Colin,
>>
>> I have removed the"old" user (DOMAIN\smithb) from the site. The actual
>> user
>> account in the AD was never deleted, the account name for this user was
>> just
>> changed (from smithb to bsmith). But now when adding the user back to
>> WSS
>> with DOMAIN\bsmith, after WSS recognises the account and offers to send
>> an
>> email, I press finish and then back in the user list it still lists the
>> account as DOMAIN\smithb.
>>
>> There is another post (unanswered) I've discovered that looks like the
>> same
>> problem Subject: "Truly purge a user account" posted by Jeff Koviak
>> 9/8/04
>> (sorry, can't work out how to link to the URL of that post!)
>>
>> "Colin St Rose" wrote:
>>
>>> Did you remove the user from the site????? The server
>>> does cache the sid and a profile. SO you must remove it
>>> from the server, not just from the site. The Site User
>>> page..
>>> /Colin
>>>
>>>
>>> >-----Original Message-----
>>> >Am running Small Business Server 2003 with WSS out of the
>>> box. All is
>>> >working well, except for this strange problem:
>>> >For whatever reason, an existing domain user's account
>>> name was changed in
>>> >the AD. For example, it was DOMAIN\bsmith but now it has
>>> changed to
>>> >DOMAIN\smithb. If i try to make a change to say the site
>>> group permissions
>>> >to the existing account as it was added to Sharepoint, I
>>> get a "The user does
>>> >not exist" error which is fair enough. So I delete this
>>> sharepoint user,
>>> >then add a new user entering the new acount name,
>>> DOMAIN\smithb. Sharepoint
>>> >recognises this fine and happily sends of the invite
>>> email. However, when I
>>> >go back to the user list, the Username is now listed as
>>> the old username
>>> >again, i.e. DOMAIN\bsmith. And if I try to change
>>> permissions I again get
>>> >the user does not exist error. Why is Sharepoint
>>> grabbing this non existant
>>> >AD account, even though it acknoweldges the new account
>>> during the add user
>>> >process???? Almosr like its caching it or something.
>>> >
>>> >Any help appreciated!!
>>> >.
>>> >
>>>
>
>
- Next message: jerryc: "Live Audio - WSS"
- Previous message: Colin St Rose: "Re: Adding a click-on calender"
- In reply to: Todd Klindt: "Re: Problems adding users"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
