Post reply

Login failed for user ''sa''. Reason: Not associated with a trusted SQL Server connection.

  • February 28, 2006 at 4:03 am

    #112019

    Hi

    I am running Win2003SBS server which has the named instance MSDE on it

    When I run a script from Filemaker or even try to connect to a databsae on this server using the 'sa' account I get this error.

    Also running osql -U sa from a cmd prompt shows this error.

    Firstly I checked to see if SQL Server was set to “mixed mode” authentication. I checked it out and SQL Server was set to “Windows only“ mode. Changed it [and verified LoginMode value was 2]and restarted the MSSQLSERVER service. [also trying rebooting server]

    still getting this error??? are there any tools/hacks that can change the 'sa' p'word...

    HELP?

  • February 28, 2006 at 4:57 am

    #623646

    Your words "named instance" might give the problem away   Perhaps you have a default instance of SQL as well as the named instance that you wish to connect to and you changed loginMode for the default instance rather than your named instance or vice-versa?

    The osql command, connecting to a named instance (or another server) should read

    osql -U sa -S SERVER\INSTANCE

    However, if you are running SBS Premium then you have SQL Server Standard, not MSDE?

    In any case, you could also try the following...

    Install the SQL Server 2000 120 day evaluation version - just get the client tools installed

    Use enterprise manager to register and connect to your MSDE instance using Windows auth

    Use the GUI to easily change the sa password and also verify in the server properties window that you indeed to have mixed mode authentication enabled.

    This can all be done via TSQL (Through your OSQL command line) but I can never remember the particular params of all the procs (and I don't think MSDE has Books Online) and it is easier to use the GUI for some of the adhoc changes such as mixed vs windows only mode...

    Good luck!

  • February 28, 2006 at 11:25 am

    #623761

    Yeh it was a case of it being 'too easy' after SQL Server 2000 was installed.

    All sorted and 'everyone is talking to everyone' again.

    Not sure what caused it in the first place, but not being a DB guy my self, apart from this being very frustrating, I have learnt much from this little adventure. Thanks so much for your advice...

    [it saved me many a grey hair]

    Paul

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

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