ERecruiting - Extended Requisition Workflow created object not found

Hello All,
I am using Workflow WS16900010 (MSS - eRecruiting Scenario) for raising an extended requisition request. While this workflow has executed to success, I am not able to identify the requisition object (NB) which has been created as a result of this workflow. How does the recruiter fill in this requisition object and release it for the manager to be able to do candidate assessment.
Kindly help!
Thanks,
Uthra KJ

Hi SDN users,
Me too facing this issues, by using WF16900009, WF16900010. The workflows as well as notifications are completed and the requisition notification status is displayed in the Status Overview iView. Unfortunatelly no NB (Requisition) object is created in table HRP5125, nor in the recruiter maintenance page for requisitioins.
We're running both ERP HR and E-Recruiting on the same system.
ERP2005 EA-HR 600 SP23 adn ERECRUIT 600 SP11.
Pls help me as the issue urgent.
Thanks & Regards,
Sudheer Kumar P.

Similar Messages

LIBOVD ERROR - "validateContextToken: workflow session was not found for given context. Create a new workflow session with token"

Hello everyone,
I have the following scenario:
We're using "Oracle SOA Suite 11g 11.1.1.7.0" (Patched w/ 17893896) mainly for a BPM/Human workflow composite. Former, we were having the error bellow:
<Mar 16, 2015 1:13:03 PM BRT> <Error> <oracle.soa.services.workflow.query> <BEA-000000> <<.> Verification Service cannot resolve user identity. User weblogic cannot be found in the identity repository. Workflow Context token cannot be null in request.
ORABPEL-30511
When that error ocurred, no one was able to use the system (BPM/Human Workflow).
I opened an SR, and after some analysis from the support, it recommended me to set up "virtualize=true" in EM, and restarting the domain. Then it started logging the following:
connection to ldap://[10.200.10.57]:7001 as cn=Admin.
javax.naming.NamingException: No LDAP connection available to process request for DN: cn=Admin.
Looking up on support KB, I found this note Doc ID 1545680.1 and increased from Max size of Connection Pool 10 to 200. That did work successfully! Problem now is that the <SERVER>_diagnostic.log is being filled up with the following error:
[2015-03-31T16:03:46.421-03:00] [soa_server2] [ERROR] [] [oracle.soa.services.workflow.verification] [tid: [ACTIVE].ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: e0194e38aa6c9a2f:39fc1ff9:14c5def5247:-8000-00000000000a5653,0] [APP: soa-infra] <.> validateContextToken: workflow session was not found for given context. Create a new workflow session with token=51490173-e3d0-41dd-ae99-983915aa8454;;G;;Z+P7Oe9ABnoTUQD9ECryEW2l0/8yRcqPDyZsOWBCuzMmRgA3Qsj601TxmWQ87z2MjuwW5AH+KzgjIwkPmhJFdpc1FrE6Y/MrN1bxIDHJWu2/zP3iSNwKD07hRrh/U37Ea0TvaQyuaHJIog9y3Ptmzw==
One important point is that we're using only the embedded WLS ldap. So I am not 100% sure if we should be using the virtualize flag=true, once all docs I read point out that this should be done when using multi-ldap providers.
Also, I only got this error in the "diagnostic.log".
Although, no user has complained about using the system, I really want to work it out. Anyone has any suggestions?
Thanks in advance!

I have moved your thread from Certification to SOA Suite to get proper assistance.
Thanks,
Lisa

Object not found in store error when trying to load MimeContent of an email (containing attachments)

This is a weird one and I'm hoping someone can reproduce this and give me some help.
We have a system that uses the EWS Managed API to send emails. Optionally an email may need to be saved out as an rfc822 (.eml) file afterwards for storing in our own database. In order to save to a file I need to load up the MimeContent of the message.
And this is where an "Object not found in store" exception can get thrown.
The really strange part is that the exception only seems to occur if the email contains an attachment and if there is too much of a delay between sending the email and trying to access the MimeContent!
My test code is something like:
// Set up the basics
_item = new EmailMessage(P7ExchangeService.Service);
_item.Subject ="Hello world";
_item.ToRecipients.Add("some name", "[email protected]");
_item.Body = new MessageBody(BodyType.HTML, @"<html><head></head><body>hello world<image src=""cid:blah""/></body></html>");
// Add attachment
FileAttachment att = _item.Attachments.AddFileAttachment("blah", "c:\temp\blah.jpg");
att.IsInline = true;
att.ContentId = "blah";
// Send and save
_item.SendAndSaveCopy();
// Wait a bit (see comments below)
Thread.Sleep(5000);
// Now try and save out
var propCollection = _item.GetLoadedPropertyDefinitions();
propCollection.Add(ItemSchema.MimeContent);
_item.Load(new PropertySet(propCollection)); // EXCEPTION!
// ... etc
On some systems it seems that the sending can take a while, hence my Thread.Sleep() call to simulate this.
Its when I try and load up the MimeContent that I will then get the exception. But ONLY if I sleep (simulating the occasional delay seen on customer sites) and ONLY if the email contains an attachment.
The mimecontent is necessary in order to save out to a file (by accessing the _item.MimeContetn property).
Can someone please explain the exception and/or provide a better way of doing this??

This is normal EWS doesn't return the Id of the Item in the SentItems Folder so you need to use a workaround like
http://blogs.msdn.com/b/exchangedev/archive/2010/02/25/determining-the-id-of-a-sent-message-by-using-extended-properties-with-the-ews-managed-api.aspx .
If you want to understand the issue you can enable tracing and look at responses, the actually Id your trying to load the MimeContent from is probably the Id of the draft message. Eg to send a message via EWS with attachments multiple operations must be
used to construct it and when the messages finally gets sent the copy in the drafts folder is deleted and a copy is created in the SentItems folder. However the Id isn't returned for the SentItems copy hence you need the workaround.
Cheers
Glen

ODI not able to detect primary/foreign keys from XML- user lacks privilege or object not found

Hi Guys,
Im trying to load an xml file with two entities address and employee as below. The topology reverse engineering everything works fine. Im even able to view the xml data in ODI, but when i try to load the data from these two entities joining by the schema primary keys and foreign keys which odi created on reverse engineering process for xml, im getting the below error. Im able to load data from one entity, error only occurs when i use the join odi creates internally to identify the xml components employee and address
XML File:
<?xml version="1.0" encoding="UTF-8" ?>
<EMP>
<Empsch>
<Employee>
<EmployeeID>12345</EmployeeID>
<Initials>t</Initials>
<LastName>john</LastName>
<FirstName>doe</FirstName>
</Employee>
<Address>
<WorkPhone>12345</WorkPhone>
<WorkAddress>Test 234</WorkAddress>
</Address>
</Empsch>
</EMP>
Topology: jdbc:snps:xml?f=C:/Temp/RR/Empsch.xml&s=Empsch&re=EMP&dod=true&nobu=false
Error Message:
-5501 : 42501 : java.sql.SQLException: user lacks privilege or object not found: EMPSCH.EMPSCHPK
java.sql.SQLException: user lacks privilege or object not found: EMPSCH.EMPSCHPK
    at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
    at org.hsqldb.jdbc.JDBCPreparedStatement.<init>(Unknown Source)
    at org.hsqldb.jdbc.JDBCConnection.prepareStatement(Unknown Source)
    at com.sunopsis.jdbc.driver.xml.SnpsXmlConnection.prepareStatement(SnpsXmlConnection.java:1232)
    at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at oracle.odi.core.datasource.dwgobject.support.OnConnectOnDisconnectDataSourceAdapter$OnDisconnectCommandExecutionHandler.invoke(OnConnectOnDisconnectDataSourceAdapter.java:200)
    at $Proxy2.prepareStatement(Unknown Source)
    at oracle.odi.runtime.agent.execution.sql.SQLCommand.doInitializeStatement(SQLCommand.java:83)
    at oracle.odi.runtime.agent.execution.sql.SQLCommand.getStatement(SQLCommand.java:117)
    at oracle.odi.runtime.agent.execution.sql.SQLCommand.getStatement(SQLCommand.java:111)
    at oracle.odi.runtime.agent.execution.sql.SQLDataProvider.readData(SQLDataProvider.java:81)
    at oracle.odi.runtime.agent.execution.sql.SQLDataProvider.readData(SQLDataProvider.java:1)
    at oracle.odi.runtime.agent.execution.DataMovementTaskExecutionHandler.handleTask(DataMovementTaskExecutionHandler.java:70)
    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2913)
    at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625)
    at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:577)
    at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:468)
    at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2128)
    at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:366)
    at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
    at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:300)
    at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:292)
    at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:855)
    at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
    at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
    at java.lang.Thread.run(Thread.java:662)
Caused by: org.hsqldb.HsqlException: user lacks privilege or object not found: EMPSCH.EMPSCHPK
    at org.hsqldb.error.Error.error(Unknown Source)
    at org.hsqldb.ExpressionColumn.checkColumnsResolved(Unknown Source)
    at org.hsqldb.QueryExpression.resolve(Unknown Source)
    at org.hsqldb.ParserDQL.compileCursorSpecification(Unknown Source)
    at org.hsqldb.ParserCommand.compilePart(Unknown Source)
    at org.hsqldb.ParserCommand.compileStatement(Unknown Source)
    at org.hsqldb.Session.compileStatement(Unknown Source)
    at org.hsqldb.StatementManager.compile(Unknown Source)
    at org.hsqldb.Session.execute(Unknown Source)
    ... 27 more
Please advice
Thanks
Revanth

Thats obvious from the xml file contents you have given here. In this xml file You have four complex type. Two of them are employee and address. However the employee doesnot have any relation with address as you have not added the relationship. Thats why its failing. Its not the fault of ODI.
Also I would suggest not to use auto generated dtd by ODI as you might face problem in future. For example the address type of XML has 8 attributes and 4 of them are not mandatory. That means each of your xml file may have attributes between 4 to 8. This is where ODI auto generated DTD fails.
XML Schema complexType Element
Thanks
Bhabani

JMS Destination object not found

Hi everyone,
I have a weird problem with SunONE Message Queue 3.
I have a queue and a connection factory defined (using the SunONE Application Server 7 Admin Console) as well as a physical resource.
I can verify their existance using asadmin....
asadmin>list-jmsdest -u admin server1
queue_1 queue {}
asadmin>list-jms-resources -u admin server1
jms/newqueue_1
jms/newQCF_1
When I attempt to deploy a message driven EJB I get the following error
SEVERE ( 1484): javax.naming.InvalidNameException: JMS Destination object not found:`jms/newqueue_1`
This question has already been asked on the App Server board here http://swforum.sun.com/jive/thread.jspa?threadID=15517&tstart=0 (that post is nine months old btw).
I am posting this here in the hope that someone more familiar with MQ3 may have an idea of how to help us.
Thanks in advance.

I have now solved this problem. External JNDI resources are required in the AppServer.
They can be created with the following commands:
asadmin>create-jndi-resource jndilookupname jms/newQCF_1 resourcetype javax.jms.QueueConnectionFactory factoryclass com.sun.jndi.fscontext.RefFSContextFactory enabled=true --property java.naming.provider.url=file\:///c\:/java/mqjndi:java.naming.security.authentication=none newQCF_1
asadmin>create-jndi-resource jndilookupname jms/queue_1 resourcetype javax.jms.Queue factoryclass com.sun.jndi.fscontext.RefFSContextFactory enabled=true --property java.naming.provider.url=file\:///c\:/java/mqjndi newqueue_1
Both these commands assume that the file system context is being used however the LDAP commands are similar (just more properties).
This step, which seems vital, is missing from the AppServer documentation (in fact it specifically states that this step is not necessary). The irony is that I found the answer in the IBM MQ documentation!

ERROR:NameNotFoundException: Object not found in lookup of MYDB

NW 7.0 SP3
I have defined a datasource MYDB by VA,and it tests OK.
I wonder about how to use it in J2EE project or in WebDynpro Project.
I created a J2EE project ,in the Web Model ,i new a class Test:
public static Connection myconn(){
     Context ctx = new InitialContext();
     Connection conn = null;
     DataSource dataSource = null;
     dataSource = (DataSource) ctx.lookup("MYDB");
    conn = dataSource.getConnection();
    return conn;
then in webcontent ,I new a JSP page:
<%
Connection conn = com.Test.myconn();
java.sql.Statement st = conn.createStatement();
String str = "select * from TMP_NAME";
ResultSet rs = st.executeQuery(str);
rs.next();
String str1 = rs.getString(1);
%>
after build and deploy the *.ear,the server returns an error:
         com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of MYDB.
Now I do not know anything else should I do,such as create a reference,and so on.
Thanks for you all help!

Hi,
Try the code as below:
DataSource ds = (DataSource) context.lookup("java:comp/env/jdbc/MYDB")
Go through the below help link:
http://help.sap.com/saphelp_nw2004s/helpdata/en/82/fdbf2085f65f43a71e755fc904478d/content.htm
Go through the below thread for more info:
Re: datasource using VA
Regards,
Charan

NameNotFoundException: Object not found in lookup of FilenameModuleBean

Hello,
after migration from XI 3.0 to PI 7.10 we have a problem with a Java-Module in the File-Adapter.
In XI 3.0 we hat only a EAR-File. We converted it into a SCA-File an deploy it with the JSPM.
I also can see the Objekt in the JNDI-Browser under:
localejbs/sap.com/fnmodear/FilenameModuleBean
rfcaccessejb/sap.com/fnmodear/FilenameModuleBean
sap.com/fnmodear/FilenameModuleBean
ejbCosNaming/sap.com/fnmodear/FilenameModuleBean
but not under:
AF_Modules/ (I don´t know if it matters)
In the File-Adapter we try FilenameModuleBean in the Module Name, but we get the following error message:
18.11.2010 17:02:59 Fehler Adapter Framework caught exception: Object not found in lookup of FilenameModuleBean.
18.11.2010 17:02:59 Fehler Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of FilenameModuleBean..
It seems that he can´t look up the JNDI name.
I hope anyone can help me with the problem.
Best Regards
Georg
Edited by: Georg Kunkel on Nov 18, 2010 5:21 PM

Hi Georg,
I believe the java module "FilenameModuleBean" in your case is a custom adapter module and hence it would not be available under AF_Modules. The AF_Module is for the modules which are shipped with PI by SAP like PayloadSwapBean, XMLConvertorBean etc.
As a checklist, please check the following entries in the module tab of the channel configuration:
1. Module Name: FilenameModuleBean
2. Type: Local Enterprise Bean
3. Module Key: Any Constant Value
4. Module parameters for this module key (Necessary only if the custom module expects any inputs)
Also as you mentioned,
>>In XI 3.0 we hat only a EAR-File. We converted it into a SCA-File an deploy it with the JSPM.
For this, there might be a case that the .SCA file was not generated properly. To properly generate the .SCA or .SDA file you can:
1. Build sca from ear using nwpacktool described in SAP note:1223957
2. Use NWDS 7.1. You can convert your EAR file to SDA file with the help of CECTL & nwcetool provided with NWDS 7.1
Check: Re: How to build an adapter module in NWDS 7.1?
You might also want to look at the following link for creating custom adapter module for PI 7.10
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c0b39e65-981e-2b10-1c9c-fc3f8e6747fa?quicklink=index&overridelayout=true
In case everything looks fine to you, a manual re-start (if possible) of the PI Server should solve the problem.
I hope this helps.
Regards, Gaurav.

EJB3.0 App Deplyed wid warnings : Object not found in lookup of JPA-DEFAULT

Hello Friends
I am getting this warning while deploying this EJB 3.0 Application
here I have
1) 4 DCs with session beans
2) One Entity DC
I have checked my jta-data-source its added properly
here is the deployment stack trace
     Description:
          1. Exception has been returned while the 'asianpaints.com/hssp_app_new' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 6358450:com.sap.engine.services.orpersistence.container.deploy.ActionException: [ERROR CODE DPL.DS.5030] Clusterwide exception: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of JPA_DEFAULT.
     at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
     at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at javax.naming.InitialContext.lookup(InitialContext.java:351)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:344)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
     at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initDataSources(ComplexModuleCreator.java:360)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.initRuntimeModels(ComplexModuleCreator.java:230)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.createModule(ComplexModuleCreator.java:154)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexModuleCreator.execute(ComplexModuleCreator.java:84)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ComplexActionAdapter.execute(ComplexActionAdapter.java:34)
     at com.sap.engine.services.orpersistence.container.deploy.impl.ApplicationCreator.execute(ApplicationCreator.java:74)
     at com.sap.engine.services.orpersistence.container.deploy.impl.PersistenceContainer.prepareStart(PersistenceContainer.java:187)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:420)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:445)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3389)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3375)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3278)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3251)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:877)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Result
Status:Warning

OK, you have properly declared the data source for your persistence unit in the persistence.xml. But you also have to maintain this data source (alias) on the server, i.e. it has to be created explicitly.
Check this [document|http://help.sap.com/saphelp_nwce711/helpdata/en/46/96ec3c33621e5ce10000000a1553f6/frameset.htm].
HTH!
-- Vladimir
PS: Please take your time to go through the [Rules of Engagement|https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement] and do not crosspost to multiple forums.

Explain plan--Object not found error

Hi All,
I want to use 'explain plan' to optimise the query.
How do i see the explain plan in toad.
when i say
explain plan set statement_id='XX' for select stmt;
select * from explain plan
where statement_id='XX';
iam geeting object not found
what parameters i need to set up before using explain plan
Please give me details.
Please suggest.
Thanks.

This should have been in TOAD Forum :-)).. Anyway,
You need to set the plan table name in view->Options->Oracle. If the specified plan table doesnt exist, create the plan table

NameNotFoundException: Object not found in lookup of 'JDBC-Alias Name'

Hi Experts,
I am getting the NameNotFoundException: Object not found in lookup exception, when accessing the DataSource using the alias name EMPLOYEE_DS from JspDynpage.
Here is the code for lookup
InitialContext ctx = new InitialContext();
// TODO chenage the alias to the right one
DataSource ds = (DataSource) ctx.lookup("jdbc/EMPLOYEE_DS ");
The same application is running using the above alias name in our development environment, but the same is not working in production system.
I have created the same Alias Name for JDBC Datasource, but still is not working.
Here is the Exception trace.
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of EMPLOYEE_DS.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:649)
at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:344)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:254)
at com.sap.engine.services.jndi.implclient.OffsetClientContext.lookup(OffsetClientContext.java:271)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
Should this alias name existed any where else, any configuration is missed.
Thanks in Advance,
Chinna.

Hi Anup,
As I said, My application is working in both Development and Quality system with the lookup
DataSource ds = (DataSource) context.lookup("jdbc/MYDB")
but the problem is in only Production system, I believe there might be some configuration missed.
As you said I have tried with
DataSource ds = (DataSource) context.lookup("java:comp/env/jdbc/MYDB")
with the abvoe lookup my application stopped working and getting the below exception and throws the below exception
com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Path to object does not exist at java:comp, the whole lookup name is java:comp/env/jdbc/REPORTING_DASHBOARD.
I believe my lookup is working without any issues, because it is working in dev and quality systems, problem might be in configuration. I have done the alias creation through nwa, following
http://<server:port>/nwa>Configuration>Application Resources-->JDBC Datasource Alias
Any more suggestions regarding this.
Thanks,
Chinna.

Exchange 2003 to 2010 Migration Mailbox Migration "Object not found"

I am introducing an Exchange 2010 Server to a single server Exchange 2003 organization. I have HT, CAS and MB roles installed already on 2010 w/ SP1. Prepped the Schema, AD, Domain and LegacyExchangePermissions by using the setup.com of the SP1
installation files.
Right now, when I try to initiate a New Local Move Request on 2010 EMC for a mailbox on Exchange 2003, I get an error for all the users saying "Object not found" with a white X in a red circle. I'm not sure what to do at this point to get Exchange 2010
recognize the 2003 mailboxes. Any ideas?
Thank you,
-S

Tim,
Here is what I'm getting from ExBPA:
Error Offline address book replica not found Organization CGU Didn't find a replica of folder 'OAB Version 4' for offline address book 'Default Offline Address List'. Either a replica doesn't exist, or this folder hasn't been created yet. If an OAB generation
attempt has not yet been made, you can ignore this error.
Error Couldn't find any writeable domain controllers Admin Group Exchange Administrative Group (FYDIBOHF23SPDLT) There were no writeable domain controllers found in Active Directory site 'Default-First-Site-Name'. At least one writeable domain controller
is required for Exchange to function properly.
Error Database backup critical Admin Group Exchange Administrative Group (FYDIBOHF23SPDLT) Database 'Public Folder Database' on server EXCH-2010 has never had a full online backup.
====
And this is what happens if I put go ahead with the move request
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00
Test User
Failed
Error:
Mailbox database "EXCH-01\First Storage Group\Mailbox Store (EXCH-01)" doesn't exist.
Click here for help...
http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.140).aspx?v=14.1.218.11&t=exchgf1&e=ms.exch.err.Ex23B42B
Exchange Management Shell command attempted:
'cgucpa.com/Users/Test User' | New-MoveRequest -TargetDatabase 'Mailbox Database'
Elapsed Time: 00:00:00
Thank you for your help,
-S

Error encountered while signing. Windows cryptographic service provider reported an error. Object not found. Error code:2148073489. Windows 7, Adobe Reader XI, Symantec PKI, Smart Card and CAC. I have seen other threads for this error but none have a reso

Error encountered while signing. Windows cryptographic service provider reported an error. Object not found. Error code:2148073489. Windows 7, Adobe Reader XI, Symantec PKI, Smart Card and CAC. I have seen other threads for this error but none have a resolution. Any help would be appreciated.
Sorry for the long title, first time poster here.

This thread is pretty old, are you still having this issue?

While Doing BW Role Uploading Getting message "Linked Objects Not Found" ?

Dear All,
I am trying to upload a BW role from EP , while doing role upoad activity, when I am giving role name, system namein the first step it is identifying the role from the system.
To that role four reports has been attached.
After uploading the role, the role has been get uploaded, but the reports which are attached to the role it is showing that "Linked Objects Not Found", for all the reports.
For all those reports I have checked the web url on BW server it is corect but then also I am getting above message.
Please any one help me out in this scenario.
Regards,
Aditya

The same problem during XI to BI integration as it was told in how-to.

While posting T.code VL02N "co object not found " what have to do

Hi
Friends..
while posting T.code VL02N "co object not found " what have to do
General Ledger related to Co object what i want todo.
showing error " Co Object not found"
Thank you.
Ashok kumar

Hi
Assign a cost centre to the cost element of the general ledger account specified.
Transaction KA02
another option is got OKB9 and assign cost center to GL account at company code level.
regards
Srinivas

PI 7.0 JMS Rcv Adapter: Object not found in lookup of XIJMSService

Hi all,
When sending messages to an JMS queue, JNDI setup, in the Message Monitoring we get the error:
"MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Object not found in lookup of XIJMSService.: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of XIJMSService."
The Error points to the Module Processor. Indeed the 2 default Modules are used:
- SAP XI JMS Adapter/ConvertMessageToBinary
- SAP XI JMS Adapter/SendBinarytoXIJMSService
This second Module contains 'XIJMSService', and according the documentation (http://help.sap.com/saphelp_nw04/Helpdata/EN/4d/a3bc97ff55c742af7faed661635baf/content.htm)
, it uses a parameter named 'modulePoolAdminLookupName' with the default value: /XIJMSService.
This is how far we get. Even when we assign a different value to the parameter 'modulePoolAdminLookupName' , the error in the Message Monitoring stays the same.
Has anyone experience with this issue, or any ideas to investigate or solve this?
Thanx in advance, Walter.

Hi all,
Issue is solved. Apparently the Java-version on our XI-server (1.4.2) could not handle the Vendor's JMS-driver we installed (ActiveMQ 4.1.2.jar) so we tried using the ActiveMQ 4.1.0.jar as the JMS-driver. Now it is OK and message are put on the destination queue.
Walter.

ERecruiting - Extended Requisition Workflow created object not found

Similar Messages

Maybe you are looking for