Could not set Portal Connection properties

Hi Mates,
First let me tell what configurations i have
SAP Netweaver 2004 (java stack)
Enterpriseportal running on 50000
VS.Net with PDK.net2.0
SAP .net connector 2.0
I am trying to add new portal in VS.net solution explorer
I am not sure what properties i need to give
Host - hostname
isSSL - false
password - ******
port - (tried both 50000 and 8050)
remember password - true
timeout -15
username - administrator ( this is my portal adminitsrator)
Can someone help me to sort out this issue.
cheers
ram

Hi Rima,
Thanks for your reply, I dont know it worked now which didnt worked sometime back. I tried to deploy the portal application i am getting following error.. Can i know what is wrong with my portal.
Portal Runtime Error
An exception occurred while processing a request for :
iView : PortalApplication4.PortalComponent1
Component Name : PortalApplication4.PortalComponent1
iView cannot display.
Could not connect to the .NET runtime server.
Contact your administrator if the problem persists.
Possible reasons:
1. The Portal Runtime for .NET service is not running or installed.
2. The .NET Runtime Servers Configuration property of 'iViewProcessorService' service is not correct. Check the syntax of server nodes, hosts and ports settings.
Exception id: 10:07_13/11/06_0002_7810250
See the details for the exception ID in the log file

Similar Messages

MSS Reporting - Could not set up connection to ITS

Hello,
I'm trying to activate MSS Reporting and have followed the configuration steps in ESS / MSS Configuration
(SAP Best Practices for SAP HCM V2.600) (N06).
After this I don't get any MDT related reports in the launchpad. When executing test program
PWPC_RPT_START_REPORT_TEST

have you converted the entries to LPA
ie are you using report category RPTO ?
please read the steps here
http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=199820849

Error trying to run SSIS Package via SQL Server Agent: DTExec: Could not set \Package.Variables[User::VarObjectDataSet].Properties[Value] value to System.Object

Situation:
SSIS Package designed in SQL Server 2012 - SQL Server Data Tools
Windows 7 - 64 bit.
The package (32 bit) extracts data from a SQL Server db to an Excel Output file, via an OLE DB connection.
It uses 3 package variables:
*) SQLCommand (String) to specify the SQL Statement to be executed by the package
Property path: \Package.Variables[User::ExcelOutputFile].Properties[Value]
Value: f:\Output Data.xls
*) EXCELOutputFIle (String) to specify path and filename of the Excel output file
Property path: \Package.Variables[User::SQLCommand].Properties[Value]
Value: select * from CartOrder
*) VarObjectDataSet (Object) to hold the data returned by SQL Server)
Property path: \Package.Variables[User::VarObjectDataSet].Properties[Value]
Value: System.Object
It consists out of 2 components:
*) Execute SQL Task: executes the SQL Statement passed on via a package variable. The resultng rows are stored in the package variable VarObjectDataSet
*) Script Task: creates the physical output file and iterates VarObjectDataSet to populate the Excel file.
Outcome and issue:The package runs perfectly fine both in SQL Server Data Tools itself and in DTEXECUI.
However, whenever I run it via SQL Server Agent (with 32 bit runtime option set), it returns the errror message below.
This package contains 3 package variables but the error stating that a package variable can not be set, pops up for the VarObjectDataSet only. This makes me wonder if it is uberhaupt possible to set the value of a package variable
of type Object.
Can anybody help me on this please ?
Message
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 6:40:20 PM DTExec: Could
not set \Package.Variables[User::VarObjectDataSet].Properties[Value] value to System.Object. Started: 6:40:20 PM Finished: 6:40:21 PM Elapsed: 0.281 seconds. The package execution failed. The step failed.
Thank you very much in advance
Jurgen

Hi Visakh,
thank you for your reply.
So, judging by your reply, not all package variables used inside a package need to be set a value for when run in DTEXEC ?
I already tried that but my package ended up in error (something to do with "... invocation ...." and that error is anything but clearly documented. Judging by the error message itself, it looks like it could be just about anything. that is why I asked my
first question about the object type package variable.
Now, I will remove it from the 'set values' list and try another go cracking the unclear error-message " ... invocation ...". Does an error message about " ... invocation ..." ring any bells, now that we are talking about it here ?
Thx in advance
Jurgen
Yes exactly
You need to set values only forthem which needs to be controlled from outside the package
Any variable which gets its value through expression set inside package or through a query inside execute sql task/script task can be ignored from DTExec
Ok I've seen the invocation error mostly inside script task. This may be because some error inside script written in script task. If it appeared after you removed the variable then it may because some reference of variable existing within script task.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

DNS Set Up system throw as ORA-12154; TNS :could not resolve the connect id

Hi,
While i'm creating DNS set up system throws below message
unable to connect
SQLState=08004
DNS Set Up for instantclient(win32-10.2.0.4) system throw as ORA-12154; TNS :could not resolve the connect identified specified.
operationg system:xp
dir path:C:\Oracle\instantclient10_2
TNSNAMES.ORA(C:\Oracle\instantclient10_2\NetWork\ADMIN) Contants
YourTNSName =sankar
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST =localhost)(PORT =1521))
(CONNECT_DATA =
(SID =sankar)
(SERVER = DEDICATED)
dir contains:
sqresus.dll,
sqresja.dll
sqoras32.dll
sqora32.dll
oraociei10.dll
oraocci10.dll
orannzsbb10.dll
ojdbc14.jar
ocijdbc10.dll
ociw32.dll
oci.dll
classes12.jar

user7197586 wrote:
Hi
I have been created one DBLink it's created but when i am trying to access the data through the link it's raise error as
"ORA-12154: TNS:could not resolve the connect identifier specified"
CREATE
PUBLIC DATABASE LINK
Vrd_tcplink
CONNECT TO
"SAPVRD"
IDENTIFIED BY
"manager123"
USING
'VRD_TCP.WORLD'
created this above dblink
Kindly Suggest to wau out.
Regards,
Sachin
When using a dblink, the database with the link is acting as a client to the remote database ... exactly like sqlplus running on the db server.
read: http://edstevensdba.wordpress.com/2011/02/26/ora-12154tns-03505/ ora-12154tns-03505

Could not create pool connection with MySql

When starting weblogic server I obtain the following error message when the conection
pool for a MySql database should be established. What's the mistake I am doing? #The
examples in the weblogic.properties put a "server=DEMO to the props. What is this
server related to the MySql RDBMS? Is it mandatory? After the error message produced
by Weblogic you'll find some information about the MySql setup (my.ini) I have made.
Mi Mai 01 01:33:50 CEST 2002: <WebLogicServer> Invoking main-style startup weblogic.jdbc.common.internal.JdbcStartup
weblogic.jdbc.common.internal.JdbcStartup
Mi Mai 01 01:33:50 CEST 2002: <JDBC Pool> Creating connection pool ejbTestPool
with:
{aclName=weblogic.jdbc.connectionPool.ejbTestPool, maxCapacity=2, initialCapacity=1,
url=jdbc:mysql://Blizzard:3306/ejbTest, props=user=du-it;password=du-it;server=3.23.4
9-nt, capacityIncrement=1, driver=org.gjt.mm.mysql.Driver, poolName=ejbTestPool}
Mi Mai 01 01:33:50 CEST 2002: <JDBC Pool> Sleeping in createResource()
Mi Mai 01 01:33:51 CEST 2002:<E> <JDBC Pool> Failed to create connection pool "ejbTes
tPool"
weblogic.common.ResourceException: weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: Invalid authorization specification: Access denied for user:
du-it@blizzard' (Using password: YES)
at org.gjt.mm.mysql.MysqlIO.init(MysqlIO.java:278)
at org.gjt.mm.mysql.Connection.<init>(Connection.java:230)
at org.gjt.mm.mysql.Driver.connect(Driver.java:126)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connecti
onEnvFactory.java:146)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connecti
onEnvFactory.java:108)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator
.java:771)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:4
16)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:3
30)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connecti
onEnvFactory.java:154)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connecti
onEnvFactory.java:108)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator
.java:771)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:4
16)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:3
30)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connecti
onEnvFactory.java:124)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator
.java:771)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:4
16)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:3
30)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
MySql:
#This File was made using the WinMySQLAdmin 1.4 Tool
#29.04.2002 14:46:57
#Uncomment or Add only the keys that you know how works.
#Read the MySQL Manual for instructions
[mysqld]
basedir=D:/db/mysql
#bind-address=169.254.102.136
datadir=D:/db/mysql/data
#anguage=D:/db/mysql/share/german
#slow query log#=
#tmpdir#=
port=3306
#set-variable=key_buffer=16M
[WinMySQLadmin]
Server=D:/db/mysql/bin/mysqld-nt.exe
user=du-it
password=du-it

When starting weblogic server I obtain the following error message when the conection
pool for a MySql database should be established. What's the mistake I am doing? #The
examples in the weblogic.properties put a "server=DEMO to the props. What is this
server related to the MySql RDBMS? Is it mandatory? After the error message produced
by Weblogic you'll find some information about the MySql setup (my.ini) I have made.
Mi Mai 01 01:33:50 CEST 2002: <WebLogicServer> Invoking main-style startup weblogic.jdbc.common.internal.JdbcStartup
weblogic.jdbc.common.internal.JdbcStartup
Mi Mai 01 01:33:50 CEST 2002: <JDBC Pool> Creating connection pool ejbTestPool
with:
{aclName=weblogic.jdbc.connectionPool.ejbTestPool, maxCapacity=2, initialCapacity=1,
url=jdbc:mysql://Blizzard:3306/ejbTest, props=user=du-it;password=du-it;server=3.23.4
9-nt, capacityIncrement=1, driver=org.gjt.mm.mysql.Driver, poolName=ejbTestPool}
Mi Mai 01 01:33:50 CEST 2002: <JDBC Pool> Sleeping in createResource()
Mi Mai 01 01:33:51 CEST 2002:<E> <JDBC Pool> Failed to create connection pool "ejbTes
tPool"
weblogic.common.ResourceException: weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was:
java.sql.SQLException: Invalid authorization specification: Access denied for user:
du-it@blizzard' (Using password: YES)
at org.gjt.mm.mysql.MysqlIO.init(MysqlIO.java:278)
at org.gjt.mm.mysql.Connection.<init>(Connection.java:230)
at org.gjt.mm.mysql.Driver.connect(Driver.java:126)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connecti
onEnvFactory.java:146)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connecti
onEnvFactory.java:108)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator
.java:771)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:4
16)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:3
30)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connecti
onEnvFactory.java:154)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connecti
onEnvFactory.java:108)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator
.java:771)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:4
16)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:3
30)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connecti
onEnvFactory.java:124)
at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator
.java:771)
at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:4
16)
at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:3
30)
at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117)
at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200)
at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109)
at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
MySql:
#This File was made using the WinMySQLAdmin 1.4 Tool
#29.04.2002 14:46:57
#Uncomment or Add only the keys that you know how works.
#Read the MySQL Manual for instructions
[mysqld]
basedir=D:/db/mysql
#bind-address=169.254.102.136
datadir=D:/db/mysql/data
#anguage=D:/db/mysql/share/german
#slow query log#=
#tmpdir#=
port=3306
#set-variable=key_buffer=16M
[WinMySQLadmin]
Server=D:/db/mysql/bin/mysqld-nt.exe
user=du-it
password=du-it

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.

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

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: 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

Network adapter could not establish a connect from external server

hi,
I've set up a jdbc thin driver properly using
the following input:
"jdbc:oracle:thin:@ipaddress:1521:DBname",
"username", "password"
When outside users try to connect externally (outside the network) there is a different ipaddress. Although they are able to ping,
telnet, run jsp etc... using the external address, they get the following error when they try the thin driver connection:
i/o exception: network adapter could not establish a connection
They change the ipaddress in the connection string to match the external ip. We are using oracle 8i, JRun on Linux. I have a feeling it has something to do with the tnsnames.ora file but I can't be sure.
Any ideas?
Thanks in advance!

this is expected behavior ...
the jdbc thin driver requires the use of an ip address that the calling program has acces to ...
internally you have one ip address exposed.
apparently you have another ip address set up for the external customer.
fyi
jdbc thin driver don'ts use the tnsnames.ora file -- they use "host:port:sid" because they are required to be platform independent and not access local datafiles or environment variables on the execution platform.
jdbc oci drivers do use tnsnames.ora which provides the host:port:sid info in their entries.

HOW TO RESOLVE(Test failed: The Network Adapter could not establish the connection)

Hii
I want to create new databse as sysdba in jdev.I followed the steps as given in
Oracle JDeveloper 11g Release 2 Tutorials - Designing and Building Database Tables
In step 7 create database user and database connection, I am not able to do that and getting the error
(Test failed: The Network Adapter could not establish the connection).
Please help me.

Hi,
Could you please provide all value you pass to the connection properties on the connection creation panel? First of all, you should choose "Generic JDBC" as the connection type in order to use BDB SQL JDBC driver.
Regards,
Cindy

Io exception: The Network Adapter could not establish the connection

Hi All,
I run tomcat and connect to Oracle fine, both on the same machine.
I also run some batch processes daily and they often run without problems. The batch processes lots of selects and updates/inserts onto Oracle.
These tend to work fine, but sometimes when they run I get
java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
So a batch process will be running doing lots of selects and updates then it just decides it had enough and throws this error each time it tries to connect. Meanwhile tomcat continues to run fine through the same TNS listener, but subsequent batch jobs fail to connect.I normally have to restart the TNS Listener.
I connect through the same class whether connecting through Tomcat or from the batch process with this:
public static Connection getConnection(String caller) throws SQLException{
try{
Connection con;
if (standalone){
try{Class.forName(driver);}catch(ClassNotFoundException e){}
con=DriverManager.getConnection(url,user,password);
return con;
}else{
if (ds==null)initialiseContext();
con=ds.getConnection();
return con;
}catch(SQLException e){
ds=null;
logger.debug("Problem in DBAccess.getConnection()...");
logger.debug(e.getMessage());
e.printStackTrace();
throw e;
I specifiy params such as MaxIdle with Tomcat using the xml config but not when its standalone - could this be affecting it?
Any idea?
Thanks.

lovingbarcelona wrote:
* Yep I get the same on the dev box.
* I am definitely closing all the connections, I keep a close watch on that.
Oracle should be able to handle lots of connections no problem, I agree, and it is through tomcat.
Yet the exception that you get says that it isn't. Oracle, for example, on a single box shouldn't be able to handle 100,000 simultaneous connections.
I would be very surprised if it couldn't handle 1,000. And if there was an issue at that point it would be a resource bound issue, like CPU (on the single box) rather than connections.
You suggested licensing issues?I believe at one time, not necessarily now, the Oracle server would be sold such that it limited the number of simultenous connections. This could have been a relatively low number. There are quite a few assumptions in that - the major one would be it is based on my faulty memory and second would be that it was years ago.
By the way you are not running this on a unix variant system without redoing the kernel limits to set up for a server system right?

Network adapter could not establish the connection

Hi,
Iam new to using Oracle please help me in this problem. Iam trying to connect oracle8i in my home pc(win 98) in java.. I have said..
String url="jdbc:oracle:thin:@testhost:1521:sid";
DriverManager.getConnection(url,"scott","tiger");
Actually i have added the service name using Oracle Net 8 Assistant ... it asked me service name so i gaved "fobjects". then host and port number then i gave "testhost" and port number as 1521. then i tried to use the test service but i couldnt get it... it gaved me error called " ORA12545- Connect failed because target host or obejct doe not exist ..Even then i pressed finished button to accomplish the thing...ans when i executed the java program with the above service name setup it said SO Excpetion : Network adapter could not establish the connection.
Well What the wrong i have done, help me...
Regards
Lensi.

hi,
I think you have to register the driver first. pls try the following program...
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
* This class tests the environment to check if JDBC is configured and
* connection to database is possible thru JDBC. Uses THIN driver to connect.
public class JDBCCheck {
public JDBCCheck() { }
private Connection conn = null;
private final int NO_DRIVER = 1;
private final int INVALID_URL = 17002;
private final int INVALID_CREDENTIALS = 1017;
private final int NULL_URL = 2;
private final int DATABASE_DOWN = 1034;
public static void main(String[] args) {
JDBCCheck check = new JDBCCheck();
check.dbconnect();
public void dbconnect() {
if(loadDriver())
if(connect())
doSomething();
public boolean loadDriver() {
boolean loadeddriver = false;
String jdbcDriver = System.getProperty("jdbc.driver.class");
// Use Oracle driver if nothing is set
if(jdbcDriver == null) jdbcDriver = "oracle.jdbc.driver.OracleDriver";
log("Loading JDBC Driver : class="+jdbcDriver+" ...");
// try to load driver
try {
Class.forName(jdbcDriver);
log("Loaded JDBC Driver ");
loadeddriver = true;
} catch (ClassNotFoundException noclassEx) {
error(NO_DRIVER,noclassEx);
return loadeddriver;
public boolean connect() {
boolean connected = false;
String jdbcURL = System.getProperty("jdbc.url");
String username = System.getProperty("jdbc.username");
String password = System.getProperty("jdbc.password");
if(username == null || password== null) {
username = "scott";
password = "tiger";
if(jdbcURL == null) error(NULL_URL,new Exception(" jdbc.url cannot be null "));
log("Connecting with URL="+jdbcURL+" as "+username+"/"+password);
try {
conn = DriverManager.getConnection(jdbcURL,username,password);
log("Connected to Database");
connected = true;
} catch (SQLException sqlEx) {
error(sqlEx.getErrorCode(),sqlEx);
return connected;
public void doSomething() {
Statement stmt = null;
ResultSet rset = null;
try {
stmt = conn.createStatement();
log("Created Statement object");
rset = stmt.executeQuery(" SELECT 'PASSED' FROM Dual ");
log("Retrieved ResultSet object");
if(rset.next())
log("Connection :"+rset.getString(1));
} catch (SQLException sqlEx) {
} finally {
try {
log("Closing Statment & ResultSet Objects");
if (rset != null) rset.close();
if (stmt != null) stmt.close();
if (conn != null) {
log("Disconnecting...");
conn.close();
log("Disconnected from Database");
} catch (Exception e) { }
public void log(String logMsg) {
System.out.println("Log: "+logMsg);
public void error(int errcode, Exception ex) {
String jversion = System.getProperty("java.version").substring(0,3);
String os = System.getProperty("os.name");
String excp = ex.toString();
// Driver not found in classpath
if(errcode == NO_DRIVER) {
String jarname = "classes12.jar";
String nlsjarname = "nls_charset12.jar";
if(jversion.equals("1.1")) {
jarname = "classes111.jar";
nlsjarname = "nls_charset11.jar";
else if(jversion.equals("1.4"))
jarname = "ojdbc14.jar";
System.out.println(" Error: JDBC Drivers not present in CLASSPATH ");
System.out.println("\n Your CLASSPATH is :"+System.getProperty("java.class.path"));
System.out.println("\n To add Oracle JDBC Drivers to CLASSPATH ");
// Windows
if(os.indexOf("Windows") != -1) {
System.out.println(" >set CLASSPATH=<path-to-"+jarname+">;<path-to-"+
nlsjarname+">;%CLASSPATH%;");
} else {
System.out.println(" $CLASSPATH=<path-to-"+jarname+">:<path-to-"+
nlsjarname+">:$CLASSPATH:");
System.out.println(" $export CLASSPATH");
System.out.println(" Oracle JDBC Drivers can be found in "+
"<ORACLE_HOME>/jdbc/lib directory or "+
"downloaded from http://otn.oracle.com/software/");
} else if (errcode == NULL_URL) {
System.out.println("Error: jdbc.url was not supplied");
System.out.println("Usage: java -Djdbc.url=jdbc:oracle:thin:@<hostname>:<port>:<db_sid> JDBCCheck ");
} else if (errcode == INVALID_URL) {
// Check if Invalid Database SID
if( excp.indexOf("ERR=12505") != -1)
System.out.println("Error: Invalid Database SID was specified in jdbc.url ");
System.out.println("Error: Invalid JDBC URL or DB Listener is down, refer to http://myjdbc.tripod.com/basic/jdbcurl.html ");
} else if (errcode == INVALID_CREDENTIALS) {
System.out.println("Error: Invalid username/password was specified ");
System.out.println("Try connecting to the database thru SQL Plus using the same username/password");
} else if (errcode == DATABASE_DOWN ) {
System.out.println("Error: The Database you are tying to Connect is down ");
System.out.println(" Start the Database and then try to connect ");
} else {
System.out.println("Error code not handled : "+errcode);
System.out.println("\nException Message :"+excp);
System.exit(0);
while running thig pgm, you should pass the driver URL..
java -Djdbc.url=jdbc:oracle:thin:@<hostname>:<port>:<db_sid> JDBCCheck

Jdbc. The Network Adapter could not establish the connection. Help Please!!

I've found several responses over this issue, but none works for me.
I'm trying to setup a simple jdbc connection from a simple program.
Platform:
Fedora Core 4 (FC4) on AMD 64 bits
Java 1.4.2_04 (64 bits)
ORacle 10g or Oracle 9.2.0.4 (none works);
Tips:
- I can't connect to a remote server, nor to a local server
- I can connect using SQLplus
- TNSPing works fine
- Listener it's up
- my connection string is jdbc:oracle:thin:user/name@host:port:sid
- Also try jdbc:oracle:thin:user/name@//host:port/sid
- I'v tryied with classes12.jar, odbj14.jar
- my hostname it's ok.
I've monitored ip traffic on remote computer. While using TNSPING I detect activity. While using jdbc, no.
Please, any idea??

Thanks for your reply.
To your questions:
- I´v tried both IP, host, and even host.domain
- I can connect from remote workstation using toad, and from local using sqlplus.
- I can´t connect via jdbc.
Folowing:
A) my sample code
B) the stack trace
C) the listener status (from my 9i server. Also tryied another servr with 10g)
when I call this program, I´ve tried severl connection strings:
jdbc:oracle:thin:user/pass@sdd51:1521:ebf
jdbc:oracle:thin:user/pass@:sdd51.sdd.com.ar:1521:ebf
jdbc:oracle:thin:user/pass@:10.10.10.51:1521:ebf
also try the other sintax:
jdbc:oracle:thin:user/pass@//sdd51:1521/ebf
In the classpath, I´tryied:
clasess12.jar
ojdbc14.jar
nls_charset12.jar
thanks
A)=================================================
// Import the JDBC classes
import java.sql.*;
import oracle.jdbc.pool.OracleDataSource;
import java.io.*;
import java.util.*;
public class test
// The query we will execute
static final String query = "select 'Hello JDBC: ' || sysdate from dual";
// The connection to the database
static Connection conn;
// Create the User Interface
static public void main (String args[])
try {
String connect_string = args[0];
 // See if we need to open the connection to the database
 if (conn == null)
// Create a OracleDataSource instance and set URL
OracleDataSource ods = new OracleDataSource();
ods.setURL(connect_string);
 // Connect to the databse
 System.out.println ("Connecting to " + connect_string + "\n");
 conn = ods.getConnection ();
 System.out.println ("Connected\n");
 // Create a statement
 Statement stmt = conn.createStatement ();
 // Execute the query
 System.out.println ("Executing query " + query + "\n");
 ResultSet rset = stmt.executeQuery (query);
 // Dump the result
 while (rset.next ())
 System.out.println (rset.getString (1) + "\n");
 // We're done
 System.out.println ("done.\n");
catch (Exception e)
e.printStackTrace();
 // Oops
 System.out.println (e.getMessage () + "\n");
B)=================================================
java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
 at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
 at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156)
 at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
 at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:212)
 at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:251)
 at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:224)
 at java.sql.DriverManager.getConnection(DriverManager.java:512)
 at java.sql.DriverManager.getConnection(DriverManager.java:171)
 at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:102)
 at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:85)
 at test.main(test.java:66)
C)=================================================
LSNRCTL for Linux: Version 9.2.0.1.0 - Production on 30-JAN-2006 17:39:59
Copyright (c) 1991, 2002, Oracle Corporation. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(PORT=1521))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 9.2.0.1.0 - Production
Start Date 24-JAN-2006 11:16:18
Uptime 6 days 6 hr. 23 min. 40 sec
Trace Level off
Security OFF
SNMP OFF
Listener Log File /opt/oracle/product/9.2.0/network/log/listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=sdd51.sdd.com.ar)(PORT=1521)))
Services Summary...
Service "ebf" has 1 instance(s).
Instance "ebf", status READY, has 1 handler(s) for this service...
The command completed successfully

SIOCSIFFLAGS: Unknown error 132, could not set interface eth1 UP. Help

After lots of trouble getting my wireless card working and installing the ipw2200-fw drivers to get it working i have encountered an other problem.
I set up a netcfg profile called mynetwork but now whenever i try to connect using netcfg mynetork, i get:
SIOCSIFFLAGS: Unknown error 132
Could not set interface 'eth1' UP
Being a noob I have no clue how to fix this. Anyone know how to make it work?

See this bug report for some clues:
https://bugs.archlinux.org/task/19507
Also, duck duck go/google is your friend: please search before posting...

Could not set Portal Connection properties

Similar Messages

Maybe you are looking for