SQL Server 2005 - Reporting Services Data Sources Named Pipes VS TCP/IP
Feb 28, 2007
Can anyone shed light on why I cannot get away from named pipes in my SQL2005 Reporting Services Data Sources? Can it not just use TCP/IP? My configuration uses two servers, one in which the reportserver is setup on, and another which hosts the database that is reported against. We are trying to avoid having to open up named pipes on the server that stores the data.
Any help would be appreciated.
An error has occurred during report processing.
Cannot create a connection to data source 'wc_datasource'.
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. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Thanks!
View 1 Replies
ADVERTISEMENT
Jul 23, 2007
All,
I apologize for not doing the legwork to see if i can answer my own question, but I am close to a loosely planned SQL 2005 migration and don't have time and resources to test my own theories.
Is there a way for a Reporting Services 2000 server to connect to SQL server 2005 databases? I've tried creating a new data source and changing a report to this data source, but it seems like the report is still using the old data source. I'm guessing i might need to register new data providers on the 2000 RS server and then change the existsing data sources.
Ideas?
Thx in advance,
-Peter
View 3 Replies
View Related
Dec 21, 2005
I keep getting errors. It all started when I enabled named pipes on my SQL Server 2005 server. Ever since then I've had connection problems up the butt.
Most recently I got this error so does this mean that SQL Server is still trying to use named pipes even if I only have TCP/IP enabled in SQL Server Configuration Manager?
Error:
TITLE: Connect to Server
------------------------------
Cannot connect to BG-SQL2005.
------------------------------
ADDITIONAL INFORMATION:
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. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
I get this when I try to connect to my DB period and I know the users are setup correctly, even tried both Windows Authentification and SQL authentification, no luck. It was working happily for a few days it seemed before I enabled named pipes in the SQL Server Configuration Manager.
View 11 Replies
View Related
Sep 19, 2005
I have a group of reports that are the same for 3 different companies, the difference is the data connection. Is there a way I can change the data connection based on a variable passed in at the time of report execution?
View 12 Replies
View Related
Sep 9, 2006
Hi My project is in .NET 2003 i.e. framework 1.1 and database in SQLServer 2000. But the reports have been developed using SQLServer 2005 Reporting Services. Now when I am trying to deploy them through deployment project of .NET its giving me following error:"Using other editions of SQL Server for report data sources and/or the report server database" is not supported in this edition of Reporting Services. Now I am really confused with this. Can any one please guide me regarding this ASAP. Thanks, Falguni
View 4 Replies
View Related
Apr 24, 2006
I'm using SQL Express with Advance Services & I get this error when I try to deploy my reports. Why do I get this error
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'EDPSYS'. (rsErrorOpeningConnection)
The feature: "Remote access to report data sources and/or the report server database" is not supported in this edition of Reporting Services. (rsOperationNotSupported)
Justin Song
View 4 Replies
View Related
Sep 22, 2015
I have a requirement where we have to connect to two different data-sources one is Database Table and another one is Excel Source. I know we can do this by creating a SSIS package and loading the excel data into database table and then based on some relationship between the tables we can create the data-set in SSRS. But I am looking for some other approach where I can do this without creating the SSIS package.
View 4 Replies
View Related
Sep 5, 2013
I have a report designed in RB3 that uses a data source from a SQL database that is on the report server. I want to add data to the report from an access database an a network drive.
I can add the second data source and create a data set to add data to the report. The dataset query returns data from the Access database but when I run the report I get the following error.
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'Feasibility'. (rsError OpeningConnection)
Also when I test the connection to the Access data base I get error ERROR (IM002) (Microsoft)(ODBC Driver Manger) Data source name not found and no default driver specified.
I noticed that Report Builder is connecting to the report server. If I disconnect from the report server I can a can connect to the Access data base but not the SQL database.
How can I get the report to run against both data sources?
View 2 Replies
View Related
Jan 24, 2008
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. (provider: Named Pipes Provider,
View 2 Replies
View Related
Apr 10, 2008
Hi,I have SQL Server Express Edition. I tried working out some ASP.NET Labs in my local system. Here is the link of the Virtual Lab which I tried. http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032286906&EventCategory=3&culture=en-US&CountryCode=USI recieve this error in my local system. 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. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)I tried working out solutions from various websites. But the no solution is effective. Could anyone help me in solving this issue.
View 1 Replies
View Related
Aug 9, 2007
For SRS??? If so, what's the work around?
View 12 Replies
View Related
Jun 14, 2007
I see Named Pipes disabled by default in SQL 2005. Is this for any specific reasons?
View 1 Replies
View Related
Jul 29, 2007
I have SQL 2005 Std Edition, Mixed Security, and remotely connecting by TCP/IP works great.
Named Pipes (and the SQL Native Client) is the only issue.
The problem _appears_ to be that I'm not authenticated under the SQL Machine; however, I'm not attempting to use Windows Authentication, I'm strictly using SQL, so I do not understand why I'm having a problem.
My reasoning for the above conclusion, is that the command "net use \[server_name]ipc$" will allow me to connect to the server, and Named Pipes will begin working. Again, remember that I'm only trying to access named pipes using SQL Authentication.
I've read through everything on the forum and tried everything I could find. Below are the answers from the most common suggestions posted here:
------------------------------------------------------------------------
Version: SQL Server 2005 - 9.00.1399.06 (Intel X86)
This is the Default & Only Instance of SQL 2005, named: MSSQLSERVER
------------------------------------------------------------------------
1. The error message with the SQL Native driver (v 9.00.3042):
Error 1326, SQL State 08001
[Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [1326]
2. The error messgae with the ODBC SQL driver (v 03.85.1117):
Error 1326, SQL State 01000
[Microsoft][ODBC SQL Server Driver][Named Pipes]Connection Open (Connect())
Connection Failed: SQL Error 17, State 08001
[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.
3. Local Connection on Win2003 Server works fine for IP & Named Pipes
4. Remote Connection using SQL Authentication
WORKS for IP, does not work for Named Pipes
5. Absolutely *no firewalls* or blocked ports are being used on either machine
6. Configuration Manager & Surface Area Config -- both enabled TCP/IP & Named Pipes
Currently listening on ALL IP's. The LOG reports:
Server is listening on [ 'any' <ipv4> 1433].
Server named pipe provider is ready to accept connection on [ \.pipesqlquery ].
Server is listening on [ 127.0.0.1 <ipv4> 1434].
Dedicated admin connection support was established for listening locally on port 1434.
7. Can telnet to server on 1433
8. Status of NETSTAT on server:
C:...>netstat -ano|findstr 1433
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING 656
C:...>netstat -ano|findstr 1434
TCP 127.0.0.1:1434 0.0.0.0:0 LISTENING 656
UDP 0.0.0.0:1434 *:* 2544
9. Tried both named instance and unnamed instance (although I'm not sure
if I'm passing the 'named' instance properly):
Tested: \MYSERVERpipesqlquery
Tested: \MYSERVERpipeMSSQL$MSSQLSERVERsqlquery
(although the named instance doesn't work on the server either)
10.I've setup an alias for the named pipe connection. This was based on a suggestion
posted here, but didn't work.
11.I've removed the shared-memory protocol, on another suggestion here, but no luck.
12.If I execute "net use \[server_name]ipc$" it asks for credentials and if I
enter the server credentials I have no problem with executing that command.
In other words the logged-on user is not an authenticated member of the server;
however, I'm not attempting to use windows authentication, I'm using
SQL Authentication.
------------------------------------------------------------------------
Thank you in advance for any suggestions,
Rusten
View 5 Replies
View Related
Mar 17, 2008
Hi to all,
We have 4 client machine and 1 server machine, that server have all the sql server 2005 database€™s.
A project developed from client1 with Asp.net 2005 now I need to access that project from client2 so I type http://My Ip address/Folder Name/home.aspx in my browser here when the sql connection is open(SqlConnection.Opn()) then I meet this problem
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. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Please reply me.
View 2 Replies
View Related
Apr 10, 2008
Hi,I have SQL Server Express Edition. I tried working out some ASP.NET Labs in my local system. Here is the link of the Virtual Lab which I tried. http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032286906&EventCategory=3&culture=en-US&CountryCode=USI recieve this error in my local system. 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. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)I tried working out solutions from various websites. But the no solution is effective. Could anyone help me in solving this issue.
View 3 Replies
View Related
Feb 23, 1999
I have a question. When my SQL server was originally configured, it was only setup to use named pipes. Now I am needing to setup a P&M server (through Site Server 3.0), but I must have my SQL server to accept tcp/ip network connections. I don't know how to enable named pipes & tcp/ip. Any help would be greatly appreciated.
Steve Robitzsch
View 2 Replies
View Related
Oct 3, 2000
I have a simple ASP page calling a COM+ function. The COM+ function is attempting to execute a stored proc on a SQL Server 2000 database. I am getting the following error:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC SQL Server Driver][Named Pipes]Specified SQL server not found.
The connection string I am using looks as follows:
driver={SQL Server};server=10.10.1.60;database=eSystem;uid=sa; pwd=;
- I have Named Pipes *disabled* on the SQL Server machine (at 10.10.1.60).
- As you can see, the connection string contains an IP Address and not the name of the SQL machine
- The server running the ASP page can ping the server sitting at 10.10.1.60
- The eSystem database does exist on the SQL machine sitting at 10.10.1.60
I suspect my error has to do with Named Pipes being used and I don't want to use Named Pipes. Could someone help me?
Thanks very much.
View 2 Replies
View Related
Aug 7, 1999
We had a crash of SQL server this week, everything came up fine, with the exception, SQL EM would no longer connect to SQL Server via named Pipes Library. SQL Server [DB-Library] Not found or Server does not exist.
Client Applications are able access the DB, ISQL /w acesses and runs SP's fine
DBCC CHECKDB returned no errors. I have to Reporting funtions that utilze Crystal Reports to connect to the DB. I am unable to do that n=now. This really is causing major problems. Any assistance would be appreciated.
I have already tryed Client Config. and adding the TCP/IP in the Advanced Tab wih Named pipes identified as "." and "(local)" [without quotes]. this did not work either.
If I have a corrupt Dll, can I reload it, or do I need to reload SQL Server, and rebuild databases from Datadumps?
View 6 Replies
View Related
Jul 17, 2006
Hello,
I have a big problem with SQL Server 2000 and Visual Basic .Net. I wont disable named Pipes from code write in Visual Basic (.Net). How make this ?
This problem is very important for me.
Help me! Please!!!
View 1 Replies
View Related
Dec 20, 2006
Hi,
I have windows 2003 (SP1) server with sql server 2000 (SP3) .
In the server network utility, I have enables only TCP/IP protocol and disabled the Named pipe protocol.
Now if I try to connect to the sql server from a remote machine, I get the message saying "unable to connect either server does not exist or ......".
I have configured the firewall to allow communication on TCP port 1433. It didn't help. I tried to disable the firewall completely, still it didn't work.
It works only if I enable Named pipe in the server's server network utility.
- Abhijit
View 1 Replies
View Related
Jun 9, 2008
I get this error when I try and log into my SQL Server 2005 database:
"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. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)" Does any one have solutions please reply. thanks & regards Priya.
View 1 Replies
View Related
Sep 14, 2015
We have transaction replication configured across multiple SQL instances and could find one of the replication (from publisher to subscriber) net transport sessions is happening via Named pipes rather than TCP. where to troubleshoot this issue and what action to be taken to make it happen via TCP.
View 0 Replies
View Related
Dec 5, 2007
Hello All!
I'm getting the following error message below from SQL server error log, see below.
And the following error on the web browers:
"System.Data.SqlClient.SqlException: 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. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) "
I have see this link (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=192622&SiteID=1) and other links and done the changes they recommend, but it does not give any positive results.
I have also in the firewall added named pipes internal and external port 445.
I have also in RUN executed "cliconfg.exe" and enable the tcp ip port number 1433 and named pipes "sqlquery".
In the sql server configuration manager, have I enabled both tcp/ip and named pipes. The same in the server surface area configuration. I have also enabled remote access.
Still having the same problem??!!??
Iam out of ideas ...
Please need help, thanks in forehand!
Nikita
SQL SERVER LOG file:
2007-12-05 11:31:11.12 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2007-12-05 11:31:11.12 Server Error: 17054, Severity: 16, State: 1.
2007-12-05 11:31:11.12 Server The current event was not reported to the Windows Events log. Operating system error = 1502(error not found). You may need to clear the Windows Events log if it is full.
2007-12-05 11:31:11.12 Server (c) 2005 Microsoft Corporation.
2007-12-05 11:31:11.12 Server All rights reserved.
2007-12-05 11:31:11.12 Server Server process ID is 1744.
2007-12-05 11:31:11.12 Server Authentication mode is MIXED.
2007-12-05 11:31:11.12 Server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'.
2007-12-05 11:31:11.12 Server This instance of SQL Server last reported using a process ID of 4884 at 5.12.2007 11:30:09 (local) 5.12.2007 9:30:09 (UTC). This is an informational message only; no user action is required.
2007-12-05 11:31:11.12 Server Registry startup parameters:
2007-12-05 11:31:11.12 Server -d C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf
2007-12-05 11:31:11.12 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG
2007-12-05 11:31:11.12 Server -l C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf
2007-12-05 11:31:11.20 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-12-05 11:31:11.20 Server Detected 2 CPUs. This is an informational message; no user action is required.
2007-12-05 11:31:11.67 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2007-12-05 11:31:11.75 Server Database mirroring has been enabled on this instance of SQL Server.
2007-12-05 11:31:11.75 spid4s Starting up database 'master'.
2007-12-05 11:31:11.93 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2007-12-05 11:31:12.11 spid4s SQL Trace ID 1 was started by login "sa".
2007-12-05 11:31:12.20 spid4s Starting up database 'mssqlsystemresource'.
2007-12-05 11:31:12.23 spid4s The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2007-12-05 11:31:12.49 spid8s Starting up database 'model'.
2007-12-05 11:31:12.49 spid4s Server name is 'ESPMK60134SQLEXPRESS'. This is an informational message only. No user action is required.
2007-12-05 11:31:12.51 spid4s Starting up database 'msdb'.
2007-12-05 11:31:12.65 spid8s Clearing tempdb database.
2007-12-05 11:31:13.03 Server A self-generated certificate was successfully loaded for encryption.
2007-12-05 11:31:13.03 Server Server is listening on [ 'any' <ipv4> 1175].
2007-12-05 11:31:13.03 Server Server named pipe provider is ready to accept connection on [ \.pipeMSSQL$SQLEXPRESSsqlquery ].
2007-12-05 11:31:13.03 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2007-12-05 11:31:13.07 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2007-12-05 11:31:13.32 spid8s Starting up database 'tempdb'.
2007-12-05 11:31:13.42 spid4s Recovery is complete. This is an informational message only. No user action is required.
2007-12-05 11:31:13.42 spid11s The Service Broker protocol transport is disabled or not configured.
2007-12-05 11:31:13.42 spid11s The Database Mirroring protocol transport is disabled or not configured.
2007-12-05 11:31:13.46 spid11s Service Broker manager has started.
View 3 Replies
View Related
Jan 6, 2006
This was originally posted in the SSIS Forum, but a member of the IS team suggested it be moved here. "Most recently I got this error (Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) so does this mean that SQL Server is still trying to use named pipes even if I only have TCP/IP enabled in SQL Server Configuration Manager?"
I'm having the same issue, and here's our scenario:
Installed SQL Server 2005 Developer Edition on a machine with WinXP SP2 and enabled remote connections over TCP/IP
Installed SQL Server 2005 Standard Edition on a machine with Win2003 SP1 (remote connections over TCP/IP enabled by default)
Attempted to 'Copy Database' from Developer Edition TO Standard Edition using 'Detach and Attach' method and recieved the error on the Win2003 machine: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
Attempted to 'Copy Database' from Developer Edition TO Standard Edition using 'SQL Management Objects' method and recieved the error on the Win2003 machine: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
Reinstalled Standard Edition on the Win2003 SP1 machine
Checked all the settings on both machines several times, restarted services etc., and read every post I could find referencing the error.
Same error
Lost my last hair
Thanks in advance,
Steve
View 77 Replies
View Related
Dec 5, 2007
My configuration is: Vista Home Premium, SQL Server Express and I'm trying to access a database on an instance named AxisSQLServer in a C# application.
As a result of a previous post (SQL Network Interface, error 28), I have selected "Local and Remote, using TCP/IP only" in the Surface Area Configuration for Services and Connections.
SQL Server is started.
SQL Server Browser is started.
Both programs have been added as exceptions to the firewall (don't understand why I would need to do this since everything is on the same box).
Have turned off McAfee AV.
My connection string reads:
string connectionString = "Data Source=localhost;" +
"Initial Catalog=AxisSQL;Integrated Security=SSPI";
where AxisSQL is the database I'm trying to read.
I have looked at and followed numerous forums and blogs and always get the same error.
Stan
View 1 Replies
View Related
May 2, 2008
Hi,
I'm encountering an issue with "Named Pipes Provider, error: 40 windows" and am having problems determining how to fix it due to the environment I'm using. I have two SQL Servers installed on two separate Win2K3 Server boxes, one is SQL Server 2000 and the other is SQL Server 2005. The SQL Server 2000 contains the actual application data. The 2005 database is used only for Reporting Services. I've set up the reports on SSRS such that their datasources hit the 2000 server. This is using SQL Server authentication.
When testing the reports via SSRS (in Visual Studio 2005), the connection to the data works and the reports are generated fine. When I deploy them to the reporting server and launch IE to test locally (still on the 2005 box), I get this "Named Pipes Provider, error 40" issue. I made sure that Named Pipes and TCP were enabled and the port set at 1433 (to match that on the 2000 box).
Now I changed the datasource's authentication from SQL Server to Windows authentication. I tested this in SSRS and this works too. When I redeployed the reports with this authentication change, testing the reports via IE locally (on the 2005 box) worked (using Administrator login). Great. Now when I open IE on an external box, i.e. on the 2000 box, and try to test the reports using that server's Administrator login, I get this same error 40 issue. I've been through a few threads describing the error 40, fiddling around with the SQL Server configuration as well as SSRS, to no avail. I have a feeling this error 40 issue has to due with permissions/authentication between the SQL Server boxes but I can't really be sure. Anyone have any ideas on how to troubleshoot my situation. Thanks.
larry
View 4 Replies
View Related
Oct 5, 2015
I've been reading about the protocols and i've been trying to connect to my SQL SERVER using each one of the protocols, but i think I'm missing something, i dont have any problems using Shared Memory and TCP protocols, but I'm not pretty sure how to connect to my remote SQL SERVER using NAMED PIPES protocols. The books On Line of Microsoft refer that you can connect using this protocol using the next syntax: Connecting to a default instance by specifying a named pipe name:
APPHOSTpipeunitapp
Connecting to a named instance by specifying a named pipe name:
APPHOSTpipeMSSQL$SQLEXPRESSSQLquery
Connecting to default instance by name, forcing a named pipes connection:
np:APPHOST
Connecting to named instance by name, forcing a named pipes connection:
np:APPHOSTSQLEXPRESS
But I can't connect to my remote SQL SERVER, if i try the same with my local SQL SERVER i don't have any problems. I've been reading the articles so many times searching something about Named Pipes is only for local connections, but Microsoft say that it's posible to connect to a remote SQL SERVER, but i don't know how to do that. The firewall is disabled, I changed the APPHOST in the above syntax for the IP address of my SQL SERVER but it didn't work..
View 2 Replies
View Related
Jun 18, 2007
My connection string (to a remote instance of SQL Server Exress 2005) is exactly the same when the web files are located on my local machine or my remote machine, and while it works fine when I use the local web files, I get the following error when I use the remote files:
"Named Pipes Provider: Could not open a connection to SQL Server [53]"
As you can see, since it works from the local version, I've setup SQL to accept remote connections via TCP/IP and Named Pipes. I'm using IIS7 on the local, and IIS6 on the remote, in case that makes a difference. I have other sites setup the same way, which work fine.
Any thoughts?
View 5 Replies
View Related
Aug 7, 2005
HiI'm a complete sql/asp.net newbie and want to try this tutorial:http://beta.asp.net/GuidedTour/First I installed:Visual Web Developer 2005 Express Edition Beta 2systemsettingssoftware shows the "sql server 2005 express edition ctp (sqlexpress)" installedmmcservice shows me the SQL Server (SQLExpress) is runningFollowing the guided tour I use the commandline, type cmd, and type in the commandbox: "C:Program FilesMicrosoft SQL Server90ToolsinnSQLCMD90" -S "localhostSqlExpress"Instead of localhost I also tried computername.smallbusiness.local (thats my fully domain name). However I always receive the error:
Named Pipes Provider: Could not open a connection to SQL Server [2]Thank you very much for all your help
View 1 Replies
View Related
Sep 28, 2007
Hi,
I have merge replication configured over VPN and the replication is failing to connect to the subscriber through Named pipes with the error Named Pipes Provider, error: 40 - Could not open a connection to SQL Server ......
Actually , I am having issues with Named pipes connection from publisher to subcriber. I have enabled the protocols and also enabled the remote connections using both tcp/ip and named pipes. I have created the client network alias using named pipes
Also, due to security reasons only few ports have been released on the subscriber. Please provide me some information on the following.
1) Does any port specifically be released for listening on named pipes? i am able to connect using tcpip with out any issues as 1433 has been released.
2) How to configure the replciation to use tcpip and not named pipes (guess by default it will use named pipes)?
View 1 Replies
View Related
Oct 20, 1999
I am trying to run a sql script that was written by a third party to set up the tables and stored procedures of a 6.5 database. The script crashes
about half way through. The error looks like this...
The vendor said that I needed to change the client configuration to tcp/ip sockets instead of the named pipes that I was using. When I change
this setting I can no longer connect to the server through enterprise manager. The error message is...
I am not sure if the db-library is not set up correctly for the server or why it will not connect through the tcp/ip socket. I ran the ping command
from the command line and it returns a valid connection to the server. This doesn't make a lot of sense to me.
Does anyone have any experience with this problem or suggestions of something to try to fix this problem. Any ideas would be great. Thanks.
View 2 Replies
View Related
Oct 20, 1999
Sorry I forgot to attach the error messages.
This is the message when the script crashes...
DB-Library: Unexpected EOF from SQL Server. Connection broken.
Net-Library error 109: ConnectionCheckForData (PeekNamedPipe()).
DB-Library Process Dead - Connection Broken
This is the message when I try to connect to the server using tcp/ip sockets...
A connection could not be established to SERVERNAME - [DB-Library]Unable to connect SQL Server is unavailable or does not
exist. General network error.
View 1 Replies
View Related
