SQL Server 2005 connection problem

  • Hi everyone - I have created a new user using the the object explorer in the Microsoft SQL Server Mangement Studio. I then try to make a connection by right-clicking on teh server->connect->sql authentification and then entering username and password. When I press OK I get the following message:

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

    I would be grateful for any advice,

    Thanks

  • you server could be set to use windows authentication only

    go to 2005 server management studio, right click on the server,choose properties and then click on security - ensure it is set to "windows and sql authentication mode"

    MVDBA

  • Thanks for the response but I have already set the properties to "windows and sql authentication mode" and am still getting this message.

  • tyy this

    go to server 2005 menu on the start menu and find the sql server 2005 surface area configuration tool

    under remote components ensure that local and remote connections are allowed

    MVDBA

  • Sorry Old Hand on account of the late reply,

    In actual fact before I got your last message I deinstalled 2005 and installed 2000. I continued to experience the same problem until I installed the latest service pack which solved

    my problem (apparently it fixes certain bugs).

    Anyway at the moment I am just testing differnet servers. So I have installed the sql server 2005 express edition and am getting the same connection error - "No TCP/IP connection".

    I have enabled TCP Protocol on the surface area configuration tool and have the connection status on mixed mode - but still no success. Sorry, do you have anymore ideas?

    Thanks

  • How did you connect to create the user?

    Can you do the same remotely?

    Did you create a User or a Login? CREATE USER? CREATE LOGIN? Did you GRANT any access (to dbs, roles, etc.)?

  • do you have a firewall installed blocking your sql ports ?

    MVDBA

  • I created the new user over Login->New Login. There's is then a dialog box where I set the username, password, authentification mode etc. I have also included this user in my master database users section.

  • And the error is the same locally or remotely?

    Check the application log, if there are no entries for failed logins, then your problem is not on SQL Server, if there are;

    Try running sp_helpuser and sp_helplogins

  • Sorry, but the sql ports are not being blocked by a firewall.

    Thank anyway

  • I can access the database locally now (in the Express version). However, this is not possible remotely. I am actually trying to connect to it through a java app - here my connection string:

    DriverManager.registerDriver(new com.microsoft.sqlserver.jdbc.SQLServerDriver());

    Connection connection = DriverManager.getConnection("jdbc:sqlserver://my ip address","username","password");

  • Oh and I also attach the port number 1433 to my ip adress.

  • if you're attempting connect remotely is this via you LAN or are you coming through the internet via VPN?

    i've seen this problem with juniper before.

    MVDBA

  • via LAN

    I have just noticed another point. I can register locally but only by using windows authentifcation. When I am in the connect to server dialog from Microsoft SQL Server Management Studio Express and select SQL Server Authentification from the drop down then give a user name and password that I have already applied under Logins and users (with SQl authentication) I get this message from the server:

    SELECT permission denied on object 'configurations', database 'mssqlsystemresource', schema 'sys'. (Microsoft SQL Server, Error: 229)

  • if you hadn't already said that you were on mixed mode authentication id'd swear that you were on windows only auth

    by the way - is the server a member of a domain?

    are the servers named instances? (you mentioned having express and 2005 and 2000 on the same machine?) just checking that your connection strings are supplying the instance name nd that the slash is the right way

    (it's always something stupid like that when it goes wrong for me)

    the permission error relating to schema sys looks like you don't have permissions for your default schema or database for that server.

    MVDBA

Viewing 15 posts - 1 through 15 (of 18 total)

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