Could not open port 3601

Hello,
I installed WEB AS6.40 and all the services are running properly. But when I try to access the j2ee engine thru http://ipaddress:50000/index.html, I get the error connection failed in the browser. The j2ee_engine port is correct. In the default trace i get an error Can't open 3601. Message server is running in this port 3601. What could be the problem ? Kindly help.

Hi Rukmani,
This alerts me some thing.When you have installed WAS 6.40 did you change the default instance number for port.If you have left that as 00 then 50000 should work or else if you have changed that to 01 or 02 you should change the port as 50010 0r 50020 accordingly.
One more possibility is that if you have any other applications running on the same port then either you have to free that particular port which is in use or else choose an another port.
Hope it helps.
Regards,
Guru Subramanian B
p.s :- Reward points for useful answers.

Similar Messages

Could not open connection to the host, on port 23: Connect failed

Can anyone please help with this telnet problem on CISCO 877 ADSL Router
I am trying to telnet into my ISP Router remotely using public IP which has been dynamically assigned to the router by the ISP.
I can Ping the Router and I can also go out to the internet on that router but, I can not telnet into that router from Inside the Network nor Outside the Network. There are no Firewalls involved.
I have tried to clear the config and reconfigure it again, it does not help, I have also applied same config on another CISCO 877 ADSL Router it still does not work.
ERROR i get on the Command Prompt: Could not open connection to the host, on port 23: Connect failed
I have shown some of the Show Run out put below if that helps,
ip nat inside source list 1 interface Dialer0 overload
access-list 1 permit x.x.x.x 0.0.0.7
dialer-list 1 protocol ip permit
line vty 0 4
password 7 ***********
login
Manny Thanks
Punit

Find Below the Requested Sh run outputs
ADSL-ROUTER1#sh run | beg line vty
line vty 0 4
password 7 ***********
login
scheduler max-task-time 5000
end
I have removed the IP for security reasons
ADSL-ROUTER1#sh ip route
Gateway of last resort is 0.0.0.0 to network 0.0.0.0
     x.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
S       x.x.x.x/29 is directly connected, Vlan1
C       x.x.x.x/32 is directly connected, Dialer0
     x.0.0.0/32 is subnetted, 1 subnets
C       x.x.x.x is directly connected, Dialer0
S*   0.0.0.0/0 is directly connected, Dialer0
I also keep getting the message below on the console done know if this is part of the problem
Mar 13 07:17:32.213: %IP_VFR-4-FRAG_TABLE_OVERFLOW: Vlan1: the fragment table h
as reached its maximum threshold 16
Hope this output helps
Thanks

Could not open a connection to host on port 23 : Connect failed

Hi,
I am using Oracle Unbrakeable Linux 5, when i try to connect to the server from the client machine using TELNET, i get the following error
c:/> telnet 192.168.6.184
Connecting to 192.168.6.184...Could not open a connection to host on port 23 : Connect failed.
regards,
Charan

Hi,
i did the following but still doesn't work
# mv /etc/securetty /etc/securetty.bak
The following is the Hosts file
=====================
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1     localhost.localdomain     localhost
192.168.6.184     vision12.dsrc2.com     vision12
#::1          localhost6.localdomain6     localhost6
192.168.6.181     prod20.dsrc2.com     prod20
============================================================
When i try to connect to other server using TELNET from this server, i am able to connect. and when i try to connect to this server from other server using TELNET i am able to connect. But, when i try to connect from the CLIENT Machine, i am not able to connect, the client machine is Windows 2000 Professional.
SERVER to SERVER communication using TELNET is working.
CLIENT to SERVER communication using TELNET is not working.
regards,
Charan

Telent:could not open connection to the host on port 23 connect failed

Hi,
How to run commands of OEL5 host OS from windows XPP virtual machine(Vmware Player) on standalone desktop PC?
While runing the telnet command on windows XPP virtual machine it's gives error
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>cd\
C:\>telnet 192.168.1.2
Connecting To 192.168.1.2...Could not open connection to the host, on port 23: Connect failed
C:\>
Thanks
Regard
GSM

user9230833 wrote:
Launcher means shortcut to execute any file which is inside folder in Linux.Launcher are created on desktop to execute by one click of mouse.You need to create a command file that contains the required instructions to run putty with whatever relevant command line switches in order to start the remote program/process on Linux.
For example, you have a trusted ssh connection (no password prompting) between your Windows account and the Linux vmware account. You need to execute command line +/home/vmware/bin/vmstart myVM+ on Linux.
Your command file in Window will look something as follows:
@echo off
"c:\program files\putty\pssh.exe" vmware@my-linux-server "/home/vmware/bin/vmstart myVM"Once you've create this command file (.cmd file extention), you can create a desktop shortcut for it and assign an icon to it.
However, first test the command file via an interactive console session to ensure it works. Also, I'm not sure you can script telnet using putty - but putty's ssh does support the standard ssh command line and one can execute programs/commands on the remote server in this fashion.
Setting up trusted ssh connections is also important as passwords is a weak security mechanism. It requires a secret to be used and coded into scripts/software that needs to be authenticated.
With ssh you generate a public/private key combination, and provide the public key as unique identifier for your o/s user and platform to a remote server (e.g. Linux). This now enables your platform and o/s user to be authenticated via the privatre/public key pair when your platform establishes a connection with the server.
In putty, generate a ssh key (RSA). Copy and paste the public key into the Linux server account's "+home/vmware/.ssh/authorized_keys+" file. Make sure that the +.ssh+ directory and key have user read/write permissions only. And that's it - no password needed by your account to ssh into the Linux server account. No secrets that need to be kept secret (and that can be stolen and used from any other platform to gain access).

I could not open iPhoto on my mac pro ...clicking on it report generates with just ok button enable

i could not open iPhoto application tried to uninstall and install it again still same problem....
Error message comes up like this :
Process:               iPhoto [1365]
Path:                  /Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier:            com.apple.iPhoto
Version:               ???
Build Info:            iPhotoProject-910029000000000~1
App Item ID:           408981381
App External ID:       729712666
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           iPhoto [1365]
User ID:               501
Date/Time:             2015-01-04 15:09:44.980 +1100
OS Version:            Mac OS X 10.10.1 (14B25)
Report Version:        11
Anonymous UUID:        3D91453B-A9AC-9C65-61B6-B0E5F96324D5
Time Awake Since Boot: 4600 seconds
Crashed Thread:        0
Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: /Library/Frameworks/iTunesLibrary.framework/Versions/A/iTunesLibrary
Referenced from: /Applications/iPhoto.app/Contents/MacOS/iPhoto
Reason: image not found
Binary Images:
    0x7fff6625c000 -     0x7fff66292837 dyld (353.2.1) <4696A982-1500-34EC-9777-1EF7A03E2659> /usr/lib/dyld
Model: MacBookPro11,1, BootROM MBP111.0138.B11, 2 processors, Intel Core i5, 2.4 GHz, 8 GB, SMC 2.16f68
Graphics: Intel Iris, Intel Iris, Built-In
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x802C, 0x384B54463531323634485A2D314736453120
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x802C, 0x384B54463531323634485A2D314736453120
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x112), Broadcom BCM43xx 1.0 (7.15.124.12.10)
Bluetooth: Version 4.3.1f2 15015, 3 services, 19 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0256F, 251 GB
USB Device: Internal Memory Card Reader
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.2
please help me out.....!!!!!!

Thanks LarryHN for replying me I tried that as well but finally I got the solution, I have by mistake deleted one of the iTunes library framework file while removing the virus.
Following steps are done by me to solve the problem:
1) I have removed the iPhoto by dragging it into the trash from applications
2) I have empty the trash
3) I have shutdown the laptop
4) while starting it back, press and hold the command and r button until the apple symbol goes off , after which you can select the reinstall OS option -> that will rebuilt your OS if something has been removed without removing your files or data.
5) after completion, install the iPhotos from app store
Now, its working perfectly

Named Pipes Provider: Could not open a connection to SQL Server

We are running into an error on a SQL request from SQL-IDA to the SQL-IDB server. Both servers are on Windows 2005 with MS SQL Server 2003 SP3.
OLE DB provider "SQL-IDA" for linked server "SQL-IDB" returned message "Login timeout
expired".
OLE DB provider "SQL-IDA" for linked server "SQL-IDB" returned message "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.".
Msg 53, Level 16, State 1, Line 0
Named Pipes Provider: Could not open a connection to SQL Server [53].
It seems to suggest that SQL-IDA cannot find the network path to SQL-IDB. We've followed the steps in this article http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277 but it did not resolve our issue. Is it possible that the MSDTC dynamic port range
should be set to a specific range on both servers?
Any help is greatly appreciated.
Albert

Hi Albert,
Can you try to use the SQL Server Management Studio on server ‘SQL-IDA’ to connect to the instance on server ‘SQL-IDB’ to see if it works or not?
There are possible reasons to error 53:
a) typo in the server name, or using "/" rather than "\" between server name and instance name, e.g. "myserver/myinst" is not correct.
b) name resolution to the server name is not correct, "ping -a yourserver" would tell if that's the case
c) The server machine is firewall'ed and file sharing is not in the exception list. You need put "File and Printer Sharing" in exception.
For more information:
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server (Microsoft SQL Server, Error: XXX).
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Stephanie Lv
TechNet Community Support

Telnet not working i need help : Could not open connection to the host !!

hello all im back today with big problem with telnet i dont know why !!
i have to computers one of them in my home and the other one in my office both of them use windows 7 so
home PC internet IP : 82.205.100.161
office PC internet IP : 82.102.237.175
so i go to control panel and then to windows features and i check Telnet Client and Telnet server
then i turn off my firewall
then i start telnet service
then i execute netstat -ab to know telnet port :
[tlntsvr.exe]
TCP [::]:135 Hacker-HP:0 LISTENING
is there anythink i need to do to get that damn connection over internet NOT LAN !! pleaze help me i still get this sucks error : Could not open connection to the host
peace
Dr.BL@CKDeaTH

Hi,
Telnet server use TCP port 23 by default.
Here is a screenshot of my lab server,
To verify if the TCP port 23 has been opened, we can use the portqry tool.
Here is the download link,
http://www.microsoft.com/en-us/download/details.aspx?id=17148
Best Regards.
Steven Lee
TechNet Community Support

Re: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

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. Great. Now when I open IE on an external box, i.e. on the 2000 box, and try to test the reports, 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

Named Pipes Provider, error: 40 - Could not open a connection to SQL Server :
I. Incorrect connection string, such as using SqlExpress.
Check out: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=558456&SiteID=17
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1245564&SiteID=1
The typical error when dealing with Express includes:
a. User is not aware of SqlExpress was installed as a named instance, consequently, in his/her connection string, he/she only specify ".","localhost" etc instead of ".\SqlExpress" or "<machinename>\Sqlexpress".
b. Np was disabld by default after installing SqlExpress.
c. If Sqlexpress was installed on the remote box, you need to enable remote connection for Express.
Please read the following blog for best practice of connecting to SqlExpress.
http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx
II. Named Pipes(NP) was not enabled on the SQL instance.
Check out: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=136253&SiteID=1
Oppose to SQL 2000 which turn on all protocols, SQL 2005 SKUs turn off NP by default. So, when you see this error, please check:
1) Go to SQL Server Configuration Manager, See Server has NP enabled.
2) %windir%\program files\microsoft sql server\mssql.1\mssql\log, notepad ERRORLOG, see whether Server is listening on NP. You should see "Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ] or [\\.\pipe\mssql$<InstanceName>\sql\query]"
3) Notice that "sql\query" is the default pipe name, so you need to know server is listening on which pipe name. eg: if you specify server pipe name is "sql\query1", then you would see in the errorlog that server listening on [ \\.\pipe\sql\query1 ], and go to SQL Server Configuration Manager, click client Named Pipe properties, see whether the pipe name is same with the one server listening on.
4) If you are using SQL Native Client ODBC/OLEDB provider({SQL Native Client} or SQLNCLI), go to SQL Configuration Manager, click client protocols, make sure NP and TCP are both enabled. Right click properties of NP, make sure client is using the same pipe name as server for connection.
5) If you are using MDAC ODBC/OLEDB({SQL Server} or SQLOLEDB) provider, in command line, launch "cliconfg.exe" and make sure NP enabled and right pipe name specified.
III. Remote connection was not enabled.
Check out: when you right click on the Server in SQL Server Management Studio, in Connections, the Remote server connections part, you have enabled the "Allow remote connections to this server" check box
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=322792&SiteID=1
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=763875&SiteID=1
If you are making a remote connection, namely, your target SQL Server is on the different box as client application, you might need to check whether:
a. "File and Printer Sharing" was opened in Firewall exception list.
b. Please see the blog for enabling remote connection for express and troubleshooting tips of remote connection.
http://blogs.msdn.com/sql_protocols/archive/2005/11/14/492616.aspx
http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx
IV. Server not started, or point to not a real server in your connection string.
Check out: Open SQL Server Surface Area Configuration and ensure all the required services are started, Remote Connections are configured.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=348662&SiteID=1
a. use "sc query mssqlserver" for default instance or "sc query mssql$<instancename>" to make sure SQL Server was started. Sometimes, reseason behind the broken of your client application w/ this error:40 might be SQL server restarted and failed, so, it'd better for you to double check.
b. User specified wrong server in their connection string, as described in the forum discussion, "MSSQLSERVER" is an invalid instance name. Remember, when you connect to default instance, <machinename> could be best representitive for the instance, when you connect to a named instance such as sqlexpress, you should specify <machinename>\<instancename> as data source in your connection string.
V. Other reasons such as incorrect security context.
Check out: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=192622&SiteID=1
Such error also occured during user operation such as moving database or db mirroring or cluster, any DB OP that might invovle different sql instances, namely, the destination database is located in another sql instance and user is not aware of the state of the destination. I recommend you first isolate whether this fail is during connection stage or data operation stage.
a. During data operation, you are normally asked to type in the destination server name whether it is default to "(local)" or another server "<remotemachinename>". So, remember the exact string that represent the target instance, then when the error repros, open command line, use "sqlcmd -S<representitive> -E" ,see what happens, if the connection fail, please follow up above I - IV troubleshooting lists. otherwise continue.
b. If you can make basic conection, but still face the error, then there must be something that server reject the connection or client close the connection for some reason.
VI. Please try basic connectivity tests between the two mahcines you are working on. One simple way to verifty connectivity is to use command line tools, such as osql.exe. For example, osql -E -Stcpervername\instancename. If it connects cross-machine successfully, please also verify that your connection string in your scenario is correct.
Here are some blogs which could be helpful: just follow the basic connectivity troubleshooting guidelines on the SQL Protocols blog, see:
SQL Server 2005 Connectivity Issue Troubleshoot - Part I
http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx
and
SQL Server 2005 Connectivity Issue Troubleshoot - Part II
http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx
Hope this helps.

Heart beat could not open connection, error code 110

Hi, where can I find error codes for NFR and NSM?
I have problems with some agents connecting to the engine:
2/17/2010 16:02:55 EngineInterface: Heart beat could not open connection, error code 110
Both engine and agent runs on the same server (10.236.19.147):
AgentNCP Service Config
Host Address: 10.236.19.147
Service Ports: HTTPS: 3037 HTTP: 0
Data Path: /var/opt/novell/filereporter/agentncp
Debug Logging: Enabled
Heartbeat: 60 seconds
Engine Address: 10.239.19.147:3035
Use SSL: Yes
Alternate Hostname: huanovellfs1
Engine Service Config
Host Address: 10.236.19.147
Service Ports
Client HTTPS: 3033 HTTP: 0
Agent HTTPS: 3035 HTTP: 0
Data Path: /var/opt/novell/filereporter/engine
Debug Logging: Enabled
Heartbeat: 60 seconds
DSI Address: 10.236.19.89:8009
Use SSL: Yes
Scans per Volume: 2
Another OES2 server connects fine to the engine, butI have a Netware agent, which also fails to connect:
Feb 17, 2010 4:08:11 PM SR Interface: Heart beat could not open connection.
NFR is 1.0.0
Thanks for any input.
Istvan

Hi Istvan! Sorry for the delay in our response! we are in the process
of building a list of error codes for everyone! in the meantime the 110
means the following:
// Couldn't create a new network interface
#define CC_STATUS_CCS_CANT_CREATE 110
Is this an NSM integration installation?
Also, remove the alternate hostname.
If you don't mind, let's move this support issue to
filereporter"@"novell.com!
Thank you!
icseke wrote:
> Hi, where can I find error codes for NFR and NSM?
>
> I have problems with some agents connecting to the engine:
>
> 2/17/2010 16:02:55 EngineInterface: Heart beat could not open
> connection, error code 110
>
> Both engine and agent runs on the same server (10.236.19.147):
>
>
> AgentNCP Service Config
> ------------------------------------------------------------------------------
> Host Address: 10.236.19.147
> Service Ports: HTTPS: 3037 HTTP: 0
>
> Data Path: /var/opt/novell/filereporter/agentncp
> Debug Logging: Enabled
> Heartbeat: 60 seconds
> Engine Address: 10.239.19.147:3035
> Use SSL: Yes
> Alternate Hostname: huanovellfs1
>
> Engine Service Config
> ------------------------------------------------------------------------------
> Host Address: 10.236.19.147
> Service Ports
> Client HTTPS: 3033 HTTP: 0
> Agent HTTPS: 3035 HTTP: 0
>
> Data Path: /var/opt/novell/filereporter/engine
> Debug Logging: Enabled
> Heartbeat: 60 seconds
> DSI Address: 10.236.19.89:8009
> Use SSL: Yes
> Scans per Volume: 2
>
> Another OES2 server connects fine to the engine, butI have a Netware
> agent, which also fails to connect:
>
> Feb 17, 2010 4:08:11 PM SR Interface: Heart beat could not open
> connection.
>
> NFR is 1.0.0
>
> Thanks for any input.
>
> Istvan
>
>

Error 40 , could not open a sql connection

I have recently bought Kaspersky Internet Security 2014. Before the installation of Kaspersky, SqlServer 2008 R2 express edition was working without any error. But after it's installation I got error saying:
" A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)".
Please help me to get out of this. I have checked all the ports, TCP/IP enabled, SqlServer borwser services.

Ya, Kaspersky was not the problem. I was connecting to wrong instance. Before, i used to connect with
"Data Source=MANCHANA123\SQLEXPRESS;Initial Catalog=Musicworld;Integrated Security=True".
And it was working fine.
Currently, it is not working with same command, I need to make change like this..
Data Source=MANCHANA123\\SQLEXPRESS;Initial Catalog=Musicworld;Integrated Security=True
Use of "\\" instead of "\" .AND now i have no problem here.
Thank you so much Shanky_621 for answering me..

Named pipes provider : could not open a connection to a SqL server . . . . .

Hey all, i need help
I have a job which was running quite peacefully for the last EVER, but since last Saturday it keeps failing and then run successfully and then fails. . . . .and gives me the below error.
Executed as user: Sx\xxx. Microsoft (R) SQL Server Execute Package Utility Version 10.0.5500.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 9:00:00 PM Progress: 2014-03-11
21:00:02.16 Source: {122F32F1-F99F-4A5A-BA70-F5426B2747DA} Executing query "DECLARE @Guid UNIQUEIDENTIFIER EXECUTE msdb..sp...".: 100% complete End Progress Progress: 2014-03-11 21:00:02.19
Source: Manually replicate tables Executing query " USE DBNAME ".: 50% complete End Progress Error: 2014-03-11 21:00:22.35 Code: 0xC002F210 Source: Manually replicate
tables Execute SQL Task Description: Executing the query " exec usp_ReplicateEsourceTable 'Ebase'; ..." failed with the following error: "Named Pipes Provider: Could not open a connection to SQL
Server [53]. OLE DB provider "SQLNCLI10" for linked server "ServerName" returned message "Login timeout expired". OLE DB provider "SQLNCLI10" for linked server "ServerName" returned message "A
network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information
see SQL Server Books Online.".". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. End Error Progress: 2014-03-11
21:00:22.45 Source: Notify on failure Executing query "exec msdb.dbo.sp_notify_operator @profile_name =...".: 100% complete End Progress DTExec: The package execution returned DTSER_FAILURE (1).
Started: 9:00:00 PM Finished: 9:00:23 PM Elapsed: 22.25 seconds. The package execution failed. The step failed.
I have already tested the linked server connection between those servers and its fine. And what is weird is that when i run the job manually it runs successfully.
Any ideas?

Hi,
How often does the job run? Does the query fail intermittently?
I suggest you check the following configuration on both servers:
1. In SQL Server Configuration Manager, expand SQL Server Native Client Configuration, right-click
Client Protocols, and then click Properties. What’s the order of protocol?
2. Check if the default port of TCP/IP is set to 1433.
By default, the top protocol is to use TCP/IP and then Named Pipes. There are two possible situations:
1. Connection fails and client protocol is using TCP/IP 1433.
When server A remotes to server B, it will use TCP/IP connection. If it encounters some issue during connecting (such as network issues), it will use Named Pipes instead. If the Name Pipes 445 still fails, thus the above error message will
be thrown out. It will use Name Pipes afterwards until the SQL Server service is restarted.
2. The port number is not 1433.
However, the remote machine is listening 1433. Then, the linked server will trying to use TCP/IP first. Because of the port error, it will change to Name Pipes.
Thanks.
Tracy Cai
TechNet Community Support

Could not open a connection to SQL Server

Hello -
I am trying to install the Office SharePoint training from this link (http://www.microsoft.com/downloads/details.aspx?familyid=673DC932-626A-4E59-9DCA-16D685600A51&displaylang=en)
I get the error below. TCP/IP / Named Pipes both selected in SQL Surface area. any ideas? MOSS and SQL are installed on the same server.
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)
More information has been written to the server event log.

There are a lot of reasons Could not open a connection to SQL Server, you have to check following things to fix the issue:
1) SQL Server (MSSQLSERVER)
2) SQL Server Browser
3) SQL Server Port 1433
4) Allow remote connections to this server
5) Ping for your IP Host Address
You may also refer these articles also Could not open a connection to SQL Server & the
underlying provider failed on open
Hope above steps would help to resolve your issue.

Named Pipes Provider: Could not open a connection to SQL Server [2]

Hi
I'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 2
systemsettings\software shows the "sql server 2005 express edition ctp (sqlexpress)" installed
mmc\service shows me the SQL Server (SQLExpress) is running
Following the guided tour I use the commandline, type cmd, and type in the commandbox:
"C:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLCMD90" -S "localhost\SqlExpress"
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

Typically I have found problems with connection strings as one of a few things:
1. Your instance is named different than the default. I labeled mine BrettSQLServer instead of the regular instance.
2. Your default storage of the your database has a user the system does not like and won't give it access.
3. You have ports blocked that SQL Server is trying to access.
1. Your instance should show up under 'SQL Server Configuration Manager'. Start>MS SQL Server 2008 > Configuration Tools> SQL Server Configuration Manager. You should see a left view panel where you can click 'SQL Server Services'. This
will show on the right all of your SQL services that are running. The most important one is SQL Server({Your SQL Server Name}). You will see column headers's displaying: "Name, State, Start Mode, Log on as, ProcessID" by default. If
you don't see a version of this you may have no installed SQL server properly and gotten SQL management studio but not the server. If you have the server and it's off or not running that is another problem. If your "LOG On AS" is a service account
is "NT ...." or something besides "Local System" that may be a problem. Without getting into the symantecs of protection suffice to say you log in with less than system, yes you are more secure but some built in functions for connections may not work.
2. Going off of rights of your 'Log On As' I WOULD USE 'System' NOT "NT Authority....". The reason is that you can access less things with 'NT Authority....' but yes you are more secure for that reason. If you are just trying to connect at home
to test non secure things I don't see the harm. If you are setting up a database for a multinational corporation than, Yes I would use a more secure account. If you need to change it while still in SQL Server Confi Manager: Right Click> SQL
Server(Your Version) > On 'Log On' tab > Choose drop down for 'Built-in Account' select 'Local System'. As extra steps make sure by some strange reason your database locales have this user by default(They should). MS likes to install database
as default to: C:\Program Files\Microsoft SQL Server\MSSQL10.{instanceName}\MSSQL. If you go to this location by going: right click>Properties>Security Tab .. and you fail to see your user that SQL server is defined as you may have lots of
issues.
3. Turn off Windows Firewall during SQL installation. If you are scared of being attacked during this down window, disconnect your NIC and reconnect later. I have not added a port manually in a while but it is simply easier to just
turn off your firewall during install. Having your TCP/IP connection from SQL Server blocked is kind of bad if you need to connect to it that way later.
Problems most commonly encountered with SQL Server by users I have seen and I myself encountered a lot with full blown SQL Server Enterprise as well as Express versions of SQL:
Connection string DO not work for BIDS, ADO.net, Linq, etc...
Once you follow steps above just go {ComputerName}\{SQL Server Instance} as your connection name. That mostly always works. As a preliminary test you should install SQL Management Studio first before doing connection strings for a basic test
that it can access your server. When you first boot it up and click 'New Database Engine Query' it will display Server Type: "Database Engine" and a blank field or autopopulated field for 'Servername'. The {ComputerName}\{SQL Server Instance} almost
always works. If it works and you can connect, you know that you have access, if you don't start there first before getting into connection strings through .NET languages. I suggest just adding an easy alias, my local SQL box is simply called
'Brett'. Go again back to SQL Server Configuration Manager. On the left side click 'SQL Native Client ...' > 'Aliases' > New > type in whatever you want. Go back to the left pane click on 'SQL Server Services' ensure the service
'SQL Server Browser' is running and set to run automatic. Have fun accessing SQL Server with your alias.
Help I can't get FileStream to work and I ran 'spconfigure' in SQL and it still doesn't work.
Kind of annoying that more sites don't list that it is entirely in the Configuration manager and has zilch to do with setting the option if the config has it off. I am not a master of the sp_configure TSQL access method but I know during installs turning
it on fails to REALLY turn it on. Once again go to SQL Config Manger > SQL Server Services > Right click your instance > Select FILESTREAM tab > enable both check boxes. Restart SQL Server. Install Adventureworks 2008 and whatever
else failed due to filestream access levels.
Medium to Advanced on some things, but always wanting to know more

Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

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

Nan,
Before I get on with this post - thank you for your reply.
The XPSP2 machine actually had the firewall disabled, and I verified that it could accept connections on the the associated ports with the Shields Up utility. I tested this on both machines.
I can connect to the server from the XPSP2 machine, Import / Export, manage, view logs, and do everything EXCEPT get the Copy Database package to run. SQL Server Agent always fails on the last step with the following error:
Event Type: Error
Event Source: SQLISPackage
Event Category: None
Event ID: 12550
Date:  1/10/2006
Time:  1:34:15 PM
User:  NT AUTHORITY\SYSTEM
Computer: 401SERVER
Description:
Event Name: OnError
Message: Failed to connect to server BETHESDA.
StackTrace:    at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
   at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.OpenConnection(Server& server, ServerProperty serverProp)
InnerException-->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)
StackTrace:    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnect(WindowsIdentity impersonatedIdentity)
   at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
Operator: NT AUTHORITY\SYSTEM
Source Name: BETHESDA_401SERVER_Transfer Objects Task
Source ID: {86F355AD-3B74-4D7B-8D2D-C743C790A269}
Execution ID: {91B7C32C-C439-4EDB-8A0F-9F8BF207BC06}
Start Time: 1/10/2006 1:34:15 PM
End Time: 1/10/2006 1:34:15 PM
Data Code: 0
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Have you (or anyone else) successfully executed a Copy Databse task?
Steve

"Could Not Open the Communication Device" ???

I use a dial up connection. Everytime I try to connect to the internet, after it dials a message box pops up that says "Could Not Open the Communication Device". Has anyone else had this problem? And how do I fix it?
Please help me.

I found this in Mac Help:
If you haven't entered your network settings, open Network preferences, choose your modem port (internal or external) from the Show pop-up menu, and enter the settings provided by your ISP, such as the access phone number, your user name, and your password.
You can also use the Network Setup Assistant to help you enter network settings. Click "Assist me" in the Network pane of System Preferences and follow the onscreen instructions.
Also verify that the number you are dialing is correct.
Try this too.
Some ISPs may require a PPP connection terminal script to connect to the Internet using a modem. If it is required, contact your ISP for the terminal script
To use a PPP connection terminal script follow these steps:
In the Finder, navigate to the Library folder on your startup disk.
If the Library folder does not contain a Terminal Scripts folder, you will need to create it. Choose File menu > New Folder, and name the new folder "Terminal Scripts."
Copy the terminal script file from your ISP to the Terminal Scripts folder.
To activate the terminal script, choose Apple menu > System Preferences.
Click Network and choose your modem port (internal or external) from the Show pop-up menu.
Select the PPP tab and click the PPP Options button.
Choose your connection script from the Terminal Script pop-up.
Click OK and then click Apply Now.
If the Terminal Script pop-up menu is dimmed, then the script is not being recognized. Check that the script is valid, and it is installed in the correct location.
-Internet Wiz

Could not open port 3601

Similar Messages

Maybe you are looking for