rsErrorOpeningConnection error occurred during the pre-login hands
ezeget.com
correct the pre-login handshaking that seems to be necessary to complete the
satisfactory connection to my SQL Server.
The full error given is
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'AVEVANETDataSource'.
(rsErrorOpeningConnection)
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.)
The thing is I can connect to this Server and DataSource when I connect from
the same machine that the SQL Server exists on, but a Report Server existing
on a separate machine on the same LAN fails with this pre-login named pipes
thing.
I noticed that if I used an IP address instead of the machine name the
pre-login bit dissapears but the named pipes continues.
I even tried prefixed the IP address with np: but same error!!??
I have checked with our infrastructure people who say that DNS thingies are
all OK!!
HELP!!! Please
--
Steve G
ezeget.com
The key is to use the SQL Server Configuration Manager on the server
preventing the connection, and enable the SQL Server 2005 Network
Configuration Protocol TCP/IP. Then restarting the SQL Server magically fixes
the error. Nothing to do with Named Pipes though so a bit of a red herring
there.
I would score this one a a solution to the original posting but since I
posted both I am not allowed to.
So if any kind person reading this actually could set that flag on my behalf
you would be hepling all the other millions of people out there with the same
connectivity (or lack of connectivity issue)
Cheers and have a nice day!
--
Steve G