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
Similar Messages
-
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 -
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 -
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.
-
An error has occurred during the execution of the BIND_SUPPORT_PACKAGES pha
Hello,
I am upgrading SRM 7.02/NW 7.00 to SRM 7.02/NW 7.30 on Linux/MAXDB. But i am facing the following issue in BIND_SUPPORT_PACKAGES.
java.lang.NullPointerException: while trying to invoke the method com.sap.sdt.j2ee.tools.kernel.detect.KernelPatchConfig.getKernelComponentDetails() of an object returned from com.sap.sdt.j2ee.tools.newsdu.NonDeployableComponentsProperties.getJ2eeKernelPatchConfig() java.lang.NullPointerException: while trying to invoke the method com.sap.sdt.j2ee.tools.kernel.detect.KernelPatchConfig.getKernelComponentDetails() of an object returned from com.sap.sdt.j2ee.tools.newsdu.NonDeployableComponentsProperties.getJ2eeKernelPatchConfig()
Could you please help me on this.
Thanks & Regards,
NishithaHi Nishitha,
Check if you have you included the correct support packages and stack as it says non deployable components? Is your stack.xml correct?
Thanks,
Ravi -
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. -
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 -
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? -
Error occured during the execution of the JSPM_main phase
Hi,
When ever I try to Start JSPM i get the following error saying that Cannot detect system kernel under the directory c:\usr\sap\EPD\sys directory and also error occured during the execution of the JSPM_main phase.
Can any one help me in this regard.
Thanks in advance.
Thanks
VenuHi Anand,
Please find the log file below.
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\EPD\JC20\j2ee\JSPM\log\log_2007_04_03_16_57_45\JSPM_MAIN_1_01.LOG]/>
<!PATTERN[JSPM_MAIN_1_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
#1.5#C000AC190C09000000000016019B539300042D33A14D91C0#1175599679640#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##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#JSPM/JSPMPhases/JSPM_MAIN#
#1.5#C000AC190C09000000000017019B539300042D33A14DD040#1175599679656#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##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.jspm.phases.PhaseTypeJSPM#
#1.5#C000AC190C09000000000018019B539300042D33A1531000#1175599680000#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.showInitDialog(DialogController.java:560)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.showInitDialog(DialogController.java:560)#Java###Starting Initialize dialog...##
#1.5#C000AC190C0900000000001E019B539300042D33A15C5AE8#1175599680609#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:462)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:462)#Java###Detecting system parameters...##
#1.5#C000AC190C0900000000001F019B539300042D33A15C5AE8#1175599680609#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#Java###You can find additional information in log file .#1#C:
usr
sap
EPD
JC20
j2ee
JSPM
log
log_2007_04_03_16_57_45
DETECT_SYSTEM_PARAMETERS_01.LOG#
#1.5#C000AC190C0900000000002D019B539300042D33A1AA1558#1175599685703#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:483)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.initializeDataModelAndLogging(SystemInitializer.java:483)#Java###Detection of system parameters has finished.##
#1.5#C000AC190C0900000000002E019B539300042D33A1AA4FF0#1175599685718#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:470)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:470)#Java###Initialize dialog has been processed.##
#1.5#C000AC190C0900000000002F019B539300042D33A1AA4FF0#1175599685718#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1043)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1043)#Java###Starting dialog...#1#LogIn#
#1.5#C000AC190C09000000000039019B539300042D33AA43E180#1175599830000#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1048)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.loginDialog(DialogController.java:1048)#Java###Dialog has been confirmed by the user.#1#LogIn#
#1.5#C000AC190C0900000000003A019B539300042D33AA467D78#1175599830171#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#Java###Checking connectivity for SDM server on host , port ...#2#aprins02#52018#
#1.5#C000AC190C0900000000003B019B539300042D33AA539CD8#1175599831031#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl#Java###Connection to SDM server on host , port is valid.#2#aprins02#52018#
#1.5#C000AC190C0900000000003C019B539300042D33AA65F810#1175599832234#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.deployedsdu.DeployedComponentsProvider.refresh(DeployedComponentsProvider.java:192)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.deployedsdu.DeployedComponentsProvider.refresh(DeployedComponentsProvider.java:192)#Java###Detecting components of the J2EE engine...##
#1.5#C000AC190C0900000000003D019B539300042D33AA65F810#1175599832234#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.trace.JspmExtLoggingManager.logReferenceToExtLog(JspmExtLoggingManager.java:167)#Java###You can find additional information in log file .#1#C:
usr
sap
EPD
JC20
j2ee
JSPM
log
log_2007_04_03_16_57_45
DETECT_SYSTEM_COMPONENTS_01.LOG#
#1.5#C000AC190C09000000000052019B539300042D33B5C8DEE8#1175600023265#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.trace.JspmExtLoggingManager.logError(JspmExtLoggingManager.java:275)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.jspm.trace.JspmExtLoggingManager.logError(JspmExtLoggingManager.java:275)#Java###Error during operation. For more information about the operation, see the previous message. For more information about the error, see the next messages.##
#1.5#C000AC190C09000000000053019B539300042D33B5C91D68#1175600023281#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.trace.JspmExtLoggingManager.logMaximumLogSeverity(JspmExtLoggingManager.java:258)#######Thread[main,5,main]##0#0#Warning#1#com.sap.sdt.jspm.trace.JspmExtLoggingManager.logMaximumLogSeverity(JspmExtLoggingManager.java:258)#Java###There are some WARNING messages in the child log .#1#C:
usr
sap
EPD
JC20
j2ee
JSPM
log
log_2007_04_03_16_57_45
DETECT_SYSTEM_COMPONENTS_01.LOG#
#1.5#C000AC190C09000000000054019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##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#C000AC190C09000000000055019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.tools.proc.OsProcessController.startProcess(OsProcessController.java:285)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.proc.OsProcessController.startProcess(OsProcessController.java:285)#Java###java.io.IOException: CreateProcess: C:/usr/sap/EPD/JC20/exe/disp+work -V error=2##
#1.5#C000AC190C09000000000056019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.tools.proc.OsProcessController.startProcess(OsProcessController.java:284)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.proc.OsProcessController.startProcess(OsProcessController.java:284)#Java###Error while executing process C:/usr/sap/EPD/JC20/exe/disp+work.##
#1.5#C000AC190C09000000000057019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:130)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:130)#Java###Could not start process C:/usr/sap/EPD/JC20/exe/disp+work.##
#1.5#C000AC190C09000000000058019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j2ee.tools.kernel.KernelRetriever.getCommandOutput(KernelRetriever.java:240)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.kernel.KernelRetriever.getCommandOutput(KernelRetriever.java:240)#Java###disp+work executable file cannot be run.##
#1.5#C000AC190C09000000000059019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:767)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:767)#Java###Could not detect current system kernel in the C:
usr
sap
EPD
JC20
exe directory.##
#1.5#C000AC190C0900000000005A019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:435)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:435)#Java###Could not detect central instance kernel in directory C:
usr
sap
EPD
JC20
exe.##
#1.5#C000AC190C0900000000005B019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentsFromSystem(DetectKernelComponent.java:464)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentsFromSystem(DetectKernelComponent.java:464)#Java###Could not detect system kernel under the C:
usr
sap
EPD
SYS directory.##
#1.5#C000AC190C0900000000005C019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectComponentsFromSystem(DetectKernelComponent.java:554)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectComponentsFromSystem(DetectKernelComponent.java:554)#Java###Could not detect version information of the current system kernel.##
#1.5#C000AC190C0900000000005D019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.deployedsdu.DeployedComponentsProvider.refresh(DeployedComponentsProvider.java:220)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.jspm.deployedsdu.DeployedComponentsProvider.refresh(DeployedComponentsProvider.java:220)#Java###Could not detect deployed components.##
#1.5#C000AC190C0900000000005E019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##com.sap.sdt.jspm.gui.SystemInitializer.initializeBusinessObjects(SystemInitializer.java:676)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.jspm.gui.SystemInitializer.initializeBusinessObjects(SystemInitializer.java:676)#Java###Cannot initialize application data.##
#1.5#C000AC190C0900000000005F019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##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#JSPM/JSPMPhases/JSPM_MAIN#
#1.5#C000AC190C09000000000060019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##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/04/03 16:57:59#
#1.5#C000AC190C09000000000061019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##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/04/03 17:03:43#
#1.5#C000AC190C09000000000062019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##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:05:43.640#
#1.5#C000AC190C09000000000063019B539300042D33B5C95800#1175600023296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_MAIN##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#
Thanks
Venu -
Ng An exception occurred during the execution of the current web request.
An exception occurred during the execution of the current web request. Please contact the administrator to review the stack trace in the event log for more information about the error.
this error occured while making changes to the mapings, there was "&" in the source account and some test also loaded in the text,
the versio n of FDM is 11.1.2.0
I understand that because of loading & in the source account it is causing this issue,
How to delete this invalid char from database, which table and column will contain this information, Please advise me how to proceed on this.
thanks,
msrThis TSQL will do the trick. It's not the cleanest as I just wrote it, but it will dynamically remove the & from the data mapping tables and replace any invalid entries with the phrase INVALID.
--Remove && from Data Maps
--Charles Beyer ([email protected])
--NOTES : 'Hackish' version for demonstration purposes
-- Declare working variables
DECLARE @strTableName varchar(255)
DECLARE @strSql Nvarchar(500)
-- Create cursor to iterate through each Data Map table. Look in special table sysobjects to get a list of the tables.
DECLARE crsDataMapTables Cursor For
select name
from sysobjects
where name like 'tdatamap%'
and xtype = 'U'
Open crsDataMapTables
Fetch Next from crsDataMapTables Into @strTableName --Get the name of the first Data Map table and place it into working variable
While @@FETCH_STATUS = 0 Begin --While records (table names) exist, execute loop logic
print 'Cleaning table : ' + @strTableName
--Multi-pass updates to check the SrcKey, TargKey, and WhereClauseValue fields for the invalid character
--Dynamic SQL is used below so that we can use the Table Name from the cursor..
Set @strSQL = 'UPDATE ' + @strTableName + ' set SrcKey = ''Invalid'' where SrcKey like (''%&%'')'
exec (@strSQL)
Set @strSQL = 'UPDATE ' + @strTableName + ' set TargKey = ''Invalid'' where TargKey like (''%&%'')'
exec (@strSQL)
Set @strSQL = 'UPDATE ' + @strTableName + ' set WhereClauseValue = ''Invalid'' where WhereClauseValue like (''%&%'')'
exec (@strSQL)
Fetch Next from crsDataMapTables Into @strTableName
End
--Dispose of Cursor as we are done.
Close crsDataMapTables
Deallocate crsDataMapTables
-
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 -
Netsh becoming cetsh during the execution of the script
netsh becoming cetsh during the execution of the script - for DHCP
Hi Venky6262,
As Philippe said, please post more detailed information about this issue to help us to troubleshoot, like what do you want to achieve with the cmd netsh, your code and the error.
In addition, there are good examples to use Netsh commands for DHCP:
http://technet.microsoft.com/en-us/library/cc787375(v=ws.10).aspx
Best Regards,
Anna -
We have a weird situation we're trying to troubleshoot for quite a while: We have multiple .vsd files stored on our network in DFS shares.. We have multiple users who cannot open the files, when they try by navigating to the file and double-clicking it,
they get "An error (1502) occurred during the action Open. File not found"
However, if they copy and paste the file to the same exact network folder, THAT file they can open with no problem!
The problem is very bizarre. I've checked obvious things such as file/folder permissions, versions of Visio installed, things in common between people who can and can't open the files.. I even did some testing today with some strange results...
Windows 7 x64 machine with Visio 2010 Pro installed (x86):
1. Opened file by double-clicking it in explorer, "Got the 1502 error"
2. Tried it again, this time I just get "File not found"
3. Opened Vizio, did a File --> Open --> navigated to the file and opened it that way... 1502 error.
4. Copy/pasted the file into the same folder where it's stored, then double-clicked the copy and it opens fine.
5. Closed the copy, tried to open the original, still get file not found / error 1502.
The file does exist, it IS there.. sometimes the user just copies it to their local desktop (well, it's not really local, it's redirected) and it opens fine there.. other users email themselves a copy of the file and then open it that way.. it works for
some, not for others.. and there's no discernible pattern yet to identify who this is affecting. Anyone have any ideas?
-Keith
-Keith ElkinHi,
Based on the error message, the issue may be caused by the Visio file is occupied by some other program in DFS.
>>4. Copy/pasted the file into the same folder where it's stored, then double-clicked the copy and it opens fine.<< If you did this step, the Visio file would rename in the same folder, like file1.vsd. Thus, it opened well.
Thus, I recommend you check the file's status in computer management in DFS server, see the below image:
If the affected Visio files were occupied, please try to clean them(right click>close the file) to test.
Hope it's helpful.
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Sorry,
This didn't help, the files are not open, locked open, and the issue still persists. Any other suggestions?
-Keith
-Keith Elkin -
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. -
Fill the LOV with data during the execution
Hi
I am using Oracle 10g
I want to ask please if there is a way to fill the LOV with data during the execution
so can I change the query specified in LOV wizard during the execution and get a new record set according to the value in the text boxes
thank you for helpYou can use the SET_LOV_PROPERTY built-in to change the record group of the LOV and to create a new record group you can use the CREATE_GROUP_FROM_QUERY built-in.
it will be something like this.
RG_ID := FIND_GROUP('<record group name>');
IF NOT ID_NULL(RG_ID) THEN
DELETE_GROUP(RG_ID);
END IF ;
RG_ID := CREATE_GROUP_FROM_QUERY('<record group name>', '<your SQL statement here>');
POP_GROUP := POPULATE_GROUP('<record group name>');
SET_LOV_PROPERTY('<LOV name>', GROUP_NAME, '<record group name>');Use the online help for more information about these built-ins.
Tony
Maybe you are looking for
-
Caller ID not working since i upgraded to IOS6
Has anyone had trouble with Caller Id on the IOS6 upgrade on and iPhone 4s??
-
How do i find my airport extreme's ip address
How do I find the ip address for my AirPort Extreme?
-
Connecting to SQL Server from Solaris using Perl & Oracle.
Hey All, Using the DBI.pm provided by the default Perl package that comes integrated with Oracle server, I am being able to connect to the Oracle database through Perl. But is there a way I can connect to SQL Server through Perl using any package pro
-
Whenever I save a screenshot or an image from internet it doesn't appear in the photos app. I am also not able to take photos on camera? It is kind of strange. New iPad and hasn't been thrown around or anything. Thanks for your help.
-
Fatal error in APE 12 upon startup
I just downloaded APE 12 and i get the following message when i attempt to start a new project "Premiere Elements has encountered an error" Src\Core\Preferences.cpp-338 how do i fix this?