Driver={SQL Server}; Server=myserver; Database=ERdB;
UID=ERdB_User; PWD=password; (This user has access)
--
Provider=SQLOLEDB.1;Password=pr0ducts;Persist Security
Info=True;User ID=ERdB_User;Initial Catalog=erdB;Data
Source=myServer;Use Procedure for Prepare=1;Auto
Translate=True;Packet Size=4096;Workstation
ID=myPCName;Use Encryption for Data=False;Tag with column
collation when possible=False (This one is generated by
FPage)
Both of these work in Front Page if it's Socksified as
well as the Browser (ie6 on XP) if it's Socksified, but
if I remove Socks, I get the error.
I also tried an alternate DSN that points to an Alias SQL
instance using Named Pipes by specifing the appropriate
DLL used in the Client Network Utility for SQL.
I am baffled. HELP!!!!!!
I am not sure what you mean by Socks5. Do you mean you configured a proxy
server on the Internet Server?
Does SQL Server has latest SP3 installed? Is there any firewall involved?
You may check the following articles.
INF: TCP Ports Needed for Communication to SQL Server Through a Firewall
http://support.microsoft.com/default.aspx?scid=kb;EN-US;287932
Q328306 INF: Potential Causes of the "SQL Server Does Not Exist or Access
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q328306
This posting is provided "AS IS" with no warranties, and confers no rights.
Regards,
Bill Cheng
Microsoft Support Engineer
--------------------
| Content-Class: urn:content-classes:message
| From: "CMiller" <chad....@hp.com>
| Sender: "CMiller" <chad....@hp.com>
| Subject: [DBNETLIB]SQL Server does not exist or access denied
| Date: Thu, 5 Jun 2003 15:41:41 -0700
| Lines: 44
| Message-ID: <066d01c32bb3$a2045880$a401...@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcMrs6IEpqQugTQpSX6g2ZOutRvNyQ==
| Newsgroups: microsoft.public.sqlserver.connect
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.connect:36022
| NNTP-Posting-Host: TK2MSFTNGXA12 10.40.1.164
| X-Tomcat-NG: microsoft.public.sqlserver.connect
Yes. I use a socks server to 'get out' of out network and communicate
with various servers on the outside, usually via PCAnywhere. This setup
allows me to traverse our routers as our company has everything locked
down pretty well.
What I don't understand is if Ports 1433/34 are blocked by our routers
internally, then why can I browse a SQL powered website on my external
server which only allows ports 80 and 443, but I get this "DBNETLIB]
SQL Server does not exist or access denied" error when using the web
component. To me, this suggests that the web component is trying to find
the SQL server using one of these blocked ports. But why? It's on the
same machine! The instance of SQL should just show up. There is no need
to look for the instance via TCP/IP or even Named pipes. Shouldn't a DSN
on the local box be good enough? It works for everything else, but this
component.
You said --> "Does SQL Server has latest SP3 installed? Is there any
firewall involved?"
Yes, and YES, big time. SP3 and the latest patches are applied. I have
also read most of the articles you attached, but I am sure I glazed over
some of the important parts!
Our firewall does block 1433/34 thanks to that last SQL virus. The
server that this site is hosted on also blocks all ports but 80 and 443,
but the SQL powered sites work fine, it's just this wed component that
fails. I understand why 1433/34 are needed normally, but why then do all
other SQL things work, but this component does not?
The alternative I have is to hand code the spreadsheet generation [from
a recordset] manually, but I lose all the fancy features and embedded
advantages of the component. It would take me days to manually write an
equivelent using VB/ADO, etc. (I need to dive into .NET, I'm sure that
would solve my prob)
Thanks for the help.
Chad
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Can you ping the SQL Server from the computer where the OWC component lies?
Do you mean that SQL Server is on the same computer as OWC (so SQL Server
is also on Internet server)? If so, Shared Memory will be used instead of
TCP/IP. Can you use Query Analyzer to connect to SQL Server from the OWC
computer? If you view OWC page from the computer where OWC lies, does it
succeed? I am a little confused at the structure of your network topology.
I suggest that you first add a TCP/IP alias on OWC computer to point to SQL
Server and make sure Query Analyzer can connect to SQL Server.
If all the above is fine and just OWC cannot connect, can you directly
create OWC page using FrontPage on this Internet computer and check if it
can connect to the SQL Server?
This posting is provided "AS IS" with no warranties, and confers no rights.
Regards,
Bill Cheng
Microsoft Support Engineer
--------------------
| From: Chad Miller <chad....@hp.com>
| References: <066d01c32bb3$a2045880$a401...@phx.gbl>
| X-Newsreader: AspNNTP 1.50 (ActionJackson.com)
| Subject: Re: [DBNETLIB]SQL Server does not exist or access denied
| Mime-Version: 1.0
| Content-Type: text/plain; charset="us-ascii"
| Content-Transfer-Encoding: 7bit
| Message-ID: <OWpI2WqL...@TK2MSFTNGP11.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.connect
| Date: Mon, 09 Jun 2003 09:39:33 -0700
| NNTP-Posting-Host: actionjackson133.dsl.frii.net 216.17.147.133
| Lines: 1
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.connect:36081
| X-Tomcat-NG: microsoft.public.sqlserver.connect
--> Can you ping the SQL Server from the computer where the OWC
component lies? YES, it's on the same server
--> Do you mean that SQL Server is on the same computer as OWC (so SQL
Server is also on Internet server)? YES
--> If so, Shared Memory will be used instead of TCP/IP. Can you use
Query Analyzer to connect to SQL Server from the OWC computer? YES, SQL
Analyzer connects via Windows Auth (with my NT Logon) AND SQL Auth using
the same UID/PWD the rest of the site uses.
--> If you view OWC page from the computer where OWC lies, does it
succeed? Actually, NO. Sitting directly on the server fails, but again,
only with this component. The rest of the site works ok. This has me
really baffled.
--> I suggest that you first add a TCP/IP alias on OWC computer to point
to SQL Server and make sure Query Analyzer can connect to SQL Server.
I tried making an alias with Client Net Util. using TCP/IP, dynamic
Port, but this fails with: Msg6, Level 16, State 1 [Microsoft][ODBC SQL
Server Driver][TCP/IP Sockets]Specified SQL Server not found. TCP/IP is
the first protocol in the order. I allow both Named Pipes and TCP/IP. I
have not been able to successfully set up an alias on my dev server, or
LCCC.
--> If all the above is fine and just OWC cannot connect, can you
directly create OWC page using FrontPage on this Internet computer and
check if it can connect to the SQL Server?
Office and FP are not installed on the server because I will get roasted
(by other members) if I introduce FP extensions to this server! We've
had too many problems in the past when mixing FP Ext with ASP. Could
this be the problem? I can't see how since the page loads OK when SOCKS
is involved.
Thanks a ton for your help. I hope I've explained myself well enough.
There are certain aspects that I am a little vague on myself...
It is quite strange that Query Analyzer can connect to the SQL Server on
LCCC, while you cannot setup a TCP/IP alias for LCCC.
Could you post the SQL Server error log, so that I can check?
This posting is provided "AS IS" with no warranties, and confers no rights.
Regards,
Bill Cheng
Microsoft Support Engineer
--------------------
| From: Chad Miller <anon...@devdex.com>
| References: <OWpI2WqL...@TK2MSFTNGP11.phx.gbl>
| X-Newsreader: AspNNTP 1.50 (ActionJackson.com)
| Subject: Re: [DBNETLIB]SQL Server does not exist or access denied
| Mime-Version: 1.0
| Content-Type: text/plain; charset="us-ascii"
| Content-Transfer-Encoding: 7bit
| Message-ID: <eWzXCT3L...@TK2MSFTNGP11.phx.gbl>
| Newsgroups: microsoft.public.sqlserver.connect
| Date: Tue, 10 Jun 2003 10:21:40 -0700
| NNTP-Posting-Host: actionjackson133.dsl.frii.net 216.17.147.133
| Lines: 1
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.connect:36098
| X-Tomcat-NG: microsoft.public.sqlserver.connect
Can you use Query Analyzer to connect to SQL Server from
the OWC computer? Yes. I used multiple UIDs and PSWs and
they all connect fine.
If you view OWC page from the computer where OWC lies,
does it succeed? No. The page hangs, then I get the SQL
Error, and in the source of the page near the bottom, the
message "This page requires the Microsoft Office Web
Components." appears. I didn't see this before because
for some reason it is not rendered in the browser, but
the server adds it to the source along the way. OWC IS
installed on LCCC, but that's it. No Office and No
FrontPage extensions.
I thought I sent a reply with a better explanation of my
topology, but It appears it vanished. Here is what I have:
I am in a corp network (HP) where I manage Win2k web
servers for both production and development, as well as a
win2k inTERnet box (I'll call LCCC, the one I've having
issues with) that I remotely manage. LCCC sits on an
external network, essentially on the inTERnet and we use
IIS to filter out IPs. My ASP/SQL application on the
development site (inTRAnet) works fine connecting to SQL
for me and it also works fine on LCCC for me an external
users as far as it delivering data from the SQL2000 db,
save for this OWC component. The Excel sheet builder
works on the development box, but not on LCCC. We're at SP
(latest) and all patches have been religiously applied
without incident. (I mentioned that ports 1433/34 are
blocked by our corp routers) but this does not seem to
affect me hitting the external site through a browser
norally. **Structurally, the only difference is that my
dev server accesses SQL2000 on a different machine, but
on the same network while LCCC has a local instance of
SQL2000 installed. Again, the LCCC delivers up SQL data
just fine.
I've had difficulty setting up an alias and DSN on LCCC.
Setting up the Alias in the Client Network Utility that
points to the local instance using TCP/IP works OK, but
making the DSN fails whether I use NT Auth, or a valid
SQL account. I get "Connection Failed: SQL State '01000'
SQL Server Error: 11001 []ODBC SQL Server Driver][TCP/IP
Sockets] ConnectionOpen (Connect())" and the SQL Server
not found error. It's similar to the error I get in the
browser, except the browser has the [DBNETLIB] in front
of it.
Per one of the Q docs referenced, I tried adding
the "network=DBNETLIB" to the connect string to no avail.
I think if I solve the Alias issue, it might solve the
problem. What am I doing wrong or what am I forgetting?
>.
>
Just want to let you I am performing further research on it. If there is
update, I will let you know.
This posting is provided "AS IS" with no warranties, and confers no rights.
Regards,
Bill Cheng
Microsoft Support Engineer
--------------------
| Content-Class: urn:content-classes:message
| From: "Chad Miller" <chad....@hp.com>
| Sender: "Chad Miller" <chad....@hp.com>
| References: <066d01c32bb3$a2045880$a401...@phx.gbl>
<OWpI2WqL...@TK2MSFTNGP11.phx.gbl>
<WsxBKv1L...@cpmsftngxa06.phx.gbl>
| Subject: Re: [DBNETLIB]SQL Server does not exist or access denied
| Date: Wed, 18 Jun 2003 13:10:50 -0700
| Lines: 187
| Message-ID: <023101c335d5$b67c6e20$a501...@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcM11bZ8gTK6rhZATtijCTk4zr79Tw==
| Newsgroups: microsoft.public.sqlserver.connect
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.connect:36216
| NNTP-Posting-Host: TK2MSFTNGXA13 10.40.1.165
| X-Tomcat-NG: microsoft.public.sqlserver.connect
From your description, Setting up the Alias in the Client Network Utility
that points to the local instance using TCP/IP works OK. Do you mean you
can connect with Query Analyzer with that alias to the local SQL Server?
If so, how do you set up your OWC page? Could you let me know the detailed
steps you create the page? I think we do not need a DSN. I can see when we
specify connection in Office Chart component, we can select Microsoft SQL
Server, not ODBC DSN.
This posting is provided "AS IS" with no warranties, and confers no rights.
Regards,
Bill Cheng
Microsoft Support Engineer
--------------------
| Content-Class: urn:content-classes:message
| From: "Chad Miller" <chad....@hp.com>
| Sender: "Chad Miller" <chad....@hp.com>
| References: <066d01c32bb3$a2045880$a401...@phx.gbl>
<OWpI2WqL...@TK2MSFTNGP11.phx.gbl>
<WsxBKv1L...@cpmsftngxa06.phx.gbl>
| Subject: Re: [DBNETLIB]SQL Server does not exist or access denied
| Date: Wed, 18 Jun 2003 13:10:50 -0700
| Lines: 187
| Message-ID: <023101c335d5$b67c6e20$a501...@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcM11bZ8gTK6rhZATtijCTk4zr79Tw==
| Newsgroups: microsoft.public.sqlserver.connect
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.connect:36216
| NNTP-Posting-Host: TK2MSFTNGXA13 10.40.1.165
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
With success inside my network on my development server,
I have been using a OLE type connection (ie: DSN-less).
I use the following code in an include that every page
uses:
UID = Session("SQLUser")
PWD = Session("SQLPwd")
Set DBConnection = Server.CreateObject "ADODB.Connection")
SQLconStr = "Driver={SQL Server}; Server=" & SQLServer
& "; Database=" & dB & "; UID=" & UID & "; PWD="& PWD
& ";"
DBConnection.Open SQLconStr
I have been unable to set up an Alias. In the Client
Tool, I specify an Alias name using TCP/IP, then I create
a DSN. In the DSN dropdown, my new Alias is listed, but
when I finish the wizard and test the connection, I
get: "[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]
Specified SQL server not found." I get this on both the
development and the external server, so I gave up on DSNs
and Aliasing because my OLE conn works for the rest of
the site anyway.
Query Analyzer does NOT connect using the Alias either,
though the alias name does show up in the list. QA does
work if I use [Local] and a valid user/pass.
To set up the component, I open Frontpage(2002-SP1) and
add a web component. Through the ActiveX Data Source tab,
I select Edit, +New SQL Server Connection, then my local
server (LCCCSQL) and supply a valid user/pass and select
the table. Voila! It finds all the data and presents the
page fine. I then save this page on the webserver and it
works as expected via a browser. The connection string
created by front page looks like this:
<c:ConnectionString>Provider=SQLOLEDB.1;Password=pr0
ducts;Persist Security Info=True;User
ID=ERdB_ServiceCenter;Data Source=LCCCSQL;Use Procedure
for Prepare=1;Auto Translate=True;Packet
Size=4096;Workstation ID=CHADMXW4000;Use Encryption for
Data=False;Tag with column collation when
possible=False;Initial
Catalog=erdB</c:ConnectionString>
If I substitute this connection string with:
Driver={SQL Server}; ServerLCCCSQL; Database=ERdB;
UID=myUser; PWD=myPass;
the component STILL works flawlessly, so I know the issue
is not with the connection string. I've also done it with
a DSN (not using Aliases) and it works fine.
The problem is when I copy this page to the 'external'
server and attempt to pull up the page. This is when I
get the [NETLIB] error.
What I don't understand is if everything (relatively) is
identical code-wise, why does only the component choke on
the external server, and not the rest of the SQL-powered
site? I did mention that I can open a browser using
SocksCap (Which traverses ports) and the component opens
and displays the data just fine from the external server.
Again, this leads me to believe that ports 1433/34 are
being engaged somehow. Since the SQL instance is local to
the external server, this should not be the case, should
it?
>.
>
This seems to be a weird issue. Could you post the SQL Server error log?
From your description, if you create TCP/IP alias to point to the SQL
Server, Query Analyzer cannot connect, while it can connect using
"(local)". Since when connecting using "(local)", it uses Shared Memory
protocol instead of TCP/IP protocol, I want to check if SQL Server listens
on TCP/IP port.
This posting is provided "AS IS" with no warranties, and confers no rights.
Regards,
Bill Cheng
Microsoft Support Engineer
--------------------
| Content-Class: urn:content-classes:message
| From: "Chad Miller" <chad....@hp.com>
| Sender: "Chad Miller" <chad....@hp.com>
| References: <066d01c32bb3$a2045880$a401...@phx.gbl>
<OWpI2WqL...@TK2MSFTNGP11.phx.gbl>
<WsxBKv1L...@cpmsftngxa06.phx.gbl>
<023101c335d5$b67c6e20$a501...@phx.gbl>
<WoxwRv5N...@cpmsftngxa06.phx.gbl>
| Subject: Re: [DBNETLIB]SQL Server does not exist or access denied
| Date: Mon, 7 Jul 2003 10:21:28 -0700
| Lines: 362
| Message-ID: <003b01c344ac$33483620$a501...@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcNErDNIWyDwY5OTREWjhptJxByOMQ==
| Newsgroups: microsoft.public.sqlserver.connect
| Path: cpmsftngxa09.phx.gbl
| Xref: cpmsftngxa09.phx.gbl microsoft.public.sqlserver.connect:2022
2003-07-03 18:09:30.79 server Microsoft SQL Server
2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195:
Service Pack 4)
2003-07-03 18:09:30.79 server Copyright (C) 1988-2002
Microsoft Corporation.
2003-07-03 18:09:30.79 server All rights reserved.
2003-07-03 18:09:30.79 server Server Process ID is 860.
2003-07-03 18:09:30.81 server Logging SQL Server
messages in file 'C:\Program Files\Microsoft SQL
Server\MSSQL\log\ERRORLOG'.
2003-07-03 18:09:30.90 server SQL Server is starting
at priority class 'high'(2 CPUs detected).
2003-07-03 18:09:31.26 server Working Set size set to
974064 kilobytes.
2003-07-03 18:09:32.00 server SQL Server configured
for thread mode processing.
2003-07-03 18:09:32.01 server Using dynamic lock
allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2003-07-03 18:09:32.25 server Attempting to initialize
Distributed Transaction Coordinator.
2003-07-03 18:09:35.78 spid4 Starting up
database 'master'.
2003-07-03 18:09:38.41 server Using 'SSNETLIB.DLL'
version '8.0.760'.
2003-07-03 18:09:38.41 spid5 Starting up
database 'model'.
2003-07-03 18:09:38.47 spid4 Server name is 'LCCC-
OS1'.
2003-07-03 18:09:38.63 spid8 Starting up
database 'msdb'.
2003-07-03 18:09:38.63 spid9 Starting up
database 'pubs'.
2003-07-03 18:09:38.63 spid10 Starting up
database 'Northwind'.
2003-07-03 18:09:38.67 spid11 Starting up
database 'Org_Alerts'.
2003-07-03 18:09:38.67 spid12 Starting up
database 'erdB'.
2003-07-03 18:09:38.71 spid13 Starting up
database 'erdB_Bakup'.
2003-07-03 18:09:38.75 spid14 Starting up
database 'nsd_hardware'.
2003-07-03 18:09:38.80 server SQL server listening on
192.170.22.11: 1433.
2003-07-03 18:09:38.80 server SQL server listening on
127.0.0.1: 1433.
2003-07-03 18:09:39.33 spid5 Clearing tempdb database.
2003-07-03 18:09:39.44 server SQL server listening on
TCP, Shared Memory.
2003-07-03 18:09:39.44 server SQL Server is ready for
client connections
2003-07-03 18:09:41.25 spid5 Starting up
database 'tempdb'.
2003-07-03 18:09:44.44 spid4 Recovery complete.
2003-07-03 18:09:44.44 spid4 SQL global counter
collection task is created.
2003-07-03 18:09:51.34 spid51 Using 'xpsqlbot.dll'
version '2000.80.194' to execute extended stored
procedure 'xp_qv'.
2003-07-03 18:30:20.54 server SQL Server terminating
because of system shutdown.
>| <c:ConnectionString>Provider=SQLOLEDB.1;Password=pr0
>| ducts;Persist Security Info=True;User
>| ID=ERdB_ServiceCenter;Data Source=LCCCSQL;Use
Procedure
>| for Prepare=1;Auto Translate=True;Packet
>| Size=4096;Workstation ID=CHADMXW4000;Use Encryption
for
>| Data=False;Tag with column collation when
>| possible=False;Initial
>| Catalog=erdB</c:ConnectionString>
>.
>
>| <c:ConnectionString>Provider=SQLOLEDB.1;Password=pr0
>| ducts;Persist Security Info=True;User
>| ID=ERdB_ServiceCenter;Data Source=LCCCSQL;Use
Procedure
>| for Prepare=1;Auto Translate=True;Packet
>| Size=4096;Workstation ID=CHADMXW4000;Use Encryption
for
>| Data=False;Tag with column collation when
>| possible=False;Initial
>| Catalog=erdB</c:ConnectionString>
>.
>
From the SQL Server error log you posted:
2003-07-03 18:09:38.80 server SQL server listening on 192.170.22.11:
1433.
2003-07-03 18:09:38.80 server SQL server listening on 127.0.0.1: 1433.
SQL Server 2000 SP3 is listening on TCP/IP port 1433. Please perform the
following steps on the local computer:
a. Start the Client Network Utility.
b. In the General tab of the Server Alias Configuration dialog box, click
Add, and then click TCP/IP.
c. Enter an alias name in the Server Alias text box (LCCCOS1). The alias
can contain any name.
d. Enter the SQL Server 2000 computer name or IP address (192.170.22.11) in
the Computer Name text box. Do not add an instance name.
e. Use Query Analyzer to connect to "LCCCOS1". Does it work?
This posting is provided "AS IS" with no warranties, and confers no rights.
Regards,
Bill Cheng
Microsoft Support Engineer
--------------------
| Content-Class: urn:content-classes:message
| From: "Chad Miller" <chad....@hp.com>
| Sender: "Chad Miller" <chad....@hp.com>
| References: <066d01c32bb3$a2045880$a401...@phx.gbl>
<OWpI2WqL...@TK2MSFTNGP11.phx.gbl>
<WsxBKv1L...@cpmsftngxa06.phx.gbl>
<023101c335d5$b67c6e20$a501...@phx.gbl>
<WoxwRv5N...@cpmsftngxa06.phx.gbl>
<003b01c344ac$33483620$a501...@phx.gbl>
<j7ufu3WR...@cpmsftngxa09.phx.gbl>
| Subject: Re: [DBNETLIB]SQL Server does not exist or access denied
| Date: Thu, 10 Jul 2003 08:27:04 -0700
| Lines: 567
| Message-ID: <013c01c346f7$b788fb20$a101...@phx.gbl>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Thread-Index: AcNG97eIKXslIBlpRAC33SZr/Q/k6g==
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Newsgroups: microsoft.public.sqlserver.connect
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.connect:36580
| NNTP-Posting-Host: TK2MSFTNGXA09 10.40.1.161
| X-Tomcat-NG: microsoft.public.sqlserver.connect