I have a sql server (2005 standard edition) on Win xp machine. i can connect to this server from my machine ok but others on the network try to connect i get following error
"An error has occurred during report processing.
Cannot create a connection to data source 'dataSource1'.
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. 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. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) "
but my remote connection allows remote connects. i also enabled "Named pipes" and "VIA" protocols under sql configuration manager but no avail.
any ideas on this one.
Thanks for your help.
Cheersyou need to config to enable this via surface area config tool|||Thanks for that and actually i tried that too but no avail.|||
Try disabling VIA, and restarting the SQL Server.
|||PeterVIA is already disabled|||i also have sqlexpress on the same machine ,does it make any difference ?
BTW i stoped sqlexpress service but still made no difference!|||
The error you get most frequently indicates that TCP and/or Named Pipes are not enabled on the target SQL Server 2005.
The first thing is to make sure that these protocols are enables, and then restart the target SQL Server.
If you have SQL Server 2005 client tools installed on the remote client machine you can test the connection over TCP and Named Pipes, resp., by running the following commands:
sqlcmd -E -Stcp:<targetServer>
or
sqlcmd -E -Snp:<targetServer>
Notes:
- the switches -E -S are case sensitive, and must be in capital letters
- replace <targetMachine> with the name of the machine running the target SQL Server 2005.
If you still get errors their text may be helpful in troubleshooting further.
|||PeterThank you very much for your help.those 2 commands really helped.
first command (uses tcp) it connected ok but 2nd command(using np) gave an error.
so on target server i enabled Named pipes and restarted server and tried to connect again from remote machine and guess what it connect nicely. and now i can connect to target server from my report manager page also which was originally giving problem.
Thanks again for your help :)
one question remained though we've another sql server on a different machine which has too only TCP/IP enabled but all other PCs in the network able to connect without any problem!!
why my PC was any different ?
Thanks|||
How does your application specify the server in the connection string?
If it uses an alias, does the alias specify Named Pipes as the protocol? Is there any chance the connection string specifies the Named Pipes protocol through the "Network Library" or "Net" property, e.g. as "Network Library=dbnmpntw"?
|||Peterhere my application is Report Manager page (http://localhost/reportserver) and connection does not specify any protocols.
we installed sql server with default settings so i dont think there is any alias|||
I have had identical connection problem problems. The two commands are extremely helpful for diagnosis. I wish I had known them earlier. Thank you!
No matter what I try (enabling, disabling, stopping, restarting, ...), I cannot get TCP work, but the name pipes can be made work easily and I can certainly live with it.
hz
|||Hi all
I am fascinated by this discussion. I have had similar problems.
I have access to 100 computers in the university library on the same network. Each pc is running Windows XP and has a copy os SQL Server 2005 installed (the full version and express).
I am manually connecting servers (but would love to know how to in T-SQL as well ;-)). A friend has helped me before, and we disabled Named Pipes and enabled TCPIP on some of the computers. We were then able to use the wizzard to connect these computers. I am using SQL Server Authentication, and each database, and all connections are using the same login, and I have set this up to have server role "svsadmin".
Unfortunately this does not work now. I have followed the instructions suggested above (and enabled both TCPIP and Named Pipes), and now, while I am able to connect the servers on different machines, the connected server does not have an icon that indicates that it is either
* started (green triangle) or
* stopped (red triangle)
but an empty little circle at the base of the satabase cream cylinder
I hope I have given the right amount of info.
Thanks in advance.
Greg
|||Greg
did you mean ,you cant see whether "server" running or not ?
if so "sql server configuration manager" under configuration tools you should be able to see whether sql server running or not.
BTW if you dont use sqlexpress i suggest you uninstall it as it resolved many issues for me.i guess sql server 2005 and sqlexpress conflicting each other!
|||Hi
Thanks for the response.
I have uninstalled SQL Server Express on 2 of the machines.
The servers are running - I'm sure of that, but unbelievably slowly. I have been able to view (in SQL Server Managment Studio) the contents of tables on either the local or networked server. (The server status is still being denoted by the empty white disc superimposed on the yellow server cylinder...)
So they must be running right? The SQL Server Configuration Manager agrees - but to me the server manager is telling me that the server is running locally, which is the case. The problem relates to the connected database...
Despite deleting the database, unfortunately still getting this unusual situation. I'm able to explore a database on either server from either computer once I have connected the servers. But unfortunately I can not use T-SQL to input into a table on the networked server. (I am using sp_addlinkedserver to link the server successfully.)
Could the problem be a network setting, and if so, what should I ask the network administrator to change?
Thanks
Greg
|||am out of ideas on this Greg.
BTW after uninstalling sqlexpress have you restarted machines ?
if not give it a try and see .
No comments:
Post a Comment