Registering SQL Server in Enterprise Manager

I have a couple of users that have been using the SQL Server 2000 Enterprise
Manager. They had our production server (as well as a test server)
registered on their machines as valid servers. Yesterday these users started
experiencing a problem with accessing the production server via Enterprise
Manager. When they tried to access the server they would receive the message
"Cannot open user default database. Login Failed". Each of these users is in
an AD group (defined as a user in SQL Server) that has access to our
production database. I verified the access of the group and everything looks
fine. The default database exists and the group is defined as a user. None
of these users are owners of objects in their default database.
The only way I have found to fix this was to go through security on our
production server and add their actual network user name. The whole reason I
have the group set up is so I don't have to add users individually. I also
verified the setup of our test server. This also uses a group instead of
individual network sign ons. They aren't having any problems accessing the
test server from Enterprise Manager.
How do I fix this so I don't have to have individual network sign ons?
Thanks for any help.
Nancy
That sounds pretty strange. Did you try deleting the group's login in SQL
and re-creating it?
-Argenis
"Nancy Kafer" <nkafer@.homesteaderslife.com> wrote in message
news:ONbr4QOIFHA.3628@.TK2MSFTNGP15.phx.gbl...
> I have a couple of users that have been using the SQL Server 2000
Enterprise
> Manager. They had our production server (as well as a test server)
> registered on their machines as valid servers. Yesterday these users
started
> experiencing a problem with accessing the production server via Enterprise
> Manager. When they tried to access the server they would receive the
message
> "Cannot open user default database. Login Failed". Each of these users is
in
> an AD group (defined as a user in SQL Server) that has access to our
> production database. I verified the access of the group and everything
looks
> fine. The default database exists and the group is defined as a user. None
> of these users are owners of objects in their default database.
> The only way I have found to fix this was to go through security on our
> production server and add their actual network user name. The whole reason
I
> have the group set up is so I don't have to add users individually. I also
> verified the setup of our test server. This also uses a group instead of
> individual network sign ons. They aren't having any problems accessing the
> test server from Enterprise Manager.
> How do I fix this so I don't have to have individual network sign ons?
> Thanks for any help.
> Nancy
>
|||I thought about doing that but I hadn't yet because I didn't want to have to
recreate the security for the tables in the database. One thing I did do
though was added a new AD group with these users and then added that to the
SQL Server security. This still didn't fix the problem. I'm thinking the
only way to fix it may be to try deleting the original AD group from SQL
Server and then re-adding it.
Thanks.
Nancy
"Argenis Fernandez" <argenis@.spam.sucks.gmail.com> wrote in message
news:ewrCUZQIFHA.1396@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> That sounds pretty strange. Did you try deleting the group's login in SQL
> and re-creating it?
> -Argenis
> "Nancy Kafer" <nkafer@.homesteaderslife.com> wrote in message
> news:ONbr4QOIFHA.3628@.TK2MSFTNGP15.phx.gbl...
> Enterprise
> started
Enterprise[vbcol=seagreen]
> message
is[vbcol=seagreen]
> in
> looks
None[vbcol=seagreen]
reason[vbcol=seagreen]
> I
also[vbcol=seagreen]
the
>