Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dusualsuspect
Starting Member
2 Posts |
 Posted - 2008-04-03 : 01:54:49
|
| Hello All,I know this issue has been dealt with every where in the universe. but none seem to solve my problem. I need help desperatelyThe set up is Classic ASP/Sql Server 2000 in an intranet:Computer-A is the Sql server2000 running Windows XP Professional. On it i created a login, AA, as a dbowner of a database called XXX. Inside XXX, AA is right there as a user.i configured the SqlServer to accept mixed (Windows and Sql) logins. I restarted the computer and i logged into sqlserver successfully as AA. Everything is fine here.Computer-B is the web server running IIS in Windows XP Professional. I successfully created a system ODBC named EEEE to connect to XXX using the AA login. Everything is fine up to this point.But, to my greatest surprise when i use - conn.Open("DSN=EEEE;UID=AA;PWD=AApassword;") in a classic ASP page, it returns this very famous error.What did i do wrong? Please help |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2008-04-04 : 13:52:00
|
| Could you run a test , if possible , if you have the SQL Server tools on Computer-B , could you try and logon , using SQL Authentication, is this successfull? If not then investigate the connection between tese 2 servers . For example , are you using TCP/IP or Named PipesJack Vamvas--------------------Search IT jobs from multiple sources- http://www.ITjobfeed.com |
 |
|
|
dusualsuspect
Starting Member
2 Posts |
Posted - 2008-04-07 : 06:07:49
|
| Hello Jack,I will do like you suggested. However, the clients protocols are listed as follows:Named PipesTCP/IPThanks Jack |
|
|
|
|
|
|
|
|
Not associated with a trusted SQL Server connectio