Re: Lost "guest" user, cannot get back.
From: Kimberly L. Tripp (Kimberly@nospam.sqlskills.com)
Date: 11/12/02
- Next message: Hal Berenson: "Re: expire sql server 2000 passwords"
- Previous message: someone: "NT/ SQL authentication"
- In reply to: Bo Eaton: "Lost "guest" user, cannot get back."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Kimberly L. Tripp" <Kimberly@nospam.sqlskills.com> Date: Mon, 11 Nov 2002 15:10:40 -0800
Hey there Bo - I'm probably missing something here BUT sp_grantdbaccess is
the wrong procedure to use... You don't want to grant access to a login
(which is what sp_grantdbaccess does) you want to add a "guest" account to
the database. These are two VERY different things. What you really need to
do is
sp_adduser 'guest'
within the databases where you want a guest account. You DO NOT want a login
named guest and you do not want to use sp_grantdbaccess.
Now as for why this account is disappearing - that doesn't seem to make
sense other than some SysAdmin is maybe running some setup script that drops
it? From a first guess, I'd say that the dump is not related to this
issue??? So - here's what you need to think about - What else are you doing
between the "re-install" and the time the dump occurs? Are you adding a
guest LOGIN? Are you running a script to do "setup" of the server? Did
someone recently say that there were security issues on the server and
create a script to help? If they did then I bet this is the script that's
blowing away the guest USERNAME. Do you have any scripts that execute a
bunch of these sp_grandbaccess commands? I can only guess that some
automated script is somehow corrupting the real guest USERNAME when they run
it?
Only speculation on why you're getting the stack dump BUT the sp_adduser
should help if the guest account gets removed. You might want to start a
profiler trace that ONLY traces for this command (sp_dropuser) and then you
might be able to isolate when/how it gets removed.
hth,
kt
"Bo Eaton" <eatonbof@paho.org> wrote in message
news:#bcP4qaiCHA.1800@tkmsftngp09...
> Two problems that may be related:
>
> 1. Some databases, including master, lose the guest login. I run
> "sp_grantdbaccess guest", with a successfull return, until I am blue in
the
> face, but there is still no guest user in sysusers or in the enterprise
> manager user list. "sp_revokedbaccess guest" gives the correct error that
it
> cannot revoke access, because the user does not exist in the database.
>
> 2. After running the server for a period of weeks, it enters a state in
> which it returns an error such as "[Microsoft][ODBC SQL Server Driver][SQL
> Server]SqlDumpExceptionHandler: Process 136 generated fatal exception
> c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this
> process." and variations. The SQL user (not NT security) is a user in the
> database. If I make the user a "System Administrator" for the entire
server,
> the error goes away. Obviously, however, I do not want to make every user
a
> System Administrator. If I re-intall SQL Server the problem disappears for
a
> while, as well.
>
> Thanks.
>
>
- Next message: Hal Berenson: "Re: expire sql server 2000 passwords"
- Previous message: someone: "NT/ SQL authentication"
- In reply to: Bo Eaton: "Lost "guest" user, cannot get back."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
