Post reply

SQL Server Error: 18452 Not associated with a ...

  • November 30, 2004 at 11:24 am

    #163936

    Hi.  We have a users trying to access a SQL Server instance but when they try from their server they get the following error:

    Connection failed:  SQLState: '28000', SQL Server Error: 18452, [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '(null)', Reason: Not associated with a trusted SQL Server connection.

    What can I do to get the remote server to acknowledge Mary Jane when logging in as mjane?

  • November 30, 2004 at 11:49 am

    #531924

    Well need more data, but

    -is the user mjane a domian account ?? 

    -is the account domain\mjane a user in the sql security and assigned to some database??

    -how is the users connecting, QA, isql, etc ?

     

    JR

  • November 30, 2004 at 11:59 am

    #531927

    -is the user mjane a domian account ?? Local

    -is the account domain\mjane a user in the sql security and assigned to some database?? Yes

    -how is the users connecting, QA, isql, etc ?   ODBC

  • November 30, 2004 at 12:29 pm

    #531933

    What is your SQL Server authentication mode?

  • November 30, 2004 at 1:23 pm

    #531947

    Servers setup for Mixed.

    Auth through Windows

  • November 30, 2004 at 2:11 pm

    #531968

    thanks, 1 more question

    -is the user mjane a domian account ?? Local 

    HERE THE QUESTION-->The account is local in the SQL server o is locally created in the clients machine

    In client machine type the next in command prompt

    %username%

    isql -SServerName,1433 -E

    Then copy paste the results

    ---is the account domain\mjane a user in the sql security and assigned to some database?? Yes  -----> OK

    ---how is the users connecting, QA, isql, etc ?   ODBC ---->OK

    ---Servers setup for Mixed.  ----> OK

    JR

  • December 1, 2004 at 12:16 am

    #532002

    Is there a windows thrust ?

    To test :

    1) map a new drive at the client to a disk(or test-share) of your sqlserver and use your own windows account (not the client's). (don't use reconnect at logon  )

    2) now perform in a cmd-box "isql -SServerName -E"

    3) if it works now, it is the disk-connection's credentials that are in use for the connection ! So there is your obstruction

     

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • December 1, 2004 at 7:54 am

    #532054

    You need to setup a connection alais.

    <<< run on the client >>>

    Start the Client Network Utility (its in the SQL Server program group).

    select the Alais tab >>> click the Add button.

    select the library type "named pipes" or "TCP\IP".

    in the "Service Alais" box on the top enter the servername\instance. if server name is serverxx and the instance name is abc123 then enter "serverxx\abc123"

    click apply >>> OK.

    >>> you should be able to connect ...

    Don't count what you do, do what counts.

    SQL Draggon

  • December 1, 2004 at 7:57 am

    #532055

    We're checking on credentials now and trying the CNU fix.  I'll let you know how it goes

    Thanks

    Don't drive faster than your guardian angel can fly

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply