Error while recording process using a component with a custom data type

Hello,
I created a component that returns a CheckAttachmentResult object. This object contains an int named resultCode and a String named resultMessage. In the CheckAttachmentResult class, I do have a getter and a setter function for both values.
When I use the component, I can retrieve the CheckAttachmentResult object, see the values that are set (i.e. resultMessage and resultCode) and work on them (for instance build a condition on the resultCode).
However when the current process goes into a subprocess after having used this component, I get the following error:
Failed evaluating outgoing routes for action=template:ReceptionDtpBriefingV2/branch:main-branch/pool:POOL/swimlane:Extraction du DTP/action:Check DTP attachments: java.lang.NullPointerException at com.adobe.idp.auditworkflow.dsc.service.storage.ProcessRecordingStorageImpl.persistDocume ntVariables(ProcessRecordingStorageImpl.java:409)
    at com.adobe.idp.auditworkflow.dsc.service.storage.ProcessRecordingStorageImpl.serialize(Pro cessRecordingStorageImpl.java:390)
    at com.adobe.idp.auditworkflow.dsc.service.storage.ProcessRecordingStorageImpl.persist(Proce ssRecordingStorageImpl.java:151)
    at com.adobe.idp.auditworkflow.dsc.service.AuditWorkflowServiceImpl.auditEvent(AuditWorkflow ServiceImpl.java:62)
    at sun.reflect.GeneratedMethodAccessor1278.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at com.adobe.idp.dsc.component.impl.DefaultPOJOInvokerImpl.invoke(DefaultPOJOInvokerImpl.jav a:118)
    at com.adobe.idp.dsc.interceptor.impl.InvocationInterceptor.intercept(InvocationInterceptor. java:140)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor$1.doInTransaction(Transa ctionInterceptor.java:74)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.execute(EjbTr ansactionCMTAdapterBean.java:342)
    at com.adobe.idp.dsc.transaction.impl.ejb.adapter.EjbTransactionCMTAdapterBean.doRequiresNew (EjbTransactionCMTAdapterBean.java:284)
    at sun.reflect.GeneratedMethodAccessor236.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
    at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:214)
    at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:149)
    at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:154)
    at org.jboss.webservice.server.ServiceEndpointInterceptor.invoke(ServiceEndpointInterceptor. java:54)
    at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:48)
    at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:106)
    at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:389)
    at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:166)
    at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:153)
    at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192)
    at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:122)
    at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624)
    at org.jboss.ejb.Container.invoke(Container.java:873)
    at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:415)
    at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:88)
    at $Proxy169.doRequiresNew(Unknown Source)
    at com.adobe.idp.dsc.transaction.impl.ejb.EjbTransactionProvider.execute(EjbTransactionProvi der.java:143)
    at com.adobe.idp.dsc.transaction.interceptor.TransactionInterceptor.intercept(TransactionInt erceptor.java:72)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.interceptor.impl.InvocationStrategyInterceptor.intercept(InvocationStra tegyInterceptor.java:55)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.interceptor.impl.InvalidStateInterceptor.intercept(InvalidStateIntercep tor.java:37)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.interceptor.impl.AuthorizationInterceptor.intercept(AuthorizationInterc eptor.java:109)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.interceptor.impl.JMXInterceptor.intercept(JMXInterceptor.java:48)
    at com.adobe.idp.dsc.interceptor.impl.RequestInterceptorChainImpl.proceed(RequestInterceptor ChainImpl.java:60)
    at com.adobe.idp.dsc.engine.impl.ServiceEngineImpl.invoke(ServiceEngineImpl.java:115)
    at com.adobe.idp.dsc.routing.Router.routeRequest(Router.java:118)
    at com.adobe.idp.dsc.provider.impl.base.AbstractMessageReceiver.routeMessage(AbstractMessage Receiver.java:91)
    at com.adobe.idp.dsc.provider.impl.vm.VMMessageDispatcher.doSend(VMMessageDispatcher.java:21 5)
    at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispat cher.java:57)
    at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)
    at com.adobe.workflow.audit.WorkflowAudit.invokeCallback(WorkflowAudit.java:471)
    at com.adobe.workflow.audit.WorkflowAudit.breakpointRouteEvaluationCompleted(WorkflowAudit.j ava:268)
    at com.adobe.workflow.engine.PEUtil.evaluateRules(PEUtil.java:425)
    at com.adobe.workflow.engine.SynchronousBranch.getNextActionOrStallOnFailure(SynchronousBran ch.java:801)
    at com.adobe.workflow.engine.SynchronousBranch.updateBranchInstanceStatus(SynchronousBranch. java:649)
    at com.adobe.workflow.engine.SynchronousBranch.execute(SynchronousBranch.java:887)
    at com.adobe.workflow.engine.ProcessEngineBMTBean.continueBranchAtAction(ProcessEngineBMTBea n.java:2773)
    at com.adobe.workflow.engine.ProcessEngineBMTBean.asyncInvokeProcessCommand(ProcessEngineBMT Bean.java:704)
    at sun.reflect.GeneratedMethodAccessor503.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
    at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(StatelessSessionConta iner.java:214)
    at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:149)
    at org.jboss.webservice.server.ServiceEndpointInterceptor.invoke(ServiceEndpointInterceptor. java:54)
    at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValidationInterceptor.java:48)
    at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:106)
    at org.jboss.ejb.plugins.AbstractTxInterceptorBMT.invokeNext(AbstractTxInterceptorBMT.java:1 58)
    at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBMT.java:62)
    at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(StatelessSessionInstance Interceptor.java:154)
    at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.java:153)
    at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192)
    at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor. java:122)
    at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624)
    at org.jboss.ejb.Container.invoke(Container.java:873)
    at org.jboss.ejb.plugins.local.BaseLocalProxyFactory.invoke(BaseLocalProxyFactory.java:415)
    at org.jboss.ejb.plugins.local.StatelessSessionProxy.invoke(StatelessSessionProxy.java:88)
    at $Proxy202.asyncInvokeProcessCommand(Unknown Source)
    at com.adobe.workflow.engine.ProcessCommandControllerBean.doOnMessage(ProcessCommandControll erBean.java:156)
    at com.adobe.workflow.engine.ProcessCommandControllerBean.onMessage(ProcessCommandController Bean.java:99)
    at sun.reflect.GeneratedMethodAccessor457.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:585)
    at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
    at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke(MessageDrivenContainer.j ava:475)
    at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionI nterceptor.java:149)
    at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(MessageDrivenInstanceInterc eptor.java:101)
    at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterceptor.java:106)
    at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptorCMT.java:335)
    at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:166)
    at org.jboss.ejb.plugins.RunAsSecurityInterceptor.invoke(RunAsSecurityInterceptor.java:94)
    at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:192)
    at org.jboss.ejb.MessageDrivenContainer.internalInvoke(MessageDrivenContainer.java:389)
    at org.jboss.ejb.Container.invoke(Container.java:873)
    at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainerInvoker.java:1077)
    at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl.onMessage(JMSContainerI nvoker.java:1379)
    at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:256)
    at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:904 )
    at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:160)
    at org.jboss.mq.SpySession.run(SpySession.java:333)
    at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:180)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
    at java.lang.Thread.run(Thread.java:595)
It turns out that this error is related to the recording of the process. When I stop the recording, this error disappears. Do you have any idea on what goes wrong ? Did I miss something or made something wrong ?
I attached the component.xml file of the component to this post.
Thank you in advance
Steve

This seems to be recorded in CAR#405941. The whole thing is a bit strange but I will try to go over the potential workarounds as best as I can. I tested a lot of these myself and here is what I found.
1. Make sure the custom control you have made was created in LabVIEW 2012 or you save it to a previous version. If you save it to a previous version you might also need to open the .ctl in LabVIEW 2012 and resave it (I needed to do this). I tried creating my own control in 2012 as well as saving the control to a previous version, both worked but I did not end up with the same result (I don't understand this but I wanted to mention it so that you knew).
2. It seems that you are able to make the shared variable programmatically by modifying the community example to fit your needs. If you do not need to create many variables this may be the best option if it works for you.
I would also try adding the variable from the LabVIEW project you are working on. This was not a direct troubleshooting step but there are multiple ways to do things in LabVIEW and sometimes one of them works while the other does not.
Edit: Community Example is here https://decibel.ni.com/content/docs/DOC-16863
Matt J
Professional Googler and Kudo Addict
National Instruments

Similar Messages

Version number conflicts with NI custom data types

Custom data type version number conflicts
Options
Mark as New
Bookmark
Subscribe
Subscribe to RSS Feed
Highlight
Print
Email to a Friend
Report to a Moderator
07-11-2011 08:10 AM
I am new to Teststand software interface. While doing my first software release under the guidance of a more experienced colleague, we discovered that Teststand will not run if it detects version number conflicts between custom data types on my machine vs. the production test machine. I verified differences between all .seq files in my test program directory, but I did not realize that the version number difference exists in the StationGlobals.ini file, which is stored in a different location. After discovering this, I modified the version number in one of the files. However, two releases later, I discovered that the version number mismatches in another two files. This raises several questions for me :
1. Is there a way in Teststand to view all the .seq files where a custom data type is used and then change its version number in one attempt?
2. Under what instances does Teststand upgrade the version number of a custom data type?
3. Are there any tools or scripts within Teststand that can allow the version number of custom data types to be changed in all .ini files when a difference is discovered between the current production test station settings and a new release?
Please help.

Have you read this? http://zone.ni.com/devzone/cda/tut/p/id/7060
I can tell you that your situation is not uncommon with TestStand. The key is just doing it right the first time. haha
#1- I doubt that this is possible because then TestStand would have to know every location of every .seq on the machine. You will only see it when you open the sequence file.
#2- TestStand updates the version every time you change it. You should get a message popup when you try to save that asks if you want to increment the version or not. There's also a check box that says Remove Modified Mark From Types. Look under Station Options in the File tab. There are some settings there about Type conflicts.
#3- http://zone.ni.com/devzone/cda/tut/p/id/7910
http://digital.ni.com/public.nsf/allkb/4153576DA04BEB098625743D00704A09
Hope this helps,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Error while calling badi using class cl_exithandler with getInstance

hi experts...we are using SAP ECC 6.0 version
I have created BADI Def   and Implementation using se18   and se19 with some interface methods..
Problem:
I'm writing a report to call that using class CL_EXITHANDLER but it shows an Exception..
" Exception condition "DATA_INCONS_IN_EXIT_MANAGEM" raised."
Report example:
DATA: CL_EXIT TYPE REF TO CL_EXITHANDLER,
      IF_USER_INSTANCE TYPE REF TO ZIF_EX_USER_MAILID1.
CALL METHOD cl_exithandler=>get_instance
EXPORTING
   EXIT_NAME                       = 'ZBADI_USERMAIL_DEF'
*    NULL_INSTANCE_ACCEPTED        = SEEX_FALSE
* IMPORTING
*    ACT_IMP_EXISTING              =
CHANGING
    instance                       = IF_USER_INSTANCE
* EXCEPTIONS
*    NO_REFERENCE                  = 1
*    NO_INTERFACE_REFERENCE        = 2
*    NO_EXIT_INTERFACE             = 3
*    CLASS_NOT_IMPLEMENT_INTERFACE = 4
*    SINGLE_EXIT_MULTIPLY_ACTIVE   = 5
*    CAST_ERROR                    = 6
*    EXIT_NOT_EXISTING             = 7
*    DATA_INCONS_IN_EXIT_MANAGEM   = 8
*    others                        = 9
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
so i found that all EXITs are in the Table " SXS_ATTR"
but what i have created BADI has not exist in that Table so that it gets an Exception(while i'm debugging found this)
so kindly tel me whats problem my BADI "ZBADI_USERMAIL_DEF" not maintained that Database table
but in Implentation class its working fine..

yes i have created badi in Enhancement spot so regarding what u told i'm using GET BADI and CALL BADI
DATA:W_HANDLE TYPE REF TO ZBADI_USERMAIL_DEF.
GET BADI W_HANDLE.
CALL BADI w_handle->get_user_mailid
EXPORTING
    uname = UNAME
changing
    mailid = W_EMAIL
WRITE: / 'UNAME:',UNAME.
WRITE: / 'EMAIL ID',W_EMAIL.
CALL BADI w_handle->get_user_address_data
EXPORTING
    uname    = UNAME
changing
    addrdata = W_ADDRDATA
IF W_ADDRDATA IS NOT INITIAL.
WRITE: / W_ADDRDATA-BNAME,W_ADDRDATA-NAME1,W_ADDRDATA-NAME2,W_ADDRDATA-TELPR,W_ADDRDATA-TELNR,W_ADDRDATA-TEL01.
ENDIF.
but here BADI are not called
Interface implementation class methods not executed so kindly tel me whats problem here.
Thanks in Advance
sivakumar

Error while importing process flow mdls in OWB 11.2.0.3

Hi All,
I am facing below error while importing process flow mdls in OWB 11.2.0.3:
ERROR
Informational: MDL1328: PROJECT MTH not imported since the object in MDL file
is the same as the object in the workspace.
Error at line 11: MDL1261: Error importing PROCESS_FLOW_MODULE MTH.MTH_PF.
Detailed Error Message:
MDL1409: Cannot import PROCESS_FLOW_MODULE with physical name <MTH_PF>
because a PROCESS_FLOW_MODULE <MTH_PF> with the same physical name already
exists.
Can someone please let me know on how this can be resolved.
Thanks in Advance.

the first information warning message is ok, the 2nd ones should be gone if you use the replace mode
OMBIMPORT FROM MDL_FILE 'pfm_mod.mdl' USE REPLACE_MODE MATCH_BY NAMES
let me know if that fix it

Error while migrating users using CSSImportExportUtility

Error while migrating users using CSSImportExportUtility
I'm tring to export all user and group information from a Hyperion Shared Services 9.2.1 by using CSSExport.bat
When there was only native directory in HSS, i can export these information successfully.
But when I enabled NTLM external user authentication following error occurred:
Exception in thread "main" java.lang.UnsatisfiedLinkError: getOSVersion
at com.hyperion.css.spi.impl.ntlm.NTLMProvider.getOSVersion(Native Metho
d)
at com.hyperion.css.spi.impl.ntlm.NTLMProvider.<clinit>(Unknown Source)
at com.hyperion.css.spi.impl.ntlm.NTLMConnectionClient.getUsers(Unknown
Source)
at com.hyperion.css.CSSAPIExtnImpl.getUsers(Unknown Source)
at com.hyperion.css.CSSAPIImpl.getUsers(Unknown Source)
at com.hyperion.css.CSSAPIImpl.initialize(Unknown Source)
at com.hyperion.css.exchange.NativeProviderManager.<init>(Unknown Source
at com.hyperion.css.exchange.ImportExportManager.cssExport(Unknown Sourc
e)
at com.hyperion.css.exchange.CommandUtility.run(Unknown Source)
at com.hyperion.css.exchange.CommandUtility.main(Unknown Source)
I searched reference documents on the web, found this article: (http://download.oracle.com/docs/cd/E12825_01/epm.111/readme/mdm_111110_readme.html)
Troubleshooting Tip: If HSS is configured for an NTLM provider, DRM services may not start due to error: "Exception Emdm_Exception with message 'Could not Initialize CSS. Error: 'getOSVersion'."
You may receive the following error after clicking the "Enable CSS" button in DRM Console: “LoadLibrary("C:\Hyperion\Master Data Management\mdm_ntier_css_validator.dll") failed - The specified module could not be found.”
To resolve both of these conditions, update the Windows System Path on the Data Relationship Management server with the applicable JRE and CSS pathing below.
NOTE: Reboot the Data Relationship Management server machine after making any changes to the Windows Path.
NOTE: Ensure that only one JRE version and one CSS version are referenced in the Windows Path.
? For HSS 9.3.1:
%HYPERION_HOME%\common\JRE\Sun\1.5.0\bin;%HYPERION_HOME%\common\JRE\Sun\1.5.0\bin\client;%HYPERION_HOME%\common\CSS\9.3.1\bin;
? For HSS 9.3.0:
%HYPERION_HOME%\common\JRE\Sun\1.5.0\bin;%HYPERION_HOME%\common\JRE\Sun\1.5.0\bin\client;%HYPERION_HOME%\common\CSS\9.3.0\bin;
? For HSS 9.2.0.3:
%HYPERION_HOME%\common\JDK\Sun\1.4.2\jre\bin;%HYPERION_HOME%\common\JDK\Sun\1.4.2\jre\bin\client;%HYPERION_HOME%\common\CSS\9.2.0.3\bin;
? For HSS 9.2.0:
%HYPERION_HOME%\common\JDK\Sun\1.4.2\jre\bin;%HYPERION_HOME%\common\JDK\Sun\1.4.2\jre\bin\client;%HYPERION_HOME%\common\CSS\9.2.0\bin;
I found these is no directory "%HYPERION_HOME%\common\CSS\9.2.0\bin;" exists but "%HYPERION_HOME%\common\CSS\9.2.1\bin;"
I configured PATH by setting to above, and tried CSSExport again, still failed.
Than I disabled the NTLM is HSS, tried CSSExport again. It was successful.
So I am convinced that the problem caused by NTLM or PATH environment variable or some files associated.
Does anybody know the solution ?

I recommend you upgrade at least to 10.1.0.5. 10.1.0.2 comes with the very first version of csalter.plb, which has not the current implementation. From and to which character set do you try to migrate?
-- Sergiusz

Error while Loading Budgets Using AMG

Error while Loading Budgets Using AMG
Dear All,
I am trying to load Budgets into ORACLE Projects using AMG API's..
I have developed PL/SQL which uses below procedures of pa_budget_pub package.
init_budget;
load_budget_line;
execute_draft_budget;
baseline_budget;
Procedure execute_create_draft_budget fails with following error message.
error message: Please enter a valid product code for this project.
error message: You entered an invalid API parameter.Please enter valid parameter and try again. Parameter Name: Resource List Parameter Value: 1446
error message: Project: AC044. Please specify a valid resource list.
error message: Project: AC044. Please specify a valid resource list.
Could somebody explain me how to resolve this error message and load the budget lines.
Thanks in Advance.
Afsal Basha.

What I'm saying is, verify the column name. Dont post if not possible.
Example follows, with one table intentionally "hidden".
SQL> create table "tEsT" ("MaxNumber" float, "MaxnumbeR" number);
SQL> select table_name,column_name from user_tab_columns where table_name like 't%';
TABLE_NAME                     COLUMN_NAME
tEsT                           MaxNumber
tEsT                           MaxnumbeR
teST                           iD
teST                           MaxNumberHth,
Fredrik

Error while deploying process flow

hi All,
i am getting below error while deploying 1 process flow.
Description : Runtime User : OWBPC Started : 2011-06-02 19:18:06.0
Name Action Status Log
None Error ORA-00942: table or view does not exist
None Error RPE-02053: The Oracle Workflow version cannot be retrieved. This may have been caused by an incomplete or incorrect installation of Oracle Workflow or the schema may not contain an Oracle Workflow repository. Please check the location details, reinstall Oracle Workflow, if necessary and try again
i added only 1 mapping in process flow and mapping containing both tables in taret schema.
kindly tell me how to fix it.?
rgds,
Pc

hi..thnx for replying..
i have already installed owf manager from below location in my pc..
D:\app\pc\product\11.1.0\db_1\owb\wf\install
and installation was successful..then too I am getting same error while deploying process flow.. im using oracle 11g.. direct me now plz..
Edited by: PC on Jun 3, 2011 3:48 PM

JSPM: Error while detecting start profile for instance with ID _c.

Hi Experts,
we have an error when we start JSPM with message "cannot initialize application data. Error while detecting start profile for instance with ID _c." . Until now nothing has been updated yet. The system can be started up and shut down without any problem. The profiles are found in /usr/sap/PMA/SYS/profile
Our BI system is currently Netweaver 7.0 with SPS14. We plan to update it to SPS20. But when we start JSPM, we have abover error.
could somebody give a help? Thank you very much.
Rongfeng
P.S. the log file DETECT_SYSTEM_PARAMETERS_01.LOG:
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/log/log_2009_11_18_10_28_50/DETECT_SYSTEM_PARAMETERS_01.LOG]/>
<!PATTERN[DETECT_SYSTEM_PARAMETERS_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
#1.5^H#C000995FC0200000000000207BD47BD40004789C01294DB0#1258511336558#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:397)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:397)#Java###Initializing JSPM data model...##
#1.5^H#C000995FC0200000000000217BD47BD40004789C01295968#1258511336561#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.detectProfileDirectory(InitialParametersDetector.java:1468)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectProfileDirectory(InitialParametersDetector.java:1468)#Java###Detected profile directory .#1#/usr/sap/PMA/SYS/profile#
#1.5^H#C000995FC0200000000000227BD47BD40004789C0141AFE0#1258511338156#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:936)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:936)#Java###Detecting the parameters of the database...##
#1.5^H#C000995FC0200000000000237BD47BD40004789C014205D0#1258511338178#/System/Server/Upgrade/JSPM##com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:261)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:261)#Java###Executing command with arguments .#2#dbinfo#/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/config/DBINFO.XML#
#1.5^H#C000995FC0200000000000247BD47BD40004789C01421570#1258511338182#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#Java###Java process ID , name has been started.#2#5#com.sap.sdt.dmt.main.DMT#
#1.5^H#C000995FC0200000000000257BD47BD40004789C01421958#1258511338183#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#Java###Command line: #2# #/opt/IBMJava2-amd64-142/jre/bin/java -cp .:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/sdt_dmt.jar:/oracle/client/10x_64/instantclient/ojdbc14.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/jddi.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/opensqlsta.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/tc_sec_secstorefs.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/frame.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/exception.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/logging.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/jperflib.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/lib/util.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/tc_sec_secstorefs.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/exception.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/logging.jar:/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/./lib/opensqlsta.jar:/sapmnt/PMA/global/security/lib/tools/info/IAIKSecurityFS.list:/sapmnt/PMA/global/security/lib/tools/iaik_jce.jar:/sapmnt/PMA/global/security/lib/tools/iaik_smime.jar:/sapmnt/PMA/global/security/lib/tools/iaik_jsse.jar:/sapmnt/PMA/global/security/lib/tools/w3c_http.jar:/sapmnt/PMA/global/security/lib/tools/iaik_ssl.jar:/sapmnt/PMA/global/security/lib/engine/info/IAIKSecurityFS.list:/sapmnt/PMA/global/security/lib/engine/iaik_jce.jar com.sap.sdt.dmt.main.DMT -rootdir=/usr/sap/PMA/DVEBMGS10/j2ee/JSPM -descriptor=csrt29_PMA -logfile=/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/log/log_2009_11_18_10_28_50/DMT_01.LOG dbinfo /usr/sap/PMA/DVEBMGS10/j2ee/JSPM/config/DBINFO.XML#
#1.5^H#C000995FC0200000000000267BD47BD40004789C01422128#1258511338185#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#Java###Standard out: #2# #/usr/sap/PMA/DVEBMGS10/j2ee/JSPM/log/log_2009_11_18_10_28_50/DMT_01_01.OUT#
#1.5^H#C000995FC0200000000000277BD47BD40004789C01424838#1258511338195#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:126)#Java###Process ID has been started.#1#5#
#1.5^H#C000995FC0200000000000287BD47BD40004789C014253F0#1258511338198#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:182)#Java###Waiting for process ID , name to finish.#2#5#java#
#1.5^H#C000995FC0200000000000297BD47BD40004789C017402B0#1258511341454#/System/Server/Upgrade/JSPM##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:215)#Java###Process ID , name has been finished, exit code .#3#5#java#0#
#1.5^H#C000995FC02000000000002A7BD47BD40004789C01741638#1258511341459#/System/Server/Upgrade/JSPM##com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:273)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:273)#Java###Command has been executed.#1#dbinfo#
#1.5^H#C000995FC02000000000002B7BD47BD40004789C017421F0#1258511341462#/System/Server/Upgrade/JSPM##com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:984)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectDb(InitialParametersDetector.java:984)#Java###Detection of the parameters of the database has finished. Database type is , database name is and database version is .#3#ORA#Oracle#10.2.0.2.0#
#1.5^H#C000995FC02000000000002C7BD47BD40004789C01744CE8#1258511341473#/System/Server/Upgrade/JSPM##com.sap.sdt.j2ee.tools.sysinfo.AbstractInfoController.updateProfileVariable(AbstractInfoController.java:284)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sysinfo.AbstractInfoController.updateProfileVariable(AbstractInfoController.java:284)#Java###Parameter has been detected. Parameter value is .#2#/J2EE/StandardSystem/DefaultProfilePath#/usr/sap/PMA/SYS/profile/DEFAULT.PFL#
Sorry, I don't know how to format post
Edited by: Rongfeng Shi on Nov 18, 2009 4:20 AM

Hi Rongfeng,
There is not much information about the error in the log file you have pasted above.
Please repeat the issue and catch the log files once again.
Are you able to open SDM ?
Best Regards
Raghu

Getting error while publishing workflow using SP designer for SharePoint 2013

Hi,
I am try to setup Workflow manager for our sharepoint applications.
WF manager set ran without any issue.
I registered the SPWorkflow service which succeeded as well. The Workflow service application shows "Workflow is connected"
I am creating a workflow using sharepoint designer using my credential (not Service account). I am able to save it but while publishing, its prompting with an error.
The error says "Errors were found while compiling the workflow.The workflow files were saved but cannot run." Clicking advanced button show
"Microsoft.SharePoint.SPException: We're sorry, we weren't able to complete the operation, please try again in a few minutes. If you see this message repeatedly, contact your administrator.
at Microsoft.SharePoint.SPScaleOutDatabaseMap.CreateSqlSession(ISPScaleOutDatabaseMapProvider mapProvider, Byte[] compositeKey, Guid forceRefreshVersion, Guid& version)
at Microsoft.SharePoint.SPScaleOutDatabaseCommandExecutor.Execute(ExecuteDelegate operation, ISPScaleOutDatabaseMapProvider mapProvide"
Any help would be highly appreciated
Thanks,

Hi,
According to your post, my understanding is that you got error while publishing workflow using SharePoint designer for SharePoint 2013.
Please check whether the Central Admin > Manage Service Application-> “App Management Service” is started.
Please check whether the “Configure service application associations”, ”App Management Service” is already associated.
Then please check whether the “Manage Services on server” and the “App Management Service” is started.
In addition, please try to re-register Workflow Service.
If the issues still exists, please follow the steps in the
Steps to Verify that Server Is Correctly Set Up. After you verified that the server is correctly set up, follow the steps in the
Steps to Troubleshoot Workflow Management Service and
Troubleshooting the Service Bus for Windows Server then retry your action related to publishing workflows
More information:
http://wp.ahcheng.com/2013/03/23/error-were-found-when-compiling-the-workflow-the-workflow-files-were-saved-but-cannot-be-run/
http://sp2013.pro/2013/04/solution-errors-were-found-when-compiling-the-workflow-the-workflow-files-were-saved-but-cannot-be-run-cannot-set-unknown-member/
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Error while trying to use '{' in the query

Hi,
The below mentioned query is giving Error while trying to use '{'
Query:
select s,x from table(SEM_MATCH(
'{?s rdf:type <http://www.cs.com/sbip/dwh/mdm/data_modeling#Base_Term> .
?s ?p ?x}',
SEM_Models('foundation'),
SEM_RuleBases('OWLPRIME'),
SEM_ALIASES(SEM_ALIAS('dm','http://www.cs.com/sbip/dwh/mdm/data_modeling#'),
SEM_ALIAS('owl','http://www.w3.org/2002/07/owl#')), null, 'INVALID'))
where regexp_like(x,'Customers','i');
Error details:
ORA-29532: Java call terminated by uncaught Java exception: oracle.spatial.rdf.server.TokenMgrError: Lexical error at line 1, column 1. Encountered: "{" (123), after : ""
ORA-06512: at "MDSYS.RDF_MATCH_IMPL_T", line 178
ORA-06512: at "MDSYS.RDF_MATCH_IMPL_T", line 67
ORA-06512: at line 4
I am unable to use Option, Filter in query.
Any solution?
Please let me know do i need to apply any patch?
Note: I am using Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
Regards,
Kavitha.

Hi,
For OPTIONAL support in 11.1.0.7.0, you need the following patch
Patch 7600122: CURLY BRACE SYNTAX,VIRTUAL MODELS, NETWORK INDEXES AND HINTO FRAMEWORK SUPPORT
Support for SPARQL FILTERs in SEM_MATCH is not available for 11.1.0.7.0. You will need version 11.2.0.1.0 or later for FILTER support. With 11.2.0.1.0, we recommend that you apply our latest patch set:
Patch 9819833: SEMANTIC TECHNOLOGIES 11G R2 FIX BUNDLE 2
All of the above patches are available through My Oracle Support.
Thanks,
Matt

Error while executing SAP E-Commerce Application with UME system

When attempting to login to the B2B application (http://hostname:port/b2b/init.do), we receive the following error:
Error while executing SAP E-Commerce Application with UME system; try again to log on. If the problem persists, call our hotline.
I checked the defaultTrace log and every time the login page is called the following messages are displayed:
#System.err#sap.com/crm~b2b#System.err#Guest#0##n/a##70cf2ba0756b11df86050003ba827311#SAPEngine_Application_Thread[impl:3]_0##0#0#Error##Plain###com.sap.engine.services.servlets_jsp.server.exceptions.WebIllegalStateException: The output is committed.
#System.err#sap.com/crm~b2b#System.err#Guest#0##n/a##70cf2ba0756b11df86050003ba827311#SAPEngine_Application_Thread[impl:3]_0##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:354)#
another 40 lines of similar text
When a login is attempted, the following messages are appended to the trace file:
#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#Guest#0##n/a##f6384ec0756b11df81380003ba827311#SAPEngine_Application_Thread[impl:3]_0##0#0#Debug##Plain###[actionxecution]='begin' [actionclass]='com.sap.isa.user.action.PrepareLoginBaseAction' [path]='/preparelogin'#
tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#USER1#7439##n/a##f6384ec0756b11df81380003ba827311#SAPEngine_Application_Thread[impl:3]_0##0#0#Debug##Plain###[actionxecution]='end' [actionclass]='com.sap.isa.user.action.PrepareLoginBaseAction' [path]='/preparelogin' [forward]='/login.do' [exectime]='42'#
#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#USER1#7439##n/a##f6384ec0756b11df81380003ba827311#SAPEngine_Application_Thread[impl:3]_0##0#0#Debug##Plain###[jcofuncionexecution]='begin' [funcname]='CRM_ISA_SSO_LOGIN_CHECKS' [ashost]='<hostname>' [sysid]='CRM'#
#tracing.isa.runtime#sap.com/crm~b2b#tracing.isa.runtime#USER1#7439##<hostname>_CJM_678801250#USER1#f6384ec0756b11df81380003ba827311#SAPEngine_Application_Thread[impl:3]_0##0#0#Debug##Plain###[jcofunctionexecution]='end' [funcname]='CRM_ISA_SSO_LOGIN_CHECKS' [ashost]='<hostname>' [sysid]='CRM' [exectime]='12'#
I have modified the userid and hostname in the above trace output.
Does anyone know how we can debug this issue further?
Thanks,
Setu

Hi,
Are you using UME login type for your B2B Scenario?
In your B2B XCM setting have you selected UME related login type?
eCommerce Developer

Unknown error while updating module use!

I restarted XE with "/etc/init.d/oracle-xe stop /etc/init.d/oracle-xe start" and then see this error message in the terminal console. Every serveral minutes, the error "Unknown error while updating module use!" is echoed.
Any advice?

Look for the alert_xe.log file, maybe you'll find some additional information there if that message is related to your XE instance.
C.

Error while creating stock using tcode: MB1C

Error while creating stock using tcode: MB1C
The Error is: Check table T004F:entry G006 does not exist

Hi ,
Please check the FSV (field status variant) for your company code in OBY6 .
then go to transaction code OB14 --> enter the FSV --> Check if field status group G006(Material account) is maintained there or not.
if not please maintain it.
Thanks & Regards
Anshu

Getting error while creating subsite using custom template in sharepoint2013

Hi,
I am getting the following error while creating subsite using custom template in sharpoint2013. even publish features are enabled.
Please suggest me on this.
Thanks in advance.

You need to enable the PerformancePoint Service Site Collection Features(PPSMonDatasourceCtype)
on the target site collection. go to site action > site settings> site collections features > and enable it and now try again.
Similar case: http://imughal.wordpress.com/2012/09/20/dependency-feature-ppsmondatasourcectype-id-05891451-f0c4-4d4e-81b1-0dabd840bad4-for-feature-bicenterdataconnections-id-3d8210e9-1e89-4f12-98ef-643995339ed4-is-not-activated-at-this-scop/
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

INVALID_QUEUE_NAME : Error while scheduling message using qRFC

Hello SDNers
We are currently performing our PI 7.1 upgrade and one of our scenario uses a Sender SOAP of the type EOIO. We tried executing this scenario in PI 7.1 XID environment and in it worked fine without any errors but in our PI 7.1 QA environment it is giving the following errors
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">SCHEDULE_ERROR</SAP:Code>
<SAP:P1>XBQOC___*</SAP:P1>
<SAP:P2>INVALID_QUEUE_NAME</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error while scheduling message using qRFC (queue name = XBQOC___*, exception = INVALID_QUEUE_NAME)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can you please exaplian what could be the issue we are facing.
Thanks.
Kiran
Edited by: Kiran Sakhardande on Oct 22, 2008 4:08 PM

HI Kiran,
Have gone throgh the following link?
INVALID_QUEUE_NAME
Regards
Sridhar Goli

Error while recording process using a component with a custom data type

Similar Messages

Maybe you are looking for