March 21, 2003 at 12:50 pm
This may be in the wrong place, but....
I have SQL Server (default instance) running on my Windows 2K pro PC. I also have installed MDAC 2.7 and the 2.7 Refresh patch. The server is running OK.
The problem I'm having is trying to create a data source to connect to a database. I see the default "local" data souce under System DSN. I'm trying to create another DSN to connect to a separate DB.
I have created a user and password using Enterprise Manager fot the DB, and all went well. When attempting to create the DSN, and using SQL Server authentication (the user and password I have created), I received the following error afer attempting to connect:
Connection failed:
SQLState: '28000'
SQL Server Error: 18452
[Micrsoft][OBDC SQL Server Driver][SQL Server]Login Failed for user 'myusername'. Reason: Not associated with a trusted SQL Server Connection
I looked up the error on the MS site in the knowledge base, and am still wondering what's going on.
Sorry if the post is long - wanted to make sure I included enough info (which I may have not). Anyone here have any ideas? I have triple checked to make sure all the username/password stuff is in order, and it is. I am unable to create a DSN for any DB in the SQL Server. I tried un-installing SQL Server and then re-installing....no luck.
Thanks.
Warren
March 21, 2003 at 1:11 pm
Right click your SQL Server --> Properties --> Security Tab --> Make sure Authentication is 'SQL Server and Windows' is selectd.
Try use QA to login to SQL Server to confirm the userid and password are correct.
During the creation of DSN, ensure you choose 'SQL Server Authentication'.
March 21, 2003 at 1:22 pm
Allen,
Thanks a million! Worked fine. I'm still an amatuer at SQL Server, but grasping things. Glad you understood my post.
Warren
June 23, 2003 at 7:19 am
You beauty !!!!
I have been stuck with this problem for ages, and have search high and low for an answer.
Thank you so much
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply