ASP Connection String for Privileged Account

[sucaba.r]

I don't know if this is a unique problem, or I'm going about it the
wrong way. I currently connect to one of our SQL servers via a
priviliged account (by using RUNAS). Works with no problem. I now
need the ability to connect to the same SQL server using ASP. I have
the following connect string, but I'm not sure how to specify the
domain in the string, or is there some other way?

<%
Set demoConn = Server.CreateOb ject("ADODB.Con nection")
demoPath="DRIVE R={SQL Server};" & _
"SERVER=mysqlse rver;UID=myuser name;" & _
"PWD=mypassword #;DATABASE=qdb"
demoConn.open demoPath
%>

Thanks!

[sucaba.r]

Well I moved response.end after democonn.open, but still getting the
error. Obvious? Not to me...obviously! :-)
Bob Barrows [MVP] wrote:

su******@gmail. com wrote:

Obviously I'm doing something wrong. Here's my code:

<%
dim demopath
Set demoConn = CreateObject("A DODB.Connection ")
demoPath="Provi der=SQLOLEDB;" & _
"Data Source=enpefrqd b01;Integrated Security=SSPI;" & _
"Initial Catalog=qdb"
demoConn.open demoPath
response.write demopath
response.end
%>

BTW, thanks for all the help Bob.

Ask yourself:
Which line of code is raising the error?
Then
Which line of code do I want to prevent from being executed by using
response.end?

The solution should be obvious ... :-)
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[Bob Barrows [MVP]]

This was in response to your previous post about not getting the
response.write to work ...
Nothing to do with your ADO error

su******@gmail. com wrote:

Well I moved response.end after democonn.open, but still getting the
error. Obvious? Not to me...obviously! :-)
Bob Barrows [MVP] wrote:

su******@gmail. com wrote:

Obviously I'm doing something wrong. Here's my code:

<%
dim demopath
Set demoConn = CreateObject("A DODB.Connection ")
demoPath="Provi der=SQLOLEDB;" & _
"Data Source=enpefrqd b01;Integrated Security=SSPI;" & _
"Initial Catalog=qdb"
demoConn.open demoPath
response.write demopath
response.end
%>

BTW, thanks for all the help Bob.

Ask yourself:
Which line of code is raising the error?
Then
Which line of code do I want to prevent from being executed by using
response.end?

The solution should be obvious ... :-)
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so
I don't check it very often. If you must reply off-line, then remove
the "NO SPAM"

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[sucaba.r]

So the KB article you're referring to is: Q247931?

Bob Barrows [MVP] wrote:

This was in response to your previous post about not getting the
response.write to work ...
Nothing to do with your ADO error

su******@gmail. com wrote:

Well I moved response.end after democonn.open, but still getting the
error. Obvious? Not to me...obviously! :-)
Bob Barrows [MVP] wrote:

su******@gmail. com wrote:
Obviously I'm doing something wrong. Here's my code:

<%
dim demopath
Set demoConn = CreateObject("A DODB.Connection ")
demoPath="Provi der=SQLOLEDB;" & _
"Data Source=enpefrqd b01;Integrated Security=SSPI;" & _
"Initial Catalog=qdb"
demoConn.open demoPath
response.write demopath
response.end
%>

BTW, thanks for all the help Bob.

Ask yourself:
Which line of code is raising the error?
Then
Which line of code do I want to prevent from being executed by using
response.end?

The solution should be obvious ... :-)
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so
I don't check it very often. If you must reply off-line, then remove
the "NO SPAM"

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[Bob Barrows [MVP]]

I don't know, there are a few KB articles cited in that article as I
remember it. Any one of them could be relevant to your problem. I cannot
tell which one because I am not sitting at the keyboard of your server
looking at its configuration settings. IOW, you are going to have to sort
this out yourself using the information I've provided.

Oh wait, one last thing. Is your web server W2003? Are you using SQL 2000?
Is it up-to-date with its service packs? SQL 2000 SP4 fixed a problem with
connections from W2003 servers.

That's it. There is nothing more I can offer.

su******@gmail. com wrote:

So the KB article you're referring to is: Q247931?

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[sucaba.r]

Thanks for all the help Bob. I do appreciate it.

Bob Barrows [MVP] wrote:

I don't know, there are a few KB articles cited in that article as I
remember it. Any one of them could be relevant to your problem. I cannot
tell which one because I am not sitting at the keyboard of your server
looking at its configuration settings. IOW, you are going to have to sort
this out yourself using the information I've provided.

Oh wait, one last thing. Is your web server W2003? Are you using SQL 2000?
Is it up-to-date with its service packs? SQL 2000 SP4 fixed a problem with
connections from W2003 servers.

That's it. There is nothing more I can offer.

su******@gmail. com wrote:

So the KB article you're referring to is: Q247931?

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[sucaba.r]

One more question. Is there a relationship between the ODBC System DSN
login on the IIs server, and the SQL server I'm trying to connect to?
In other words, are the login credentials on the IIs server being used,
or the SQL server? Or both?

[Bob Barrows [MVP]]

su******@gmail. com wrote:

One more question. Is there a relationship between the ODBC System
DSN login on the IIs server, and the SQL server I'm trying to connect
to? In other words, are the login credentials on the IIs server being
used, or the SQL server? Or both?

You are using SQLOLEDB, which is the OLE DB Provider for SQL Server, not
ODBC. Totally different and separate technology.
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[sucaba.r]

Okay, so the System DSN login information (on the IIs server) is not
being used?

Bob Barrows [MVP] wrote:

You are using SQLOLEDB, which is the OLE DB Provider for SQL Server, not
ODBC. Totally different and separate technology.

[Bob Barrows [MVP]]

:-)
I think that's what I said, but yes, that is correct.

Again ... you are not having a login problem (which would result in an error
containing the words "login failed".). You are having a "SQL Server does not
exist or access denied" problem, which is a completely different thing.

There are two stages in establishing a connection to a database server:
1. Finding it on the network and verifying that you can communicate with it
2. Providing login credentials

Step 1 is the one that is failing for you. As to why you are having this
problem, I could not say without going through the troubleshooting steps
described in the KB articles linked to from the aspfaq article.

http://support.microsoft.com/default.aspx/kb/328306

su******@gmail. com wrote:

Okay, so the System DSN login information (on the IIs server) is not
being used?

Bob Barrows [MVP] wrote:

You are using SQLOLEDB, which is the OLE DB Provider for SQL Server,
not ODBC. Totally different and separate technology.

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

[sucaba.r]

Got it. Just thought the "access denied" part of the error might be
pointing to a credential problem. I'll stop...for real. :-)

Bob Barrows [MVP] wrote:

:-)
I think that's what I said, but yes, that is correct.

Again ... you are not having a login problem (which would result in an error
containing the words "login failed".). You are having a "SQL Server does not
exist or access denied" problem, which is a completely different thing.

There are two stages in establishing a connection to a database server:
1. Finding it on the network and verifying that you can communicate with it
2. Providing login credentials

Step 1 is the one that is failing for you. As to why you are having this
problem, I could not say without going through the troubleshooting steps
described in the KB articles linked to from the aspfaq article.

http://support.microsoft.com/default.aspx/kb/328306

su******@gmail. com wrote:

Okay, so the System DSN login information (on the IIs server) is not
being used?

Bob Barrows [MVP] wrote:

You are using SQLOLEDB, which is the OLE DB Provider for SQL Server,
not ODBC. Totally different and separate technology.

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"