Mixed Mode Authentication not consistent between Windows Users using Mgmt Studio

Question

Post reply

Mixed Mode Authentication not consistent between Windows Users using Mgmt Studio

Leifton

SSC Veteran

Points: 298
More actions
July 5, 2013 at 7:28 am

#279957

Currently experiencing strange issue I have not seen before on a SQL Server 2008 R2 instance running on Windows Server 2008 R2. Access to SQL Server via Mgmt Studio under the 'sa' user does not work regardless of which Windows User is logged in. The only way to access SQL Server via Mgmt Studio is to log into Windows with the administrator user and use Windows Authentication to authenticate against SQL Server.
SQL Server Configuration:
Mixed Mode Authentication
Shared Memory Prorocol Access Only (Other protocols have been tried)
SQL Native Client 10 being used to access Sql Server
All of the above is only experienced when using Management Studio. When accessing via ODBC programmatically, configured SQL Server user works just fine regardless of which Windows user is logged in.
Forum Etiquette: How to post Reporting Services problems

[/url]

Forum Etiquette: How to post data/code on a forum to get the best help - by Jeff Moden
[/url]

How to Post Performance Problems - by Gail Shaw
[/url]

Steve-0 SSChasing Mays Points: 600 More actions · Answer 1

What is the returned message when you try to login with 'sa'.

Leifton SSC Veteran Points: 298 More actions · Answer 2

The most recent errors I have noted have all been:

A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)

Thanks,

-Leif

Steve-0 SSChasing Mays Points: 600 More actions · Answer 3

Can you also confirm that you left the other Client Protocols enabled?

Leifton SSC Veteran Points: 298 More actions · Answer 4

All other client protocols are disabled. The only protocol that is enabled is Shared Memory. This is part of our standard configuration for all deployments.

mister.magoo SSC-Forever Points: 47174 More actions · Answer 5

Leifton (7/5/2013)
All other client protocols are disabled. The only protocol that is enabled is Shared Memory. This is part of our standard configuration for all deployments.

Your standard deployment is for local access only????

Anyway, have you checked that the Shared Memory Endpoint has not been changed from it's default of "TSQL Local Machine" ?

Have you tried granting sa access to that endpoint - to see if permissions have been lost?

what does your sys.endpoints data look like?

/*------------------------

select *

from sys.endpoints

------------------------*/

name endpoint_id principal_id protocol protocol_desc type type_desc state state_desc is_admin_endpoint

-------------------------------------------------------------------------------------------------------------------------------- ----------- ------------ -------- ------------------------------------------------------------ ---- ------------------------------------------------------------ ----- ------------------------------------------------------------ -----------------

Dedicated Admin Connection 1 1 2 TCP 2 TSQL 0 STARTED 1

TSQL Local Machine 2 1 4 SHARED_MEMORY 2 TSQL 0 STARTED 0

TSQL Named Pipes 3 1 3 NAMED_PIPES 2 TSQL 0 STARTED 0

TSQL Default TCP 4 1 2 TCP 2 TSQL 0 STARTED 0

TSQL Default VIA 5 1 5 VIA 2 TSQL 0 STARTED 0

MM

select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);

Leifton SSC Veteran Points: 298 More actions · Answer 6

mm,

Yes, it is our standard deployment. Local access is preferred in our case.

The output on the remote machine experiencing the problem is nearly identical to yours (different column names being the difference). I guess I am not sure how to tell if 'sa' can access a particular endpoint. Related to that is I do not now how to grant 'sa' access to an endpoint if it is determined that 'sa' cannot access it.

Thank You,

Leif