Wrong PageDef.xml during ReturnListener execution? Bug?
Hi Everyone,
JDeveloper 10.1.3.3.0
We're facing a strange issue, that we're not sure whether this is by design or whether this is a bug...
We have a commandLink with a returnListener on page yyy.jspx that calls another page via a dialog:xxx (useWindow=false).
On page xxx.jspx we have a af:returnActionListener on a command button that is set to return a value.
In the request backing bean on the returnListener from the commandLink on yyy.jspx, we add a call getBindings to get the BindingContainer to do some OperationBinding stuff. According to the debug on getBindings, it shows it is referring to xxxPageDef.xml instead of the yyyPageDef.xml, even though the returnListener is on a component in yyyPageDef.xml.
However, if we set the bindings value of an <attributeValues>, it happens on the perspective of yyyPageDef.xml
We'd like to know whether this is the proper behaviour before we go ahead and code the action bindings to the yyyPageDef while ignoring xxxPageDef. Otherwise, we'll need to put our calls in both xxx and yyy in case this gets changed in the future.
Is behaviour supposed to be different depending on whether the commandLink useWindow = true or false?
We believe that this Is this similar to the following thread.
Re: ADF BC : problem with binding when returning from dialog
Hi Frank,
I've checked further, and it is only a problem with <methodActions> when you are returning from a dialog that has useWindow = false.
yyy.jspx with yyyPageDef.xml calls xxx.jspx via a dialog with useWindow=false.
xxx.jspx returns using returnActionListener component.
yyy.jspx in the returnListener backing_bean code:
When you reference <attributeValues> you get them based on definitions in yyyPageDef.xml
When you reference <methodActions> you get them based on definitions in xxxPageDef.xml
We expected the <methodActions> to be calling methods defined in the yyyPageDef.xml, because the returnListener is on a component on yyy.jspx.
I think this is a bug, and is easily reproduced.
Similar Messages
-
An error has ocurred during the execution of the Extract_Rom
I have this problem
Trouble Ticket Report----
Upgrade to SAP NetWeaver'04s
SID................: J2E
Hostname...........: sapepd
Install directory..: d:/usr/sap/J2E
Upgrade directory..: D:\usr\sap\jupgrade
Database...........: Microsoft SQL Server
Operating System...: NT
JDK version........: 1.4.2_11 Sun Microsystems Inc.
SAPJup version.....: 1.1.101
Source release.....: 630
Target release.....: 700
Current usages.....: DI;EP;AS
ABAP stack present.: false
The execution of PREPARE/EXTRACT/EXTRACT_ROMS ended in error.
0 of 1 extractions have been successful. 1 extractions have not been
successful. See previous messages.
Could not extract AKK from mount point D:\DVD\51031778 Kernel7
\KU_WINDOWS_I386. See previous messages.
Could not execute file system operation with name Extract and
parameters archive:SAPEXE.SAR,
target_dir:D:\usr\sap\jupgrade\data\kernel.
The SAPCAR process has ended with an error exit code 6. See
D:\usr\sap\jupgrade\log\EXTRACT_SAPEXE.SAR_ROM_08.OUT.
More information can be found in the log file
D:\usr\sap\jupgrade\log\EXTRACT_ROMS_ROM_08.LOG.
Use the information provided to trouble-shoot the problem. There might
be an OSS note providing a solution to this problem. Search for OSS
notes with the following search terms:
com.sap.sdt.ucp.phases.PhaseTypeExtractRom
com.sap.sdt.ucp.tools.dda.ManagedRomsException
0 of 1 extractions have been successful. 1 extractions have not been
successful. See previous messages.
EXTRACT_ROMS
PREPARE
NetWeaver Upgrade
SAPJup
Java Upgrade
END of Trouble Ticket Report----
*******************BEGIN THE EXTRACT_ROMS_ROM_08.LOG********
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[D:\usr\sap\jupgrade\log\EXTRACT_ROMS_ROM_08.LOG]/>
<!PATTERN[EXTRACT_ROMS_ROM_08.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
#1.5#C000AC10C8070000000006E60010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:720)#Java###Phase has been started.#1#PREPARE/EXTRACT/EXTRACT_ROMS#
#1.5#C000AC10C8070000000006E70010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:721)#Java###Phase type is .#1#com.sap.sdt.ucp.phases.PhaseTypeExtractRom#
#1.5#C000AC10C8070000000006E80010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java### Parameter =#2#dialog#ExtractRom#
#1.5#C000AC10C8070000000006E90010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:345)#Java### Parameter =#2#romFile#RequiredRoms.xml#
#1.5#C000AC10C8070000000006EA0010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.PhaseTypeExtractRom.checkParameters(PhaseTypeExtractRom.java:696)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.PhaseTypeExtractRom.checkParameters(PhaseTypeExtractRom.java:696)#Java###Checking phase parameters .#2#dialog#romFile#
#1.5#C000AC10C8070000000006EB0010573800043525AE7C1868#1184335864273#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.PhaseTypeExtractRom.checkParameters(PhaseTypeExtractRom.java:702)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.PhaseTypeExtractRom.checkParameters(PhaseTypeExtractRom.java:702)#Java###Phase parameters have been checked. All required phase parameters have been set.#1#2#
#1.5#C000AC10C8070000000006F80010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031807JAva Components
LABEL.ASC#
#1.5#C000AC10C8070000000006F90010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
DVD
51031807JAva Components
LABELIDX.ASC#
#1.5#C000AC10C8070000000006FA0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031807JAva Components
J2EE_OSINDEP
LABEL.ASC#
#1.5#C000AC10C8070000000006FB0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
DVD
51031807JAva Components
J2EE_OSINDEP
LABELIDX.ASC#
#1.5#C000AC10C8070000000006FC0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031807JAva Components
J2EE_OSINDEP
UT_SRM
LABEL.ASC#
#1.5#C000AC10C8070000000006FD0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031807JAva Components
J2EE_OSINDEP
UT_SCM
LABEL.ASC#
#1.5#C000AC10C8070000000006FE0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031807JAva Components
J2EE_OSINDEP
UT_ERP
LABEL.ASC#
#1.5#C000AC10C8070000000006FF0010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031807JAva Components
J2EE_OSINDEP
UT_CRM
LABEL.ASC#
#1.5#C000AC10C8070000000007000010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
LABEL.ASC#
#1.5#C000AC10C8070000000007010010573800043525B1777E18#1184335914303#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
DVD
51031778 Kernel7
LABELIDX.ASC#
#1.5#C000AC10C8070000000007020010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_LINUX_X86_64
LABEL.ASC#
#1.5#C000AC10C8070000000007030010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_LINUX_X86_64_AUPG
LABEL.ASC#
#1.5#C000AC10C8070000000007040010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_WINDOWS_I386
LABEL.ASC#
#1.5#C000AC10C8070000000007050010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_WINDOWS_I386_AUPG
LABEL.ASC#
#1.5#C000AC10C8070000000007060010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_WINDOWS_IA64
LABEL.ASC#
#1.5#C000AC10C8070000000007070010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_WINDOWS_IA64_AUPG
LABEL.ASC#
#1.5#C000AC10C8070000000007080010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_WINDOWS_X86_64
LABEL.ASC#
#1.5#C000AC10C8070000000007090010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_WINDOWS_X86_64_AUPG
LABEL.ASC#
#1.5#C000AC10C80700000000070A0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_LINUX_X86_64
LABEL.ASC#
#1.5#C000AC10C80700000000070B0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_LINUX_X86_64_AUPG
LABEL.ASC#
#1.5#C000AC10C80700000000070C0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_WINDOWS_I386
LABEL.ASC#
#1.5#C000AC10C80700000000070D0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_WINDOWS_I386_AUPG
LABEL.ASC#
#1.5#C000AC10C80700000000070E0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_WINDOWS_IA64
LABEL.ASC#
#1.5#C000AC10C80700000000070F0010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_WINDOWS_IA64_AUPG
LABEL.ASC#
#1.5#C000AC10C8070000000007100010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_WINDOWS_X86_64
LABEL.ASC#
#1.5#C000AC10C8070000000007110010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_WINDOWS_X86_64_AUPG
LABEL.ASC#
#1.5#C000AC10C8070000000007120010573800043525B177B8B0#1184335914318#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:95)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:95)#Java###Validatable parameter has been validated by validator .#2#DVDMountPointTable#DVDMountPointTable#
#1.5#C000AC10C8070000000007130010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031807JAva Components
LABEL.ASC#
#1.5#C000AC10C8070000000007140010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
DVD
51031807JAva Components
LABELIDX.ASC#
#1.5#C000AC10C8070000000007150010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031807JAva Components
J2EE_OSINDEP
LABEL.ASC#
#1.5#C000AC10C8070000000007160010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
DVD
51031807JAva Components
J2EE_OSINDEP
LABELIDX.ASC#
#1.5#C000AC10C8070000000007170010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031807JAva Components
J2EE_OSINDEP
UT_SRM
LABEL.ASC#
#1.5#C000AC10C8070000000007180010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031807JAva Components
J2EE_OSINDEP
UT_SCM
LABEL.ASC#
#1.5#C000AC10C8070000000007190010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031807JAva Components
J2EE_OSINDEP
UT_ERP
LABEL.ASC#
#1.5#C000AC10C80700000000071A0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031807JAva Components
J2EE_OSINDEP
UT_CRM
LABEL.ASC#
#1.5#C000AC10C80700000000071B0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
LABEL.ASC#
#1.5#C000AC10C80700000000071C0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processIndexFile(RomManager.java:285)#Java###Label index file found.#1#D:
DVD
51031778 Kernel7
LABELIDX.ASC#
#1.5#C000AC10C80700000000071D0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_LINUX_X86_64
LABEL.ASC#
#1.5#C000AC10C80700000000071E0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_LINUX_X86_64_AUPG
LABEL.ASC#
#1.5#C000AC10C80700000000071F0010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_WINDOWS_I386
LABEL.ASC#
#1.5#C000AC10C8070000000007200010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_WINDOWS_I386_AUPG
LABEL.ASC#
#1.5#C000AC10C8070000000007210010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_WINDOWS_IA64
LABEL.ASC#
#1.5#C000AC10C8070000000007220010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_WINDOWS_IA64_AUPG
LABEL.ASC#
#1.5#C000AC10C8070000000007230010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_WINDOWS_X86_64
LABEL.ASC#
#1.5#C000AC10C8070000000007240010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KN_WINDOWS_X86_64_AUPG
LABEL.ASC#
#1.5#C000AC10C8070000000007250010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_LINUX_X86_64
LABEL.ASC#
#1.5#C000AC10C8070000000007260010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_LINUX_X86_64_AUPG
LABEL.ASC#
#1.5#C000AC10C8070000000007270010573800043525B177F730#1184335914334#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_WINDOWS_I386
LABEL.ASC#
#1.5#C000AC10C8070000000007280010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_WINDOWS_I386_AUPG
LABEL.ASC#
#1.5#C000AC10C8070000000007290010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_WINDOWS_IA64
LABEL.ASC#
#1.5#C000AC10C80700000000072A0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_WINDOWS_IA64_AUPG
LABEL.ASC#
#1.5#C000AC10C80700000000072B0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_WINDOWS_X86_64
LABEL.ASC#
#1.5#C000AC10C80700000000072C0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.dda.RomManager.processLabelFile(RomManager.java:340)#Java###Label file found.#1#D:
DVD
51031778 Kernel7
KU_WINDOWS_X86_64_AUPG
LABEL.ASC#
#1.5#C000AC10C80700000000072D0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:139)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:139)#Java###Process ID , name has been started.#2#36#SAPCAR#
#1.5#C000AC10C80700000000072E0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:141)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:141)#Java###Command line: #2# #D:
usr
sap
jupgrade
exe
SAPCAR -xvf D:/DVD/51031778 Kernel7/KU_WINDOWS_I386/DBINDEP/SAPEXE.SAR -R D:
usr
sap
jupgrade
data
kernel#
#1.5#C000AC10C80700000000072F0010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:142)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:142)#Java###Standard out: #2# #D:
usr
sap
jupgrade
log
EXTRACT_SAPEXE.SAR_ROM_08.OUT#
#1.5#C000AC10C8070000000007300010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##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#36#
#1.5#C000AC10C8070000000007310010573800043525B17835B0#1184335914350#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##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#36#SAPCAR#
#1.5#C000AC10C8070000000007320010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##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#36#SAPCAR#6#
#1.5#C000AC10C8070000000007330010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.extract.SapcarArchiveHandler.checkExitCode(SapcarArchiveHandler.java:201)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.extract.SapcarArchiveHandler.checkExitCode(SapcarArchiveHandler.java:201)#Java###The SAPCAR process has ended with an error exit code 6. See D:
usr
sap
jupgrade
log
EXTRACT_SAPEXE.SAR_ROM_08.OUT.##
#1.5#C000AC10C8070000000007340010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.extract.AbstractExtractOperation.generateExtractExecutionException(AbstractExtractOperation.java:229)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.extract.AbstractExtractOperation.generateExtractExecutionException(AbstractExtractOperation.java:229)#Java###Could not execute file system operation with name Extract and parameters archive:SAPEXE.SAR, target_dir:D:
usr
sap
jupgrade
data
kernel.##
#1.5#C000AC10C8070000000007350010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:231)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:231)#Java###Could not extract AKK from mount point D:
DVD
51031778 Kernel7
KU_WINDOWS_I386. See previous messages.##
#1.5#C000AC10C8070000000007360010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:748)#Java###Exception has occurred during the execution of the phase.##
#1.5#C000AC10C8070000000007370010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.extract.SapcarArchiveHandler.checkExitCode(SapcarArchiveHandler.java:201)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.extract.SapcarArchiveHandler.checkExitCode(SapcarArchiveHandler.java:201)#Java###The SAPCAR process has ended with an error exit code 6. See D:
usr
sap
jupgrade
log
EXTRACT_SAPEXE.SAR_ROM_08.OUT.##
#1.5#C000AC10C8070000000007380010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.tools.extract.AbstractExtractOperation.generateExtractExecutionException(AbstractExtractOperation.java:229)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.extract.AbstractExtractOperation.generateExtractExecutionException(AbstractExtractOperation.java:229)#Java###Could not execute file system operation with name Extract and parameters archive:SAPEXE.SAR, target_dir:D:
usr
sap
jupgrade
data
kernel.##
#1.5#C000AC10C8070000000007390010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:231)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:231)#Java###Could not extract AKK from mount point D:
DVD
51031778 Kernel7
KU_WINDOWS_I386. See previous messages.##
#1.5#C000AC10C80700000000073A0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:339)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.tools.dda.RomExtractor.extract(RomExtractor.java:339)#Java###0 of 1 extractions have been successful. 1 extractions have not been successful. See previous messages.##
#1.5#C000AC10C80700000000073B0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:792)#Java###Phase has been completed.#1#PREPARE/EXTRACT/EXTRACT_ROMS#
#1.5#C000AC10C80700000000073C0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#Java###Start time: .#1#2007/07/13 10:11:04#
#1.5#C000AC10C80700000000073D0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:794)#Java###End time: .#1#2007/07/13 10:11:54#
#1.5#C000AC10C80700000000073E0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:795)#Java###Duration: .#1#0:00:50.092#
#1.5#C000AC10C80700000000073F0010573800043525B1787048#1184335914365#/System/Server/Upgrade/Phases/PREPARE/EXTRACT/EXTRACT_ROMS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:796)#Java###Phase status is .#1#error#
/////////////////////////////////7END THE FILE////////////////////////777
I read the notes and I donu00B4t find the problem
Best Regards,
Luis Moreno.
-
SMQ2: SYSFAIL Comparison error during the execution of a simple
Hi folks, I have an operation mapping interface determination with exactly 1 target message of occurence 0..1, that means the mapping output can be nothing for some input messages, that means a target message is not produced so that the output looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<Messages><Message1/></Messages>
In services builder the test finishes successfully when no output message is produced. Also in integration builder i can test the configuration and it works without errors.
But in runtime the message status is set to "Recorded for Outbound Processing" in SXI_MONITOR and the queue status of the message to "Message has errors". The message stops in SMQ2 with "SYSFAIL" as status and statusText "Comparison error during the execution of a simple" (truncated).
Anybody experienced the same? How has the output of an operation mapping to look like when no target message is produced?
I also tested with an output like this when no target is produced, but this results in System error "Split mapping created no messages" in SXI_MONITOR:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1></ns0:Message1></ns0:Messages>
Thanks for your help, best regards, MartinYou seem to be having a multi-mapping involved.
The operation mapping has to produce at least the start and end tag.....even if the entire message is not present
Ex:
<SRC>
<First>
<Middle>
<Last>
</SRC>
If above is the structure, then it should be ensured that at least <SRC></SRC> is created by your mapping program....however in your case this is not happening....the tags that you see Messages and Message1 are due to the multi-mapping program and your message should be more than this.
if you say that occurence is 0..1 then what you can do is map this 0..1 node (root) with at least a blank Constant.
Unless you create a message (even though empty) you will continue to receive the error message.
Regards,
Abhishek. -
Unhandled exception occurred during the execution of the workflow instance
I had a workflow and library working with no issues, but had to move the library and export the workflow to another subsite (though on the same web site/collection). I followed these how-tos:
http://msdn.microsoft.com/en-us/library/office/jj819316%28v=office.15%29.aspx
http://technet.microsoft.com/en-us/library/ee428301%28v=office.15%29.aspx
Anyway, I've stripped all actions from the workflow and only have an Assign Task, but get this below:
An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ArgumentException: ContentTypeId at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance
instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
To troubleshoot, I removed all library columns, removed then re-added the Custom Content type the New Document uses, and still the same error - with the workflow going into Suspended mode.
I also tried the removal of the file from /Relationships%20List/allitems.aspx and de-activating then re-activating the SharePoint Publishing feature, also that didn't work.
I've gone into ULS, but unable to find anything definitive, so not sure what to try next?
Thank you,
ChadHi Chad,
Glad to hear the issue is resolved. Content types could be used for multiple lists in SharePoint site at the same time.
However, I'm not quite sure why you said the resolution is for a "bug". I read the article per your link:
http://www.andrewconnell.com/blog/SP2013-Workflow-Custom-Task-Outcomes
The article is showing how to create custom outcomes buttons in task forms. As I understand, the issue you encountered is that workflow migrated from the other site shows the suspended status.
Please be more specific on the issue if assistance is needed. If this is the second question, I’d recommend you open another thread in the relevant forum and provide specific information about the issue. In order to avoid confusion and keep track of troubleshooting
steps, we usually troubleshoot one issue per thread in order to find a resolution efficiently.
Thanks for the understanding.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support -
Get Agent IP Address During Script Execution
Good Evening,
I'm looking for a little advice... I'm trying to develop a method of alerting agents to the fact they are not ready. I have a script that can dynamically change the wallpaper on an IP phone. My aim is to add a step to the "Select Resource" portion of a script that will execute if an agent doesn't answer a call presented to them. However in order for this script to work it requires the IP address of the phone the agent is logged on to. Can anybody recommend a method of getting this IP dynamically during script execution? We use EM so statically defining IPs in an XML document wouldn't be appropriate.
On a similar note I'd also need a method of executing the same script when an agent manually alters their state to ready. i.e. When they change to ready on the IP Phone Agent I'd like to be able to intercept that process as it takes place and automatically trigger this same script.
I'm using UCCX 8.5(3).
Hope that makes sense. Any suggestions regarding how to achieve this would be much appreciated.
Much appreciated,
RyanI don't write enough scripting to know for sure if the agent's phone's IP address would be available anywhere in the UCCX enviornment by default but I'm going to go with 'probably not'. You'd need to obtain this information from CUCM, the most straightforward method would likely be to use CUCM's AXL interface to pull this information. The HTTP Document Step may be able to produce the necessary AXL requests I guess, but I've never tried.
Cheers,
Kris -
Exception during mapping Execution
Hi Experts
an Matmas05 xml is coming from MDM system. & it should be posted as Matmas05 in R/3.
i imported the MDM content in IR. but the fields order in coming Matmas05 xml file and the fields order in
Matmas05 Idoc are Not same.
while Executing Mapping it throws 'Exception during mapping execution'
so pls give solution How can i solve...this error
pls ....urgent.
thanks & regards
swapnaHI swapna,
The XMl coming from MDM have the different sequence than the original Matmas05 IDOC that you have imported in IR,.
Lets take it this way as the Original Matmas IDOC structre is not matched up with the sender side Structure.
You can change the sequence of IDOC XSD file with some tools like Altova xmlSpy and make it same as sender side. Then import the modified XSD file as external defination and use it on sender side.
On Receiver side your Matmas05 structre sequence should have to be original one.
Now map the corresponding fields and execute the scenario.
thanks
Swarup -
An error has occurred during the execution of the PREPARE_JSPM_QUEUE phase
Hi ,
During upgrade of EHP1 - NW 700 i am getting a error in configuration step like An error has occurred during the execution of the PREPARE_JSPM_QUEUE phase
The validation of the deploy queue was not successful. Request to check queue sapjup-queue completed with error. JSPM version is 7.01.4.0.17. Current JSPM log directory is /usr/sap/BIP/DVEBMGS00/j2ee/JSPM/log/log_2009_08_11_11_44_10.
You can find more information in the log file /EHPI/java/log/PREPARE_JSPM_QUEUE_CSZ_01.LOG.
Use the information provided to troubleshoot the problem. An SAP Note may provide a solution to this problem. Search for SAP Notes with the following key words: com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue com.sap.sdt.sapjup.tools.sapjupjspm.JSPMRapiException The validation of the deploy queue was not successful. PREPARE_JSPM_QUEUE INIT NetWeaver Enhancement Package Installation SAPJup Java Enhancement Package Installation
When reporting problems to SAP Support, attach the trouble ticket file /EHPI/java/log/TroubleTicket_01.txt to your message
Plz help me to analyze on this issue.
Regards,
HariHi Vasil Dimitranov
Thanks for your response.I have went through the log wat u said and found that only Java Patch JSPM is deployed in my system and the others patches are found be taken from the xml file and not deployed due to this below errors.
Aug 11, 2009 11:53:33 AM [Error]: java.lang.NullPointerException:
Aug 11, 2009 11:53:33 AM [Error]: Request to check queue sapjup-queue completed with error.
Aug 11, 2009 11:53:33 AM [Error]: Request to check queue sapjup-queue completed with error.
JSPM version is 7.01.4.0.17. Current JSPM log directory is /usr/sap/BIP/DVEBMGS00/j2ee/JSPM/log/log_2009_08_11_11_44_10
Aug 11, 2009 11:53:33 AM [Info]: Message type received disconnect.
Aug 11, 2009 11:53:33 AM [Info]: Remote connection is closed.
Aug 11, 2009 11:53:34 AM [Warning]: Refusing connection.
Aug 11, 2009 11:53:34 AM [Warning]: Network input/output exception has occurred: Error during read
Aug 11, 2009 11:53:34 AM [Info]: Phase JSPM/JSPMPhases/JSPM_MAIN has been completed.
Aug 11, 2009 11:53:34 AM [Info]: Start time: 2009/08/11 11:45:25.
Aug 11, 2009 11:53:34 AM [Info]: End time: 2009/08/11 11:53:34.
Aug 11, 2009 11:53:34 AM [Info]: Duration: 0:08:08.764.
Aug 11, 2009 11:53:34 AM [Info]: Phase status is initial.
Plz help me on this to analyze regarding the check queue sapjup-queue .
Thanks in Advance.
Regards,
Hari -
ORA-12842: Cursor invalidated during parallel execution Database driver err
Hi gurus,
I have got an PL/SQL package in DWH environment and sometimes it generates the follwoing error message:
ORA-12842: Cursor invalidated during parallel execution Database driver error...
When I restart the process, it runs successfully.
Any ideas about this behaviour?
Regards
BerndMore info needed.
Which Oracle version?
Are you running up against a known bug? Check metalink.
Cheers,
Colin -
Multi-level error propagation during the execution of CFM2 transaction
Hi,
We are implementing SAP SCM 5.0 integrated to SAP R/3 Mills IS.
During the execution of CFM2 transaction, while trying to activate the integration model for the object u201COrdersu201D for the very first time, the following error message appears:
*"Multi-level error propagation carried out".*
There are also messages related to inbound queues blocked. In the case of maintenance orders, CIF_MNT_INBOUND message shows up. While working with Production orders, CIF_ORDER_INBOUND message emerges.
The items listed below should be taken into account:
-The production orders that are meant to be transferred to APO are regular production orders corresponding to several products.
-We are working with configurable materials.
-We are working with the active model (000) and for each plant we are using 2 different planning versions.
Regards,
Analía NahmíasDear Analía,
The corresponding error messages issued when executing //CCR indiacted the peg-ids are missing in liveCache.
Recommendations:
-Run transaction /SAPAPO/OM17 to check the internal consistency between database and liveCache within SCM system. Correct the inconsistencies
-Execute report /sapapo/cif_deltareport3 to correct the inconsistencies between ECC and SCM system
Regards,
Tibor -
Error CLSRSC-507 during the execution of root.sh on second node
Hi all.
OS.......: Red-Hat 6.5
RDBMS: Oracle 12.1.0.2.0
During the installation of a 2-node RAC in a RHEL 6.5, during the execution of the root.sh script in the second node, i get the following error:
[root@oraprd02 grid]# ./root.sh
Performing root user operation.
The following environment variables are set as:
ORACLE_OWNER= grid
ORACLE_HOME= /u01/app/12.1.0/grid
Enter the full pathname of the local bin directory: [/usr/local/bin]:
Copying dbhome to /usr/local/bin ...
Copying oraenv to /usr/local/bin ...
Copying coraenv to /usr/local/bin ...
Creating /etc/oratab file...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Using configuration parameter file: /u01/app/12.1.0/grid/crs/install/crsconfig_params
2015/05/04 22:47:16 CLSRSC-4001: Installing Oracle Trace File Analyzer (TFA) Collector.
2015/05/04 22:47:59 CLSRSC-4002: Successfully installed Oracle Trace File Analyzer (TFA) Collector.
2015/05/04 22:48:00 CLSRSC-363: User ignored prerequisites during installation
OLR initialization - successful
2015/05/04 22:48:46 CLSRSC-507: The root script cannot proceed on this node oraprd02 because either the first-node operations have not completed on node oraprd01 or there was an error in obtaining the status of the first-node operations.
Died at /u01/app/12.1.0/grid/crs/install/crsutils.pm line 3681.
The command '/u01/app/12.1.0/grid/perl/bin/perl -I/u01/app/12.1.0/grid/perl/lib -I/u01/app/12.1.0/grid/crs/install /u01/app/12.1.0/grid/crs/install/rootcrs.pl ' execution failed
The root.sh on the first node completed successfully. I get the succeeded message from the script in the first node.
Have anyone faced this problem? Any assistance will be most helpfull.
Thanks in advance.crsd and cssd logs were empty and there was no relevant info in crs alert
i am just reinstalling clusterware now
one thing i wanted to ask
why does owner ship of raw files change back to root (after node restart)
even though i chnged them to oracle -
Question on use of shared memory objects during CIF executions
We have a CIF that runs in background via program RIMODACT that is invoked from our external job scheduler. (The schedulere kicks off a job - call it CIFJOB - and the first step of this job executes RIMODACT.)
During the execution of RIMODACT, we call a BAdI (an implementation of SMOD_APOCF005.)
In the method of this BAdI, we load some data into a shared memory object each time the BAdI is called. (We create this shared memory object the first time the BAdI is called.)
After program RIMODACT finishes, the second step of CIFJOB calls a wrapper program that calls two APO BAPI's.
Will the shared memory object be available to these BAPIs?
Reason I'm asking is that the BAPIs execute on the APO app server, but the shared memory object was created in a CIF exit called from a program executing on the ECC server (RIMODACT).
Edited by: David Halitsky on Feb 20, 2008 3:56 PMI know what you're saying, but it doesn't apply in this case (I think.)
The critical point is that we can tie the batch job to one ECC app server. In the first step of this job (the one that executes RIMODACT to do the CIF), we build the itab as an attribute of the "root" shared memory object class.
In the second step of the batch job, we attach to the root class we built in the first step, extract some data from it, and pass these data to a BAPI that we call on the APO server. (This is what I meant by a "true" RFC - the APO BAPI on the APO server is being called from a program on the ECC server.)
So the APO BAPI never needs access to the ECC shared memory object - it gets its data passed in from a program on the ECC server that does have access to the shared memory object.
Restated this way, is the solution correct ??? -
An error has occurred during the execution of the JSPM_MAIN phase.
Hi,
When I run the go.bat for running SLD, I am getting the following exception.
An error has occurred during the execution of the JSPM_MAIN phase.
Cannot initialize application data. Could not determine profile parameters. Error while retrieving value j2ee/dbhost,j2ee/dbname,j2ee/dbtype, with retriever com.sap.sdt.tools.sysinfo.ProfileDataRetriever. Could not extract value with key j2ee/dbhost,j2ee/dbname,j2ee/dbtype, from file D:/usr/sap/CE1/SYS/profile/DEFAULT.PFL. A possible reason could be that the path to the directory containing the sappfpar executable is not included in the PATH environment variable. Could not start process sappfpar. Error while executing process sappfpar. java.io.IOException: CreateProcess: sappfpar all pf=D:/usr/sap/CE1/SYS/profile/DEFAULT.PFL error=2
You can find more information in the log file D:\usr\sap\CE1\J01\j2ee\JSPM\log\log_2007_07_11_18_49_45\JSPM_MAIN_1_01.LOG.
Use the information provided to troubleshoot the problem. An SAP Note may provide a solution to this problem. Search for SAP Notes with the following key words:
com.sap.sdt.jspm.phases.PhaseTypeJSPM
com.sap.sdt.jspm.gui.JspmUiException
Cannot initialize application data.
JSPM_MAIN
JSPMPhases
NetWeaver Upgrade
SAPJup
Java Upgrade
Any inputs regarding this highly appreciated.
Thanks
SivaYou can look at the following link, it may help
https://www.sdn.sap.com/irj/sdn/directforumsearch?userid=3474257&rankby=10001&start=90 -
Is there a way to monitor CPU usage during the execution of a vi?
I am wondering if there is a way, using LabView, to monitor the CPU usage during the execution of a vi. I want to be able to programmatically adjust the program controls based on the CPU usage. This program is designed to run all day in the background.
Thanks!JAI wrote:
> I am wondering if there is a way, using LabView, to monitor the CPU
> usage during the execution of a vi. I want to be able to
> programmatically adjust the program controls based on the CPU usage.
> This program is designed to run all day in the background.
>
> Thanks!
There are at least two Windows tools you can use to see CPU usage
(depending on what version of Windows you have). The Task Manager
(ctrl-alt-del) has a panel that shows CPU usage. There is another
program that has more options as to what to watch. Under W2K, it is in
the Administrative Tools in the Control Panel and is called Performance.
Play around with adding various new "Counters".
Another option is to measure CPU usage programmatically. George Zou
has a tool that makes the appropriate dll call. Check out
http://www.geocities.com/gzou999/index.html
Regards,
Dave Thomson
David Thomson 303-499-1973 (voice and fax)
Original Code Consulting [email protected]
www.originalcode.com
National Instruments Alliance Program Member
Certified LabVIEW Developer
Certified Instrument Driver Developer
Research Scientist 303-497-3470 (voice)
NOAA Aeronomy Laboratory 303-497-5373 (fax)
Boulder, Colorado [email protected]
There are 10 kinds of people: those who understand binary,
and those who don't. -
Unexpected error during mapping execution
Hello,
we are implementing business intelligence for Siebel 8.1. Having one strange issue and hoping anybody could help us out.
We are using OWB 10.2.0.1. Certain error appears during mapping execution LOAD_SR which basically loads service requests from Siebel DB to data warehouse.
The mapping is using two tables as input (S_SRV_REQ and S_SRV_REQ_X) which are joined by S_SRV_REQ.ROW_ID = S_SRV_REQ_X.PAR_ROW_ID (+) using Joiner operator, because I always need extension table (S_SRV_REQ_X) rows either filled either containing only nulls (when there is no corresponding extension row). Sadly, this does not work, during execution it generates:
Error:
ORA-00997: illegal use of LONG datatype
ORA-06512: at "DWH_ADM.LOAD_SR", line 32
ORA-06512: at "DWH_ADM.LOAD_SR", line 3507
ORA-06512: at "DWH_ADM.LOAD_SR", line 4553
ORA-06512: at "DWH_ADM.LOAD_SR", line 9984
ORA-06512: at line 1
Warning:
ORA-00997: illegal use of LONG datatype
In summary, these join conditions generate same error as above:
S_SRV_REQ.ROW_ID = S_SRV_REQ_X.PAR_ROW_ID (+)
S_SRV_REQ.ROW_ID (+) = S_SRV_REQ_X.PAR_ROW_ID (+)
S_SRV_REQ.ROW_ID = S_SRV_REQ_X.PAR_ROW_ID
Strangely, when I use join condition S_SRV_REQ.ROW_ID (+) = S_SRV_REQ_X.PAR_ROW_ID, it works. But then right join is used and some records get rejected by joiner operation (those who do not have corresponding rows in extension table).
Could someone help me with this issue?
Any feedback would be greatly appreciated. Thank you for your time reading this!
Edited by: user8872556 on Sep 28, 2011 2:21 AM
Edited by: user8872556 on Sep 28, 2011 2:23 AM
Edited by: user8872556 on Sep 28, 2011 2:23 AMWe still were not able to solve this issue, would greatly appreciate any effort to help us out.
-
some one can help me please
i have no idea what i must to do.
an unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.The Exception Handler gave all the info that you need. No need to print the whole stack trace.
The exception handler says
Exception Details: java.lang.IllegalArgumentException
TABLE1.NAME
Look in the session bean (assuming that is where your underlying rowset is). Look in the _init() method for statements similar to the following:
personRowSet.setCommand("SELECT * FROM TRAVEL.PERSON");
personRowSet.setTableName("PERSON");
What do you have?
Maybe you are looking for
-
VPN Clients can't access DMZ Network
Hello, I will try to describe my problem as best as possible. The title says VPN clients cannot access DMZ network, but that is not exactly the problem, the situation is this, a group of users are using an actual 10.x network where they have their se
-
Kernel Panic when I insert Snow Leopard Disc
Hi, when I insert the snow leopard retail disc, my mac startup with a kernel panic, without log in logs folder. And on screen appear this. http://img847.imageshack.us/img847/282/20111115195144.jpg
-
So, I spilled a bit of coffee on my Macbook Pro keyboard. I followed standard procedure - turned it off, turned it upside down and put it in a bag of rice for over 24 hours. Things seem to be relatively fine, despite being a bit sticky and now a few
-
JMS Adapter Supports below message
Hi Frnds, I am working on one scenario i have to read and write RFH2 Message from MQ,we decided to use jms adapter. JMS Adapter supports below Message to put in MQ, <Data> <MQRFH2> <usr> <TransactionType>GL_Update</Trans
-
Is there any way to increase DVD player SDK750SU2 output volume level? The television volume control will not raise the volume high enough when using the player.