Sorry for the crosspost (I posted this on the asp.db group last night). But
since I had no answer there, I'm hoping for better luck here. I'm pretty
much tried everything I know. Here's the problem:
I have an Intranet-based app at work, and I have it in two places there: a
dev machine and a production box. In both cases, the ASP files and SQL
Server 2000 database are on the same box. I have it running smoothly in both
places at work.
However, I've been trying to set it up at home, and cannot make the SQL
Server connection work for some reason. I've been working on this off and on
for weeks, and I just don't get what I am missing.
First, my code:
<!-- #INCLUDE FILE="includes/dbinc.asp" -->
which points to a page contaning only the followig lines:
=======================
<%
Dim strDBConnection
strDBConnection = _
"Provider=SQLOLEDB;" & _
"Persist Security Info=False;" & _
"Data Source=w2003\ticketlog;" & _
"User ID=asp;" & _
"Password=asp;" & _
"Database=argonet;"
Dim objConnection
Set objConnection = Server.CreateObject("ADODB.Connection")
objConnection.Open strDBConnection
%>
==============================
It's at this point that I should add that this code is just like the
working code from my stuff at work. Only the names have been changed. I
should also add that here at home, the machine I am working on has been
named "W2003", so when I set up SQL Server, it named the instance
W2003\TICKETLOG.(Windows NT). Yes, it has that part with the parentheses.
I don't think the slash is the problem.
Anyway, here is the message I see in the browser when I try to get to any
page which calls this connection code.
====================================
Microsoft OLE DB Provider for SQL Server error '80040e4d'
Login failed for user 'asp'.
/ticketlog/includes/argodbinc.asp, line 15
====================================
I want to add that I did go to the server in EP, went to Security, then
doule-clicked the user called asp, and went to the database tab to make sure
that db_owner and everything else is checked. I then did the same for
INETUSER.
Ok, so pretend I have never done any of this before. What steps do I need to
set up this thing? In my case, I did add a user named asp and gave full
permissions, but assume I haven't done that. Perhaps with detailed
hand-holding instructions, I'll see what I am missing. 18 1996 http://aspfaq.com/show.asp?id=2138 http://aspfaq.com/show.asp?id=2126
Is this one of yours aswell btw? http://www.issociate.de/board/post/1..._problems.html
--
Regards
Steven Burn
Ur I.T. Mate Group www.it-mate.co.uk
Keeping it FREE!
"middletree" <mi********@HTOmail.com> wrote in message news:uR*************@TK2MSFTNGP15.phx.gbl... Sorry for the crosspost (I posted this on the asp.db group last night). But since I had no answer there, I'm hoping for better luck here. I'm pretty much tried everything I know. Here's the problem: I have an Intranet-based app at work, and I have it in two places there: a dev machine and a production box. In both cases, the ASP files and SQL Server 2000 database are on the same box. I have it running smoothly in both places at work. However, I've been trying to set it up at home, and cannot make the SQL Server connection work for some reason. I've been working on this off and on for weeks, and I just don't get what I am missing. First, my code: <!-- #INCLUDE FILE="includes/dbinc.asp" --> which points to a page contaning only the followig lines: ======================= <% Dim strDBConnection strDBConnection = _ "Provider=SQLOLEDB;" & _ "Persist Security Info=False;" & _ "Data Source=w2003\ticketlog;" & _ "User ID=asp;" & _ "Password=asp;" & _ "Database=argonet;" Dim objConnection Set objConnection = Server.CreateObject("ADODB.Connection") objConnection.Open strDBConnection %> ============================== It's at this point that I should add that this code is just like the working code from my stuff at work. Only the names have been changed. I should also add that here at home, the machine I am working on has been named "W2003", so when I set up SQL Server, it named the instance W2003\TICKETLOG.(Windows NT). Yes, it has that part with the parentheses. I don't think the slash is the problem. Anyway, here is the message I see in the browser when I try to get to any page which calls this connection code. ==================================== Microsoft OLE DB Provider for SQL Server error '80040e4d' Login failed for user 'asp'. /ticketlog/includes/argodbinc.asp, line 15 ==================================== I want to add that I did go to the server in EP, went to Security, then doule-clicked the user called asp, and went to the database tab to make sure that db_owner and everything else is checked. I then did the same for INETUSER. Ok, so pretend I have never done any of this before. What steps do I need to set up this thing? In my case, I did add a user named asp and gave full permissions, but assume I haven't done that. Perhaps with detailed hand-holding instructions, I'll see what I am missing.
Try opening up Query Analyzer and connecting to that SQL Server with asp/asp
credentials. Does that work?
Ray at home
"middletree" <mi********@HTOmail.com> wrote in message
news:uR*************@TK2MSFTNGP15.phx.gbl... <% Dim strDBConnection strDBConnection = _ "Provider=SQLOLEDB;" & _ "Persist Security Info=False;" & _ "Data Source=w2003\ticketlog;" & _ "User ID=asp;" & _ "Password=asp;" & _ "Database=argonet;" Dim objConnection Set objConnection = Server.CreateObject("ADODB.Connection") objConnection.Open strDBConnection %> ==============================
I want to add that I did go to the server in EP, went to Security, then doule-clicked the user called asp, and went to the database tab to make sure that db_owner and everything else is checked. I then did the same for INETUSER.
I'm not sure what you mean. I open up QA just fine. I don't see any way to
use QA to connect with anything, though.
"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in
message news:u6**************@tk2msftngp13.phx.gbl... Try opening up Query Analyzer and connecting to that SQL Server with
asp/asp credentials. Does that work?
Hi,
I sometimes have the same problem when connecting to different SQL servers.
Try adding "Network Library=DBMSSOCN" to the end of your connection string.
Like this...
I'm not promising anything though ;-)
strDBConnection = _
"Provider=SQLOLEDB;" & _
"Persist Security Info=False;" & _
"Data Source=w2003\ticketlog;" & _
"User ID=asp;" & _
"Password=asp;" & _
"Database=argonet;" & _
"Network Library=DBMSSOCN"
Ollie
"middletree" <mi********@HTOmail.com> wrote in message
news:uR*************@TK2MSFTNGP15.phx.gbl...
Sorry for the crosspost (I posted this on the asp.db group last night). But
since I had no answer there, I'm hoping for better luck here. I'm pretty
much tried everything I know. Here's the problem:
I have an Intranet-based app at work, and I have it in two places there: a
dev machine and a production box. In both cases, the ASP files and SQL
Server 2000 database are on the same box. I have it running smoothly in both
places at work.
However, I've been trying to set it up at home, and cannot make the SQL
Server connection work for some reason. I've been working on this off and on
for weeks, and I just don't get what I am missing.
First, my code:
<!-- #INCLUDE FILE="includes/dbinc.asp" -->
which points to a page contaning only the followig lines:
=======================
<%
Dim strDBConnection
strDBConnection = _
"Provider=SQLOLEDB;" & _
"Persist Security Info=False;" & _
"Data Source=w2003\ticketlog;" & _
"User ID=asp;" & _
"Password=asp;" & _
"Database=argonet;"
Dim objConnection
Set objConnection = Server.CreateObject("ADODB.Connection")
objConnection.Open strDBConnection
%>
==============================
It's at this point that I should add that this code is just like the
working code from my stuff at work. Only the names have been changed. I
should also add that here at home, the machine I am working on has been
named "W2003", so when I set up SQL Server, it named the instance
W2003\TICKETLOG.(Windows NT). Yes, it has that part with the parentheses.
I don't think the slash is the problem.
Anyway, here is the message I see in the browser when I try to get to any
page which calls this connection code.
====================================
Microsoft OLE DB Provider for SQL Server error '80040e4d'
Login failed for user 'asp'.
/ticketlog/includes/argodbinc.asp, line 15
====================================
I want to add that I did go to the server in EP, went to Security, then
doule-clicked the user called asp, and went to the database tab to make sure
that db_owner and everything else is checked. I then did the same for
INETUSER.
Ok, so pretend I have never done any of this before. What steps do I need to
set up this thing? In my case, I did add a user named asp and gave full
permissions, but assume I haven't done that. Perhaps with detailed
hand-holding instructions, I'll see what I am missing.
A bit more info on the "Network Library" param
This was found on http://www.connectionstrings.com/
Example:
"Provider=sqloledb;Data Source=190.190.200.100,1433;Network
Library=DBMSSOCN;Initial Catalog=pubs;User ID=sa;Password=asdasd;"
Name Network library
dbnmpntw Win32 Named Pipes
dbmssocn Win32 Winsock TCP/IP
dbmsspxn Win32 SPX/IPX
dbmsvinn Win32 Banyan Vines
dbmsrpcn Win32 Multi-Protocol (Windows RPC)
Important note!
When connecting through the SQLOLEDB provider use the syntax Network
Library=dbmssocn
and when connecting through MSDASQL provider use the syntax Network=dbmssocn
"Ollie" <ol**********@hotmail.com> wrote in message
news:u3**************@TK2MSFTNGP12.phx.gbl...
Hi,
I sometimes have the same problem when connecting to different SQL servers.
Try adding "Network Library=DBMSSOCN" to the end of your connection string.
Like this...
I'm not promising anything though ;-)
strDBConnection = _
"Provider=SQLOLEDB;" & _
"Persist Security Info=False;" & _
"Data Source=w2003\ticketlog;" & _
"User ID=asp;" & _
"Password=asp;" & _
"Database=argonet;" & _
"Network Library=DBMSSOCN"
Ollie
"middletree" <mi********@HTOmail.com> wrote in message
news:uR*************@TK2MSFTNGP15.phx.gbl...
Sorry for the crosspost (I posted this on the asp.db group last night). But
since I had no answer there, I'm hoping for better luck here. I'm pretty
much tried everything I know. Here's the problem:
I have an Intranet-based app at work, and I have it in two places there: a
dev machine and a production box. In both cases, the ASP files and SQL
Server 2000 database are on the same box. I have it running smoothly in both
places at work.
However, I've been trying to set it up at home, and cannot make the SQL
Server connection work for some reason. I've been working on this off and on
for weeks, and I just don't get what I am missing.
First, my code:
<!-- #INCLUDE FILE="includes/dbinc.asp" -->
which points to a page contaning only the followig lines:
=======================
<%
Dim strDBConnection
strDBConnection = _
"Provider=SQLOLEDB;" & _
"Persist Security Info=False;" & _
"Data Source=w2003\ticketlog;" & _
"User ID=asp;" & _
"Password=asp;" & _
"Database=argonet;"
Dim objConnection
Set objConnection = Server.CreateObject("ADODB.Connection")
objConnection.Open strDBConnection
%>
==============================
It's at this point that I should add that this code is just like the
working code from my stuff at work. Only the names have been changed. I
should also add that here at home, the machine I am working on has been
named "W2003", so when I set up SQL Server, it named the instance
W2003\TICKETLOG.(Windows NT). Yes, it has that part with the parentheses.
I don't think the slash is the problem.
Anyway, here is the message I see in the browser when I try to get to any
page which calls this connection code.
====================================
Microsoft OLE DB Provider for SQL Server error '80040e4d'
Login failed for user 'asp'.
/ticketlog/includes/argodbinc.asp, line 15
====================================
I want to add that I did go to the server in EP, went to Security, then
doule-clicked the user called asp, and went to the database tab to make sure
that db_owner and everything else is checked. I then did the same for
INETUSER.
Ok, so pretend I have never done any of this before. What steps do I need to
set up this thing? In my case, I did add a user named asp and gave full
permissions, but assume I haven't done that. Perhaps with detailed
hand-holding instructions, I'll see what I am missing.
It gave me a different error:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
denied.
"Ollie" <ol**********@hotmail.com> wrote in message
news:u3**************@TK2MSFTNGP12.phx.gbl... Hi,
I sometimes have the same problem when connecting to different SQL
servers. Try adding "Network Library=DBMSSOCN" to the end of your connection
string. Like this...
I'm not promising anything though ;-)
strDBConnection = _ "Provider=SQLOLEDB;" & _ "Persist Security Info=False;" & _ "Data Source=w2003\ticketlog;" & _ "User ID=asp;" & _ "Password=asp;" & _ "Database=argonet;" & _ "Network Library=DBMSSOCN"
Ollie
"middletree" <mi********@HTOmail.com> wrote in message news:uR*************@TK2MSFTNGP15.phx.gbl... Sorry for the crosspost (I posted this on the asp.db group last night).
But since I had no answer there, I'm hoping for better luck here. I'm pretty much tried everything I know. Here's the problem:
I have an Intranet-based app at work, and I have it in two places there:
a dev machine and a production box. In both cases, the ASP files and SQL Server 2000 database are on the same box. I have it running smoothly in
both places at work.
However, I've been trying to set it up at home, and cannot make the SQL Server connection work for some reason. I've been working on this off and
on for weeks, and I just don't get what I am missing.
First, my code: <!-- #INCLUDE FILE="includes/dbinc.asp" --> which points to a page contaning only the followig lines:
======================= <% Dim strDBConnection strDBConnection = _ "Provider=SQLOLEDB;" & _ "Persist Security Info=False;" & _ "Data Source=w2003\ticketlog;" & _ "User ID=asp;" & _ "Password=asp;" & _ "Database=argonet;" Dim objConnection Set objConnection = Server.CreateObject("ADODB.Connection") objConnection.Open strDBConnection %> ==============================
It's at this point that I should add that this code is just like the working code from my stuff at work. Only the names have been changed. I should also add that here at home, the machine I am working on has been named "W2003", so when I set up SQL Server, it named the instance W2003\TICKETLOG.(Windows NT). Yes, it has that part with the parentheses. I don't think the slash is the problem.
Anyway, here is the message I see in the browser when I try to get to any page which calls this connection code.
==================================== Microsoft OLE DB Provider for SQL Server error '80040e4d' Login failed for user 'asp'. /ticketlog/includes/argodbinc.asp, line 15 ====================================
I want to add that I did go to the server in EP, went to Security, then doule-clicked the user called asp, and went to the database tab to make
sure that db_owner and everything else is checked. I then did the same for INETUSER.
Ok, so pretend I have never done any of this before. What steps do I need
to set up this thing? In my case, I did add a user named asp and gave full permissions, but assume I haven't done that. Perhaps with detailed hand-holding instructions, I'll see what I am missing.
Try "Network Library=dbnmpntw" as you are not using the IP address.
Have you tried "localhost" instead of "w2003" in the Data Source"???
"middletree" <mi********@HTOmail.com> wrote in message
news:ut**************@TK2MSFTNGP15.phx.gbl...
It gave me a different error:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
denied.
"Ollie" <ol**********@hotmail.com> wrote in message
news:u3**************@TK2MSFTNGP12.phx.gbl... Hi,
I sometimes have the same problem when connecting to different SQL
servers. Try adding "Network Library=DBMSSOCN" to the end of your connection
string. Like this...
I'm not promising anything though ;-)
strDBConnection = _ "Provider=SQLOLEDB;" & _ "Persist Security Info=False;" & _ "Data Source=w2003\ticketlog;" & _ "User ID=asp;" & _ "Password=asp;" & _ "Database=argonet;" & _ "Network Library=DBMSSOCN"
Ollie
"middletree" <mi********@HTOmail.com> wrote in message news:uR*************@TK2MSFTNGP15.phx.gbl... Sorry for the crosspost (I posted this on the asp.db group last night).
But since I had no answer there, I'm hoping for better luck here. I'm pretty much tried everything I know. Here's the problem:
I have an Intranet-based app at work, and I have it in two places there:
a dev machine and a production box. In both cases, the ASP files and SQL Server 2000 database are on the same box. I have it running smoothly in
both places at work.
However, I've been trying to set it up at home, and cannot make the SQL Server connection work for some reason. I've been working on this off and
on for weeks, and I just don't get what I am missing.
First, my code: <!-- #INCLUDE FILE="includes/dbinc.asp" --> which points to a page contaning only the followig lines:
======================= <% Dim strDBConnection strDBConnection = _ "Provider=SQLOLEDB;" & _ "Persist Security Info=False;" & _ "Data Source=w2003\ticketlog;" & _ "User ID=asp;" & _ "Password=asp;" & _ "Database=argonet;" Dim objConnection Set objConnection = Server.CreateObject("ADODB.Connection") objConnection.Open strDBConnection %> ==============================
It's at this point that I should add that this code is just like the working code from my stuff at work. Only the names have been changed. I should also add that here at home, the machine I am working on has been named "W2003", so when I set up SQL Server, it named the instance W2003\TICKETLOG.(Windows NT). Yes, it has that part with the parentheses. I don't think the slash is the problem.
Anyway, here is the message I see in the browser when I try to get to any page which calls this connection code.
==================================== Microsoft OLE DB Provider for SQL Server error '80040e4d' Login failed for user 'asp'. /ticketlog/includes/argodbinc.asp, line 15 ====================================
I want to add that I did go to the server in EP, went to Security, then doule-clicked the user called asp, and went to the database tab to make
sure that db_owner and everything else is checked. I then did the same for INETUSER.
Ok, so pretend I have never done any of this before. What steps do I need
to set up this thing? In my case, I did add a user named asp and gave full permissions, but assume I haven't done that. Perhaps with detailed hand-holding instructions, I'll see what I am missing.
I'm at work now, so I'll have to try that tonight.
No, I haven't tried localhost yet.
"Ollie" <ol**********@hotmail.com> wrote in message
news:uL**************@tk2msftngp13.phx.gbl... Try "Network Library=dbnmpntw" as you are not using the IP address.
Have you tried "localhost" instead of "w2003" in the Data Source"???
"middletree" <mi********@HTOmail.com> wrote in message news:ut**************@TK2MSFTNGP15.phx.gbl... It gave me a different error:
[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
"Ollie" <ol**********@hotmail.com> wrote in message news:u3**************@TK2MSFTNGP12.phx.gbl... Hi,
I sometimes have the same problem when connecting to different SQL servers. Try adding "Network Library=DBMSSOCN" to the end of your connection string. Like this...
I'm not promising anything though ;-)
strDBConnection = _ "Provider=SQLOLEDB;" & _ "Persist Security Info=False;" & _ "Data Source=w2003\ticketlog;" & _ "User ID=asp;" & _ "Password=asp;" & _ "Database=argonet;" & _ "Network Library=DBMSSOCN"
Ollie
"middletree" <mi********@HTOmail.com> wrote in message news:uR*************@TK2MSFTNGP15.phx.gbl... Sorry for the crosspost (I posted this on the asp.db group last night). But since I had no answer there, I'm hoping for better luck here. I'm pretty much tried everything I know. Here's the problem:
I have an Intranet-based app at work, and I have it in two places
there: a dev machine and a production box. In both cases, the ASP files and SQL Server 2000 database are on the same box. I have it running smoothly in both places at work.
However, I've been trying to set it up at home, and cannot make the SQL Server connection work for some reason. I've been working on this off
and on for weeks, and I just don't get what I am missing.
First, my code: <!-- #INCLUDE FILE="includes/dbinc.asp" --> which points to a page contaning only the followig lines:
======================= <% Dim strDBConnection strDBConnection = _ "Provider=SQLOLEDB;" & _ "Persist Security Info=False;" & _ "Data Source=w2003\ticketlog;" & _ "User ID=asp;" & _ "Password=asp;" & _ "Database=argonet;" Dim objConnection Set objConnection = Server.CreateObject("ADODB.Connection") objConnection.Open strDBConnection %> ==============================
It's at this point that I should add that this code is just like the working code from my stuff at work. Only the names have been changed. I should also add that here at home, the machine I am working on has been named "W2003", so when I set up SQL Server, it named the instance W2003\TICKETLOG.(Windows NT). Yes, it has that part with the
parentheses. I don't think the slash is the problem.
Anyway, here is the message I see in the browser when I try to get to
any page which calls this connection code.
==================================== Microsoft OLE DB Provider for SQL Server error '80040e4d' Login failed for user 'asp'. /ticketlog/includes/argodbinc.asp, line 15 ====================================
I want to add that I did go to the server in EP, went to Security, then doule-clicked the user called asp, and went to the database tab to make sure that db_owner and everything else is checked. I then did the same for INETUSER.
Ok, so pretend I have never done any of this before. What steps do I
need to set up this thing? In my case, I did add a user named asp and gave full permissions, but assume I haven't done that. Perhaps with detailed hand-holding instructions, I'll see what I am missing.
But when you connect the DB using QA, are you logging into the SQL Server as
the "asp" user or are you using your own logon credentials?
Ray at work
"middletree" <mi********@HTOmail.com> wrote in message
news:Ot**************@TK2MSFTNGP10.phx.gbl... I'm not sure what you mean. I open up QA just fine. I don't see any way to use QA to connect with anything, though.
"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in message news:u6**************@tk2msftngp13.phx.gbl... Try opening up Query Analyzer and connecting to that SQL Server with asp/asp credentials. Does that work?
I didn't log on. I just opened it like any other program.
"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in
message news:eB**************@TK2MSFTNGP09.phx.gbl... But when you connect the DB using QA, are you logging into the SQL Server
as the "asp" user or are you using your own logon credentials?
Ray at work
"middletree" <mi********@HTOmail.com> wrote in message news:Ot**************@TK2MSFTNGP10.phx.gbl... I'm not sure what you mean. I open up QA just fine. I don't see any way
to use QA to connect with anything, though.
"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in message news:u6**************@tk2msftngp13.phx.gbl... Try opening up Query Analyzer and connecting to that SQL Server with asp/asp credentials. Does that work?
Right, probably because it's automatically logging you in with your Windows
credentials, like if you're opening it up from Enterprise Manager. Instead
of doing that, manually launch the program and specify asp/asp login
credentials. Or, if you have it already open, do a File---Connect, and
that'll give you the option to specificy other login credentials.
Ray at work
"middletree" <mi********@verywarmmail.com> wrote in message
news:%2****************@TK2MSFTNGP15.phx.gbl... I didn't log on. I just opened it like any other program.
"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in message news:eB**************@TK2MSFTNGP09.phx.gbl... But when you connect the DB using QA, are you logging into the SQL
Server as the "asp" user or are you using your own logon credentials?
Ray at work
"middletree" <mi********@HTOmail.com> wrote in message news:Ot**************@TK2MSFTNGP10.phx.gbl... I'm not sure what you mean. I open up QA just fine. I don't see any
way to use QA to connect with anything, though.
"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote
in message news:u6**************@tk2msftngp13.phx.gbl... > Try opening up Query Analyzer and connecting to that SQL Server with asp/asp > credentials. Does that work? >
OK, I'll try that at home tonight. But let's say that asp/asp combo does
work using QA, then what?
Or if it doesn't, then what?
"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in
message news:#p**************@TK2MSFTNGP10.phx.gbl... Right, probably because it's automatically logging you in with your
Windows credentials, like if you're opening it up from Enterprise Manager.
Instead of doing that, manually launch the program and specify asp/asp login credentials. Or, if you have it already open, do a File---Connect, and that'll give you the option to specificy other login credentials.
Ray at work
"middletree" <mi********@verywarmmail.com> wrote in message news:%2****************@TK2MSFTNGP15.phx.gbl... I didn't log on. I just opened it like any other program.
"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in message news:eB**************@TK2MSFTNGP09.phx.gbl... But when you connect the DB using QA, are you logging into the SQL Server as the "asp" user or are you using your own logon credentials?
Ray at work
"middletree" <mi********@HTOmail.com> wrote in message news:Ot**************@TK2MSFTNGP10.phx.gbl... > I'm not sure what you mean. I open up QA just fine. I don't see any way to > use QA to connect with anything, though. > > > "Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in > message news:u6**************@tk2msftngp13.phx.gbl... > > Try opening up Query Analyzer and connecting to that SQL Server
with > asp/asp > > credentials. Does that work? > > > >
"middletree" <mi********@verywarmmail.com> wrote in message
news:%2****************@TK2MSFTNGP09.phx.gbl... OK, I'll try that at home tonight. But let's say that asp/asp combo does work using QA, then what?
Then you ruled out that it's a login credentials issue.
Or if it doesn't, then what?
Then it's a login credentials issue.
:]
Ray at work
Thanks. What I meant was, I don't know what to do at that point.
"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in
message news:ug**************@TK2MSFTNGP09.phx.gbl... "middletree" <mi********@verywarmmail.com> wrote in message news:%2****************@TK2MSFTNGP09.phx.gbl... OK, I'll try that at home tonight. But let's say that asp/asp combo does work using QA, then what?
Then you ruled out that it's a login credentials issue.
Or if it doesn't, then what?
Then it's a login credentials issue.
:]
Ray at work
Well that very much depends on the result!
Ray at work
"middletree" <mi********@verywarmmail.com> wrote in message
news:OX**************@TK2MSFTNGP10.phx.gbl... Thanks. What I meant was, I don't know what to do at that point.
"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in message news:ug**************@TK2MSFTNGP09.phx.gbl... "middletree" <mi********@verywarmmail.com> wrote in message news:%2****************@TK2MSFTNGP09.phx.gbl... OK, I'll try that at home tonight. But let's say that asp/asp combo
does work using QA, then what?
Then you ruled out that it's a login credentials issue.
Or if it doesn't, then what?
Then it's a login credentials issue.
:]
Ray at work
If it's not a login credentials issue, then we need to look elsewhere for
the problem.
If you cannot login using asp/asp then there are two possibilities:
1. SQL Server is configured to do Integrated Authentication only, which
means that it is configured to only allow Windows accounts to log in.
Authentication will need to be switched to "Mixed" if you want to use a
non-Windows login, i.e. a SQL Login
2. SQL is configured correctly to allow "Mixed" authentication, but the
"asp" login account was never created on the SQL Server. In this case, you
will need to add the "asp" login account and grant it rights to your
database.
Bob Barrows
middletree wrote: Thanks. What I meant was, I don't know what to do at that point.
"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in message news:ug**************@TK2MSFTNGP09.phx.gbl... "middletree" <mi********@verywarmmail.com> wrote in message news:%2****************@TK2MSFTNGP09.phx.gbl... OK, I'll try that at home tonight. But let's say that asp/asp combo does work using QA, then what?
Then you ruled out that it's a login credentials issue.
Or if it doesn't, then what?
Then it's a login credentials issue.
:]
Ray at work
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
Yes, well, you and Ray are correct. When I tried to connect using the
asp/asp combo, it wouldn't let me in. When I went into the registration
properties, it said Windows authentication, when i could have sworn I
checked it abouit 10 times and it said mixed.
Anyway, in that window, I tried to change it to SQL authentication, and
typed asp/asp in there, and it wouldn't let me. It said that asp is not a
valid user.
This is really, really frustrating. 5 years of doing ASP with SQL Server,
and I have never had this kind of problem before. I am not sure what to do.
I guess I'll go in there and dig some more, make some changes, see what
happens.
Anyway, thanks for your help.
"Bob Barrows [MVP]" <re******@NOyahoo.SPAMcom> wrote in message
news:Oa**************@TK2MSFTNGP14.phx.gbl... If it's not a login credentials issue, then we need to look elsewhere for the problem.
If you cannot login using asp/asp then there are two possibilities:
1. SQL Server is configured to do Integrated Authentication only, which means that it is configured to only allow Windows accounts to log in. Authentication will need to be switched to "Mixed" if you want to use a non-Windows login, i.e. a SQL Login 2. SQL is configured correctly to allow "Mixed" authentication, but the "asp" login account was never created on the SQL Server. In this case, you will need to add the "asp" login account and grant it rights to your database.
Bob Barrows
middletree wrote: Thanks. What I meant was, I don't know what to do at that point.
"Ray Costanzo [MVP]" <my first name at lane 34 dot commercial> wrote in message news:ug**************@TK2MSFTNGP09.phx.gbl... "middletree" <mi********@verywarmmail.com> wrote in message news:%2****************@TK2MSFTNGP09.phx.gbl... OK, I'll try that at home tonight. But let's say that asp/asp combo does work using QA, then what?
Then you ruled out that it's a login credentials issue.
Or if it doesn't, then what?
Then it's a login credentials issue.
:]
Ray at work
-- Microsoft MVP -- ASP/ASP.NET Please reply to the newsgroup. The email account listed in my From header is my spam trap, so I don't check it very often. You will get a quicker response by posting to the newsgroup.
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: AMC |
last post by:
Hi,
I'm using an include file to store the connection string to a database.
Whenever I try to reference that string to open a connection in the page
that includes the file I get the error 'empy...
|
by: Pandis Ippokratis |
last post by:
Hi,
I have the following problem: I am implementing a server in Java and
I use jdbc to connect to an Oracle 9.0.2 db. All seem to work fine,
but when I intensionally cause a network failure...
|
by: Utada P.W. SIU |
last post by:
Thanks~~
|
by: lauren quantrell |
last post by:
Admitedly a very open-ended question but here goes ...
Why so may "Connection failure" error messages when my Access 2K users
are executing stored procedures that contain UPDATE or INSERT...
|
by: Diffident |
last post by:
Hello All,
I am trying to redirect users to a standby webpage in case our application
is down due to database server failure. To facilitate this I am opening a
test connection within a try/catch...
|
by: Jac |
last post by:
Hey,
How can I test if there is an connection-exception when using database
application block from the enterprise service?
I stopped the sqlserver.
I do now the following :
Database db =...
|
by: pvrsatya |
last post by:
hi all
i am using TCP/Ip
i am running server application in one PC
client application in other PC
i am connecting these thro PC's in LAN
If i remove the LAN cable
|
by: tulika dutta |
last post by:
after 8 hrs my MySQL connection with JDBC gets time out. It gives the error
java.sql.SQLException: No operations allowed after connection closed.Connection was implicitly closed due to underlying...
|
by: Cintury |
last post by:
Hi all,
I've developed a mobile application for windows mobile 5.0 that has been in use for a while (1 year and a couple of months). It was developed in visual studios 2005 with a back-end sql...
|
by: samadams_2006 |
last post by:
Hello,
I have a problem that I'm hoping someone will be able to help me
resolve.
1) I have a C# Web Site in which I connect to the database: "Install
Microsoft SQL Server 2005 Express...
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new...
|
by: conductexam |
last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and...
| |