Unable to lookup referenced beans

I've got a problem looking up referenced beans! I'm having three beans; TaxonomyManager, TaxonomyDependencyManager and TaxonomyEntity and the situation is as follows: the TaxonomyManager uses the TaxonomyDependencyManager (both stateless sessionbeans), the latter uses the TaxonomyEntity (entitybean). They all look eachother up using the java:comp/env namespace where they have been bound (in the deployment descriptors)
Situation 1: My client (RMIInitialContextFactory) looks up the TaxonomyManager does a call. The TaxonomyManager tries to look up the TaxonomyDependencyManagerHome and succeed. It tries to CREATE a TaxonomyDependencyManager and FAILS in the create method. See exception below
Situation 2: My client looks up the TaxonomyDependencyManager DIRECTLY and DOES NOT fail. So in this case (same situation) it works!
Situation 3: My client looks up the TaxonomyManager, does a call. No the TaxonomyManager does not lookup the TaxonomyDependencyManager using the java:comp/env namespace but it looks it up DIRECTLy (using JNDI name: smarthaven/taxonomy/TaxonomyDependencyManager). That works as well.
So the thing that goes wrong is: a bean that is bound in the ENV (java:comp/env namespace) that tries to look up another bean, that, in it's create method looks up another bean (all bound in the java:comp/env namespace)! All the other situations succceed...
Again there's NO problem or whatsoever with the deployment. Directly looking up the beans works!!!
The exception:
com.evermind.server.rmi.OrionRemoteException: Error in ejbCreate(): null
at com.evermind.server.ejb.StatelessSessionEJBHome.getContextInstance(StatelessSessionEJBHome.java:192)
at TaxonomyDependencyManager_StatelessSessionBeanWrapper79.getTaxonomyLocks(TaxonomyDependencyManager_StatelessSessionBeanWrapper79.java:267)
at com.smarthaven.component.taxonomy.TaxonomyManagerBean.checkLock(TaxonomyManagerBean.java:518)
at com.smarthaven.component.taxonomy.TaxonomyManagerBean.saveTaxonomy(TaxonomyManagerBean.java:365)
at TaxonomyManager_StatelessSessionBeanWrapper75.saveTaxonomy(TaxonomyManager_StatelessSessionBeanWrapper75.java:1305)
at java.lang.reflect.Method.invoke(Native Method)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:80)
at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)
Nested exception is:
java.lang.NullPointerException
at com.evermind.server.ejb.DelayedHomeBinding.getInstance(DelayedHomeBinding.java:44)
at com.evermind.naming.MapContext.lookup(MapContext.java:53)
at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:122)
at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:64)
at javax.naming.InitialContext.lookup(Unknown Source)
at com.smarthaven.component.taxonomy.TaxonomyDependencyManagerBean.ejbCreate(TaxonomyDependencyManagerBean.java:83)
at TaxonomyDependencyManagerHome_StatelessSessionHomeWrapper80.callCreate(TaxonomyDependencyManagerHome_StatelessSessionHomeWrapper80.java:123)
at com.evermind.server.ejb.StatelessSessionEJBHome.getContextInstance(StatelessSessionEJBHome.java:179)
at TaxonomyDependencyManager_StatelessSessionBeanWrapper79.getTaxonomyLocks(TaxonomyDependencyManager_StatelessSessionBeanWrapper79.java:267)
at com.smarthaven.component.taxonomy.TaxonomyManagerBean.checkLock(TaxonomyManagerBean.java:518)
at com.smarthaven.component.taxonomy.TaxonomyManagerBean.saveTaxonomy(TaxonomyManagerBean.java:365)
at TaxonomyManager_StatelessSessionBeanWrapper75.saveTaxonomy(TaxonomyManager_StatelessSessionBeanWrapper75.java:1305)
at java.lang.reflect.Method.invoke(Native Method)
at com.evermind.server.rmi.RMICallHandler.run(RMICallHandler.java:80)
at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:64)

I found a thread that suggested creating a "Java Service Facade" from persistence.xml. The thread said that the original persistence.xml was created incorrectly, but the entries created with the facade worked.

Similar Messages

Error 485680 reservation warning(node_join) - Unable to lookup local_only f

SETUP
3xT5220
1xStorageTek 2540 FC RAID
SC 3.2
OS 10 Patchlevel 137111-08
Two of the 3 cluster nodes are directly connected to the RAID.
Multipathing enabled on all cluster nodes (stmsboot -e).
PROBLEM
On the node, which was added to an already established cluster as the third node, that is NOT connected to the RAID, I'm seeing hte following messages:
Cluster.CCR: [ID 485680 daemon.warning] reservation warning(node_join) - Unable to lookup local_only flag for device dsk/d10.
Cluster.CCR: [ID 485680 daemon.warning] reservation warning(node_join) - Unable to lookup local_only flag for device dsk/d9
svc.startd[8]: [ID 652011 daemon.warning] svc:/system/cluster/globaldevices:default: Method "/usr/cluster/lib/svc/method/globaldevices start" failed with exit status 96.
with exit status 96.
svc.startd[8]: [ID 748625 daemon.error] system/cluster/globaldevices:default misconfigured: transitioned to maintenance (see 'svcs -xv' for details)
Cluster.CCR: [ID 916112 daemon.error] /usr/cluster/bin/scgdevs: Filesystem /global/.devices/node@3 is not available in /etc/mnttab.
# svcs -xv
svc:/system/cluster/globaldevices:default (Suncluster globaldevices service)
State: maintenance since January 12, 2009 2:38:26 PM EST
Reason: Start method exited with $SMF_EXIT_ERR_CONFIG.
   See: http://sun.com/msg/SMF-8000-KS
   See: /var/svc/log/system-cluster-globaldevices:default.log
Impact: 3 dependent services are not running:
        svc:/system/cluster/mountgfs:default
        svc:/system/cluster/clusterdata:default
        svc:/system/cluster/ql_rgm:default
svc:/system/cluster/scsymon-srv:default (Sun Cluster SyMON Server Daemon)
State: maintenance since January 12, 2009 2:38:41 PM EST
Reason: Start method exited with $SMF_EXIT_ERR_CONFIG.
   See: http://sun.com/msg/SMF-8000-KS
   See: /var/svc/log/system-cluster-scsymon-srv:default.log
Impact: This service is not running.
# cat /var/svc/log/system-cluster-globaldevices:default.log
[ Jan 12 02:37:52 Disabled. ]
[ Jan 12 02:37:53 Rereading configuration. ]
[ Jan 12 02:47:55 Rereading configuration. ]
[ Jan 12 02:48:28 Enabled. ]
[ Jan 12 02:49:07 Executing start method ("/usr/cluster/lib/svc/method/globaldevices start") ]
[ Jan 12 02:49:10 Method "start" exited with status 96 ]
[ Jan 12 06:14:43 Executing start method ("/usr/cluster/lib/svc/method/globaldevices start") ]
[ Jan 12 06:14:46 Method "start" exited with status 96 ]
[ Jan 12 09:50:26 Executing start method ("/usr/cluster/lib/svc/method/globaldevices start") ]
[ Jan 12 09:50:34 Method "start" exited with status 96 ]
[ Jan 12 13:17:27 Executing start method ("/usr/cluster/lib/svc/method/globaldevices start") ]
[ Jan 12 13:17:30 Method "start" exited with status 96 ]
[ Jan 12 14:28:54 Executing start method ("/usr/cluster/lib/svc/method/globaldevices start") ]
[ Jan 12 14:29:02 Method "start" exited with status 96 ]
[ Jan 12 14:38:23 Executing start method ("/usr/cluster/lib/svc/method/globaldevices start") ]
[ Jan 12 14:38:26 Method "start" exited with status 96 ]This prevents my scalable resource group from coming online on the third cluster node.
From the cluster error message guide:
+485680 reservation warning(%s) - Unable to lookup local_only flag for device %s.+
Description: The device fencing program was unable to determine if the specified device is marked as local_only. This device will be treated as a non- local_only device and nodes not within the cluster will be fenced from it.
Solution: If the device in question is marked marked as local_only and is being used as the boot device or the mirror of a boot device for a node, then that node may be unable to access this device and hence, unable to boot. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
Any idea what's going on or how to prevent it?

I have isolated the issue to ssh and the login window. I can use these same administrator credentials to initiate ARD sessions, configure the server via Server admin or WGM, authenticate to perform privileged finder operations.
restarts do not change anything.
per a related post, but not identical investigated /var/db/dslocal/nodes/Default/config/ I only had one of the referenced files, not the several hundred those posters seemed to have. I made a backup, and removed it, followed by a restart. There was no effect.
I opened Server Admin, and turned off ssh, verified that remote login was not checked in System Preferences. Logged out, no effect, restarted again no effect.
There is no joy with trying Local Administrator.
This is a clean 10.5.4 Install (Monday, August 3) DNS works per Anthony Rocco's setup instructions and verification methods. DNS was working prior to upgrading to OD Master. Kerberos logins worked properly. I was going through and setting up share points and setting ACLs when I realized I lost access.
I would take any suggestions people might have...
thanks,
Ion

How to lookup a Bean?

i have successfully deployed an EJB by using J2EE deploytool.
my source code to lookup the Bean as following:
Context ctx = new InitialContext(System.getProperties());
java.lang.Object objref = ctx.lookup("skey");
home = (SessionKeyHome)PortableRemoteObject.narrow(objref, com.ibm.sessionkey.SessionKeyHome.class);
i have read serval books and articles,there are different codes for lookuping a bean.Why?and when should we use this or that?
But i get the error msg:
Warning: unable to read transaction.interoperability config property
java.io.FileNotFoundException: /export/home/ass/config/security.properties
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:103)
at com.sun.enterprise.util.Utility.getPropertiesFromFile(Utility.java:42)
at com.sun.enterprise.iiop.security.SecurityMechanismSelector.<clinit>(SecurityMechanismSelector.java:102)
at com.sun.enterprise.iiop.IIOPSSLSocketFactory.getEndPointInfo(IIOPSSLSocketFactory.java:211)
at com.sun.corba.ee.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:73)
at com.sun.corba.ee.internal.iiop.ConnectionTable.getConnection(ConnectionTable.java:68)
at com.sun.corba.ee.internal.iiop.GIOPImpl.getConnection(GIOPImpl.java:70)
at com.sun.corba.ee.internal.corba.InitialNamingClient.locateObject(InitialNamingClient.java:769)
at com.sun.corba.ee.internal.corba.InitialNamingClient.getIORUsingHostInfo(InitialNamingClient.java:597)
at com.sun.corba.ee.internal.corba.InitialNamingClient.resolveCorbaloc(InitialNamingClient.java:573)
at com.sun.corba.ee.internal.corba.InitialNamingClient.resolveUsingORBInitRef(InitialNamingClient.java:544)
at com.sun.corba.ee.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1080)
at com.sun.corba.ee.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:981)
at com.sun.corba.ee.internal.corba.ORB.resolve_initial_references(ORB.java:2425)
at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:52)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:120)
at javax.naming.InitialContext.lookup(InitialContext.java:347).java:23)
javax.naming.CommunicationException: Can't find SerialContextProvider
at com.sun.enterprise.naming.SerialContext.getProvider(SerialContext.java:63)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:120)
at javax.naming.InitialContext.lookup(InitialContext.java:347)

Hi,
There r two ways to lookup. One is that u specify the provider while running the client. E.g:
java -D java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
-Djava.naming.provider.url=t3://localhost:7001
or alternatively u can specify these two properties in the Properties object of your client. e.g:
Properties props = new Properties();
props.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
props.put(Context.PROVIDER_URL,"t3://localhost:7001");
Context ctx = null;
Object obj = null;
try
ctx = new InitialContext(props);
obj = ctx.lookup("HelloJNDI");
Which method to use is matter of convenience.
Values of provider url & initialContext will change depending on the app server u r using.
I hope this will help u.

Unable to lookup home: Path to object does not exist at : java:comp#

Hallo,
I do not understand why I am getting the exception:
Unable to lookup home: Path to object does not exist at : java:comp#
if i have defined in the ejb-j2ee-engine.xml the jndi name:
<enterprise-beans>
 <enterprise-bean>
 <ejb-name>MyConverterBean</ejb-name>
 <jndi-name>MyConverterBean</jndi-name>
 <session-props/>
 </enterprise-bean>
</enterprise-beans>
and in the ejb-jar.xml :
<enterprise-beans>
 <session>
 <description>the converter bean</description>
 <display-name>MyConverter</display-name>
 <ejb-name>MyConverterBean</ejb-name>
 <home>converter.MyConverterHome</home>
 <remote>converter.MyConverter</remote>
 <local-home>converter.MyConverterLocalHome</local-home>
 <local>converter.MyConverterLocal</local>
 <ejb-class>converter.MyConverterBean</ejb-class>
 <session-type>Stateless</session-type>
 <transaction-type>Container</transaction-type>
 </session>
</enterprise-beans>
I am creating the EJB in this way:
ic = new InitialContext();
objRef = ic.lookup("java:comp/env/ejb/MyConverter");
home = (MyConverterHome)PortableRemoteObject.narrow(objRef, MyConverterHome.class);
converter = home.create();
I checked in the Administrator tool under JDNI / ejbContext and I can see MyConverterBean in the list.
Do you have any idea what I am doing wrong?
thanks a lot for your help,
SAPLernen

Hi Vladimir,
do you have some example or tutorial of how can i implement java proxies from a java stand alone application.
i allready make everyting but i'm still having problem.
this line give me a null
queryOutLocalHome = (UsersSyncMI_PortTypeLocalHome)ctx.lookup("java:comp/env/ejb/UsersSyncMI_PortTypeBean");
this is my java class that invoke my ejb java proxy
package com.gsk.xi.demo;
import java.util.Properties;
import javax.naming.Context;
import javax.naming.InitialContext;
import com.sap.aii.proxy.xiruntime.core.MessageSpecifier;
public class InvokeProxy {
 private Object objRef = null;
 private InitialContext ic = null;
 public String getRole(String name, String pwd){
 String role="0";
 UsersSyncMI_PortTypeLocalHome queryOutLocalHome=null;
 UsersSyncMI_PortTypeLocal queryOutLocal=null;
 try{
 Context ctx = null;
 Object ref = null;
 Properties p = new Properties();
 p.put(Context.INITIAL_CONTEXT_FACTORY,"com.sap.engine.services.jndi.InitialContextFactoryImpl");
 p.put(Context.PROVIDER_URL, "buasapp012.gwamericas.corpnet1.com:50004");
 p.put(Context.SECURITY_PRINCIPAL, "J2EE_ADMIN");
 p.put(Context.SECURITY_CREDENTIALS, "was1234");
 ctx = new InitialContext();
 //objRef = ic.lookup("java:comp/env/ejb/UsersSyncMI_PortTypeBean");
 //queryOutLocalHome = (UsersSyncMI_PortTypeLocalHome)PortableRemoteObject.narrow(objRef, UsersSyncMI_PortTypeLocalHome.class);
 queryOutLocalHome = (UsersSyncMI_PortTypeLocalHome)ctx.lookup("java:comp/env/ejb/UsersSyncMI_PortTypeBean");
 queryOutLocal = queryOutLocalHome.create();
 MessageSpecifier msg = queryOutLocal.$messageSpecifier();
 msg.setSenderService("JAVA");
 queryOutLocal.$messageSpecifier(msg);
 UserDT_Type reqtype = new UserDT_Type();
 reqtype.setUsername(name);
 reqtype.setPassword(pwd);
 UsersDBMTResponse_Type response = new UsersDBMTResponse_Type();
 response = queryOutLocal.usersSyncMI(reqtype);
 role = role + response.getStatementResponse().getRow().getRole();
 catch(Exception ex){
 System.out.println(ex.getMessage());
 return role;
} //end of class
thanks for your time
Lionel

Unable to lookup EJBHOme in Cluster!!

 HELP!
 I am running a client program that attempts to call a stateless EJB (MediaAgent) on a cluster called
 mycluster running on port 63889. The cluster contains objects (EJBs) only.
 Here's the wierd part. When the client performs a listing of the EJBs on mycluster, it shows
 the bean I want, MediaAgentHome.
 But when it tries to do a lookup, I get this error:
 The client was unable to lookup the EJBHome
 The deployment of thje EJB with JNDI name MediaToolHome on the WebLogic Server t3://mycluster:63889
 What in God's name is going on here?!?!
 It can list it but can't look it up??
 Any ideas?
 Thanks,
 Dave


Hi,
 You should use t3://<managed-server1-ip>:<managed-server1-port>,<managed-server2-ip>:<managed-server2-port> as your cluster's provider-url.
 Also, "<managed-server1-ip>:<managed-server1-port>,<managed-server2-ip>:<managed-server2-port>" as your cluster's listen address.
 The following lonks may helpful to you
 http://e-docs.bea.com/wls/docs81/cluster/features.html#1007508
 http://e-docs.bea.com/wls/docs81/cluster/failover.html#1008850
 http://e-docs.bea.com/wls/docs81/cluster/load_balancing.html#1045512
 Regards
 Prasanna Yalam

Error- Unable to lookup in the system.

Dear All,
For my backend server I have created system object on portal.
Then I have made 1 transaction iview for the same system object.
In the preview of the iview it is showing me correct screen and its operations are also fine.
But when I am attaching that iview to ane role and attaching that role to any user and viewing that iview thru tht users login it is giving me an error
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
Unable to lookup System 'TEST'. Please check the system object and the alias..
See the details for the exception ID in the log file
Can anyone guide me in the above issue ?
Regards,
Aditya

Hi All,
While checking the permissions under SAP Authorizations it is giving me an error
classcom.sapportals.connector.connection.ConnectionFailed ExceptionConnection Failed: Nested Exception. Failed to get connection.
I have check all the parameters under connector property also
they are fine.
One more thing if this role I attched to administrator account it is working properly.But for normal user it is giving the run time error as mentioned above.
Please anyone help me out in this situation.
Regards,
Aditya

Unable to find referenced object problem

Hi ,
when i made compile for Adf BC Application Jdeveloper version ( 11.1.2.3 ) , it result compile error
Error : ************ unable to find referenced object Object=************** Owner= ********************
Notes :- this application contains view objects that depend upon jar file for the Entity Object

Hi,
Did you add the dependencies
http://docs.oracle.com/cd/E15051_01/web.1111/b31974/reusing_components.htm
http://andrejusb.blogspot.com/2011/04/strange-day-adf-library-profile.html
http://adfhowto.blogspot.com/2010/10/adding-lib-jar-dependency-to-my-project.html

Prob in IR :Internal error during bean lookup for bean RepObjectAccessBean

Hi,
I am facing the problem in IR .
Internal error during bean lookup for bean RepObjectAccessBean
is the Error window I am getting frequently, After getting this error, It is no allowing to open any of the IR Objects.
Thanks in advance,
Dhanabal T

Hi Dhanabal,
i got the same error. But it is clear.
Please chek once ur configuration part. The error is in configuration part only.
once check all the steps in ur configuration part.
REgards,
chandra.

How to lookup a bean from a standalone app.

I've got the following question..
I've created a stateless sessionbean and deployed it in the J2EE Server 1.3.1. (That one you get from Sun when you download the J2EE SDK) I've created a client for my bean, and when i execute it with the 'runclient -client my.ear -name myclientclass' command, it works just fine.
But, i now want to run it as a standalone application, without the 'runclient' command. I am able to create an initialcontext (without any properties), but my bean can not be found in 'java:comp/env/ejb/bean' (the same name i use with the 'runclient' command, so the bean should be there). My guess is that i should add some initial context properties, but which ones? All the examples i can find are with ldap context factories. Can anyone give me any advice on how to connect to the J2EE server and lookup my bean?
Thanks in advance.
Nick

Hi,
You could write something as below
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContextFactory");
env.put(Context.PROVIDER_URL, "jnp:localhost:1099");
env.put("java.naming.factory.url.pkgs","org.jboss.naming:org.jnp.interfaces");
try {
Context ctx = new InitialContext(env);
Session_LocalHome session_lh = (Session_LocalHome) ctx.lookup("Session_Home");
Session_ session_ = session_lh.create();
OR
Use a jndi.properties file which would have the same entries as above, please search over internet and find out what to include in it.
One more thing to note is, in above example i said
env.put(Context.PROVIDER_URL, "jnp:localhost:1099");
meaning the lookup is on port 1099, this is not same for all the servers. Check your server documentation and find out " What is the port number on which your server listens ? "
Regards
Meka Toka

Unable to lookup the Deploy Service. java.lang.ClassCastException in NWDS

Hi All,
I am getting the following exception while deploying an application in NWDS.
Please help me in resolving this issue
Sep 6, 2007 10:24:32 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[001]Deployment aborted
Settings
SDM host : bala
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/BALU/LOCALS1/Temp/temp64339RFCFlightList.ear
Result
=> deployment aborted : file:/C:/DOCUME1/BALU/LOCALS1/Temp/temp64339RFCFlightList.ear
Aborted: development component 'RFCFlightList'/'local'/'LOKAL'/'0.2007.09.06.22.24.23'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: Unable to lookup the Deploy Service. java.lang.ClassCastException
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).DMEXC)
Deployment exception : The deployment of at least one item aborted

Hi Bala
Some of the services at your server are not running..ask your system admin to restart the SDN server and try to deploy once
Regards
Chaitanya.A

Unable to lookup System ...check the system object and the alias

Hi,
I am working on EP6 Sp 9. I have created iviews and integrated j2ee application by appIntegartor . everything is working fine . but these iviews are working only with superadmin role . with any other role am getting the error message "Unable to lookup System 'NNNJ2ee'. Please check the system object and the alias.."
Have created a role and done appropriate user mapping. Connection Test goes through successfully and iViews work fine as expected, but just in administrator login.
i found a a thread dissucing about the same problem in this forum and followed the solution given by them(assigning eu_role to the user) .
But still it is not working for me.
can anyone please help me in finding the solution .
Thanks,
Lakshmi

Hi,
The cause is :
When you create an item with the 'super admin role' user's , you don't have the role : 'eu_role' assigned.
So when you create a new item the role 'eu_role' is not spread to end user.
The solution is :
First add the 'eu_role' to the super admin user. For all next item created it's work fine.
For item already created,
- right click on the object, Select open permissions.
- In the display option, choose Permissions
- Search for role : 'eu_role'
- Add the permissions
- check the box 'End User'
- Save
- And test
For me it's work fine. Let me know if it's good for you...
Regards
Alain Chanemouga @ SAP

Unable to lookup System object and the alias..

Hello All,
I am implementing the Business Package for CRM.
I have created the SAP_CRM and SAP_BW systems and assigned them the same aliases as mentioned in the instructions in http://help.sap.com/saphelp_crm40/helpdata/en/11/0584016208bc4988c3791d6213b6d0/content.htm
I have tested the connections to the WAS, as well as ITS server after configuring them from the portal system administration.
However, I get the exception.
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
Unable to lookup System 'SAP_CRM'. Please check the system object and the alias..
The error in the log is as follows:
#1.5#00112FCBC32C005E000000A9000007EC000412303370C08B#1145898137593#com.sap.portal.sapapplication#sap.com/irj#com.sap.portal.sapapplication#user1#95##LABNW_J2E_19311950#user1#15374a50d3b411da8f1e00112fcbc32c#SAPEngine_Application_Thread[impl:3]_36##0#0#Error#1#/System/Server#Plain###ApplicationIntegratorException: com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unable to lookup System &\#39;SAP_CRM&\#39;.
Please check the system object and the alias.com.sapportals.portal.appintegrator.ApplicationIntegratorException: Unable to lookup System &\#39;SAP_CRM&\#39;.
Please check the system object and the alias.
 at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.getSystemLogonMethod(SingleSignOnLayer.java:243)
 at com.sapportals.portal.appintegrator.layer.SingleSignOnLayer.processLayer(SingleSignOnLayer.java:55)
 at com.sapportals.portal.appintegrator.LayerProcessor.processActionPass(LayerProcessor.java:173)
 at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doOnPOMReady(AbstractIntegratorComponent.java:71)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:396)
 at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:252)
 at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:369)
 at com.sapportals.portal.prt.pom.PortalNode.processEventQueue(PortalNode.java:800)
Any hints recommendations for the same.
Thank You.
Sumit.

Hi Sumit,
System is an object in Portal Content Directory (PCD). User of portal should have permissions to access it. Looking up is a kind of access.
Please go to System Administration -> System Configuration -> System Landscape. Find your system and right-click on it, then choose 'Permissions'. There you should make sure that your portal user has permissions.
You can read about permissions here:<a href="http://help.sap.com/saphelp_nw04/helpdata/en/f6/2604e505fd11d7b84200047582c9f7/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/f6/2604e505fd11d7b84200047582c9f7/frameset.htm</a>
There is an extract probably related to your problem:
" If an iView is based on a system object defined in your system landscape (see System Landscape), you must assign end user permission for the relevant user, group, or role to the system object, as well. End user permission assigned to a system permits the iView to retrieve data from the respective back-end application through the system object at runtime."
Regards,
Sergei
Message was edited by: Sergei Dneprov

Unable to lookup the ServerLifeCycleRunTimemBean exception when try to start managed server

I have two domains, FRDomain and NewServer2. I can startup all servers on FRDomain, including newly created non-default servers. For xyzDomain, I can start up the admin server, but none of my other managed servers. When I try, I get
weblogic.management.scripting.ScriptException: Error occured while performing start : Unable to lookup the ServerLifeCycleRuntimeMBean for server NewServer2
Syntax:
nmConnect(.....)
nmStart('AdminServer')
connect(...)
start ('NewServer2','Server')
FYI: This is WIndows 2008 Server

Hi, the topology of th network ist the next:
ISP (DATACENTER) -> SRV1 (phisical) + SRV2 &SRV3 (virtual)
Every one of them have 2 NIC ( for server 2 and 3 - virtual too)
NIC1 - operates on private level - 192.168.1.1 dns, gate,dc (srv1)
NIC2 - real ip address, gate - gateway of ISP dns - 192.168.1.1
When set up NIC1 - everything is ok .
NIC2 - action is : set ip and mask - enable without gate - then it is in unidentified status and go in public state.
disable nic2, set up gateway - and dns - 192.168.1.1 and again enable - everything is ok
But after restart - nic2 - goes again in Domainauthenticated mode. :(
Additional:
On srv2 - i put RRAs role and smthing stange is that after enable rras service - all ports are shutted and machine pretendet to be invisible.

Network error: Unable to lookup host names

on one client running the cisco any connect, It is unable to connect and keeps giving an error
Network error: Unable to lookup host names.
any idea about this?

You tell us that this happens on one client. Are there other clients which work ok? If so then I would wonder about some problem with the install of the client on this PC. Perhaps you might un-install and install again?
HTH
Rick

Business components : unable to find referenced object

Hi,
i work on Jdev Studio Edition Version 11.1.1.1.0.
I often have this message in the message-log window :
Business Components: Unable to find referenced object
Object: easyges.monActivite.mesInfos.MonSuperieur.
Owner: easyges.crah.AppModuleCRAH
BC Project: easyges.view.ViewController
What do i have to do with that?
Thanks for your answer ?
David

i am moving to views current way.hi this is my error.
Error: jeg.adf.pm.setworkbench.model.views.ImportProjectVO: Unable to find referenced object.
Object=model.Entity.ImportProjectEO
Owner=jeg.adf.pm.setworkbench.model.views.ImportProjectVO
BC Project: model.JacobsModel

Unable to lookup referenced beans

Similar Messages

Maybe you are looking for