May 28, 2008 at 4:21 am
We are in a process of moving our ASP application from server1 to server2. The app originally on server1 used database installed in server2 (SQL Server 2000). Now both the app and database are on the saem server. Before deplyoing the app we wanted to test the appl with a testing/development database (SQL Server 2000) on a remote server (server3). Initially i was hitting the production database(server2) to check if the app was properly configured on the IIS. The applications ran absolutely fine without any trouble. But when i tried using the testing/ development database on server3 it gave me the following error:
*************************************************
Microsoft OLE DB Provider for SQL Server error '80004005'
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection.
/LM/W3SVC/1/Root/ /global.asa, line 29
*************************************************
i have created an 'sa' user on the server2 SQL Server 2000 instance that has admin privileges.
I read many articless on net that this error and majorily they suggested two solutions:
1.) Check to see if the Authentications for the server is "Mixed" and not "Windows Only". I have verified that it is mixed.
2.) Windows 2003 server doesn't support SQL Server 2000 version less than SP4. I havent tried this.
Please help me...its urgent.
May 28, 2008 at 4:39 am
Firstly, don't ever, ever, ever, ever use the sa account for an application's login. You're asking for security problems.
Create an account just for the application that has just the permissions necessary for the app to work.
Can you post the connection string you're using please.
Also, in the future, please post SQL 2000-related questions in the SQL 2000 forums. In the 2005 forums you may get suggestions that are only applicable to SQL 2005.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 28, 2008 at 4:45 am
Thanks for a prompt reply.
I have tried using the non 'sa' connection resulting in the error.
This is what i am using as my connection string:
"provider=SQLOLEDB;uid=sa;pwd=sabidev;server= "
I also use the following non 'sa' login:
"provider=SQLOLEDB;uid=sumit_test;pwd=sumit@test;server= "
May 28, 2008 at 5:12 am
Ok, you could try something like this (replacing placeholders with pertenant values)
Provider=sqloledb;Data Source=myServerAddress;Initial Catalog=myDataBase;
User Id=myUsername;Password=myPassword;
What version is your SQL Server (run SELECT @@Version)
Can you connect from query analyser using the 'sumit_test' login?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 28, 2008 at 5:45 am
Yes i am able to connect using Sumit_Test login.
I have also tried using actual value rathe than place holders. Its still the same.
May 28, 2008 at 5:48 am
You are trying to connect to Server3 and your initial post indicates:
"I have created an 'sa' user on the server2 SQL Server 2000 instance that has admin privileges."
Then you go on to say you made sure the server is in mixed authentication mode. Make sure you were looking at the correct server. Then, check your login. Just create an empty text file and give it the ".udl" file extension. Then, double-click on it. Select the SQL server OLEDB provider and enter the server, database, user, and password and click the test button. Click OK to save and open the text file with notepad - use the connection string it generated as your connection string. This will ensure you are using a tested username and password.
When you are done with all of this, you should go change your sa password from "sabidev" because you just posted it on a public forum.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply