Named pipes vs TCP/IP

Hi all.
We have a customer with some connection problems running Remote desctop
(Terminal server). In the startuplog of the SQL2000 server we can't find
anything else than:
2005-10-26 07:28:49.95 server SQL server listening on Shared Memory, Named
Pipes.
On our server we have the following started. What should we do to get the
server listening on the TCP/IP too? We think this could be the problem.
2005-10-24 12:10:06.71 server SQL server listening on 10.120.1.26: 1433.
2005-10-24 12:10:06.78 server SQL server listening on 127.0.0.1: 1433.
2005-10-24 12:10:07.67 server SQL server listening on TCP, Shared Memory,
Named Pipes.
Thanks all.
geir
Is the IP netlib enabled (Server Network Utility)?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Geir Holme" <geir@.multicase.no> wrote in message news:u1OjFIJ5FHA.1032@.TK2MSFTNGP11.phx.gbl...
> Hi all.
> We have a customer with some connection problems running Remote desctop
> (Terminal server). In the startuplog of the SQL2000 server we can't find
> anything else than:
> 2005-10-26 07:28:49.95 server SQL server listening on Shared Memory, Named
> Pipes.
> On our server we have the following started. What should we do to get the
> server listening on the TCP/IP too? We think this could be the problem.
>
> 2005-10-24 12:10:06.71 server SQL server listening on 10.120.1.26: 1433.
> 2005-10-24 12:10:06.78 server SQL server listening on 127.0.0.1: 1433.
> 2005-10-24 12:10:07.67 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
>
>
> Thanks all.
> geir
>

Named pipes vs TCP/IP

Hi all.
We have a customer with some connection problems running Remote desctop
(Terminal server). In the startuplog of the SQL2000 server we can't find
anything else than:
2005-10-26 07:28:49.95 server SQL server listening on Shared Memory, Named
Pipes.
On our server we have the following started. What should we do to get the
server listening on the TCP/IP too? We think this could be the problem.
2005-10-24 12:10:06.71 server SQL server listening on 10.120.1.26: 1433.
2005-10-24 12:10:06.78 server SQL server listening on 127.0.0.1: 1433.
2005-10-24 12:10:07.67 server SQL server listening on TCP, Shared Memory,
Named Pipes.
Thanks all.
geirIs the IP netlib enabled (Server Network Utility)?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Geir Holme" <geir@.multicase.no> wrote in message news:u1OjFIJ5FHA.1032@.TK2MSFTNGP11.phx.gbl...
> Hi all.
> We have a customer with some connection problems running Remote desctop
> (Terminal server). In the startuplog of the SQL2000 server we can't find
> anything else than:
> 2005-10-26 07:28:49.95 server SQL server listening on Shared Memory, Named
> Pipes.
> On our server we have the following started. What should we do to get the
> server listening on the TCP/IP too? We think this could be the problem.
>
> 2005-10-24 12:10:06.71 server SQL server listening on 10.120.1.26: 1433.
> 2005-10-24 12:10:06.78 server SQL server listening on 127.0.0.1: 1433.
> 2005-10-24 12:10:07.67 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
>
>
> Thanks all.
> geir
>

Named pipes vs TCP/IP

Hi all.
We have a customer with some connection problems running Remote desctop
(Terminal server). In the startuplog of the SQL2000 server we can't find
anything else than:
2005-10-26 07:28:49.95 server SQL server listening on Shared Memory, Named
Pipes.
On our server we have the following started. What should we do to get the
server listening on the TCP/IP too? We think this could be the problem.
2005-10-24 12:10:06.71 server SQL server listening on 10.120.1.26: 1433.
2005-10-24 12:10:06.78 server SQL server listening on 127.0.0.1: 1433.
2005-10-24 12:10:07.67 server SQL server listening on TCP, Shared Memory,
Named Pipes.
Thanks all.
geirIs the IP netlib enabled (Server Network Utility)?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Geir Holme" <geir@.multicase.no> wrote in message news:u1OjFIJ5FHA.1032@.TK2MSFTNGP11.phx.gbl
..
> Hi all.
> We have a customer with some connection problems running Remote desctop
> (Terminal server). In the startuplog of the SQL2000 server we can't find
> anything else than:
> 2005-10-26 07:28:49.95 server SQL server listening on Shared Memory, Named
> Pipes.
> On our server we have the following started. What should we do to get the
> server listening on the TCP/IP too? We think this could be the problem.
>
> 2005-10-24 12:10:06.71 server SQL server listening on 10.120.1.26: 1433.
> 2005-10-24 12:10:06.78 server SQL server listening on 127.0.0.1: 1433.
> 2005-10-24 12:10:07.67 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
>
>
> Thanks all.
> geir
>

Named Pipers Provider, error 40, ok from local, error to remote - help

Hi.
I am new to sql server so please bear with me.
Here is the problem.
I am using VWD express to connect to a sql server 2005 db on my local
machine. The site and the sql server are local and everything is fine.
No problems.
I have a sql server hosting plan to host the db. (my local is SQL
Server 2005 and the hosted is Sql Server 2000).
I use the LOCAL VWD website to access the HOSTED sql server and it
connects with no problem. I changed data in the remote version of the
db as a double-check that I am accessing the remote db and not the
local db.
When I go ahead and upload the web site to my web host, different from
the sql host (long story), I get this error (provider: Named Pipes
Provider, error: 40 - Could not open a connection to SQL Server).
Any ideas why this error is happening. My web host verifies that my
connection string is fine, and that if I can connect with my local
machine then there should be no problem and the problems is on the
hosting end.
Thanks in advance,
RanginaldOk. Problem solved. I was using a web host with multiple hosted
domains and I think I probably had some kind of IIS app directrory
problem. I moved the site to its own hosting and all was fine with no
changes needed.
Thanks anyway. Hope this tidbit helps someone.
Rangy
Ranginald wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald|||Do you have to connect with named pipes? If not, change the connection string
to connect with TCP/IP (set Network Library=dbmssocn). Assuming that the SQL
connectivity components are properly installed on the web server and you can
ping the database server from the web server, I'd try a few things.
1. Find out the IP address and the TCP port that the SQL instance listens on.
2. Change the connection string to the IP address followed by a comma and
then the TCP port (e.g. set Server=169.12.35.51,5002). If this does not work,
you may have a problem with accessing the port. (if it's the default instance
using the default port, you don't need to test with the port number specified
explicitly).
3. Change the IP to the server name in the Server property of the connection
string, and try again. If this doesn't work, you may have a problem with
resolving the server to the IP address. Try the fully qualified domain name
instead.
If you can connect with TCP/IP, but not with names pipes, you may have a
problem with the ports used by the named pipes being blocked.
Linchi
"Ranginald" wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald
>|||How would I find out the TCP port that the SQL instance listens on?
Thanks
Linchi Shea wrote:
> Do you have to connect with named pipes? If not, change the connection string
> to connect with TCP/IP (set Network Library=dbmssocn). Assuming that the SQL
> connectivity components are properly installed on the web server and you can
> ping the database server from the web server, I'd try a few things.
> 1. Find out the IP address and the TCP port that the SQL instance listens on.
> 2. Change the connection string to the IP address followed by a comma and
> then the TCP port (e.g. set Server=169.12.35.51,5002). If this does not work,
> you may have a problem with accessing the port. (if it's the default instance
> using the default port, you don't need to test with the port number specified
> explicitly).
> 3. Change the IP to the server name in the Server property of the connection
> string, and try again. If this doesn't work, you may have a problem with
> resolving the server to the IP address. Try the fully qualified domain name
> instead.
> If you can connect with TCP/IP, but not with names pipes, you may have a
> problem with the ports used by the named pipes being blocked.
> Linchi
> "Ranginald" wrote:
> > Hi.
> >
> > I am new to sql server so please bear with me.
> > Here is the problem.
> >
> > I am using VWD express to connect to a sql server 2005 db on my local
> > machine. The site and the sql server are local and everything is fine.
> > No problems.
> >
> > I have a sql server hosting plan to host the db. (my local is SQL
> > Server 2005 and the hosted is Sql Server 2000).
> >
> > I use the LOCAL VWD website to access the HOSTED sql server and it
> > connects with no problem. I changed data in the remote version of the
> > db as a double-check that I am accessing the remote db and not the
> > local db.
> >
> > When I go ahead and upload the web site to my web host, different from
> > the sql host (long story), I get this error (provider: Named Pipes
> > Provider, error: 40 - Could not open a connection to SQL Server).
> >
> > Any ideas why this error is happening. My web host verifies that my
> > connection string is fine, and that if I can connect with my local
> > machine then there should be no problem and the problems is on the
> > hosting end.
> >
> > Thanks in advance,
> > Ranginald
> >
> >sql

Named Pipers Provider, error 40, ok from local, error to remote - help

Hi.
I am new to sql server so please bear with me.
Here is the problem.
I am using VWD express to connect to a sql server 2005 db on my local
machine. The site and the sql server are local and everything is fine.
No problems.
I have a sql server hosting plan to host the db. (my local is SQL
Server 2005 and the hosted is Sql Server 2000).
I use the LOCAL VWD website to access the HOSTED sql server and it
connects with no problem. I changed data in the remote version of the
db as a double-check that I am accessing the remote db and not the
local db.
When I go ahead and upload the web site to my web host, different from
the sql host (long story), I get this error (provider: Named Pipes
Provider, error: 40 - Could not open a connection to SQL Server).
Any ideas why this error is happening. My web host verifies that my
connection string is fine, and that if I can connect with my local
machine then there should be no problem and the problems is on the
hosting end.
Thanks in advance,
RanginaldOk. Problem solved. I was using a web host with multiple hosted
domains and I think I probably had some kind of IIS app directrory
problem. I moved the site to its own hosting and all was fine with no
changes needed.
Thanks anyway. Hope this tidbit helps someone.
Rangy
Ranginald wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald

Named Instance into a IP Server

Hello,
May be my question its simple, but I don't know the answer, I need to
connect to a named instance into a Remote Server using an IP Address, how I
can do that ?
Thanks
Hi
The default instance normally listens on an IPAddress and Port 1433, so the
client resolves the name to <IPAddress>:1433
A named instance is the same, but just listens on a different port.
<IPAddress>:<configured port>
If you need to connect via an IP only, the named instance must be setup to
use a static port. Do this though enterprize manager.
e.g. In you connection string use: 192.168.10.1:5001 for a named instance on
192.168.10.1 with a static port of 5001.
Regards
Mike
"Ing. Mike" wrote:

> Hello,
> May be my question its simple, but I don't know the answer, I need to
> connect to a named instance into a Remote Server using an IP Address, how I
> can do that ?
>
> Thanks
>

Named Instance into a IP Server

Hello,
May be my question its simple, but I don't know the answer, I need to
connect to a named instance into a Remote Server using an IP Address, how I
can do that ?
ThanksHi
The default instance normally listens on an IPAddress and Port 1433, so the
client resolves the name to <IPAddress>:1433
A named instance is the same, but just listens on a different port.
<IPAddress>:<configured port>
If you need to connect via an IP only, the named instance must be setup to
use a static port. Do this though enterprize manager.
e.g. In you connection string use: 192.168.10.1:5001 for a named instance on
192.168.10.1 with a static port of 5001.
Regards
Mike
"Ing. Mike" wrote:

> Hello,
> May be my question its simple, but I don't know the answer, I need to
> connect to a named instance into a Remote Server using an IP Address, how
I
> can do that ?
>
> Thanks
>

My question would have been...

Hi,

I am developing an application using C#.NET that accesses a remote database that that contains japanese characters.

My sample querry is strCommand = "SELECT * FROM table WHERE prodname = 'ＣＲ新海物語スペシャルＭ８'";

The result of querry displayed in the binded datagrid also contains other rows that has this prodname:

ＣＲＦ湯けむり紀行ＳＦ－Ｔ
ＣＲぱちんこハイサイＶＲ１
ＣＲホワイトエンジェルＦＳ

etc.

Thanks in advance for your help.

You forgot to ask a question.
|||

Hi,

I am developing an application using C#.NET that accesses a remote database that that contains japanese characters.

My sample querry is strCommand = "SELECT * FROM table WHERE prodname = 'ＣＲ新海物語スペシャルＭ８'";

The result of the querry above that is displayed in the binded datagrid also contains other rows that has this prodname:

ＣＲＦ湯けむり紀行ＳＦ－Ｔ
ＣＲぱちんこハイサイＶＲ１
ＣＲホワイトエンジェルＦＳ

etc.

Why does the command yields other records where the prodname field contains the 'CR' thing?

Sample querry result in a datagrid:

field1 field2 field3 prodname

a as er ＣＲ新海物語スペシャルＭ８

w aa ww ＣＲＦ湯けむり紀行ＳＦ－Ｔ

ss dd ee ＣＲぱちんこハイサイＶＲ1

sdds ddd ee ＣＲ新海物語スペシャルＭ８

rf d5r wwe ＣＲぱちんこハイサイＶＲ１

Does this strange and redundant output has something to do with the Japanese characters contained in some fields

of the table?

Thanks in advance for your help.

|||Try with the correct nvarchar syntax:

SELECT * FROM table WHERE prodname = N'ＣＲ新海物語スペシャルＭ８'