Re: Logins
From: John Kraeck (jkraeck@hillier.com)
Date: 09/10/02
- Next message: Thomas: "Analysis Services Security"
- Previous message: Steve Thompson: "Re: Permissions for the predefined database roles"
- In reply to: Bill Hollinshead [MS]: "RE: Logins"
- Next in thread: Bill Hollinshead [MS]: "Re: Logins"
- Reply: Bill Hollinshead [MS]: "Re: Logins"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "John Kraeck" <jkraeck@hillier.com> Date: Tue, 10 Sep 2002 13:43:01 -0400
Bill,
I am looking at <Servername>|Security|Logins to get the login information.
The user in question shows no information on the Database Access tab of the
Properties dialog: no databases are checked, no database roles are assigned.
On the Server Roles tab, no server roles are checked. The information
displayed by sp_helplogins is exactly what I would expect. FWIW, this user
was created in SQL 6.5 and was then upgraded. No user created since the
upgrade shows the same behaviour.
KB Q224587, does not look a likely prospect. The timeout occurs when
connecting and seems to be related to the network settings. We have several
third party applications in use which connect to the server using Access 95,
Access 97, Access 2000 and numerous VB and ASP applications using various
flavours of MDAC. I think the issue involves inconsistencies in the drivers
on some of the workstations. We did not have these issues prior to applying
SP4. Oddly, the symptoms seem remarkably like those described in KB Q300519,
which is on the fix list for SP4. I think that rigourously applying MDAC to
the same level and applying the latest Jet 3.5 and 4.0 service packs should
do the trick. It is just tedious.
The issue of an orphaned user sounds plausible, in that the user was created
when the server was at version 6.5. That server was upgraded to SQL Server
7; and we have since replaced the server itself. When the database was
moved, I recreated the SQL Server logins we had added, making sure that the
SIDs matched those on the old server, prior to actually moving the database.
The database itself was detached, the files copied to the new server, and
then reattached. But again, sp_helplogins returns exactly what I expect.
Regards,
John
"Bill Hollinshead [MS]" <billhol@online.microsoft.com> wrote in message
news:bmhxYpDWCHA.1780@cpmsftngxa10...
> I very much doubt the Enterprise Manager/login problem has anything to do
> with the timeouts <g>. For timeouts, it would be best to go through
> http://support.microsoft.com/support/kb/articles/q224/5/87.asp in the
order
> suggested.
>
> I am not sure where these symptoms are being seen <g>. Are you looking at
> "Microsoft SQL Servers"|<group_name>|<server_name>|"Security", or are you
> looking at "Microsoft SQL
> Servers"|<group_name>|<server_name>|<database_name>|"Users"? The former
> concerns logins (stored in master..sysxlogins) while the latter concerns
> users (stored in a database's sysusers table). Perhaps it would best to
run
> a sp_change_users_login Report (and search BOL for "orphaned users"). I
> also am not clear by what is being seen when that dialog is blank: does
> that mean the database checkboxes are visible but unchecked, or does that
> mean checkboxes are not visible at all? Perhaps refresh the Users or the
> Logins in SQL Enterprise Manager before opening, or, close and reopen SQL
> Enterprise Manager.
>
> Thanks,
>
> Bill Hollinshead
> Microsoft, SQL Server
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
>
- Next message: Thomas: "Analysis Services Security"
- Previous message: Steve Thompson: "Re: Permissions for the predefined database roles"
- In reply to: Bill Hollinshead [MS]: "RE: Logins"
- Next in thread: Bill Hollinshead [MS]: "Re: Logins"
- Reply: Bill Hollinshead [MS]: "Re: Logins"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
