Error while creating OLAP connection in IDT

Hi friends,
I am facing error while creating OLAP connection in IDT (BO 4.1 sp2)
I am using sql server 2012.In the screen shots you can observe server name and user name of the Sql server
I am creating OLAP connection to connect CUBE
Check the screen shots for the error
Plz help me
Here you can see the server name and user name
While creating OLAP connection I gave these credentials
This is the error I am getting

Hi..
To create connection and access the BW data, developer must have the password. and while create connection using Authentication Mode: Single Sign On, need to loin the username has pattern <SID~client/SAP userid>,
User Name: SID~client/SAP userid
Password for the SID,
Authentication as SAP.
Plese find the below link for more info: http://scn.sap.com/community/semantic-layer/blog/2014/06/19/pre-requisite-authorizations-in-sap-bw-side-before-develop-the-universe

Similar Messages

Unexpected Behavior error while creating a connection in IDT

Hi Everyone,
I have created a connection on top of a database using ODBC.
I could able to see the connection in IDT.
I have mentioned the user name and pw correctly and tried testing the connection and got the error "unexpected behavior"
PFA error.
what could be the reason? any idea?
Thanks.

I find this 32-bit vs. 64-bit ODBC somewhat confusing. I know you aren't dealing with Crystal Reports, but this blog post does provide some clarity. It has a link to this Microsoft knowledge base article from which I quote...
A 64-bit version of the Microsoft Windows operating system includes the following versions of the
Microsoft Open Database Connectivity (ODBC) Data Source Administrator tool (Odbcad32.exe):
The 32-bit version of the Odbcad32.exe file is located in the %systemdrive%\Windows\SysWoW64 folder.
The 64-bit version of the Odbcad32.exe file is located in the %systemdrive%\Windows\System32 folder.
One other warning. In my experience I have found that you cannot run both the 32-bit and 64-bit ODBC admin tools at the same time. If you have one running and try and start the other one it will just bring up the one you already had running.
To make sure I know which instance I am in at any give time I have created a dummy data source that corresponds to the instance; 32-bit or 64-bit.
Let us know how it goes.
Noel

SBO0001 error DBD:ORA12154 error while creating new connection

Dear All,
I have installed XIR3 on a windows 64 bit with oracle 10g R2 client.
The CMS is up and running and I am able to connect to the infoview and view the lsit of all the migrated objects from BOXIR2.
But, when I am trying to create a new connection for the universe or trying to execute the existing reports i am getting the following error.
(i.e I guess BO is unable to connect to DB)
*SBO0001 error DBD:ORA12154 error while creating new connection
I tried various solution from BOB but still could not solve this. Please anyone suggest few tips regarding this case
Business objects: CMS is running and able to connect to infoview and able to log on to CMC
Database client: Able to log on to DB using sqlplus and tnsping is working.
the details of the software are as follows
*BO Server configuration
OS: Windows Server 2008 R2 64 bit
Business Objects XI R3 3.0
Oracle client 10gR2 32 bit
*Database server configuration
Oracle 11g R2 64 bit
Thanks,
Mike

Mike :
I am having a similar issue with the BOE and Oracle.
Can you please provide details of which Oracle client you ended-up using..?
32-bit or 64-bit...?
Oracle client version...?
Specific client patches applied..?
Thanks,
Mark

Error while creating relational connection

HI Experts,
I used the Information Design Tool to create a relational conncetion to a SAP BW cube. Above this I created the data foundation and then the business layer (universe).
Creation of connection and universe works, but in the IDT when I click on "Test Connection" or in WebI when i want to create a report a get the following error:
[Data Federator Driver] [Server] [Connector 'testSourceConnection1400732899381'] An error occurred while trying to ping the server: java.lang.NullPointerException: while trying to invoke the method java.util.HashSet.contains(java.lang.Object) of an object loaded from field com.businessobjects.datafederator.wrappers.SapNWBI.JCOServer.JCOCallbackServer.registeredWrappers of an object loaded from local variable '<0>'.
Regards,
PRK.

Sorry Praveen,
I misunderstood the question i thought you are creating OLAP connection.
which is not the case and for relational connection you have to use IDT only.
with respect to your issue, error says issues is with connectivity.
Can you try to check that BW system is accessible from your local machine or your BO server.
Regards,
Priyank Bhayani

Error while creating jco connection for metadata?

Hi all,
we are using ep 6 sp 16.
I could create the JCO connection for application data but i am not able to create the jco connection for metadata for the same r3 server .
while creating the the connection
system name and logon group and disable
and when i click finish
it is giving following error
Failed to create new JCO client connection testmetadata: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for testmetadata at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:670) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:606) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:564) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:486) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:252) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:226) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:180) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanking.
Rajendra

Hello Rajendra,
Good to hear from u. Let me try to give a soln for this problem of yours.
I think probably the logon group has not been specified in the backend.If thats the case then do the following:
Connect to the backend server for which you are trying to create the JCO. Run the transaction SMLG. It will show u the existing logon groups. carry out the following steps if the 'PUBLIC' group is not present in the list of logon groups.
Click on the create button. In the pop-up, type the logon as 'PUBLIC'. For the instance, select the F4 help and choose the existing instance number. Click on copy and click save. Try running the transaction /nsmlg and now it should show the logon group 'PUBLIC'.
When you create the JCO connection, it should now show the logon group 'PUBLIC'.
Regards,
Prathamesh.

Error While Creating Informix Connection Pool

Hi,
I am trying to port an application from Weblogic 6.1 to Weblogic 8.1. The Application accesses Informix database. I used the following driver, url and properties while connecting to this database using Weblogic 6.1
url:->jdbc:weblogic:informix4:snss_live
Driver ClassName :-> weblogic.jdbc.informix.InformixDriver
Properties :->
port=22000
user=snssadmn
password=snssadmn
server=10.115.26.40
The above used to work fine with weblogic 6.1
With Weblogic 8.1, I am using the following properties
url :-> jdbc:bea:informix://10.115.26.40:22000;informixServer=10.115.26.40;databaseName=snss_live
Driver ClassName :-> weblogic.jdbc.informix.InformixDriver
Properties :->
informixServer=10.115.26.40
user=snssadmn
portNumber=22000
databaseName=snss_live
serverName=10.115.26.40
However using these properties I am getting the following error while deploying the Connection Pool to the Managed Server
<Dec 29, 2004 12:26:53 PM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "Btv_Vms_Pool": [BEA][Informix JDBC Driver][Informix]INFORMIXSERVER does not match either DBSERVERNAME or DBSERVERALIASES.>
<Dec 29, 2004 12:26:54 PM EST> <Error> <JDBC> <BEA-001150> <Connection Pool "Btv_Vms_Pool" deployment failed with the following error: 0:Could not create pool connection. The DBMS driver exception was: [BEA][Informix JDBC Driver][Informix]INFORMIXSERVER does not match either DBSERVERNAME or DBSERVERALIASES..>
Any idea as to why this is happening
Regards
Nitin Nair

Hi. I suspect that the databaseName property is causing the problem in
8.1. Remove it and see if that works. Also, try running:
java utils.dbping, and giving it the properties it asks for, for your
Informix connection. Once it succeeds in making a connection, it will
print out the URL and properties it used. Then define the pool with
those (and only those) properties and URL.
Joe
Nitin Nair wrote:
Hi,
I am trying to port an application from Weblogic 6.1 to Weblogic 8.1. The Application accesses Informix database. I used the following driver, url and properties while connecting to this database using Weblogic 6.1
url:->jdbc:weblogic:informix4:snss_live
Driver ClassName :-> weblogic.jdbc.informix.InformixDriver
Properties :->
port=22000
user=snssadmn
password=snssadmn
server=10.115.26.40
The above used to work fine with weblogic 6.1
With Weblogic 8.1, I am using the following properties
url :-> jdbc:bea:informix://10.115.26.40:22000;informixServer=10.115.26.40;databaseName=snss_live
Driver ClassName :-> weblogic.jdbc.informix.InformixDriver
Properties :->
informixServer=10.115.26.40
user=snssadmn
portNumber=22000
databaseName=snss_live
serverName=10.115.26.40
However using these properties I am getting the following error while deploying the Connection Pool to the Managed Server
<Dec 29, 2004 12:26:53 PM EST> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "Btv_Vms_Pool": [BEA][Informix JDBC Driver][Informix]INFORMIXSERVER does not match either DBSERVERNAME or DBSERVERALIASES.>
<Dec 29, 2004 12:26:54 PM EST> <Error> <JDBC> <BEA-001150> <Connection Pool "Btv_Vms_Pool" deployment failed with the following error: 0:Could not create pool connection. The DBMS driver exception was: [BEA][Informix JDBC Driver][Informix]INFORMIXSERVER does not match either DBSERVERNAME or DBSERVERALIASES..>
Any idea as to why this is happening
Regards
Nitin Nair

Error while creating JDBC connection pool for MSSQL database

Hi,
From my windows m/c, I am trying to configure a connection pool to connect to
an MSSQL database on another m/c. While setting the targets, i get the error :-
<Mar 11, 2004 6:17:52 PM GMT+08:00> <Error> <JDBC> <Cannot startup connection
pool "gcdb_connpool" Cannot load driver class: com.microsoft.jdbc.sqlserver.SQLServerDriver>
I have added the path of the jars for the driver in the classpath.
Any help would be appreciated.
Thanks.

Hi. Read the weblogic startup script, and follow how it creates
a classpath argument for the server. You must get the driver jars
into that classpath.
Joe
Neha wrote:
Hi,
From my windows m/c, I am trying to configure a connection pool to connect to
an MSSQL database on another m/c. While setting the targets, i get the error :-
<Mar 11, 2004 6:17:52 PM GMT+08:00> <Error> <JDBC> <Cannot startup connection
pool "gcdb_connpool" Cannot load driver class: com.microsoft.jdbc.sqlserver.SQLServerDriver>
I have added the path of the jars for the driver in the classpath.
Any help would be appreciated.
Thanks.

Urgent Error while creating UD Connect datasource

Hi Everyone,
I'm getting an error when trying to select the UD Connect Source Object.
I get error:
Errors occurred during extraction of existing UD Connect source objects: UDCADAPTERROR::RSSDK|100|Cannot open the connectio
Nº mensagem RSDS_ACCESS031.
If there is any good documnet on this issue please mail me to [email protected]
I would apreciate if anyone can help me in this issue. I Gurantee that I will appreciate it with points.
Best Regards
Baba.

Hi Michael,
Thanks a lot for your reply but I have already seen this link. I am working on UD connect for the first time but i have experience on DB connect. In DB connect we need to use same user name and pswd (used to access DB) for BI also while creating datasource is this the same concept with UD connect?. I have seen lots of posts on this issue in SDN but there are no replies. I don't know whether they solved or still they have issues? would you please send me a document related to this issue as in most of the posts they talk about a document on this issue to ID [email protected]
I have tested RFC connection in SM59 and also RFC destination name its in capital letters. Source system connection is also ok. while creating datasource in extraction tab i got stucked as I am unable to select UD source objects. If you can elaborate more on this thats really helpful, I apprecaite your time and help. I will definetely assign full points if it shows me some way to resolve this.
Regards
Satish Arra.

Error -While create a connection to Microsoft SQL Sever from Oracle SQL Dev

Dear All,
While I am trying to create a connection to Microsoft SQL Sever from Oracle SQL Developer. The following error: "Cannot connect to Microsoft SQL Server on localhost" has been occurred.
Can anyone please guide me to solve this..
Thanks in advance,
Rider

Hi,
Issue not supported in sharepoint on-premise team.
In addition, as this issue is related to Powerview, I suggest you create a new thread on for Powerview forum, more experts will assist you.
https://social.technet.microsoft.com/Forums/en-US/home?forum=powerview
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

SAP Design Studio ODBC Driver Not Found error while creating HANA connection.

Hi,
While creating SAP HANA ODBC connection in Design Studio via Tools > Preference > Application Design > Backend Connection. I am getting error ODBC Driver Not Found. Error screen shot is attached.
My Design Studio version is 1.3 win 32 bit
My OS Win 7 64 bit
I have installed both HANA client 32 bit and 64 bit.
I have tried creating DSN ODBC connection via "C:\Windows\SysWOW64\odbcad32.exe" and via Control Panel > Administrative tools > Data Sources(ODBC). But it does not detect it either.
I am not sure what needs to change to let Design Studio know which HANA client driver to use.
Please help!.

Hi Rohit,
This seems to be a known bug with Design Studio. Please see the SAP Note below on this.
1774480 - Fix launching of ODBC Data Source Administrator
Regards,
Abhijit

Error while creating a connection from JDeveloper to OC4J instance on 9iAS

I m trying to create a connection to the application server(9iAS release 2) from the JDeveloper(9.0.2.822) using the JDeveloper connection wizard. I followed all the steps, but when i click on "Test Connection" button to test the connection the error i get is "IO Error: Connection refused: connect". The description of the settings i provided in the wizard step are as follows,
Step 1
Connection name:- Connection1
Connection Type:- Oracle 9i Application Server
Step 2
Username:- admin
Password:- welcome
Deploy Password checkbox: Unchecked
Step 3 (the 9iAS server address is 192.168.30.162)
URL:- ormi://192.168.30.162/
Target Web Site:- http-web-site
Local dir where admin.jar is installed for Oracle 9iAS is installed:- C:\ora9i_d2k\j2ee\home
Step 4
Test Connection: “IO Error: Connection refused: connect”
Please advise.
Thanks
Unmesh

Hi,
You cannot connect to an Oracle9iAS environment directly using the connections node. You can only connect to an individual OC4J instance using this technique.
You need to use Oracle9iAS Distributed Management Configuration (DCM). See JDeveloper Help under Creating Application Server Connections

Error while creating a new connection in ODSM for OVD

Hi all,
I am getting the following error while creating a new connection in ODSM for OVD.
Error log:
[2012-07-10T14:50:30.005+05:30] [wls_ods1] [ERROR] [] [oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000JXkC9dU3FClqwsJb6G1FyhO000003D,0] [APP: odsm#11.1.1.2.0] Server Exception during PPR, #7[[
javax.servlet.ServletException: Could not initialize class com.octetstring.vde.admin.services.client.VDEAdminServiceSoapBindingStub
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:277)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.help.web.rich.OHWFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by:
=======
java.lang.NoClassDefFoundError: Could not initialize class
com.octetstring.vde.admin.services.client.VDEAdminServiceSoapBindingStub
at com.octetstring.vde.admin.services.client.ServerMgrServiceLocator.getVDEAdminService(ServerMgrServiceLocator.java:58)
at oracle.ldap.odsm.model.ovd.APServerProxy.connect(APServerProxy.java:248)
at oracle.ldap.odsm.model.ovd.APServerProxy.authenticateAs(APServerProxy.java:684)
at oracle.ldap.odsm.model.ovd.APServerProxy.authenticate(APServerProxy.java:286)
at oracle.ldap.odsm.model.ovd.APServerProxy.init(APServerProxy.java:216)
at oracle.ldap.odsm.model.ovd.APServerProxy.<init>(APServerProxy.java:198)
at oracle.ldap.odsm.model.ovd.OVDRoot.connectOVD(OVDRoot.java:185)
at oracle.ldap.odsm.ui.common.Connection.connect(Connection.java:120)
at oracle.ldap.odsm.ui.common.Visit.createConnection(Visit.java:663)
at oracle.ldap.odsm.ui.common.Login.saveChanges(Login.java:215)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.el.parser.AstValue.invoke(Unknown Source)
at com.sun.el.MethodExpressionImpl.invoke(Unknown Source)
at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:53)
at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1245)
at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:812)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:292)
at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
... 28 more
How to resolve this issue.Pls suggest me.
Regards,
-Deena.

Hi Deena,
This error:
"[2012-07-10T14:50:30.005+05:30] [wls_ods1] [ERROR] [] [oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator] [tid: [ACTIVE].ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 0000JXkC9dU3FClqwsJb6G1FyhO000003D,0] [APP: odsm#11.1.1.2.0] Server Exception during PPR, #7[[
javax.servlet.ServletException: Could not initialize class com.octetstring.vde.admin.services.client.VDEAdminServiceSoapBindingStub"
is known issue
Go to metalink, article: Unable To Connect To OVD 11g Webinterface Using ODSM. [ID 1282757.1]
You need to apply that patch.
I hope this helps,
Thiago Leoncio.

Error while obtaining JCO connection when creating JCO connection

Hey,
im having a problem when creating a JCO connection in the Web Dynpro Content Administrator. Creating the Modeldata (Application Data Data type) JCO Worked but when creating the JCO for the RFC Metadata (Dictionary Meta data) there is a problem:
In step 3.2 Msg server connection I cannot specify a system name and logon group, only the message server can be selected with the dropdown box.
After pushing the finish button i get the following stacktrace:
Failed to create new JCO client connection WD_RFC_METADATA_DEST: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection. at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:150) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection(SystemLandscapeFactory.java:356) at
com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at
com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish(ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:265) at
com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at
com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67) at
com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101) at
com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304) at
com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649) at
com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at
com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at
com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at
com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at
com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at
com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at
com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at
com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at
com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at
java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95) at
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_RFC_METADATA_DEST at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:664) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508) at
com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:248) at
com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:222) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101) at
com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:148) ... 30 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:558) ... 35 more
We are running WebAS 640 SP 14 on Unix.
Greetings,
Hannes
Message was edited by: Hannes Defloo

Hi
Please configure your SLD. Your SLD holds the system definition. Define a SAP WebAS abap system and then try to create a Metadata connection using WebDynpro content administrator. Now you will be able to see the msg server defined in the dropdown. Also ensure that you have the message server entry in your services file.
Refer these links for SLD
http://help.sap.com/saphelp_nw04/helpdata/en/c9/dc37520bdf4b48bb8f6d4329f073d5/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/24/8fa93e08503614e10000000a114084/content.htm
Hope that helps.
regards
Ravi

I get a error (about MDAS server) when studying create olap connection on cmc.

Hi,
I get a error when studying create olap connection on CMC. Why are u?
Kind regards.
Fatih Temiz

Hi,
please set your language to english and re- create the error.
Afterwards posta new screenshot in english.
Regards
-Seb.

Getting Connection error while creating Substituion Rule in UWL

Hi Everybody,
Getting below error while creating Substitution Rules in UWL.
"error for the u201Cconnectionu201D to SAP_R3_Finance ".
Can be able to see all Work Items belongs to me. getting the errror while creating Substitution Rule only..
Could anybody tell me what might be the Reason what steps i need to take to resolve this issue.
Thanks,
Naveen Kumar

Hi Uds,
are you running SOA Suite on a Linux server and not on your PC and just running JDeveloper on your PC?
If so try creating the repository file specifying a directory on the Linux server.
For example to:
/tmp/sample_repository
So Choose 'File' from drop down menu
Enter /tmp/sample_repository
Click on create button
This should create the file called sample_repository in /tmp on the Linux server.
Can you tell us what your environment is?
Regards Cel

Error while creating OLAP connection in IDT

Similar Messages

Maybe you are looking for