From Balasubramanian [SMTP:balasubramanian_r@f...]



My name is Bala. I am a web programmer working on ASP with SQL server as the

backend and VB components taking care of the business logic. I have been

working on a project where in the site is a portal that provides information

on engineering topics. The whole site has been designed to provide dynamic

data from SQL Server, I mean its not only the search but the content of the

site itself is driven by components.



Well, while developing, the database server and the file server were on the

same machine and the so the components were designed to use a system dsn.

The whole project worked fine and it has been completed under the impression

that the site will be hosted on a dedicated server with similar facilities.



But then, I am now facing a situation where the site has been hosted on a

dedicated server, but this server does not have SQL Server running.  Instead

the client has purchased a database (section) from another Server. I have

provided the I.P , database name and password, but though I have been able

to create System and File DSN s and the System DSN passes the test, yet,

when I use it with the Component or directly with ASP codes, the System DSN

fails to connect. Even the File DSN works fine only with direct ASP coding

and doesn't work when used by components.



This is one of the error messages

Attempting connection

[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user

'(null)'. Reason: Not associated with a trusted SQL Server connection.



While using the System DSN with the components, the error message that pops

up states "connection timed out". This comes even after I increased the

connection timeout value.



So now what do I do to connect to the External SQL Server database from

components ? The file dsn which I used with direct ASP coding worked fine

but then when it comes to the components, nothing seems to work.



Could you kindly help me out ?



Warm regards,

Bala

Bala,



It looks like your component is running as an NT user that do not have

permissions on the SQL server in question.  When you try the ASP code you

are providing the username and password of a user that do have access to the

SQL server.  Your error indicates that your are using trusted connections,

therefore NT will use the user information under which the component is

running, not the user information under which the web site user logged in.



-----Original Message-----

From: StephenB [mailto:stephen@v...]

Sent: Friday, December 08, 2000 3:11 AM

To: ASP components

Subject: [asp_components] Components and connections





From Balasubramanian [SMTP:balasubramanian_r@f...]



My name is Bala. I am a web programmer working on ASP with SQL server as the

backend and VB components taking care of the business logic. I have been

working on a project where in the site is a portal that provides information

on engineering topics. The whole site has been designed to provide dynamic

data from SQL Server, I mean its not only the search but the content of the

site itself is driven by components.



Well, while developing, the database server and the file server were on the

same machine and the so the components were designed to use a system dsn.

The whole project worked fine and it has been completed under the impression

that the site will be hosted on a dedicated server with similar facilities.



But then, I am now facing a situation where the site has been hosted on a

dedicated server, but this server does not have SQL Server running.  Instead

the client has purchased a database (section) from another Server. I have

provided the I.P , database name and password, but though I have been able

to create System and File DSN s and the System DSN passes the test, yet,

when I use it with the Component or directly with ASP codes, the System DSN

fails to connect. Even the File DSN works fine only with direct ASP coding

and doesn't work when used by components.



This is one of the error messages

Attempting connection

[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user

'(null)'. Reason: Not associated with a trusted SQL Server connection.



While using the System DSN with the components, the error message that pops

up states "connection timed out". This comes even after I increased the

connection timeout value.



So now what do I do to connect to the External SQL Server database from

components ? The file dsn which I used with direct ASP coding worked fine

but then when it comes to the components, nothing seems to work.



Could you kindly help me out ?



Warm regards,

Bala









---