Hi, All,
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
HawkHi Hawk,
Connection write using the Named Pipes library. There could be a
permission problem with Named Pipes /SMB or a restrictive Security Template
setting. Try connecting using TCP.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin,
Thanks, but how can change it to TCP? Could you tell me
more?
Have a good weekend
>--Original Message--
>Hi Hawk,
> Connection write using the Named Pipes library.
There could be a
>permission problem with Named Pipes /SMB or a
restrictive Security Template
>setting. Try connecting using TCP.
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>|||Use the SQL Client Network Utility and create a TCP alias. Enter the
actual servername for the alias, this way the client will use sockets
instead.
If you have MDAC 2.6 on the client you can also try this as a test.
osql -Stcp:ServerNameHere -UuserName -Ppassword
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thank you very much and have a good one
Hawk
Showing posts with label writefile. Show all posts
Showing posts with label writefile. Show all posts
Tuesday, March 27, 2012
connection problem
Sunday, March 25, 2012
connection problem
Hi, All,
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
Hawk
Hi Hawk,
Connection write using the Named Pipes library. There could be a
permission problem with Named Pipes /SMB or a restrictive Security Template
setting. Try connecting using TCP.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Kevin,
Thanks, but how can change it to TCP? Could you tell me
more?
Have a good weekend
>--Original Message--
>Hi Hawk,
> Connection write using the Named Pipes library.
There could be a
>permission problem with Named Pipes /SMB or a
restrictive Security Template
>setting. Try connecting using TCP.
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>
|||Use the SQL Client Network Utility and create a TCP alias. Enter the
actual servername for the alias, this way the client will use sockets
instead.
If you have MDAC 2.6 on the client you can also try this as a test.
osql -Stcp:ServerNameHere -UuserName -Ppassword
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Thank you very much and have a good one
Hawk
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
Hawk
Hi Hawk,
Connection write using the Named Pipes library. There could be a
permission problem with Named Pipes /SMB or a restrictive Security Template
setting. Try connecting using TCP.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Kevin,
Thanks, but how can change it to TCP? Could you tell me
more?
Have a good weekend
>--Original Message--
>Hi Hawk,
> Connection write using the Named Pipes library.
There could be a
>permission problem with Named Pipes /SMB or a
restrictive Security Template
>setting. Try connecting using TCP.
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>
|||Use the SQL Client Network Utility and create a TCP alias. Enter the
actual servername for the alias, this way the client will use sockets
instead.
If you have MDAC 2.6 on the client you can also try this as a test.
osql -Stcp:ServerNameHere -UuserName -Ppassword
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Thank you very much and have a good one
Hawk
Thursday, March 8, 2012
Connection failed
Hi, All,
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
Hawk
> Hi, All,
> SQL7.0, SP3 on Win2000 server+ sp1
> I remote access our client in FL, recently I get error
> message [DBNMPNTW] Connection write(writefile()) message
> then the connection failed.
> What's cause the problem how can I fix it.
>
> Thanks and have a nice day
> Hawk
>
You can test named pipes connectivity as follows:
INF: Procedure for Testing Named Pipes
http://support.microsoft.com/?id=68941
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
Hawk
> Hi, All,
> SQL7.0, SP3 on Win2000 server+ sp1
> I remote access our client in FL, recently I get error
> message [DBNMPNTW] Connection write(writefile()) message
> then the connection failed.
> What's cause the problem how can I fix it.
>
> Thanks and have a nice day
> Hawk
>
You can test named pipes connectivity as follows:
INF: Procedure for Testing Named Pipes
http://support.microsoft.com/?id=68941
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Wednesday, March 7, 2012
Connection failed
Hi, All,
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
Hawk
> Hi, All,
> SQL7.0, SP3 on Win2000 server+ sp1
> I remote access our client in FL, recently I get error
> message [DBNMPNTW] Connection write(writefile()) message
> then the connection failed.
> What's cause the problem how can I fix it.
>
> Thanks and have a nice day
> Hawk
>
--
You can test named pipes connectivity as follows:
INF: Procedure for Testing Named Pipes
http://support.microsoft.com/?id=68941
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
Hawk
> Hi, All,
> SQL7.0, SP3 on Win2000 server+ sp1
> I remote access our client in FL, recently I get error
> message [DBNMPNTW] Connection write(writefile()) message
> then the connection failed.
> What's cause the problem how can I fix it.
>
> Thanks and have a nice day
> Hawk
>
--
You can test named pipes connectivity as follows:
INF: Procedure for Testing Named Pipes
http://support.microsoft.com/?id=68941
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Connection failed
Hi, All,
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
Hawk> Hi, All,
> SQL7.0, SP3 on Win2000 server+ sp1
> I remote access our client in FL, recently I get error
> message [DBNMPNTW] Connection write(writefile()) message
> then the connection failed.
> What's cause the problem how can I fix it.
>
> Thanks and have a nice day
> Hawk
>
--
You can test named pipes connectivity as follows:
INF: Procedure for Testing Named Pipes
http://support.microsoft.com/?id=68941
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
SQL7.0, SP3 on Win2000 server+ sp1
I remote access our client in FL, recently I get error
message [DBNMPNTW] Connection write(writefile()) message
then the connection failed.
What's cause the problem how can I fix it.
Thanks and have a nice day
Hawk> Hi, All,
> SQL7.0, SP3 on Win2000 server+ sp1
> I remote access our client in FL, recently I get error
> message [DBNMPNTW] Connection write(writefile()) message
> then the connection failed.
> What's cause the problem how can I fix it.
>
> Thanks and have a nice day
> Hawk
>
--
You can test named pipes connectivity as follows:
INF: Procedure for Testing Named Pipes
http://support.microsoft.com/?id=68941
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)