JCo connection broke after deployment

At this moment we do not have setup the JDI environment (we are busy with it). When we do a deploy of Java WD with EAR files through SDM or we do it via NWDS our JCo connection is broken every time.
Initially we have set the JCo connections to 'ticket' but after we make changes to a WD and deploy it via SDM or NWDS the JCo connection is set back to UID/PW. Does anybody have any idea why this happens?
Kind regards,
Dave Arends

Hi Dave,
The configuration for JCO as JCO destinations is done on the content administrator and is independent of the application itself. So I dont understand deploying the application interferes with JCO.
Regards,
Arun

Similar Messages

Problem in Connection pooling after deploying BC4J App Module as EJB

Hi,
We have deployed the application modules on standalone OC4J as stateful EJB session beans.
The problem is that with each user, the number of database connections seem to increase. This is making the application unscalable, which defeats the purpose of using EJB!
Can someone please suggest how to limit the number of database conections in this scenario?
Can this be solved by application module pooling? How can we use the PoolMgr to work with the session beans?
We have tried to invoke disconnect on the application module after calling methods(using appmodule.disconnect(true)) and reconnect (appmodule.reconnect()) on entering the method. This keeps the number of connections low and works the first time the method is invoked. But subsequently, it gives nullpointerexception when the Row is accessed in the JSP.
The exception we are getting is :
java.lang.NullPointerException
     at oracle.jbo.client.remote.ViewUsageImpl.getStructDef(ViewUsageImpl.java:241)
     at oracle.jbo.client.remote.ViewUsageImpl.findAttributeDef(ViewUsageImpl.java:275)
     at oracle.jbo.client.remote.RowImpl.getAttributeIndexOf(RowImpl.java:368)
     at oracle.jbo.client.remote.RowImpl.getAttribute(RowImpl.java:144)
     at Supplier.client.ejb.beanmanaged.SupplierAM_IntPaymtVORowBeanManagedClient.getMdid(SupplierAM_IntPaymtVORowBeanManagedClient.java:63)
     at supplier.sccPayCheq._jspService(_sccPayCheq.java:102)
     [SRC:/Supplier/sccPayCheq.jsp:44]
The Application module configuration (in bc4j.xcfg) is:
<AppModuleConfig name="SupplierAM9iAS">
<AppServerConnectionName>StandaloneOC4JConnection</AppServerConnectionName>
<AppModuleJndiName>Supplier.SupplierAM</AppModuleJndiName>
<java.naming.security.credentials>admin</java.naming.security.credentials>
<DeployPlatform>EjbIas</DeployPlatform>
<java.naming.security.principal>admin</java.naming.security.principal>
<DtMiddleTierDeploymentProfile>ProjectMiddleTier.deploy</DtMiddleTierDeploymentProfile>
<ApplicationName>Supplier.SupplierAM</ApplicationName>
<DtDeploymentProfile>ProjectEJB.deploy</DtDeploymentProfile>
<DtCommonDeploymentProfile>ProjectCommon.deploy</DtCommonDeploymentProfile>
<JDBCDataSource>jdbc/ConnectionCoreDS</JDBCDataSource>
<jbo.server.internal_connection>jdbc/ConnectionCoreDS</jbo.server.internal_connection>
<jbo.ejb.txntype>local</jbo.ejb.txntype>
<jbo.doconnectionpooling>true</jbo.doconnectionpooling>
<ApplicationPath>ProjectEJB</ApplicationPath>
</AppModuleConfig>
The Datasource used (in $ORACLE_HOME/j2ee/home/config/data-sources.xml) is:
<data-source
          class="oracle.jdbc.pool.OracleConnectionCacheImpl"           connection-driver="oracle.jdbc.driver.OracleDriver"
          ejb-location="jdbc/ConnectionDS"
          inactivity-timeout="30"
          location="jdbc/ConnectionCoreDS"
          name="ConnectionDS"
          password="*******"
          pooled-location="jdbc/ConnectionPooledDS"
          url="jdbc:oracle:thin:@<IPADDESS>:<SID>"
          username="USER"
          xa-location="jdbc/xa/ConnectionXADS"
          max-connections="5"
          min-connections="1"/>

Can this be solved by application module pooling? How
can we use the PoolMgr to work with the session
beans?You can use a stateless checkout/checkin appmodule.
Take a look at the following help topics which explain this in good detail.
"About Application Module Pooling"
"About JSP Pages and Application Module Pooling"
The pool can help reuse the appmodule instance across requests thus reducing the number of concurrent db sessions.
Dhiraj

Connection failure after deploying to 10.1.3 app server

I am working on a three-tier application that uses session EJB facades and TopLink for persistence. I configured a datasource in the embedded OC4J server preferences in JDeveloper (10.1.3) and can successfully deploy my persistence code to the embedded server and access it from a test client.
I recently installed Oracle App Server 10g 10.1.3 to be used for integration testing. In JDeveloper, I configured a new application server connection and EJB Jar deployment profile to allow me to deploy my persistence code to the new server. When I deploy my code to the server and attempt to use one of the session EJB persistence methods, I get the following exception message:
Internal Exception: java.sql.SQLException: javax.resource.spi.ApplicationServerInternalException: Unable to create a connection. Connection factory has been stopped.Error Code: 0
In the Oracle Enterprise Manager, my application is running and the datasource and connection pool test successfully.
If I restart OC4J from Oracle Enterprise Manager, my application works correctly, at least until I have to deploy new code to the server, at which time the above error reappears. My question: Should OC4J have to be restarted each time new code is deployed? I am not making any changes to the datasource or connection pool configurations. Thanks.

Thanks Jaap.
I was told recently by someone at Oracle that Forms/Reports is supported on 10.1.3.x and eventually on 11g (not yet released), and I was also told 10.1.3 doesn't require two servers, but I'm having trouble finding much to support either claim.
Reason I'm asking is that we're currently using the client/server Forms/Reports and need to decide on a migration path and l don't know if it's wise to continue with the 10.1.2 App Server knowing it's going to be de-supported in a few short years and I don't want to go with 10.1.3 if it requires additional servers (we're small). We're looking at APEX as a possible alternative...
Tim

OBIEE 11g database connection error after deploying to server.

Hi,
I deployed RPD to obiee 11g server and when I run a report it is giving database connectivity error. In 10g we just specify OLAP_DSN, OLAP_USER and same in connection pool with database password. I did the same in 11g as well but it's not working.
Is there any other place I need to specify database connection detail?
Thanks
Jay.

coming with different names :) If you respond to your older threads will happy to respond you.
When we answer your question we love to know how it helped you. we are not asking your $$$$$$$$$$$$$

WiFi connection broke after upgrading to IOS 6.0

My WiFi connection stopped working after upgrading to IOS 6.0 on bothe iPhone 4 and iPad 3.
I reset the Network connection - no change.
I selected "Forget Network" and tried to rejoin - no luck.

You are not addressing Apple here. We are just users like yourself.
Does the iPod connect to other networks?
Does the iPod see the network?
Any error messages?
Do other devices now connect?
Try:
- Reset the iOS device. Nothing will be lost
Reset iOS device: Hold down the On/Off button and the Home button at the same time for at
least ten seconds, until the Apple logo appears.
- Power off and then back on the router
- Reset network settings: Settings>General>Reset>Reset Network Settings
- iOS: Troubleshooting Wi-Fi networks and connections
- iOS: Recommended settings for Wi-Fi routers and access points
- Restore from backup. See:
iOS: How to back up
- Restore to factory settings/new iOS device.
iOS: How to back up your data and set up as a new device
- Make an appointment at the Genius Bar of an Apple store.
Apple Retail Store - Genius Bar

Finding component that does not close JCO connections

Hi,
I'm working on a big project with many webdynpro components. My problem is that I seem to be loosing JCO connections. After a while I get JCO connection errors. I just can't find which component is causing this. I checked over and over again.
Is there a way to check how many JCO connections an application/component has or at least how many open connections a model has?
I really need to know which component is causing my loss of JCO connections.
Thanks all!
Jeschael

Hi Jeschael,
Go to System Administration -> System Configuration -> Select Web Dynpro Console -> (Model & backend- You can check JCo performance by component) or ( JCo Connection Pools you can check max. calls and active connections for JCos)
Regards,
Siva

JCO - Connection reset by peer - after 5 minute timeout

Hello
We're using SUP with the JCO Connector. This has been working flawlessly since project inception. Now, after switching to a new data center (Windows Server 2008 Server Enterprise Edition, SP2 on VMWare) we're observing a mysterious behavior with timeouts of idle connections. I hope someone in this forum knows what this might be.
JCO connections originate from SUP servers. When such connections are idle for more than 5 minutes they get disconnected from SAP -- this is in agreement with SAP timeout parameter of 300 seconds.
On our new systems we noticed that requests sent 5min+ (after timeout) show following error:
Thread-8 [22:08:55:343]: [JNI-LAYER] RFC.nativeExecute() before RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeExecute() after RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88) = RFC_SYS_EXCEPTION
Thread-8 [22:08:55:344]: [JAV-LAYER] JCO.Client.execute (Z_U_ONEMOBILE_SWO_SEARCH) threw a NON-ABAP exception: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: CPIC-CALL: 'CMRCV : rc=20
ERROR       connection to partner '---removed!---:3299'
            broken
TIME        Fri Feb 11 18:08:55 201
RELEASE     710
COMPONENT   NI (network interface)
VERSION     39
RC          -6
MODULE      nixxi.cpp
LINE        4448
DETAIL      NiIWrite: P=161.88.23.170:3299; L=0.0.0.0:49730
SYSTEM CALL WSASend
ERRNO       10054
ERRNO TEXT WSAECONNRESET: Connection reset by peer
COUNTER     3
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                                       enter, [SUCCESS]
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() before RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() after RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                   with rc = RFC_OK   leave, [SUCCESS]
Our suspicion is that the JCO client doesn't notice the fact that it gets disconnected. We used Network Monitor 3.4 to look at network traffic. Indeed, after 5 minutes the client gets a single frame (with reset flag) and no acknowledgement goes back.
What could this be?
We use
JCO 2.1.8 AMD 64-bit (contains librfc 6.40) and
JCO 2.1.9 AMD 64-bit (contains librfc 6.40) but replaced this with librfc 7.10 (after seeing Note 825494). Behavior was exactly the same. We did confirm in jco/rfc trace that those versions were actually used.
Any ideas?
Thanks and regards
Edited by: B. Gottipati on Feb 14, 2011 9:17 PM

Hello
We're using SUP with the JCO Connector. This has been working flawlessly since project inception. Now, after switching to a new data center (Windows Server 2008 Server Enterprise Edition, SP2 on VMWare) we're observing a mysterious behavior with timeouts of idle connections. I hope someone in this forum knows what this might be.
JCO connections originate from SUP servers. When such connections are idle for more than 5 minutes they get disconnected from SAP -- this is in agreement with SAP timeout parameter of 300 seconds.
On our new systems we noticed that requests sent 5min+ (after timeout) show following error:
Thread-8 [22:08:55:343]: [JNI-LAYER] RFC.nativeExecute() before RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeExecute() after RfcCallReceive(2,"Z_U_ONEMOBILE_SWO_SEARCH",0000000010CDC850,0000000000000000,0000000010C81530,000000000C79CA88) = RFC_SYS_EXCEPTION
Thread-8 [22:08:55:344]: [JAV-LAYER] JCO.Client.execute (Z_U_ONEMOBILE_SWO_SEARCH) threw a NON-ABAP exception: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: CPIC-CALL: 'CMRCV : rc=20
ERROR       connection to partner '---removed!---:3299'
            broken
TIME        Fri Feb 11 18:08:55 201
RELEASE     710
COMPONENT   NI (network interface)
VERSION     39
RC          -6
MODULE      nixxi.cpp
LINE        4448
DETAIL      NiIWrite: P=161.88.23.170:3299; L=0.0.0.0:49730
SYSTEM CALL WSASend
ERRNO       10054
ERRNO TEXT WSAECONNRESET: Connection reset by peer
COUNTER     3
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                                       enter, [SUCCESS]
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() before RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect() after RfcClose(2)
Thread-8 [22:08:55:344]: [JNI-LAYER] RFC.nativeDisconnect()                   with rc = RFC_OK   leave, [SUCCESS]
Our suspicion is that the JCO client doesn't notice the fact that it gets disconnected. We used Network Monitor 3.4 to look at network traffic. Indeed, after 5 minutes the client gets a single frame (with reset flag) and no acknowledgement goes back.
What could this be?
We use
JCO 2.1.8 AMD 64-bit (contains librfc 6.40) and
JCO 2.1.9 AMD 64-bit (contains librfc 6.40) but replaced this with librfc 7.10 (after seeing Note 825494). Behavior was exactly the same. We did confirm in jco/rfc trace that those versions were actually used.
Any ideas?
Thanks and regards
Edited by: B. Gottipati on Feb 14, 2011 9:17 PM

JCo Connection using file.properties doesn't work when deployed

Hello Experts,
I'm trying to connect to a SAP backend system using the JCo connection.
I've tyed with the standard connection, crating dinamically the connection and it works fine:
mConnection = JCO.createClient("001", // SAP client
"sap.user", // userid
"********", // password
"IT", // language
"ashost.domain.dom", // application server host name
"06"); // system number
mConnection.connect();
Then I tryed to store the login data in a file 'login.properties' put in the same package of my connection classes.
The code is:
String[] logonStr = new String[5];
Properties properties = new Properties();
try {
InputStream is = getClass().getResourceAsStream("login.properties");
properties.load(is);
} catch (Exception e) {
e.printStackTrace();
logonStr[0] = PropertyManager.getProperty(applicationProperties,"jco.client.client");
logonStr[1] = PropertyManager.getProperty(applicationProperties,"jco.client.user");
logonStr[2] = PropertyManager.getProperty(applicationProperties,"jco.client.passwd");
logonStr[3] = PropertyManager.getProperty(applicationProperties,"jco.client.ashost");
logonStr[4] = PropertyManager.getProperty(applicationProperties,"jco.client.sysnr");
mConnection = JCO.createClient(logonStr[0],      // SAP client
logonStr[1],    // userid
logonStr[2],    // password
"IT",           // language
logonStr[3],    // application server host name
logonStr[4]);   // system number
If I test locally this code it works fine and the login datas are extracted from the 'login.properties' file.
But when I deploy my PAR file in the Portal seems that the 'login.properties' file isn't found by my application...
Which could be the cause??
Could it be a permission problem??
Any Ideas?
Thanks in Advance,
Best Regards

Hi Shyam,
Thanks for your answer!
I could use the string "ashost.domain.dom" instead to extract it from the 'login.properties' but I need also the others login info as username and password.
My problem is that the 'login.properties' file is not found by my application when the PAR file is deployed in the portal...
I need to know if I need to move the 'login.properties' file in another package or something else...
Any ideas??
Have I to declare the .properties file in some configuration file (for example portalapp.xml or somthing similar..) ??
Best Regards...

Why I cannot connect to database after deploying application to OAS?

Hello experts...i have a new problem and here are the facts:
I`m using on Windows Xp:
Oracle Database 10.2.0
Oracle Application Server 10.1.3
Oracle Jdeveloper 10.1.3.3
I`m creating a new application using jdeveloper and i`m using 2 connection classes:
a) First connection class using:
InitialContext ctx=new InitialContext();
DataSource ds=ctx.lookup("jdbc/connDS");
Connection conn=ds.getConnection();
b) Second connection class using:
Connection conn = DriverManager.getConnection("jdbc:and the entire link goes here");
So far so good, but when I create a ear file using the First connection class and after i deploy it to OAS my application will not connect anymore to database!
If I will use the Second connection class, and create an ear file then deploy it to OAS, my application works fine, it connects to database but i have a problem. In my application users can upload and download the files they uploaded. The files are saved in DB as blob. The problem appears when users are downloading the files because for example file "example.doc" is uploaded on the server database and when a user try to download it the name of the file is like "example_doc" and my pc open it like an html in which is a server 500 error. Someone told me that happens because of my connection class... and I want to find out you`re opinion.
Why i cann`t connect to DB after deploy the application on OAS using the FIRST connection class?
- on Jdeveloper i can connect to DB using both of the connect classes (one at a time)
- I`m creating a war file from jdeveloper and deploy the ear file on the OAS
- on OAS i`ve created the connection pool and the data source and "The connection was establish succesfully"
Why the uploaded files are downloaded in this way? it`s the connection the problem?
- I want to tell you that when i`m extracting data from the DB table i`m not using a temp file, the conversion is made in the java class and the program throws me the file to download.
- as i told you in Jdeveloper both of the connection classes work!!! and when i`m using the FIRST connection class and try to download, the files ARE DOWNLOADED PERFECTLY CORRECT!
- if i`m using the SECOND connection class in jdeveloper, running the application on the built in oc4j instance and trying to download the same files, the files are DOWNLOADED BAD like I told you: the name of the file is like "example_doc" and my pc open it like an html in which is a server 500 error. with the pdf format is the same problem but my pc cannot open it telling something with "bad conversion...." error.
There are someone who had the same problem?
Theoretically i had to make the application to connect to the database after deploy it to OAS with the FIRST connection class and this way my files will be downloaded corectly... what to do?

no one knows nothing about this issue? :(... i`m dissapointed...

"Closed Connection" occurs too much After deployment on WebSphere

"oracle.adf.controller.faces.lifecycle.Utils buildFacesMessage ADF: Adding the following JSF error message: Closed Connection
java.sql.SQLRecoverableException: Closed Connection"
"Closed Connection" message appears to the user too much after deploying on Websphere. How to disable this message.

FYI, I followed the steps listed in Administrator's Guide for Oracle Application Development Framework
at http://docs.oracle.com/cd/E35521_01/admin.111230/e16179/monitor.htm#CHDEGIAH
and that resolved my Closed Connection issue.
3.8.1 How to Configure WebSphere to Allow Reuse of Query Result Sets
WebSphere Application Server closes shared database connections between application generated requests. You need to set two properties in WebSphere to allow reuse of result sets.
Use the WebSphere Application Server administrative console to set the non-transactional datasource and DisableMultiThreadedServletConnectionMgmt properties.
To set properties in WebSphere to reuse results sets:
Start WebSphere Application Server administrative console.
Navigate to Data sources > DB2 Universal JDBC Driver XA DataSource > WebSphere Application Server data source properties and set Non-transactional data source to enabled.
Save the configuration.
Navigate to Application servers > server_name > Web Container > Custom Properties and set DisableMultiThreadedServletConnectionMgmt to true.
Save the configuration.
Restart WebSphere Application Server.
Setting these two properties will enable your deployed application to reuse result sets across requests.

Server 2012 RTM Remote Desktop Connection Broker Role Won't Install

Hey guys,
I have been searching for and trying fixes for this for 3 days, and I've gotten no where. Thanks in advance for trying to help me out.
Here's the situation:
I have a brand new installation of the Windows Server 2012 Datacenter 64-Bit RTM from MSDN. This is my one and only server (just my personal one for home), so I'm using this single server to run all of the services that I need. After a fresh
installation, I added the AD and DNS roles and promoted the server to the PDC. Then I go to add the Remote Desktop Virtualization Services (the VM virtualization role). The installation fails, but I can't find any explanation as to why.
I've wiped out the OS and reinstalled from scratch at leat 15 times, trying various combinations, fixes, approaches, etc. including powershell, Remote Desktop Services Deployment, standard role-based deployment, etc.
Using the role-based deployment, I can get every 'Remote Desktop Services' component to install except the Remote Desktop Connection Broker. I've tried enabling RDMSUI_TRACING, but didn't get any information at all as to why it's failing. I also
cannot find RDMSDeploymentUI.txt log.
I've also tried to deploy this using Powershell using this command:
New-SessionDeployment [-ConnectionBroker] <string> [-WebAccessServer] <string> [-SessionHost] <string>
That particular item does provide some error messages, but they seem to complain about the Session Host not being able to install due to not being able to find the connection string key in the registry for the Windows Internal Database. However, I can
get the session host and every other component to install using role-based deployment, except the Connection Broker.
I've run an SFC scan, which found no issues. I've also tried applying the one update available in Microsoft Update, and tried it without applying that update (reinstalling between attempts of course).
I'm completely at a loss. Has anyone encountered this before? Any suggestions would be greatly appreciated. Is there a powershell command for just installing the Connection Broker that might provide some additional error information, or any
information at all?
I would greatly appreciate any help anyone could offer. I'm willing to try anything. Thanks for taking the time to read this.
Sincerely,
Dominick

Also Found this:
1. You try to install the Remote Desktop Connection Broker (RDCB) on a server that also has the Active Directory Domain Server (domain
controller) role installed. This configuration is not supported by Microsoft. You need to install the RDCB on a server that does not have this role installed. See: Remote Desktop Services role cannot co-exist with AD DS role on Windows Server 2012 http://support.microsoft.com/kb/2799605
2. If you don’t have the Active Directory Domain Service install, this issue might be caused by the Windows internal database (WID) that
the connection broker installs and the Windows Update KB2821895. If you have KB2821895 installed, unfortunately you can not uninstall this KB. Try to install the Remote Desktop Connection Broker (RDBC) role on a server that does not have this Windows update.
Note: There is currently no official communication from Microsoft that here is an issue with RDBC and KB2821895. However, try the RDBC installation
without this KB and see what happens.
For more information, Refer below link...
http://fabrikam.wordpress.com/2013/07/15/connection-broker-installation-failedremote-desktop-deployment-issues/

Connect RD Connection Broker to SQL

Hello I'm not being able to install RD Connection Broker with High Availability.
The RDS deployment consists on two servers running win2012
server1 - RDWA and RDG
server2 - RDSH and RDCB
The SQL server 2012 that I'm using is installed on server2 itself and had to be installed after the RDS otherwise the SQL installation failed and had to be done using the RD-install. It's working fine , I've applications that run on it.
As when configuring RDCB HA "both" RDCB hosts access directly to the SQL DB to create a new database, their accounts need to be authenticated as a SQL login with dbcreator role.
1 step: I checked a straight forward installation_
Installing and Configuring RD Connection Broker High Availability in Windows Server 2012
Failed
2 step: I checked an installation where my problem happened.
I checked RD Connection Broker HA – SQL Permissions
Added the host to a domain group and added the group as an SQL login, SQL authentication failed.
4 step: Google for how to create SQL login for a computer account and I added it by executing:
“CREATE LOGIN [MyDomain\MyComputer$]
FROM WINDOWS”
Also tried to use Add-ADcomputerServiceAccount without success.
3 step: I ended here
Taking a closer look at RD Connection Broker High Availability in Windows
Server 2012
Where I verified that none of the following explanations were correct:
The SQL Server Native client is not installed
A firewall is blocking SQL Access from the RD Connection Broker (port 1433)
The incorrect SQL Server Native Client version is specified
An incorrect SQL Server name is specified
I tried several variations of the string to use but this is the one I think it's correct:
DRIVER=SQL Server Native Client 11.0;SERVER=WIN2012-1;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;Database=RDCB
The error registered on SQL is:
"Message
Login failed for user 'RDS\WIN2012-1$'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]"
I tried to connect via ODBC with an existing username an it succeeded.
The problem seems to be with the computer account not existing as an SQL login...the thing is that it exists.
I need to set this up in order to be able to change the RDCB FQDN to a public FQDN.
How were you guys able to overcome this? Did you faced this at all?
Thanks,
David

Guys,
I suffered with a very similar problem when setting up an RDS 2012 environment using SQL Server 2014 sitting on a server core VM, and two connection brokers sitting on server core OS as well.
My SQL logs were filling with with login failed for the connection brokers computer account even though I had configured the SQL permissions correctly.
In the end it was Arjan's post above that got me fixed, rebooting the connection broker VMs. Really annoying, as I let AD propagate over night, just in case that was the issue. After simply rebooting the connection brokers, this worked. For anyone who needs
it, my SQL databases are stored on a separate D: drive and I used the string below:
DRIVER=SQL Server Native Client 11.0;SERVER=<SQL Server Name>;Trusted_Connection=Yes;APP=Remote Desktop Services Connection Broker;DATABASE=<DB Name>.
Hope this helps someone else.

Error after deploying the application in PI java system

Hi all,
I have created a test web dynpro java application and deployed in PI7.1 java engine. Using the JCO's maintained i hav connected to ECC7.1 system and created a model to call a bapi. After deploying and running the application, I got the following error. Please let me know the solution
Regards
Sagar
    500   Internal Server Error SAP NetWeaver Application Server/Java AS
The initial exception that caused the request to fail, was:
java.lang.NullPointerException
    at com.sap.conn.jco.rt.DefaultDestinationManager.checkProperties(DefaultDestinationManager.java:405)
    at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:142)
    at com.sap.conn.jco.rt.DefaultDestinationManager.searchDestination(DefaultDestinationManager.java:292)
    at com.sap.conn.jco.rt.DefaultDestinationManager.getDestinationInstance(DefaultDestinationManager.java:90)
    at com.sap.conn.jco.JCoDestinationManager.getDestination(JCoDestinationManager.java:61)
    ... 82 more
See full exception chain for details.
Failed to process request. Please contact your system administrator.
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; GTB6.3)
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Java Applets enabled
Accessibility mode disabled
Rendering engine: Lightspeed
Inline CSS: enabled
Validate by rendering: enabled
Server
Web Dynpro Runtime vendor: 'sap.com', name: 'tc/wd/webdynpro', location: 'SAP AG', counter: '7.1100.20081021173332.0000', change number: '28470', codeline: NW711_00_REL
J2EE Engine 7.11.3710.27866.20080910102732
System ID (SID) PID
Server Node ID |1698650|16986|Server 00 00_16986|sappidev01.xtium.com/10.255.30.89|SERVER|RUNNING
Java VM SAP Java 64-Bit Server VM, version:5.1.027, vendor: SAP AG
Operating system Windows 2003, version: 5.2, architecture: amd64
Application
Java EE Application (deployable object) demo.sap.com/pegatest
Web Dynpro Application Pegatestappli
Request URI /webdynpro/dispatcher/demo.sap.com/pegatest/Pegatestappli
Version vendor: 'demo.sap.com', name: 'pegatest', location: 'localDevelopment', counter: '20100112141118', change number: 'null'
Session & Other
Session Locale en_US
Session Timezone Pacific Standard Time
Time of Failure Tue Jan 12 00:39:45 PST 2010 (Java Time: 1263285585307)
Session User ClientUser(id=USER.R3_DATASOURCE.J2EE_ADMIN, name=J2EE_ADMIN)
Client Session Id bxuvisJvMVwF2Jn5_M0-ODXALydDRLAhJgFa6xkA_SAP
Client Window Id 09190ac2ff5611dea2480050568315be
Application Session Id 09190ac3ff5611dea70e0050568315be
Web Dynpro Code Generation Infos
demo.sap.com/pegatest
Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session ApplicationSession(id=09190ac3ff5611dea70e0050568315be, name=com.sap.demo.pegatest.pegatestappli.Pegatestappli). The causing exception is nested. RID=09190ac0ff5611deb9b80050568315be
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:680)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:239)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:258)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:457)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:250)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Caused by: com.sap.tc.webdynpro.progmodel.context.DictionaryException: InvocationTargetException
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getDataType(DictionaryHandler.java:192)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:434)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:978)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:294)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:950)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:954)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:69)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:205)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:552)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1296)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToApplicationDoPreprocessing(AbstractExecutionContextDispatcher.java:146)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForAppPreprocessing.doService(DispatchHandlerForAppPreprocessing.java:35)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToApplicationDoPreprocessing(ExecutionContextDispatcher.java:100)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:74)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:571)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.dispatch(ApplicationSession.java:602)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:252)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:677)
... 48 more
Caused by: com.sap.dictionary.runtime.DdException: InvocationTargetException
at com.sap.dictionary.runtime.ProviderFactory4J7.getProvider(ProviderFactory4J7.java:36)
at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:96)
at com.sap.dictionary.runtime.DdDictionaryPool.makeDictionary(DdDictionaryPool.java:75)
at com.sap.dictionary.runtime.DdDictionaryPool.makeDictionary(DdDictionaryPool.java:63)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:224)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler._getScalarType(DictionaryHandler.java:462)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getDataType(DictionaryHandler.java:171)
... 67 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at com.sap.dictionary.runtime.ProviderFactory4J7.getProvider(ProviderFactory4J7.java:21)
... 73 more
Caused by: com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination DEV_ECC6_220_METADATA does not exist
at com.sap.mdi.jco7.Factory.makeException(Factory.java:41)
at com.sap.mdi.jco7.Destination.<init>(Destination.java:35)
at com.sap.mdi.jco7.Destination.make(Destination.java:21)
at com.sap.mdi.jco7.Factory.getDestination(Factory.java:28)
at com.sap.dictionary.runtime.mdi.DataProvider.<init>(DataProvider.java:115)
... 78 more
Caused by: com.sap.conn.jco.JCoException: (106) JCO_ERROR_RESOURCE: Destination DEV_ECC6_220_METADATA does not exist
at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:163)
at com.sap.conn.jco.rt.DefaultDestinationManager.searchDestination(DefaultDestinationManager.java:292)
at com.sap.conn.jco.rt.DefaultDestinationManager.getDestinationInstance(DefaultDestinationManager.java:90)
at com.sap.conn.jco.JCoDestinationManager.getDestination(JCoDestinationManager.java:61)
at com.sap.mdi.jco7.Destination.<init>(Destination.java:32)
... 81 more
Caused by: java.lang.NullPointerException
at com.sap.conn.jco.rt.DefaultDestinationManager.checkProperties(DefaultDestinationManager.java:405)
at com.sap.conn.jco.rt.DefaultDestinationManager.update(DefaultDestinationManager.java:142)
... 85 more

yes, you are getting Cross Origin Problem .So, you need to disable the web security for chrome.
Go to properties of chrome , and add this after path of chrome.
--disable-web-security
After this restart the chrome.
Please follow the below link for reference.
windows - Is it possible to run Chrome with and without web security at the same time? - Super User
Regards
Sridevi

Can't create JCO connection in Portal7 for ESS1.0

Hi,
I am in the Process of setting up ESS/MSS Rel 1.0 in Portal 7. The Portal is a WebAS ABAP+JAVA system.
First step after installing Portal, I configured the SLD and created the Technical systems. The sld is running and I have tested the sld from the Content Administrator->WebDynpro-> check SLD. It results sld successfully tested and I am able to start the sld also.
After that I deployed the Business packages for ESS/MSS and selfservices via SDM.
Now I am trying to create the JCO connection in the Content Administrator->WebDynpro->create/maintain JCO Connections, it throws the following error
500   Internal Server Error
Web Dynpro Container/SAP J2EE Engine/6.40
Failed to process request. Please contact your system administrator.
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
   java.lang.NullPointerException
    at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
    at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
    at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
    ... 45 more
See full exception chain for details.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Version null
DOM version null
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, build ID: 7.0009.20060804145649.0000 (release=645_VAL_REL, buildtime=2006-08-26:14:41:58[UTC], changelist=413534, host=pwdfm101), build date: Fri Aug 31 20:55:03 GMT+08:00 2007
J2EE Engine 7.00 patchlevel
Java VM Java HotSpot(TM) Server VM, version:1.4.2_15-b02, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Session & Other
Session Locale en_US
Time of Failure Tue Sep 11 17:54:15 GMT+08:00 2007 (Java Time: 1189504455341)
Web Dynpro Code Generation Infos
sap.com/tcwdtools
No information available null
sap.com/tcwddispwda
No information available null
sap.com/tcwdcorecomp
No information available null
Detailed Error Information
Detailed Exception Chain
java.lang.NullPointerException
     at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:991)
     at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
     at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
     at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:236)
     at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
     at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:445)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:724)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:579)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:155)
     at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
     at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:709)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:555)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:789)
     at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:296)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:767)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.navigate(ClientComponent.java:873)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doNavigation(WindowPhaseModel.java:498)
     at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:144)
     at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
This is very urgent, can any one of u help me on this....
Thanks

Hi,
I am running Netweaver 7 and ERP2005.
J2EE support pack is 9. The sap note that you mentioned is for NW2004 and our system is running on NW2004s.
Now I am trying to reconfigure the sld. In case if you can suggest me another solution, I will be very happy to try that out...
Thanks for your reply
Edited by: Rakesh Bothra on Apr 20, 2011 4:23 AM

JCO - Get meta data - Grey status in JCO connections tab

Hi all,
I read many post on this topics within this forum but I didn't succeed to get meta data required and to set correctly my connection.
Let's start quickly to give you my conf
In the j2ee admin
-> Services > SLD Data Supplier > CIM Client Generation Settings
I set fields with : SLD7000 / 50000 and my logon info
Save and test -> result is ok !
In my web dynpro application, I am able to get correct BAPI from BCE system using my logon info. And I map my view to display data from the corresponding BAPI called.
So at this time, in my IDE, the connection to the SAP Backend system SAP works because I can get the list of BAPIs from the BCE SAP Backend System as well.
Build and deploy my application.
Now, let's go to webdynpro welcome page on my j2ee server : http://<host>:<port>/webdynpro/welcome
-> content administration
-> I select from the left tree browser my application, and open the "JCO Connections" Tab. I can see my connections previously I set in my webdynpro application. But I CAN'T use the button "Create" to configure new JCO connection. ??
Last thing:
in the BCE backend system
transaction : RZ70
I have, host = sldmain and service = sapgw47
Also, in the list of data collection programs, everything is checked as active except the program "_SLD_RFC"
I don't know if it is important....?
Finally, I give you from the exception I got in my browser only lines "Caused by"....
Caused by: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create J2EE cluster node in SLD for 'J2E.SystemHome.localhost': com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="J2E.SystemHome.localhost"
Thanks a lot for your support and help,
Best regards,
Emmanuel.

Hi Emmanuel
You said
" I select from the left tree browser my application, and open the "JCO Connections" Tab. I can see my connections previously I set in my webdynpro application. But I CAN'T use the button "Create" to configure new JCO connection. ??"
What is their status ? Is it green on red? Usually create is greyed out if it is green. What about Edit?
Try creating a new Web Dynpro component with another destination name ,deploy and then check the Content administrator if these new destinations have Create enabled
After running RZ70 did you check the Technical System in SLD administration to see if the technical details have been propogated ?
Regards
Pran

JCo connection broke after deployment

Similar Messages

Maybe you are looking for