Results 1 to 3 of 3
  1. #1
    Join Date
    Jun 2002
    Posts
    8

    Unanswered: Login failed for user '(null)'. Reason: Not associated with a trusted SQL

    I am connecting to an Access 97 db on a network drive, in which all tables are linked to a SQL Server 2000 db through a DSN. I can access the tables fine from a Windows 2000 machine, but I get this error when I try to access the tables on an NT4 machine: Login failed for user '(null)'. Reason: Not associated with a trusted SQL. I do not want to use trusted security and the DSN does have a valid SQL Server user name and password. Please help!!!

  2. #2
    Join Date
    Dec 2001
    Location
    Toronto, Canada
    Posts
    335
    When you created the linked tables within the Access database you specify which DSN to use. That DSN must be defined on all machines that will use the linked tables within the Access database. Does the NT 4.0 workstation have the DSN defined on it? If so does it have trusted connection defined or Login/Password?
    MCDBA

  3. #3
    Join Date
    Jun 2002
    Posts
    8
    I do have the dsn set up on both machines, but in further digging, I found this:

    FIX: SQL Server ODBC Driver Ignores Authentication Setting (Q279526)

    --------------------------------------------------------------------------------
    The information in this article applies to:


    Microsoft ODBC Driver for SQL Server, version 3.6
    Microsoft SQL Server 2000 (all editions)
    Microsoft Data Access Components version 2.6


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


    SYMPTOMS
    When you use the SQL Server ODBC driver version 2000.080.0194, which was released with SQL Server 2000 and Microsoft Data Access Components (MDAC) 2.6 RTM, the authentication settings for ODBC data source names (DSNs) are ignored. The driver attempts to log directly into SQL Server using NTLM authentication (integrated security) without prompting for a user ID and password.

    This can cause authentication failures, messages that database objects are not available, or unintentional modification of the wrong objects when copies of objects are maintained in multiple databases.



    RESOLUTION
    To resolve this problem, obtain the latest service pack for Microsoft Data Access Components 2.6. For additional information, please see the following article in the Microsoft Knowledge Base:

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •