Disabling Trusted Connection

Trusted connections are associated with the Windows Authentication, So if you disables the Windows authentication and allow only SQL server authentication, you can do it

In order to chnage the authentication , use , EM->rightClick on the server ->Properties ->Security -> authentication

If our application uses DSN, then you can disable this option in the curresponding ODBC DSN entry

Okay, I went to the authentication section of security and it gave me a choice of windows only and windows and sql server.  I switched it to windows + sql server.  It then asked me for the sa password which i don't ever remember setting so I left it blank.  It then asked if I wanted to restart the sql server to make the changes.  I thought that it was taking too long so I stopped the sql server + agent myself (intending to restart it).  Now it says that I have a error 1069 that the sql server cannot start due to a login failure.  Where do I go now?

>Now it says that I have a error 1069 that the sql server cannot start due to a login failure.  Where do I go now?

Run  Start->run  Services.msc
find the service MsSQlserver
Move to Logon tab, and select this account, then start the service ...

It gives me the same message as before... error 1069 and then the same message about login failure.  The only thing I did different to get this message was switch the login under security from windows only to sql + windows.  Where to now?

did u change your windows password, try browsing some othe user to start ...

I did not have a password for windows until last night when I finally put one on.  I did this after I installed sql server 2000 last week.  If this makes a difference then should I add another user to the computer/domain? I am pretty new at this, but I am a quick learner so if you tell me step-by-step what to do, it will be done.  Thanks for all your help.

After changing the password, i think this is the first time you are restarting the server ?

Previously u were using the same username and the previous password, but since the SQL service has already started, it won't recognise the password change. Now since you restart the service, you need to put the new password for that particular user,in the same way that i mentioned in my previous post

I went through the same method that you mentioned in the previous post but it won't let me go to the properties after I right click the server because it is not running and it says: " connection failed. check sql server registration properties"

Not that post,

Run  Start->run  Services.msc
find the service MsSQlserver
Move to Logon tab, and select this account, then start the service ...

Okay! That worked! When I go into Dynamics GP it still gives me the same issues with the trusted connection even though i changed it from windows only to windows + sql server... now what do i do?

check wheter  Dynamics GP  application uses DSN, then you can disable this option in the curresponding ODBC DSN entry

When i went through the install manual, when i was setting up the system dns and click on with sql server to verify the authenticity of the user, in the user it has: Administrator and then when i went to put in the password that we just changed with the other exercise, it gave me the following message:
"Connection Failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]login failed for user: AIS\Administrator"

I tried both AIS\Administrator and Administrator with the same results... not sure where to go from here...

On which user accout the sql server is starting (Start->run->services.msc->login )
is this the same as AIS\Administrator , otherwise try to change it and restrat the service

The user account the sql server is starting is indeed AIS\Administrator... where to now boss?

hmm. I  am tired ... I think you must refer the installation manual.
Also check whether the application uses DSN to connect to the sql server (refer the manual)

the installation manual goes over that section with the ODBC but it doesn't go over if there are issues... i don't know anybody else that can help me on this.  what should i do? i'm guessing it's just a simple item that is preventing the login from connecting with the sql server...

is there anybody else that can help me disable the trusted connection?

I don't remember ever setting an sa password - how do i reset it so I can then know what it is?

1. First try using a blank password with the sa login. Even though this is very naughty, many people leave it blank.
2. If that doesn't work, log into Enterprise Manager (using trusted security) go to the security tab, find the sa user and reset its password.

Do you understand the difference between Trusted (Windows) Security and SQL Security?


Back to your original issue you need to do two things:

1. Ensure that the server configuration is set to use windows AND sql server security, as per aneesh's suggestion.
2. Ensure that you pick 'with sql server authentication using a login id.......' in your DSN (but this should be in the manual)

-- YOU CAN NOT DISABLE THE WINDOWS (TRUSTED) AUTHENTICATION.

For auth .. we habe two options...
1. Windows
2. Mixed .. ie. Windows and SQL.

Now coming to the error message

"Connection Failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]login failed for user: AIS\Administrator"

-- Have we created login (in SQL) for "AIS\Administrator"....
-- If u logon to the box as "AIS\Administrator".. Can u connect to SQL?

thx
VJ

I think the issue here is that:

1. riser117 is using windows authentication but doesn't realise it
2. Great Plains does not support windows authentication.

Therefore the solution is to login using a SQL Account, rather than a windows account.

... but the clarification is appreciated as rereading this post, we hadn't made it very clear that you can't actually disable windows authentication.