ASP connection to SQL Server Problem

[Bob Barrows]

John Davis wrote:

> I had problem to make my ASP-ADO-SQL Server connection works. It
> throws the following error and I have no idea what's going on.
>
> Microsoft OLE DB Provider for SQL Server (0x80004005)
> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
> access denied.
>
> Here's the code fragment:
>
> Set dbConn = Server.CreateObject("ADODB.Connection")
> dbConn.Open "Provider=SQLOLEDB;Data
> Source=MYCOMPUTERNAME\\MYSQL;Initial Catalog=Northwind;Integrated
> Security=SSPI"
>
> Please advice.
> Thanks!!

Start here:
[url]http://www.aspfaq.com/show.asp?id=2009[/url]

HTH,
Bob Barrows

[Bob Barrows]

John Davis wrote:

> I had problem to make my ASP-ADO-SQL Server connection works. It
> throws the following error and I have no idea what's going on.
>
> Microsoft OLE DB Provider for SQL Server (0x80004005)
> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
> access denied.
>
> Here's the code fragment:
>
> Set dbConn = Server.CreateObject("ADODB.Connection")
> dbConn.Open "Provider=SQLOLEDB;Data
> Source=MYCOMPUTERNAME\\MYSQL;Initial Catalog=Northwind;Integrated
> Security=SSPI"
>
> Please advice.
> Thanks!!

Start here:
[url]http://www.aspfaq.com/show.asp?id=2009[/url]

HTH,
Bob Barrows

[Tom B]

You have two slashes after MYCOMPUTERNAME
"John Davis" <jrefactor@hotmail.com> wrote in message
news:%232wWCIrXDHA.2620@TK2MSFTNGP09.phx.gbl...

> I had problem to make my ASP-ADO-SQL Server connection works. It throws

the

> following error and I have no idea what's going on.
>
> Microsoft OLE DB Provider for SQL Server (0x80004005)
> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
> denied.
>
> Here's the code fragment:
>
> Set dbConn = Server.CreateObject("ADODB.Connection")
> dbConn.Open "Provider=SQLOLEDB;Data Source=MYCOMPUTERNAME\\MYSQL;Initial
> Catalog=Northwind;Integrated Security=SSPI"
>
> Please advice.
> Thanks!!
>
>

[Tom B]

You have two slashes after MYCOMPUTERNAME
"John Davis" <jrefactor@hotmail.com> wrote in message
news:%232wWCIrXDHA.2620@TK2MSFTNGP09.phx.gbl...

> I had problem to make my ASP-ADO-SQL Server connection works. It throws

the

> following error and I have no idea what's going on.
>
> Microsoft OLE DB Provider for SQL Server (0x80004005)
> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
> denied.
>
> Here's the code fragment:
>
> Set dbConn = Server.CreateObject("ADODB.Connection")
> dbConn.Open "Provider=SQLOLEDB;Data Source=MYCOMPUTERNAME\\MYSQL;Initial
> Catalog=Northwind;Integrated Security=SSPI"
>
> Please advice.
> Thanks!!
>
>

[John Davis]

After deleting the one slash, then it throws another error. I am using
Windows Authetication in my desktop, should I change to use SQL Server
authetication??

Microsoft OLE DB Provider for SQL Server (0x80040E4D)
??? 'MYCOMPUTER\IUSR_MYCOMPUTER' ??????


"Tom B" <shuckle@NOSPAMhotmail.com> wrote in message
news:uD5fCKtXDHA.1736@TK2MSFTNGP10.phx.gbl...

> You have two slashes after MYCOMPUTERNAME
> "John Davis" <jrefactor@hotmail.com> wrote in message
> news:%232wWCIrXDHA.2620@TK2MSFTNGP09.phx.gbl...

> > I had problem to make my ASP-ADO-SQL Server connection works. It throws

> the

> > following error and I have no idea what's going on.
> >
> > Microsoft OLE DB Provider for SQL Server (0x80004005)
> > [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or

access

> > denied.
> >
> > Here's the code fragment:
> >
> > Set dbConn = Server.CreateObject("ADODB.Connection")
> > dbConn.Open "Provider=SQLOLEDB;Data

Source=MYCOMPUTERNAME\\MYSQL;Initial

> > Catalog=Northwind;Integrated Security=SSPI"
> >
> > Please advice.
> > Thanks!!
> >
> >

>
>

[John Davis]

After deleting the one slash, then it throws another error. I am using
Windows Authetication in my desktop, should I change to use SQL Server
authetication??

Microsoft OLE DB Provider for SQL Server (0x80040E4D)
??? 'MYCOMPUTER\IUSR_MYCOMPUTER' ??????


"Tom B" <shuckle@NOSPAMhotmail.com> wrote in message
news:uD5fCKtXDHA.1736@TK2MSFTNGP10.phx.gbl...

> You have two slashes after MYCOMPUTERNAME
> "John Davis" <jrefactor@hotmail.com> wrote in message
> news:%232wWCIrXDHA.2620@TK2MSFTNGP09.phx.gbl...

> > I had problem to make my ASP-ADO-SQL Server connection works. It throws

> the

> > following error and I have no idea what's going on.
> >
> > Microsoft OLE DB Provider for SQL Server (0x80004005)
> > [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or

access

> > denied.
> >
> > Here's the code fragment:
> >
> > Set dbConn = Server.CreateObject("ADODB.Connection")
> > dbConn.Open "Provider=SQLOLEDB;Data

Source=MYCOMPUTERNAME\\MYSQL;Initial

> > Catalog=Northwind;Integrated Security=SSPI"
> >
> > Please advice.
> > Thanks!!
> >
> >

>
>

[Bob Barrows]

[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;176379[/url]
[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;253500[/url]
[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;247931[/url]
[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;279526[/url]


John Davis wrote:

> After deleting the one slash, then it throws another error. I am using
> Windows Authetication in my desktop, should I change to use SQL Server
> authetication??
>
> Microsoft OLE DB Provider for SQL Server (0x80040E4D)
> ??? 'MYCOMPUTER\IUSR_MYCOMPUTER' ??????
>
>
> "Tom B" <shuckle@NOSPAMhotmail.com> wrote in message
> news:uD5fCKtXDHA.1736@TK2MSFTNGP10.phx.gbl...

>> You have two slashes after MYCOMPUTERNAME
>> "John Davis" <jrefactor@hotmail.com> wrote in message
>> news:%232wWCIrXDHA.2620@TK2MSFTNGP09.phx.gbl...

>>> I had problem to make my ASP-ADO-SQL Server connection works. It
>>> throws the following error and I have no idea what's going on.
>>>
>>> Microsoft OLE DB Provider for SQL Server (0x80004005)
>>> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
>>> access denied.
>>>
>>> Here's the code fragment:
>>>
>>> Set dbConn = Server.CreateObject("ADODB.Connection")
>>> dbConn.Open "Provider=SQLOLEDB;Data
>>> Source=MYCOMPUTERNAME\\MYSQL;Initial Catalog=Northwind;Integrated
>>> Security=SSPI"
>>>
>>> Please advice.
>>> Thanks!!

[Bob Barrows]

[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;176379[/url]
[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;253500[/url]
[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;247931[/url]
[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;279526[/url]


John Davis wrote:

> After deleting the one slash, then it throws another error. I am using
> Windows Authetication in my desktop, should I change to use SQL Server
> authetication??
>
> Microsoft OLE DB Provider for SQL Server (0x80040E4D)
> ??? 'MYCOMPUTER\IUSR_MYCOMPUTER' ??????
>
>
> "Tom B" <shuckle@NOSPAMhotmail.com> wrote in message
> news:uD5fCKtXDHA.1736@TK2MSFTNGP10.phx.gbl...

>> You have two slashes after MYCOMPUTERNAME
>> "John Davis" <jrefactor@hotmail.com> wrote in message
>> news:%232wWCIrXDHA.2620@TK2MSFTNGP09.phx.gbl...

>>> I had problem to make my ASP-ADO-SQL Server connection works. It
>>> throws the following error and I have no idea what's going on.
>>>
>>> Microsoft OLE DB Provider for SQL Server (0x80004005)
>>> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
>>> access denied.
>>>
>>> Here's the code fragment:
>>>
>>> Set dbConn = Server.CreateObject("ADODB.Connection")
>>> dbConn.Open "Provider=SQLOLEDB;Data
>>> Source=MYCOMPUTERNAME\\MYSQL;Initial Catalog=Northwind;Integrated
>>> Security=SSPI"
>>>
>>> Please advice.
>>> Thanks!!

[John Davis]

Thanks, but still didn't work. I try to figure out

My both IIS and SQL Server 2000 are on the same machine. And I should start
SQL Server Service Manager, right? I guess this is common sense, but just
want to make sure.



"Bob Barrows" <reb_01501@yahoo.com> wrote in message
news:OwXTgutXDHA.2424@TK2MSFTNGP12.phx.gbl...

> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;176379[/url]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;253500[/url]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;247931[/url]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;279526[/url]
>
>
> John Davis wrote:

> > After deleting the one slash, then it throws another error. I am using
> > Windows Authetication in my desktop, should I change to use SQL Server
> > authetication??
> >
> > Microsoft OLE DB Provider for SQL Server (0x80040E4D)
> > ??? 'MYCOMPUTER\IUSR_MYCOMPUTER' ??????
> >
> >
> > "Tom B" <shuckle@NOSPAMhotmail.com> wrote in message
> > news:uD5fCKtXDHA.1736@TK2MSFTNGP10.phx.gbl...

> >> You have two slashes after MYCOMPUTERNAME
> >> "John Davis" <jrefactor@hotmail.com> wrote in message
> >> news:%232wWCIrXDHA.2620@TK2MSFTNGP09.phx.gbl...
> >>> I had problem to make my ASP-ADO-SQL Server connection works. It
> >>> throws the following error and I have no idea what's going on.
> >>>
> >>> Microsoft OLE DB Provider for SQL Server (0x80004005)
> >>> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
> >>> access denied.
> >>>
> >>> Here's the code fragment:
> >>>
> >>> Set dbConn = Server.CreateObject("ADODB.Connection")
> >>> dbConn.Open "Provider=SQLOLEDB;Data
> >>> Source=MYCOMPUTERNAME\\MYSQL;Initial Catalog=Northwind;Integrated
> >>> Security=SSPI"
> >>>
> >>> Please advice.
> >>> Thanks!!

>
>
>

[John Davis]

Thanks, but still didn't work. I try to figure out

My both IIS and SQL Server 2000 are on the same machine. And I should start
SQL Server Service Manager, right? I guess this is common sense, but just
want to make sure.



"Bob Barrows" <reb_01501@yahoo.com> wrote in message
news:OwXTgutXDHA.2424@TK2MSFTNGP12.phx.gbl...

> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;176379[/url]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;253500[/url]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;247931[/url]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;279526[/url]
>
>
> John Davis wrote:

> > After deleting the one slash, then it throws another error. I am using
> > Windows Authetication in my desktop, should I change to use SQL Server
> > authetication??
> >
> > Microsoft OLE DB Provider for SQL Server (0x80040E4D)
> > ??? 'MYCOMPUTER\IUSR_MYCOMPUTER' ??????
> >
> >
> > "Tom B" <shuckle@NOSPAMhotmail.com> wrote in message
> > news:uD5fCKtXDHA.1736@TK2MSFTNGP10.phx.gbl...

> >> You have two slashes after MYCOMPUTERNAME
> >> "John Davis" <jrefactor@hotmail.com> wrote in message
> >> news:%232wWCIrXDHA.2620@TK2MSFTNGP09.phx.gbl...
> >>> I had problem to make my ASP-ADO-SQL Server connection works. It
> >>> throws the following error and I have no idea what's going on.
> >>>
> >>> Microsoft OLE DB Provider for SQL Server (0x80004005)
> >>> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
> >>> access denied.
> >>>
> >>> Here's the code fragment:
> >>>
> >>> Set dbConn = Server.CreateObject("ADODB.Connection")
> >>> dbConn.Open "Provider=SQLOLEDB;Data
> >>> Source=MYCOMPUTERNAME\\MYSQL;Initial Catalog=Northwind;Integrated
> >>> Security=SSPI"
> >>>
> >>> Please advice.
> >>> Thanks!!

>
>
>

[Bob Barrows]

[email]sam1967@hetnet.nl[/email] wrote:

> On Sat, 9 Aug 2003 19:17:17 -0700, "John Davis"
> <jrefactor@hotmail.com> wrote:
>

>> Thanks, but still didn't work. I try to figure out
>>
>> My both IIS and SQL Server 2000 are on the same machine. And I
>> should start SQL Server Service Manager, right? I guess this is
>> common sense, but just want to make sure.
>>

> why not try it with access first and then try it with SQL Server.

Just curious: why would that be relevant?

[Bob Barrows]

[email]sam1967@hetnet.nl[/email] wrote:

> On Sat, 9 Aug 2003 19:17:17 -0700, "John Davis"
> <jrefactor@hotmail.com> wrote:
>

>> Thanks, but still didn't work. I try to figure out
>>
>> My both IIS and SQL Server 2000 are on the same machine. And I
>> should start SQL Server Service Manager, right? I guess this is
>> common sense, but just want to make sure.
>>

> why not try it with access first and then try it with SQL Server.

Just curious: why would that be relevant?

[Bob Barrows]

I can't offer nay advice beyond the information in the KB articles and the
aspfaq article I posted earlier. My suggestion would be to reread them very
carefully and read all the articles whose links occur in the articles. I'm
sure your answer is in there.

Bob Barrows

John Davis wrote:

> Thanks, but still didn't work. I try to figure out
>
> My both IIS and SQL Server 2000 are on the same machine. And I should
> start SQL Server Service Manager, right? I guess this is common
> sense, but just want to make sure.
>
>
>
> "Bob Barrows" <reb_01501@yahoo.com> wrote in message
> news:OwXTgutXDHA.2424@TK2MSFTNGP12.phx.gbl...

>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;176379[/url]
>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;253500[/url]
>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;247931[/url]
>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;279526[/url]
>>
>>
>> John Davis wrote:

>>> After deleting the one slash, then it throws another error. I am
>>> using Windows Authetication in my desktop, should I change to use
>>> SQL Server authetication??
>>>
>>> Microsoft OLE DB Provider for SQL Server (0x80040E4D)
>>> ??? 'MYCOMPUTER\IUSR_MYCOMPUTER' ??????
>>>
>>>
>>> "Tom B" <shuckle@NOSPAMhotmail.com> wrote in message
>>> news:uD5fCKtXDHA.1736@TK2MSFTNGP10.phx.gbl...
>>>> You have two slashes after MYCOMPUTERNAME
>>>> "John Davis" <jrefactor@hotmail.com> wrote in message
>>>> news:%232wWCIrXDHA.2620@TK2MSFTNGP09.phx.gbl...
>>>>> I had problem to make my ASP-ADO-SQL Server connection works. It
>>>>> throws the following error and I have no idea what's going on.
>>>>>
>>>>> Microsoft OLE DB Provider for SQL Server (0x80004005)
>>>>> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist
>>>>> or access denied.
>>>>>
>>>>> Here's the code fragment:
>>>>>
>>>>> Set dbConn = Server.CreateObject("ADODB.Connection")
>>>>> dbConn.Open "Provider=SQLOLEDB;Data
>>>>> Source=MYCOMPUTERNAME\\MYSQL;Initial Catalog=Northwind;Integrated
>>>>> Security=SSPI"
>>>>>
>>>>> Please advice.
>>>>> Thanks!!

[Bob Barrows]

I can't offer nay advice beyond the information in the KB articles and the
aspfaq article I posted earlier. My suggestion would be to reread them very
carefully and read all the articles whose links occur in the articles. I'm
sure your answer is in there.

Bob Barrows

John Davis wrote:

> Thanks, but still didn't work. I try to figure out
>
> My both IIS and SQL Server 2000 are on the same machine. And I should
> start SQL Server Service Manager, right? I guess this is common
> sense, but just want to make sure.
>
>
>
> "Bob Barrows" <reb_01501@yahoo.com> wrote in message
> news:OwXTgutXDHA.2424@TK2MSFTNGP12.phx.gbl...

>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;176379[/url]
>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;253500[/url]
>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;247931[/url]
>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;279526[/url]
>>
>>
>> John Davis wrote:

>>> After deleting the one slash, then it throws another error. I am
>>> using Windows Authetication in my desktop, should I change to use
>>> SQL Server authetication??
>>>
>>> Microsoft OLE DB Provider for SQL Server (0x80040E4D)
>>> ??? 'MYCOMPUTER\IUSR_MYCOMPUTER' ??????
>>>
>>>
>>> "Tom B" <shuckle@NOSPAMhotmail.com> wrote in message
>>> news:uD5fCKtXDHA.1736@TK2MSFTNGP10.phx.gbl...
>>>> You have two slashes after MYCOMPUTERNAME
>>>> "John Davis" <jrefactor@hotmail.com> wrote in message
>>>> news:%232wWCIrXDHA.2620@TK2MSFTNGP09.phx.gbl...
>>>>> I had problem to make my ASP-ADO-SQL Server connection works. It
>>>>> throws the following error and I have no idea what's going on.
>>>>>
>>>>> Microsoft OLE DB Provider for SQL Server (0x80004005)
>>>>> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist
>>>>> or access denied.
>>>>>
>>>>> Here's the code fragment:
>>>>>
>>>>> Set dbConn = Server.CreateObject("ADODB.Connection")
>>>>> dbConn.Open "Provider=SQLOLEDB;Data
>>>>> Source=MYCOMPUTERNAME\\MYSQL;Initial Catalog=Northwind;Integrated
>>>>> Security=SSPI"
>>>>>
>>>>> Please advice.
>>>>> Thanks!!

[Dan Brussee]

In article <s0ucjvsjoi0bqlmbdu0cc559s0cs43c0o9@4ax.com>, sam1967
@hetnet.nl says...

> On Sun, 10 Aug 2003 10:50:41 -0400, "Bob Barrows"
> <reb_01501@yahoo.com> wrote:
>

> >sam1967@hetnet.nl wrote:

> >> On Sat, 9 Aug 2003 19:17:17 -0700, "John Davis"
> >> <jrefactor@hotmail.com> wrote:
> >>
> >>> Thanks, but still didn't work. I try to figure out
> >>>
> >>> My both IIS and SQL Server 2000 are on the same machine. And I
> >>> should start SQL Server Service Manager, right? I guess this is
> >>> common sense, but just want to make sure.
> >>>
> >> why not try it with access first and then try it with SQL Server.

> >
> >Just curious: why would that be relevant?
> >

> i have built a few simple ASP applications and have ported them
> between SQL and access and the other way.
> i often found it useful to workon an access database first because of
> simplified security and then port it over to SQL Server.
> just an idea.
>

I see your desire to work in a less restrictive environment first, but
assuming you know you are going to SQL Server anyway, why not just get
the connection string right up front and be done with it? You can still
use Access to see the SQL Server database and even use it's Query
Designer if you need to. Just make a link to the SQL Database in Access.
You can even write stored procedures, etc.


--

Remove NOT from email address to reply. AntiSpam in action.

[Dan Brussee]

In article <s0ucjvsjoi0bqlmbdu0cc559s0cs43c0o9@4ax.com>, sam1967
@hetnet.nl says...

> On Sun, 10 Aug 2003 10:50:41 -0400, "Bob Barrows"
> <reb_01501@yahoo.com> wrote:
>

> >sam1967@hetnet.nl wrote:

> >> On Sat, 9 Aug 2003 19:17:17 -0700, "John Davis"
> >> <jrefactor@hotmail.com> wrote:
> >>
> >>> Thanks, but still didn't work. I try to figure out
> >>>
> >>> My both IIS and SQL Server 2000 are on the same machine. And I
> >>> should start SQL Server Service Manager, right? I guess this is
> >>> common sense, but just want to make sure.
> >>>
> >> why not try it with access first and then try it with SQL Server.

> >
> >Just curious: why would that be relevant?
> >

> i have built a few simple ASP applications and have ported them
> between SQL and access and the other way.
> i often found it useful to workon an access database first because of
> simplified security and then port it over to SQL Server.
> just an idea.
>

I see your desire to work in a less restrictive environment first, but
assuming you know you are going to SQL Server anyway, why not just get
the connection string right up front and be done with it? You can still
use Access to see the SQL Server database and even use it's Query
Designer if you need to. Just make a link to the SQL Database in Access.
You can even write stored procedures, etc.


--

Remove NOT from email address to reply. AntiSpam in action.

[sam1967@hetnet.nl]

On Sun, 10 Aug 2003 17:41:27 GMT, Dan Brussee
<dbrussee@NOTbetterwaycomputing.com> wrote:

>In article <s0ucjvsjoi0bqlmbdu0cc559s0cs43c0o9@4ax.com>, sam1967
>@hetnet.nl says...

>> On Sun, 10 Aug 2003 10:50:41 -0400, "Bob Barrows"
>> <reb_01501@yahoo.com> wrote:
>>

>> >sam1967@hetnet.nl wrote:
>> >> On Sat, 9 Aug 2003 19:17:17 -0700, "John Davis"
>> >> <jrefactor@hotmail.com> wrote:
>> >>
>> >>> Thanks, but still didn't work. I try to figure out
>> >>>
>> >>> My both IIS and SQL Server 2000 are on the same machine. And I
>> >>> should start SQL Server Service Manager, right? I guess this is
>> >>> common sense, but just want to make sure.
>> >>>
>> >> why not try it with access first and then try it with SQL Server.
>> >
>> >Just curious: why would that be relevant?
>> >

>> i have built a few simple ASP applications and have ported them
>> between SQL and access and the other way.
>> i often found it useful to workon an access database first because of
>> simplified security and then port it over to SQL Server.
>> just an idea.
>>

>
>I see your desire to work in a less restrictive environment first, but
>assuming you know you are going to SQL Server anyway, why not just get
>the connection string right up front and be done with it? You can still
>use Access to see the SQL Server database and even use it's Query
>Designer if you need to. Just make a link to the SQL Database in Access.
>You can even write stored procedures, etc.

fair point. i dont do this full time but it looks as though i may be
doing a lot more of it in the near future.

[sam1967@hetnet.nl]

On Sun, 10 Aug 2003 17:41:27 GMT, Dan Brussee
<dbrussee@NOTbetterwaycomputing.com> wrote:

>In article <s0ucjvsjoi0bqlmbdu0cc559s0cs43c0o9@4ax.com>, sam1967
>@hetnet.nl says...

>> On Sun, 10 Aug 2003 10:50:41 -0400, "Bob Barrows"
>> <reb_01501@yahoo.com> wrote:
>>

>> >sam1967@hetnet.nl wrote:
>> >> On Sat, 9 Aug 2003 19:17:17 -0700, "John Davis"
>> >> <jrefactor@hotmail.com> wrote:
>> >>
>> >>> Thanks, but still didn't work. I try to figure out
>> >>>
>> >>> My both IIS and SQL Server 2000 are on the same machine. And I
>> >>> should start SQL Server Service Manager, right? I guess this is
>> >>> common sense, but just want to make sure.
>> >>>
>> >> why not try it with access first and then try it with SQL Server.
>> >
>> >Just curious: why would that be relevant?
>> >

>> i have built a few simple ASP applications and have ported them
>> between SQL and access and the other way.
>> i often found it useful to workon an access database first because of
>> simplified security and then port it over to SQL Server.
>> just an idea.
>>

>
>I see your desire to work in a less restrictive environment first, but
>assuming you know you are going to SQL Server anyway, why not just get
>the connection string right up front and be done with it? You can still
>use Access to see the SQL Server database and even use it's Query
>Designer if you need to. Just make a link to the SQL Database in Access.
>You can even write stored procedures, etc.

fair point. i dont do this full time but it looks as though i may be
doing a lot more of it in the near future.

[Jeff Cochran]

Can you access SQL Server through the Query Analyzer or Enterpirse
Manager?

Read the KB articles Bob posted, they're pretty much the entire SQL
connection nuts and bolts. Plus, post the *exact* error messages,
when you tell us "it still didn't work" there's not much help we can
point you to.

Jeff

On Sat, 9 Aug 2003 19:17:17 -0700, "John Davis"
<jrefactor@hotmail.com> wrote:

>Thanks, but still didn't work. I try to figure out
>
>My both IIS and SQL Server 2000 are on the same machine. And I should start
>SQL Server Service Manager, right? I guess this is common sense, but just
>want to make sure.
>
>
>
>"Bob Barrows" <reb_01501@yahoo.com> wrote in message
>news:OwXTgutXDHA.2424@TK2MSFTNGP12.phx.gbl...

>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;176379[/url]
>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;253500[/url]
>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;247931[/url]
>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;279526[/url]
>>
>>
>> John Davis wrote:

>> > After deleting the one slash, then it throws another error. I am using
>> > Windows Authetication in my desktop, should I change to use SQL Server
>> > authetication??
>> >
>> > Microsoft OLE DB Provider for SQL Server (0x80040E4D)
>> > ??? 'MYCOMPUTER\IUSR_MYCOMPUTER' ??????
>> >
>> >
>> > "Tom B" <shuckle@NOSPAMhotmail.com> wrote in message
>> > news:uD5fCKtXDHA.1736@TK2MSFTNGP10.phx.gbl...
>> >> You have two slashes after MYCOMPUTERNAME
>> >> "John Davis" <jrefactor@hotmail.com> wrote in message
>> >> news:%232wWCIrXDHA.2620@TK2MSFTNGP09.phx.gbl...
>> >>> I had problem to make my ASP-ADO-SQL Server connection works. It
>> >>> throws the following error and I have no idea what's going on.
>> >>>
>> >>> Microsoft OLE DB Provider for SQL Server (0x80004005)
>> >>> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
>> >>> access denied.
>> >>>
>> >>> Here's the code fragment:
>> >>>
>> >>> Set dbConn = Server.CreateObject("ADODB.Connection")
>> >>> dbConn.Open "Provider=SQLOLEDB;Data
>> >>> Source=MYCOMPUTERNAME\\MYSQL;Initial Catalog=Northwind;Integrated
>> >>> Security=SSPI"
>> >>>
>> >>> Please advice.
>> >>> Thanks!!

>>
>>
>>

>

[Jeff Cochran]

Can you access SQL Server through the Query Analyzer or Enterpirse
Manager?

Read the KB articles Bob posted, they're pretty much the entire SQL
connection nuts and bolts. Plus, post the *exact* error messages,
when you tell us "it still didn't work" there's not much help we can
point you to.

Jeff

On Sat, 9 Aug 2003 19:17:17 -0700, "John Davis"
<jrefactor@hotmail.com> wrote:

>Thanks, but still didn't work. I try to figure out
>
>My both IIS and SQL Server 2000 are on the same machine. And I should start
>SQL Server Service Manager, right? I guess this is common sense, but just
>want to make sure.
>
>
>
>"Bob Barrows" <reb_01501@yahoo.com> wrote in message
>news:OwXTgutXDHA.2424@TK2MSFTNGP12.phx.gbl...

>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;176379[/url]
>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;253500[/url]
>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;247931[/url]
>> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;279526[/url]
>>
>>
>> John Davis wrote:

>> > After deleting the one slash, then it throws another error. I am using
>> > Windows Authetication in my desktop, should I change to use SQL Server
>> > authetication??
>> >
>> > Microsoft OLE DB Provider for SQL Server (0x80040E4D)
>> > ??? 'MYCOMPUTER\IUSR_MYCOMPUTER' ??????
>> >
>> >
>> > "Tom B" <shuckle@NOSPAMhotmail.com> wrote in message
>> > news:uD5fCKtXDHA.1736@TK2MSFTNGP10.phx.gbl...
>> >> You have two slashes after MYCOMPUTERNAME
>> >> "John Davis" <jrefactor@hotmail.com> wrote in message
>> >> news:%232wWCIrXDHA.2620@TK2MSFTNGP09.phx.gbl...
>> >>> I had problem to make my ASP-ADO-SQL Server connection works. It
>> >>> throws the following error and I have no idea what's going on.
>> >>>
>> >>> Microsoft OLE DB Provider for SQL Server (0x80004005)
>> >>> [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
>> >>> access denied.
>> >>>
>> >>> Here's the code fragment:
>> >>>
>> >>> Set dbConn = Server.CreateObject("ADODB.Connection")
>> >>> dbConn.Open "Provider=SQLOLEDB;Data
>> >>> Source=MYCOMPUTERNAME\\MYSQL;Initial Catalog=Northwind;Integrated
>> >>> Security=SSPI"
>> >>>
>> >>> Please advice.
>> >>> Thanks!!

>>
>>
>>

>