Welcome to dbForumz.com!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

[Microsoft][SQL Native Client]Named Pipes Provider: Could ..

 
   Database Forums (Home) -> ODBC RSS
Next:  Query from Server1, View from Server 2  
Author Message
Bill Nguyen

External


Since: Oct 30, 2003
Posts: 12



(Msg. 1) Posted: Fri Feb 15, 2008 11:08 am
Post subject: [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [233].
Archived from groups: microsoft>public>sqlserver>odbc (more info?)

I'm getting the following error trying to use 32-bit client on a Win2003
64-bit server to connect to an SQLserver 2005 on a 32-bit remote Win 2003
server.
IF I use the 64-bit ODBC manager (SQL Native client or ODBC DSN), I got
connected without any problem. The problem is the application (Great Plains
Dynamics 10) only recognized 32-bit ODBC client.

Any help is greatly appreciated.

Bill

-----------------------



---------------------------
Microsoft SQL Server Login
---------------------------
Connection failed:
SQLState: '08001'
SQL Server Error: 233
[Microsoft][SQL Native Client]Named Pipes Provider: Could not open a
connection to SQL Server [233].
Connection failed:
SQLState: 'HYT00'
SQL Server Error: 0
[Microsoft][SQL Native Client]Login timeout expired
Connection failed:
SQLState: '08001'
SQL Server Error: 233
[Microsoft][SQL Native Client]An error has occurred while establishing a
connection to the server. When connecting to SQL Server 2005, this failure
may be caused by the fact that under the default settings SQL Server does
not allow remote connections.

---------------------------
OK
---------------------------

 >> Stay informed about: [Microsoft][SQL Native Client]Named Pipes Provider: Could .. 
Back to top
Login to vote
Ross Culver

External


Since: Feb 21, 2007
Posts: 6



(Msg. 2) Posted: Fri Feb 15, 2008 3:51 pm
Post subject: Re: [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [233]. [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Bill,

Did you set SQL to accept both TCP/IP and Named Pipes remote connections in
SQL Surface Area Configuration?

Ross


"Bill Nguyen" wrote in message

> I'm getting the following error trying to use 32-bit client on a Win2003
> 64-bit server to connect to an SQLserver 2005 on a 32-bit remote Win 2003
> server.
> IF I use the 64-bit ODBC manager (SQL Native client or ODBC DSN), I got
> connected without any problem. The problem is the application (Great
> Plains Dynamics 10) only recognized 32-bit ODBC client.
>
> Any help is greatly appreciated.
>
> Bill
>
> -----------------------
>
>
>
> ---------------------------
> Microsoft SQL Server Login
> ---------------------------
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 233
> [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a
> connection to SQL Server [233].
> Connection failed:
> SQLState: 'HYT00'
> SQL Server Error: 0
> [Microsoft][SQL Native Client]Login timeout expired
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 233
> [Microsoft][SQL Native Client]An error has occurred while establishing a
> connection to the server. When connecting to SQL Server 2005, this failure
> may be caused by the fact that under the default settings SQL Server does
> not allow remote connections.
>
> ---------------------------
> OK
> ---------------------------
>
>

 >> Stay informed about: [Microsoft][SQL Native Client]Named Pipes Provider: Could .. 
Back to top
Login to vote
Bill Nguyen

External


Since: Oct 30, 2003
Posts: 12



(Msg. 3) Posted: Fri Feb 15, 2008 3:51 pm
Post subject: Re: [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [233]. [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Ross;

You saved my day. Named Pipes was not enabled. I got it working now.

Thanks a million.

Bill


"Ross Culver" wrote in message

> Bill,
>
> Did you set SQL to accept both TCP/IP and Named Pipes remote connections
> in SQL Surface Area Configuration?
>
> Ross
>
>
> "Bill Nguyen" wrote in message
>
>> I'm getting the following error trying to use 32-bit client on a Win2003
>> 64-bit server to connect to an SQLserver 2005 on a 32-bit remote Win 2003
>> server.
>> IF I use the 64-bit ODBC manager (SQL Native client or ODBC DSN), I got
>> connected without any problem. The problem is the application (Great
>> Plains Dynamics 10) only recognized 32-bit ODBC client.
>>
>> Any help is greatly appreciated.
>>
>> Bill
>>
>> -----------------------
>>
>>
>>
>> ---------------------------
>> Microsoft SQL Server Login
>> ---------------------------
>> Connection failed:
>> SQLState: '08001'
>> SQL Server Error: 233
>> [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a
>> connection to SQL Server [233].
>> Connection failed:
>> SQLState: 'HYT00'
>> SQL Server Error: 0
>> [Microsoft][SQL Native Client]Login timeout expired
>> Connection failed:
>> SQLState: '08001'
>> SQL Server Error: 233
>> [Microsoft][SQL Native Client]An error has occurred while establishing a
>> connection to the server. When connecting to SQL Server 2005, this
>> failure may be caused by the fact that under the default settings SQL
>> Server does not allow remote connections.
>>
>> ---------------------------
>> OK
>> ---------------------------
>>
>>
>
>
 >> Stay informed about: [Microsoft][SQL Native Client]Named Pipes Provider: Could .. 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
Microsoft OLE DB Provider for ODBC Drivers - I am using an system ODBC created to access data on an AS/400. I can access the data fine, using the following query. SELECT F0101.* FROM CRPDTA.PILGRIM.CRPDTA.F0101 as F0101 where the first CRPDTA is the DSN name, PILGRIM is the AS/400 catalog, the..

The dreaded Microsoft OLE DB Provider for SQL Server -2147.. - Hi, I've recently started experiencing an error in one of our development environments whereby the user is pressing "submit" and their query is timing out. Now, i've ran a trace (using the SQLProfilerTSQL_REPLAY template in SQL Profiler) whil...

Configuration Help for Microsoft OLE DB Provider for DB2 - Below is the sp_addlinkedserver command I have executed. EXEC sp_addlinkedserver @server='DB2', @provider='DB2OLEDB', @catalog='AS400', @srvproduct='Microsoft OLE DB Provider for DB2', @provstr='Initial Catalog=AS400; Data Source=CARTER...

"SQL Native Client" / "SQL Server" drivers - When creating a system DSN via the ODBC Admistrator dialog.... What is the differecne between "SQL Native Client" and "SQL Server" drivers listed in the "Create New Data Source" drivers list? How do they differ?

Access Violation in SQL Server Native Client - Hi, has anybody found a similar Error or could this verified? When I run the following Statement: insert into FACFG_SML_IDX (FACFG_SML_IDX.WERK_ID,FACFG_SML_IDX.SML_ID,FACFG_SML_IDX.LAST_INDEX) values (?,?,0) I got an access violation here is the....
   Database Forums (Home) -> ODBC All times are: Pacific Time (US & Canada)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]