The Scheduled jobs (6.5) suddenly started failing

  • There were known configuration changes.

    It is annoying the hell out of me!

    Error returned

    Msg. No.: 18452 Severity: 14 State: 1 Login Failed- User: sa Reason: Not associated with a Trusted SQL Server Connection

    Linked to this I suspect is also the following issue

    When I try to connect to SQL Server 6.5 SQL Security Manager using the SA account

    Error returned

    "This SQL Server does not support Windows NT SQL Server security stored procedures"

    I am using Standard security with Named pipes

    Some of the steps I have tried – all to no avail

    1 ) Rebooted server

    2) I have reset both the MSSQLServer service account and the NT User account.

    (The MSSQLServer service account is running as a NT user account)

    3) I have checked the registrty permission’s on

    HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer

    The local Administrators group has Full Control (ie read/Write) of this key.

    Any clues before I lose all my hair

  • From what you tell it sounds very much like the server accepts Windows authentication only. The sa account is no Windows NT account and therefore can't log on if you use Windows authentication.

    quote:


    I have checked the registrty permission’s on

    HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer

    The local Administrators group has Full Control (ie read/Write) of this key.


    The sa is not a member of local administrators so that's not important.

    Check your server properties which authentication mode is used. You can also check it in the registry. I'm not sure about SQL 6.5 but for 7.0 you find it under:

    HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer\loginmode A value of 1 means only Windows authetication is accepted. You have to change it to 0 in order to use SQL logins as well.

    [font="Verdana"]Markus Bohse[/font]

  • MarkusB,

    Thanks for the reply. Still stuck the problem

    The Login Security Mode has always been Standard. (the default). This is what is puzzling about this as I do not know of any server changes or access rights modifications.

    I checked the loginmode - it is set to 0

    regards

    Bill

Viewing 3 posts - 1 through 2 (of 2 total)

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