Error during application of scm 7.0 support pack
While applying support pack to our SCM 7.0 system (New Installation),
We encountered a SPAM error in xpra_execution phase, due to automatic
termination of job RDDEXECL scheduled by user id DDIC on client 000.
The details of the error are:
Message id: Brain
Message number : 366
Message type: A
Error: Error during SID assignment for characteristic 0REQUID (current
value 2)
We had a look at few notes mentioned by SAP support on 1319241. which
specifies a solution as
u201CIf you encounter the error message above, please run the Elementary
test - Compare Number Range and Maximum SID - for Master Data 0REQUID
in transaction RSRV. When it turns red, the error can be corrected by
pressing the "Correct Error" button.u201D
But we are already getting the light as green in the elementary test
for the Master Data 0REQUID in transaction RSRV, though we still
execute the same and problem is still the same i.e. RDDEXECL
program/job is getting terminated.
Regards
Edited by: pranav kumar on Feb 25, 2011 8:20 AM
Hi SM
Just login to client which has been mentioned in table RSADMINA,then run rsrv you will get error.correct it.then you will be able to import support packs.
Regards
Pranav
Similar Messages
-
"Error during application input" while processing IDOC with status 51
Hi ,
I tried to post an error IDOC with status "51" of message type FIDCC2 using program RBDINPUT, it just creates a message "Error during application input" . It is not calling the application dialog . Does anyone have answer for this?
Thanks,
Hemant.HI,
Kindly check the RFC entries in t-code SM58.
If any entries are their please release them manually selecting each one and press "F6".
Regards,
Anil. -
DDIC_ACTIVATION Error during application of Support Pack SAPKH47007
Hi All,
We were trying to apply Support Pack SAPKH47007 and it gave us an error in DDIC_Activation Phase and when i checked the logs it gave us this error
Relationship TMFK-TDID for table TTXS does not exist
Check dependent search help S_TMFK_SETTLE
Search help S_TMFK_SETTLE is consistent
I searched and found one Relevant Note for this SAP Note Num : 625098 and it tells us to delete the following fields
Delete the fields FLG_AK_PAYM_FICA and FLG_AK_PAYM_FIAR from the table
I went to SE11 and i dont see this fields there, and even though if i see them i dont think i can delete them coz it is asking Developer Key.
Upon further checking i found that if we delete the Contents in Pat01 and Pat03 we can go ahead and redo the support packs from begining. Can anyone throw some light on this as to how safe is this?
Regards,
Ershad Ahmed.Did you read the note I gave you?
The note says:
Symptom: An error occurs in the DDIC_ACTIVATION phase when you import Support Package SAPKH47007. The DDIC activation log records the following error messages:
Relationship TMFK-TDID for table TTXS does not exist
<...>
Solution: A general solution to the problem is available with R/3 Support Package SAPKH47010. To avoid the error, import the Support Packages SAPKH47007 and SAPKH47010 together in a queue.
If you have already encountered this error, the queue must be reset and extended to include Support Package SAPKH47010. Since you cannot reset the queue from the DDIC_ACTIVATION phase using normal means, this must be done by SAP Support (Component BC-UPG-OCS).
Markus -
Error during application deployment in cluster
Hi All,
I am seeing a weird error when I deploy my application in 2 node cluster. Few months back, the same cluster worked perfectly alright. The error relates to lookup at localhost:7001 which is no where in the configuration as admin server url is http://srai-xp:7001. I created a new domain and see the same problem.
Any pointers are greatly appreciated.
Thanks
--shashi
Here is the error log:
D:\apps\bea\user_projects\domains\nclusterdomain>startManagedWebLogic.cmd NodeSR http://srai-xp:7001
D:\apps\bea\user_projects\domains\nclusterdomain>echo off
CLASSPATH=CR190380_81sp3.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jax-qname.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\li
jsafe.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jsafejce.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\asn1.jar;;C:\j2sd
.4.2_04\lib\tools.jar;d:\apps\bea\WEBLOG~1\server\lib\weblogic_sp.jar;d:\apps\bea\WEBLOG~1\server\lib\weblogic.jar;d:\apps\bea\WEBLOG~1\common\eval\
intbase\lib\pbserver44.jar;d:\apps\bea\WEBLOG~1\common\eval\pointbase\lib\pbclient44.jar;C:\j2sdk1.4.2_04\jre\lib\rt.jar;d:\apps\bea\WEBLOG~1\server\lib\webservices.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_base.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_jce.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_krb.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_krb_jaas.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_license.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\jcsi_provider.jar;D:\apps\bea\user_projects\domains\nclusterdomain\lib\mysql-connector-java.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\nls_charset12.jar;;D:\apps\bea\user_projects\domains\nclusterdomain\lib\ojdbc14.jar;
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://[hostname]:[port]/console *
<Mar 17, 2005 4:19:27 PM PST> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<Mar 17, 2005 4:21:22 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.2_04-b05 fr
Sun Microsystems Inc.>
<Mar 17, 2005 4:21:22 PM PST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://srai-xp:7001 to ch
k if there exists a running admin server at this URL.>
<Mar 17, 2005 4:21:22 PM PST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Mar 17, 2005 4:21:22 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
<Mar 17, 2005 4:21:22 PM PST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://srai-xp:7001 to retriev
the initial configuration.>
<Mar 17, 2005 4:21:25 PM PST> <Notice> <Log Management> <BEA-170019> <The server log file D:\apps\bea\user_projects\domains\nclusterdomain\NodeSR\No
SR.log is opened. All server side log events will be written to this file.>
<Mar 17, 2005 4:21:30 PM PST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 17, 2005 4:21:30 PM PST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "NodeSR" for domain "nclusterdomain">
<Mar 17, 2005 4:21:35 PM PST> <Notice> <Cluster> <BEA-000138> <Listening for announcements from cluster XCluster on 237.0.0.101:8050.>
<Mar 17, 2005 4:21:35 PM PST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of XCluster.>
<Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 8001, ip address 153.32.158.12
<Mar 17, 2005 4:22:08 PM PST> <Notice> <Cluster> <BEA-000102> <Joining cluster XCluster on 237.0.0.101:8050>
<Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "NodeSR" for domain "nclusterdomain" running i
Production Mode>
<Mar 17, 2005 4:22:08 PM PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_de': Public ID references the old
rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_fr': Public ID references the old
rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Mar 17, 2005 4:23:33 PM PST> <Warning> <HTTP> <BEA-101247> <Application: 'C:\Temp\edc-server.ear', Module: 'help_ja': Public ID references the old
rsion of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
<Mar 17, 2005 4:23:35 PM PST> <Warning> <J2EE> <BEA-160081> <The JMS connection factory resource EDCEventQCF declared in the EJB "EventManagerBean"
part of application "edc-server" does not support XA. It cannot be used inside a transaction context.>
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:47)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:618)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:306)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:175)
at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
... 28 more
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Unable to create InitialContext ] - with nested exception:
[javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is
java.net.ConnectException: Connection refused: connect; No available router to destination]]
at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:770)
at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
<Mar 17, 2005 4:23:40 PM PST> <Error> <Deployer> <BEA-149201> <Failed to complete the deployment task with ID 0 for the application edc-server.
java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:199)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:125)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:296)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:239)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:135)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:175)
at weblogic.deployment.EnvironmentBuilder.findObject(EnvironmentBuilder.java:768)
at weblogic.deployment.EnvironmentBuilder.findObjectOrCreateLinkRef(EnvironmentBuilder.java:759)
at weblogic.deployment.EnvironmentBuilder.addUserTransaction(EnvironmentBuilder.java:555)
at weblogic.deployment.EnvironmentBuilder.<init>(EnvironmentBuilder.java:94)
at weblogic.servlet.internal.CompEnv.<init>(CompEnv.java:80)
at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:565)
at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:489)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:634)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:632)
at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:3150)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1558)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1208)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1051)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2444)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2394)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2310)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[java.net.ConnectException: t3://localhost:7001: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2327)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
>I checked all deployment descriptions and there are no references to t3://localhost:7001. Few months back, I had the complete clustering setup working on 2 machines and now when I deploy my application on same configuration, it fails with t3://localhost:7001 unreachable error. I created a new cluster configuration on one machine with 2 managed server and it deploys fine. Can not figure out what has changed ?
-
Error during Application Server Install
Hi
I get the below error during Infrastructure install as well as Application Server. But if I click ok , it completes the install , not sure whether this is critical issue.
The procedure entry point GetProcessImageFileNameW could not be located in the dynamic link library PSAPI.DLL
I am installing this in Windows XP Professional,Service pack2 . I tried installing the same in my laptop with same configuration and I did not get this error. Only difference between my laptop and desktop is , in my laptop I am running IE6.0,where as in desktop I am running IE7.0. I am not sure this is relevent here..
Any assistance would be really helpful
Thanks
BalajiI went ahead and completed the install, and it did not impose any problem..
thanks
balaji -
Error during application of stack
Hi all,
I am applying the stack using JSPM.
I got an error
An error occured during execution of JSPM_PROCESS Phase.
java.lang.StringIndexOutOfBoundsException: String index out of range: -9
Provide me solution to solve this error.<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[C:\usr\sap\NW7\DVEBMGS01\j2ee\JSPM\log\log_20071231170532\JSPM_PROCESS_1_01.LOG]/>
<!PATTERN[JSPM_PROCESS_1_01.LOG]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[Cp1252]/>
<!LOGHEADER[END]/>
#1.5#C000AC1A1C5000000000001401AB28FE0004429371740BF8#1199100937899#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##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_PROCESS#
#1.5#C000AC1A1C5000000000001501AB28FE0004429371740BF8#1199100937899#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##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#C000AC1A1C5000000000001601AB28FE0004429371744A78#1199100937915#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:246)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:246)#Java###Starting Initialize dialog...##
#1.5#C000AC1A1C5000000000001C01AB28FE00044293717AF968#1199100938353#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:342)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:342)#Java###Initializing JSPM data model...##
#1.5#C000AC1A1C5000000000001D01AB28FE00044293717AF968#1199100938353#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.InitialParametersDetector.detectProfileDirectory(InitialParametersDetector.java:1250)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectProfileDirectory(InitialParametersDetector.java:1250)#Java###Detected profile directory .#1#C:
usr
sap
NW7
SYS
profile#
#1.5#C000AC1A1C5000000000001E01AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:261)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:261)#Java###Executing command with arguments .#2#dbinfo#C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
config
DBINFO.XML#
#1.5#C000AC1A1C5000000000001F01AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:41)#Java###Java process ID , name has been started.#2#3#com.sap.sdt.dmt.main.DMT#
#1.5#C000AC1A1C5000000000002001AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:54)#Java###Command line: #2# #C:
j2sdk1.4.2_13
jre
bin
java.exe -cp .;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
sdt_dmt.jar;C:/sapdb/programs/runtime/jar/sapdbc.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
jddi.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
opensqlsta.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
tc_sec_secstorefs.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
frame.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
exception.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
logging.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
jperflib.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
util.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
tc_sec_secstorefs.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
exception.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
logging.jar;C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
lib
opensqlsta.jar;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
engine
iaik_jce.jar;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
engine
info
IAIKSecurityFS.list;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
tools
iaik_jce.jar;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
tools
iaik_jsse.jar;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
tools
iaik_smime.jar;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
tools
iaik_ssl.jar;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
tools
info
IAIKSecurityFS.list;
CP-CHN-3F-029
sapmnt
NW7
SYS
global
security
lib
tools
w3c_http.jar com.sap.sdt.dmt.main.DMT -rootdir=C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM -descriptor=cp-chn-3f-029_NW7 -logfile=DMT_01.LOG dbinfo C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
config
DBINFO.XML#
#1.5#C000AC1A1C5000000000002101AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.JavaOsProcessController.logProcessInfo(JavaOsProcessController.java:55)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
log
log_20071231170532
DMT_01.LOG_01.OUT#
#1.5#C000AC1A1C5000000000002201AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#3#
#1.5#C000AC1A1C5000000000002301AB28FE000442937184FBE8#1199100939009#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#3#java.exe#
#1.5#C000AC1A1C5000000000002401AB28FE0004429371BEEFD8#1199100942807#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#3#java.exe#0#
#1.5#C000AC1A1C5000000000002501AB28FE0004429371BEEFD8#1199100942807#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:273)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.db.dmtif.AbstractDMTController.execute(AbstractDMTController.java:273)#Java###Command has been executed.#1#dbinfo#
#1.5#C000AC1A1C5000000000002601AB28FE0004429371BFA770#1199100942854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.sysinfo.AbstractInfoController.updateProfileVariable(AbstractInfoController.java:288)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sysinfo.AbstractInfoController.updateProfileVariable(AbstractInfoController.java:288)#Java###Parameter has been detected. Parameter value is .#2#/J2EE/StandardSystem/DefaultProfilePath#C:
usr
sap
NW7
SYS
profile
DEFAULT.PFL#
#1.5#C000AC1A1C5000000000002701AB28FE0004429371BFA770#1199100942854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.InfoController.detectInstance(InfoController.java:601)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.InfoController.detectInstance(InfoController.java:601)#Java###msg.j630.sysinfo.013 #4#SCS00#C:
usr
sap
NW7
SYS
profile
NW7_SCS00_CP-CHN-3F-029#C:
usr
sap
NW7
SYS
profile
START_SCS00_CP-CHN-3F-029#CP-CHN-3F-029#
#1.5#C000AC1A1C5000000000002801AB28FE0004429371BFA770#1199100942854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.InfoController.detectInstance(InfoController.java:601)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.InfoController.detectInstance(InfoController.java:601)#Java###msg.j630.sysinfo.013 #4#DVEBMGS01#C:
usr
sap
NW7
SYS
profile
NW7_DVEBMGS01_CP-CHN-3F-029#C:
usr
sap
NW7
SYS
profile
START_DVEBMGS01_CP-CHN-3F-029#CP-CHN-3F-029#
#1.5#C000AC1A1C5000000000002901AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.InitialParametersDetector.detectHA(InitialParametersDetector.java:865)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.detectHA(InitialParametersDetector.java:865)#Java###SCS is local, so this is not a High Availability system.##
#1.5#C000AC1A1C5000000000002A01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#4#sappfpar#
#1.5#C000AC1A1C5000000000002B01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 DIR_EPS_ROOT#
#1.5#C000AC1A1C5000000000002C01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_01.out#
#1.5#C000AC1A1C5000000000002D01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#4#
#1.5#C000AC1A1C5000000000002E01AB28FE0004429371C24750#1199100943026#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#4#sappfpar#
#1.5#C000AC1A1C5000000000002F01AB28FE0004429371ED3398#1199100945839#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#4#sappfpar#0#
#1.5#C000AC1A1C5000000000003001AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#5#sappfpar#
#1.5#C000AC1A1C5000000000003101AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 SAPSYSTEM#
#1.5#C000AC1A1C5000000000003201AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_20.out#
#1.5#C000AC1A1C5000000000003301AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#5#
#1.5#C000AC1A1C5000000000003401AB28FE0004429371ED6E30#1199100945854#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#5#sappfpar#
#1.5#C000AC1A1C5000000000003501AB28FE000442937210B958#1199100948167#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#5#sappfpar#0#
#1.5#C000AC1A1C5000000000003601AB28FE000442937210B958#1199100948167#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#6#sappfpar#
#1.5#C000AC1A1C5000000000003701AB28FE000442937210B958#1199100948167#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 INSTANCE_NAME#
#1.5#C000AC1A1C5000000000003801AB28FE000442937210F7D8#1199100948183#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_21.out#
#1.5#C000AC1A1C5000000000003901AB28FE000442937210F7D8#1199100948183#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#6#
#1.5#C000AC1A1C5000000000003A01AB28FE000442937210F7D8#1199100948183#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#6#sappfpar#
#1.5#C000AC1A1C5000000000003B01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#6#sappfpar#0#
#1.5#C000AC1A1C5000000000003C01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#7#sappfpar#
#1.5#C000AC1A1C5000000000003D01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 DIR_EXECUTABLE#
#1.5#C000AC1A1C5000000000003E01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_22.out#
#1.5#C000AC1A1C5000000000003F01AB28FE00044293723BE420#1199100950996#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#7#
#1.5#C000AC1A1C5000000000004001AB28FE00044293723C22A0#1199100951012#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#7#sappfpar#
#1.5#C000AC1A1C5000000000004101AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#7#sappfpar#0#
#1.5#C000AC1A1C5000000000004201AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#8#sappfpar#
#1.5#C000AC1A1C5000000000004301AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 DIR_CT_RUN#
#1.5#C000AC1A1C5000000000004401AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_23.out#
#1.5#C000AC1A1C5000000000004501AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#8#
#1.5#C000AC1A1C5000000000004601AB28FE0004429372670EE8#1199100953825#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#8#sappfpar#
#1.5#C000AC1A1C5000000000004701AB28FE000442937291FB30#1199100956638#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#8#sappfpar#0#
#1.5#C000AC1A1C5000000000004801AB28FE000442937291FB30#1199100956638#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#9#sappfpar#
#1.5#C000AC1A1C5000000000004901AB28FE000442937291FB30#1199100956638#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_DVEBMGS01_CP-CHN-3F-029 jstartup/vm/home#
#1.5#C000AC1A1C5000000000004A01AB28FE000442937291FB30#1199100956638#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_24.out#
#1.5#C000AC1A1C5000000000004B01AB28FE00044293729239B0#1199100956654#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#9#
#1.5#C000AC1A1C5000000000004C01AB28FE00044293729239B0#1199100956654#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#9#sappfpar#
#1.5#C000AC1A1C5000000000004D01AB28FE0004429372BD25F8#1199100959467#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#9#sappfpar#0#
#1.5#C000AC1A1C5000000000004E01AB28FE0004429372BD25F8#1199100959467#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#10#sappfpar#
#1.5#C000AC1A1C5000000000004F01AB28FE0004429372BD25F8#1199100959467#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 SAPSYSTEM#
#1.5#C000AC1A1C5000000000005001AB28FE0004429372BD25F8#1199100959467#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_01.out#
#1.5#C000AC1A1C5000000000005101AB28FE0004429372BD6478#1199100959483#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#10#
#1.5#C000AC1A1C5000000000005201AB28FE0004429372BD6478#1199100959483#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#10#sappfpar#
#1.5#C000AC1A1C5000000000005301AB28FE0004429372E850C0#1199100962296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#10#sappfpar#0#
#1.5#C000AC1A1C5000000000005401AB28FE0004429372E850C0#1199100962296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#11#sappfpar#
#1.5#C000AC1A1C5000000000005501AB28FE0004429372E850C0#1199100962296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 INSTANCE_NAME#
#1.5#C000AC1A1C5000000000005601AB28FE0004429372E850C0#1199100962296#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_25.out#
#1.5#C000AC1A1C5000000000005701AB28FE0004429372E88B58#1199100962311#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#11#
#1.5#C000AC1A1C5000000000005801AB28FE0004429372E88B58#1199100962311#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#11#sappfpar#
#1.5#C000AC1A1C5000000000005901AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#11#sappfpar#0#
#1.5#C000AC1A1C5000000000005A01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#12#sappfpar#
#1.5#C000AC1A1C5000000000005B01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 DIR_EXECUTABLE#
#1.5#C000AC1A1C5000000000005C01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_26.out#
#1.5#C000AC1A1C5000000000005D01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#12#
#1.5#C000AC1A1C5000000000005E01AB28FE000442937313B620#1199100965140#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#12#sappfpar#
#1.5#C000AC1A1C5000000000005F01AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#12#sappfpar#0#
#1.5#C000AC1A1C5000000000006001AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#13#sappfpar#
#1.5#C000AC1A1C5000000000006101AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 DIR_CT_RUN#
#1.5#C000AC1A1C5000000000006201AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_27.out#
#1.5#C000AC1A1C5000000000006301AB28FE00044293733EE0E8#1199100967969#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#13#
#1.5#C000AC1A1C5000000000006401AB28FE00044293733F1F68#1199100967985#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#13#sappfpar#
#1.5#C000AC1A1C5000000000006501AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#13#sappfpar#0#
#1.5#C000AC1A1C5000000000006601AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:133)#Java###Process ID , name has been started.#2#14#sappfpar#
#1.5#C000AC1A1C5000000000006701AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:135)#Java###Command line: #2# #sappfpar pf=C:/usr/sap/NW7/SYS/profile/NW7_SCS00_CP-CHN-3F-029 rdisp/msserv_internal#
#1.5#C000AC1A1C5000000000006801AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.logProcessInfo(OsProcessController.java:136)#Java###Standard out: #2# #C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
tmp
Sappfpar_28.out#
#1.5#C000AC1A1C5000000000006901AB28FE00044293736A0BB0#1199100970798#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.launch(OsProcessController.java:120)#Java###Process ID has been started.#1#14#
#1.5#C000AC1A1C5000000000006A01AB28FE00044293736A4648#1199100970813#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:176)#Java###Waiting for process ID , name to finish.#2#14#sappfpar#
#1.5#C000AC1A1C5000000000006B01AB28FE0004429373953678#1199100973627#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.tools.proc.OsProcessController.waitFor(OsProcessController.java:209)#Java###Process ID , name has been finished, exit code .#3#14#sappfpar#0#
#1.5#C000AC1A1C5000000000006C01AB28FE00044293739B6868#1199100974033#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:350)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.InitialParametersDetector.initializeJspmDataModel(InitialParametersDetector.java:350)#Java###JSPM data model has been initialized.##
#1.5#C000AC1A1C5000000000006D01AB28FE0004429373B0E080#1199100975440#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:264)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:264)#Java###Initialize dialog has been processed.##
#1.5#C000AC1A1C5000000000006E01AB28FE0004429373B0E080#1199100975440#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.login(DialogController.java:654)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.login(DialogController.java:654)#Java###Starting dialog...#1#LogIn#
#1.5#C000AC1A1C5000000000007701AB28FE00044293754DE6E0#1199101002508#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.login(DialogController.java:659)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.login(DialogController.java:659)#Java###Dialog has been confirmed by the user.#1#LogIn#
#1.5#C000AC1A1C5000000000007801AB28FE00044293754EDCF8#1199101002571#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.checkConnectivity(DeploymentManagerImpl.java:172)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.checkConnectivity(DeploymentManagerImpl.java:172)#Java###Checking connectivity for SDM server on host , port ...#2#CP-CHN-3F-029#50118#
#1.5#C000AC1A1C5000000000007901AB28FE0004429375703FD8#1199101004759#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.checkConnectivity(DeploymentManagerImpl.java:181)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.checkConnectivity(DeploymentManagerImpl.java:181)#Java###Connection to SDM server on host , port is valid.#2#CP-CHN-3F-029#50118#
#1.5#C000AC1A1C5000000000007A01AB28FE00044293757671C8#1199101005165#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1138)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1138)#Java###Detecting kernel exchange directory of the J2EE Engine...##
#1.5#C000AC1A1C5000000000007B01AB28FE00044293757671C8#1199101005165#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1146)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1146)#Java###You can find additional information in log file $.#1#C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
log
log_20071231170532
KERNEL_DETECTION_01.LOG#
#1.5#C000AC1A1C5000000000008901AB28FE0004429375A0AA60#1199101007932#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1158)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.SystemInitializer.getMsgServerDirectoryAndUnicodeFlag(SystemInitializer.java:1158)#Java###Parameter DIR_CT_RUN from with value will be used as target directory for unicode kernel update.#2#NW7_DVEBMGS01_CP-CHN-3F-029#C:/usr/sap/NW7/SYS/exe/uc/NTI386#
#1.5#C000AC1A1C5000000000008A01AB28FE0004429375A384D8#1199101008119#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:749)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:749)#Java###Starting retrieving SDM substitution variable with name ...#1#com.sap.portal.deploy.pcd#
#1.5#C000AC1A1C5000000000008B01AB28FE0004429375A384D8#1199101008119#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:756)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:756)#Java###Connecting to SDM Server on host , port ...#2#CP-CHN-3F-029#50118#
#1.5#C000AC1A1C5000000000008C01AB28FE0004429375A3FDF0#1199101008150#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:788)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:788)#Java###You can find additional information in SDM log file .#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/log/sdmcl20071231113648.log#
#1.5#C000AC1A1C5000000000008D01AB28FE0004429375A71AD0#1199101008354#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:749)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:749)#Java###Starting retrieving SDM substitution variable with name ...#1#com.sap.portal.deploy.pcdcontent#
#1.5#C000AC1A1C5000000000008E01AB28FE0004429375A71AD0#1199101008354#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:756)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:756)#Java###Connecting to SDM Server on host , port ...#2#CP-CHN-3F-029#50118#
#1.5#C000AC1A1C5000000000008F01AB28FE0004429375A7CE80#1199101008400#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:788)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.deploymentmgr.DeploymentManagerImpl.getSubstVar(DeploymentManagerImpl.java:788)#Java###You can find additional information in SDM log file .#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/log/sdmcl20071231113648.log#
#1.5#C000AC1A1C5000000000009001AB28FE0004429375AAEB60#1199101008604#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.deployment.order.DeploymentOrderSet.xinit>(DeploymentOrderSet.java:143)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.deployment.order.DeploymentOrderSet.xinit>(DeploymentOrderSet.java:143)#Java###Parsing of file and extracting the relative deployment data model has finished.#1#C:/usr/sap/NW7/DVEBMGS01/j2ee/JSPM/config/dodf.xml#
#1.5#C000AC1A1C5000000000009101AB28FE0004429375AE7D70#1199101008838#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:197)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:197)#Java###Receiving information about deployed J2EE Engine components...##
#1.5#C000AC1A1C5000000000009201AB28FE0004429375B19668#1199101009041#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:211)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:211)#Java###A valid SQL data source for is obtained.#1#jdbc/pool/NW7#
#1.5#C000AC1A1C5000000000009301AB28FE0004429375D01ED0#1199101011042#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:225)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:225)#Java###API to the system component version tables has been obtained.##
#1.5#C000AC1A1C5000000000009401AB28FE0004429375D01ED0#1199101011042#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:228)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:228)#Java###System component version tables will be synchronized with SDM repository.##
#1.5#C000AC1A1C5000000000009501AB28FE0004429375D2BEB0#1199101011214#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:235)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:235)#Java###You can find additional information in SDM log file .#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/log/sdmcl20071231113651.log#
#1.5#C000AC1A1C5000000000009601AB28FE000442937BD618E8#1199101112097#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:412)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:412)#Java###You can find additional information in SDM log file .#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/log/sdmcl20071231113832.log#
#1.5#C000AC1A1C5000000000009701AB28FE000442937BD65768#1199101112113#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:417)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:417)#Java###Access to SDM repository has been obtained. Start to read SDM repository content.##
#1.5#C000AC1A1C5000000000009801AB28FE000442937BD9E978#1199101112347#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:421)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:421)#Java###Data about components deployed on the engine is obtained from SDM repository.##
#1.5#C000AC1A1C5000000000009901AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#JLOGVIEW#sap.com#
#1.5#C000AC1A1C5000000000009A01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C5000000000009B01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C5000000000009C01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C5000000000009D01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C5000000000009E01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C5000000000009F01AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C500000000000A001AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C500000000000A101AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.extractDataFromRepositoryExplorer(ComponentDetector700.java:609)#Java###Could not detect version information in the system component version tables for software component /. Information from SDM repository will be used.#2#CORE-TOOLS#sap.com#
#1.5#C000AC1A1C500000000000A201AB28FE000442937C8878F8#1199101123787#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:314)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:314)#Java###Data from SDM repository has been read.##
#1.5#C000AC1A1C500000000000A301AB28FE000442937C8D7A38#1199101124115#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:381)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j700.compdetector.ComponentDetector700.detectComponents(ComponentDetector700.java:381)#Java###Information about deployed J2EE Engine components has been received.##
#1.5#C000AC1A1C500000000000A401AB28FE000442937C8DB8B8#1199101124131#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.readVersionInformation(DetectSDMComponent.java:503)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.readVersionInformation(DetectSDMComponent.java:503)#Java###Retrieving SDM version by parsing ...#1#C:/usr/sap/NW7/DVEBMGS01/SDM/program/version.txt#
#1.5#C000AC1A1C500000000000A501AB28FE000442937C8DB8B8#1199101124131#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.readVersionInformation(DetectSDMComponent.java:538)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.sdmdetection.DetectSDMComponent.readVersionInformation(DetectSDMComponent.java:538)#Java###SDM version with release , SP level , patch level found in .#5#SAP_JAVASL#7.00#06#0#C:/usr/sap/NW7/DVEBMGS01/SDM/program#
#1.5#C000AC1A1C500000000000A601AB28FE000442937C8DF738#1199101124147#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:361)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:361)#Java###Looking for system kernel(s) under directory .#1#C:
usr
sap
NW7
SYS
exe#
#1.5#C000AC1A1C500000000000A701AB28FE000442937C8DF738#1199101124147#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:371)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:371)#Java###Central instance kernel directory is .#1#C:
usr
sap
NW7
SYS
exe
uc
NTI386#
#1.5#C000AC1A1C500000000000A801AB28FE000442937C8E31D0#1199101124162#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1098)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1098)#Java###Starting searching for kernel version in directory ...#1#C:/usr/sap/NW7/SYS/exe/uc/NTI386#
#1.5#C000AC1A1C500000000000A901AB28FE000442937C8E31D0#1199101124162#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1107)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1107)#Java###You can find additional information in log file .#1#C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
log
log_20071231170532
KERNEL_DETECTION_02.LOG#
#1.5#C000AC1A1C500000000000B701AB28FE000442937C9C81E0#1199101125100#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1122)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.kernel.detect.DetectKernelComponent.detectKernelComponentFromExeDirectory(DetectKernelComponent.java:1122)#Java###Kernel with release , SP level , patch level found in .#5#SAP KERNEL UNICODE WINDOWS_I386#7.00#52#0#C:/usr/sap/NW7/SYS/exe/uc/NTI386#
#1.5#C000AC1A1C500000000000B801AB28FE000442937C9C81E0#1199101125100#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:407)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j630.sysinfo.ExeDirLocator.determineMultipleKernels(ExeDirLocator.java:407)#Java###SCS kernel directory is .#1#C:
usr
sap
NW7
SYS
exe
uc
NTI386#
#1.5#C000AC1A1C500000000000B901AB28FE000442937C9F21C0#1199101125272#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:285)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.DialogController.execute(DialogController.java:285)#Java###Login dialog has been processed.##
#1.5#C000AC1A1C500000000000BA01AB28FE000442937C9F21C0#1199101125272#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:262)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:262)#Java###Starting dialog...#1#SelectPackageType#
#1.5#C000AC1A1C500000000000CE01AB28FE000442938B53B438#1199101371987#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.deployment.SelectInboxViewGranularityStep.processUI(SelectInboxViewGranularityStep.java:159)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.deployment.SelectInboxViewGranularityStep.processUI(SelectInboxViewGranularityStep.java:159)#Java###The user has chosen for Inbox granulation.#1#Support Package Stack#
#1.5#C000AC1A1C500000000000CF01AB28FE000442938B53B438#1199101371987#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:292)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:292)#Java###Dialog : the user has chosen the Next dialog button.#1#SelectPackageType#
#1.5#C000AC1A1C500000000000D001AB28FE000442938B53B438#1199101371987#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:296)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.jspm.gui.deployment.DeploymentProcessController.execute(DeploymentProcessController.java:296)#Java### dialog has been processed.#1#SelectPackageType#
#1.5#C000AC1A1C500000000000D101AB28FE000442938B53B438#1199101371987#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:181)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:181)#Java###Starting scanning Inbox for deployable J2EE Engine components...#1#
CP-CHN-3F-029
sapmnt
trans
EPS
in#
#1.5#C000AC1A1C500000000000D201AB28FE000442938B53EED0#1199101372002#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:195)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:195)#Java###You can find additional information in log file $.#1#C:
usr
sap
NW7
DVEBMGS01
j2ee
JSPM
log
log_20071231170532
SCAN_INBOX_01.LOG#
#1.5#C000AC1A1C500000000000D301AB28FE000442938B53EED0#1199101372002#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:205)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.newsdu.NewSDUProvider.listInbox(NewSDUProvider.java:205)#Java###Scanning of Inbox for deployable J2EE Engine components has finished.##
#1.5#C000AC1A1C500000000000D401AB28FE000442938B53EED0#1199101372002#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.j2ee.tools.spstackanalyzer.SPStackAnalyzer.analyzeSPStacksDir(SPStackAnalyzer.java:147)#######Thread[main,5,main]##0#0#Info#1#com.sap.sdt.j2ee.tools.spstackanalyzer.SPStackAnalyzer.analyzeSPStacksDir(SPStackAnalyzer.java:147)#Java###Starting searching for stack definition files in the Inbox...##
#1.5#C000AC1A1C500000000000D501AB28FE000442938B583878#1199101372283#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:756)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:756)#Java###Exception has occurred during the execution of the phase.##
#1.5#C000AC1A1C500000000000D601AB28FE000442938B583878#1199101372283#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:755)#######Thread[main,5,main]##0#0#Error#1#com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:755)#Java###java.lang.StringIndexOutOfBoundsException: String index out of range: -9##
#1.5#C000AC1A1C500000000000D701AB28FE000442938B583878#1199101372283#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##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_PROCESS#
#1.5#C000AC1A1C500000000000D801AB28FE000442938B583878#1199101372283#/System/Server/Upgrade/Phases/JSPM/JSPMPhases/JSPM_PROCESS##com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:793)#######Thread[main,5,main]##0#0#Info#1#c -
Error during application installation on my MacBook Pro
I am trying to install MasterWriter 2.0 onto my MacBook Pro without success.
Actions Taken:
When I contacted the 3rd Party Program TechSupport, he instructed me to delete folders, however the folders were never originally installed by the program, so he had me create them. Installation still failed
He told me to try downloading the dmg file from a different browser, originally downloaded with Chrome. Tried with Firefox and Safari. Still unable to install. However, with Safari downloaded file did receive an error message related to a .jar. 3rd Party Program Tech Support said it was my computer, he couldn't help.
After searching forums, I saw that it could be a JAVA error, as the codes I received had to do with a .jar file. Made sure to perform Software Update, installed the available JAVA update, then tried to installed program. Still unable install MasterWriter.
I have an iMac, so I tried to install on that machine. Success, however, the iMac is not the computer on which I do my writing.
Up until now, all these actions were performed in OS 10.7.4.
Then, using this situation as an excuse to upgrade OS, I clean installed the OS 10.8.1 onto my MacBook Pro.
Knowing that MasterWriter uses Java, and that I need it for Visual Thesaurus (another program on my computer), I installed a version of Java 6 as I know the OS10.8.1 doesn't install JAVA by default.
Now when I try to install MasterWriter I receive this error message: An unexpected error occurred while installing "cd51.dat". 1008:17,-4.
Searching the forums led me to references about case-sensitive files and repairing permissions.
I've reparied permissions and get the following.
Repairing permissions for “Macintosh HD”
Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.
Permissions differ on “usr/lib/ruby”; should be lrwxr-xr-x ; they are drwxr-xr-x .
Repaired “usr/lib/ruby”
Permissions repair complete
All this and I still can't install MasterWriter on my laptop. I'd appreciate suggestions. Thanks.I'm afraid I've got no more help to offer. All I can suggest is that the software may not be Mountain Lion-ready, and that you may just be encountering a different set of hurdles. Actually, that being the case, maybe MasterWriter's technical support could offer you some help this time (ie. assuming that this is actually a diffeent problem to the original one with Lion)?
If your license permits, and you have Windows 7, maybe you could install the software onto a Boot Camp partition? At least that way you'd get it running on your MBP.
Hope you get it sorted. -
Download error during application install
I get the error code 80070490, whenever I want to install a new app or when I wanted to update an existing app. I am using Nokia Lumia 630. I tried to install the application both in phone memory as well as SD card memory. But I get the same error.
Please let me know how to resolve this.Try to delete and add the Email account again.
If this doesn't work, reset your phone.
Setings-about-reset your phone.
Make sure you have backup of the important data like contacts before doing reset.
Hope this helps.
-------------------If this post helped you, click on accept as solution.------------------
-----------------------------Appreciate by clicking on white star.---------------------------- -
Implfactory.properties not found error during application installation
Hi,
I am facing some problem during deployment of application on websphere in Linux machine.
it says "implfactory.properties not found". However when i try to install the same application on some other linux machine. It goes fine.
As this is happening during installation of kit. Can u please let me know which jar file is missing from the Websphere path.
~amanHi !! Could you tell me where I might find this implfactory.jar file ?
I've looked around several systems, but have yet to find this jar.
Most systems work, and only one does not.
thanks....... -
Error during application of the NLS patch 6678700 for 6678700_ZHS language
FAILED: file XLIFFLoader.class on worker 8 for product xdo username XDO.
Time is: Thu Feb 24 2011 10:54:01
Assigned: file XLIFFLoader.class on worker 1 for product xdo username XDO.
Time is: Thu Feb 24 2011 10:54:01
Assigned: file XLIFFLoader.class on worker 3 for product xdo username XDO.
Time is: Thu Feb 24 2011 10:54:01
ATTENTION: All workers either have failed or are waiting:
FAILED: file XLIFFLoader.class on worker 1.
FAILED: file XLIFFLoader.class on worker 2.
FAILED: file XLIFFLoader.class on worker 3.
FAILED: file XLIFFLoader.class on worker 4.
FAILED: file XLIFFLoader.class on worker 5.
FAILED: file XLIFFLoader.class on worker 6.
FAILED: file XLIFFLoader.class on worker 7.
FAILED: file XLIFFLoader.class on worker 8.
ATTENTION: Please fix the above failed worker(s) so the manager can continue.。。。。
。。。。。。。。work log
Not able to read from utility map file.
adjava -ms128m -mx256m -Xrs -nojit oracle.apps.xdo.oa.util.XLIFFLoader UPLOAD -DB_USERNAME &un_apps -DB_PASSWORD &pw_apps -JDBC_CONNECTION &jdbc_db_addr -APPS_SHORT_NAME AMW -TEMPLATE_CODE AMW_RPT_SOD_VIOL_R -FILE_NAME &fullpath:amw:patch/115/publisher/templates/ZHS:AMWVIOLRPT.xlf
Could not find the main class: oracle.apps.xdo.oa.util.XLIFFLoader. Program will exit.
Error:
Program exited with status 1
Cause: The program terminated, returning status code 1.
Action: Check your installation manual for the meaning of this code on this operating system.
Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA
AD Java
Version 12.0.0
NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.
Reading product information from file...
Reading language and territory information from file...
Reading language information from applUS.txt ...
Temporarily resetting CLASSPATH to:
"F:\oracle\VIS\apps\apps_st\appl\ad\12.0.0\java\adjava.zip;F:\oracle\VIS\apps\tech_st\10.1.3\appsutil\jdk\lib\dt.jar;F:\oracle\VIS\apps\tech_st\10.1.3\appsutil\jdk\lib\tools.jar;F:\oracle\VIS\apps\tech_st\10.1.3\appsutil\jdk\jre\lib\rt.jar;F:\oracle\VIS\apps\apps_st\comn\java\lib/appsborg.zip;F:\oracle\VIS\apps\tech_st\10.1.2\forms\java;F:\oracle\VIS\apps\tech_st\10.1.2\forms\java\frmall.jar;F:\oracle\VIS\apps\tech_st\10.1.2/jlib/ewt3.jar;F:\oracle\VIS\apps\tech_st\10.1.2\j2ee\OC4J_BI_Forms\applications\formsapp\formsweb\WEB-INF\lib\frmsrv.jar;F:\oracle\VIS\apps\a"
Calling F:\oracle\VIS\apps\tech_st\10.1.3\appsutil\jdk\jre\bin\java.exe ...
java.lang.NoClassDefFoundError: oracle/apps/xdo/oa/util/XLIFFLoaderCaused by: java.lang.ClassNotFoundException: oracle.apps.xdo.oa.util.XLIFFLoader
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
Could not find the main class: oracle.apps.xdo.oa.util.XLIFFLoader. Program will exit.
Exception in thread "main" -
BRFPlus: error during application creation
Hi,
I'm getting an error in FDT_Workbench when trying to create an application with non-local ( 'System' or 'Customizing') storage type. After selecting development package and transport request, it comes back with two error messages:
*. Check if a changeable development package is assigned to the application
*. Object can only be changed in its original system Display Help
If anyone got any ideas pls let me know.
Thanks!
Sergesolved - oss note 1282506
-
ERROR during Application Server Installation
Hi SAP Experts,
I am trying to install Application Server for my ECC6.0 system, but its giving me the following error
An exception occurred while connecting to the message server instance <SID>/DVEBMGS10 on host <hostname>-123, port 3910.<br>DIAGNOSIS: The original exception was: wapsmod.ms.MsAttachFailed:
Connect to message server (<hostname>-123/3910) failed: NIEHOST_UNKNOWN..<br>SOLUTION: Make sure that the message server is started.
Please help !!
Thanks,
Nitesh JainHi,
I would trash and start again....does not take that long for a Dialog instance...
Could be a typo error when you inputted....
Be careful when it's asking for the dialog server name then asks for the databse server name as it fills in the
dialog server name for both...
Mark -
Support Pack upgrade error in Import Phase
Hello,
Currently I am upgrading SCM system with Support pack level 12 to 20 . When i am applying Basis 12 to 20. I got an error in Import_Proper phase.
Could you please help me on this? I tried and still searching solution for this..But no luck...
Os is : AIX and
Log File: /usr/sap/trans/log/SAPIB70013.xxx
Main import
Transport request : SAPKB70013
System : xxxx
tp path : tp
Version and release: 372.04.71 700
child process 934006 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_OBJECT_COLLECTION==========CT
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1212554 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_WDR_APPLICATION_WINDOW=====CT
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1171520 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_WDY_MD_EVENT_SOURCE========CI
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1331412 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_LOAD
tabname: ECSCR_DATA
len (char): 106
key: EC_TEST_DATA 00000000P10 IECATTDEFAULT
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
insert / update sequence failed due to an error in DBI.
maybe there's a concurrent process which inserted this table entry at the same time.
insert / update sequence failed due to an error in DBI.
maybe there's a concurrent process which inserted this table entry at the same time.
child process 1310922 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_END
tabname: WDY_APP_PROPERTY
len (char): 64
key: DEMO_UIEL_DROPDOWN_BY_IDX DEMO_VIEW
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
import portion 018446 - 999999 not imported because the child processes died for unknown reason
child process 1310924 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_report_interface
fcode: CLOSE_LINE_MODE
tabname: SOURCE
len (char): 40
key: CL_WDY_MD_OUTGOING_EVENT======CT
retcode: 1
SQL error -913 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -913, ER
child process 1286192 terminated -> setting rc=12 for this import portion
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_LOAD
tabname: ECSCR_DATA
len (char): 106
key: EC_TEST_DATA 00000000P10 IECATTDEFAULT
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
import portion 009158 - 018411 not imported because the child processes died for unknown reason
import portion 018412 - 018527 not imported because the child processes died for unknown reason
import portion 018528 - 999999 not imported because the child processes died for unknown reason
sap_dext called with msgnr 1:
db call info -
function: db_xrtab
fcode: RT_MI_LOAD
tabname: ECSCR_DATA
len (char): 106
key: EC_TEST_DATA 00000000P10 IECATTDEFAULT
retcode: 1
SQL error -904 accessing : [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -904, ER
Main import
End date and time : 20100909034914
Ended with return code: ===> 12 <===
| ######################################
Thanks and Regards,
Sankar
SAP BASIS ConsultantHi,
Thanks for you reply. I restarted import but no luck still. I activated some object also not working. when i call SPAM it is not going to the SPAM pager. Showing dump...
Runtime Errors CALL_FUNCTION_NOT_FOUND
Except. CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time 10.09.2010 09:41:37
Short text
Function module "POSS_UIREQ_OPT_SUBMIT" not found.
What happened?
The function module "POSS_UIREQ_OPT_SUBMIT" is called,
but cannot be found in the library.
Error in the ABAP Application Program
The current ABAP program "SAPLSTXC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
not caught in
procedure "OPEN_FORM" "(FUNCTION)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
The program "SAPLSTXC" contains the CALL FUNCTION statement.
The name of the function module to be called is "POSS_UIREQ_OPT_SUBMIT".
No function module exists with the name "POSS_UIREQ_OPT_SUBMIT".
All function modules are listed in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Pay particular attenti
upper/lower case and underscores ("_").
or
b) Transport error
c) In the case of an enqueue/dequeue module,
the lock object may not have been activated
(ABAP/4 Dictionary).
When i tried to check function module it is not there..
Could you please help on this?
Regards,
Sankar Basis Consultant -
SAP_BASIS IMPORT_PROPER Error during SPAM for CRM Upgrade
Hi All,
During SPAM IMPORT_PROPER for component SAP_BASIS, encountered error. Checking the Import Logs of the queue, we see error logs in Activate inactive runtime objects. Sample message below.
May we ask how to fix the error for us to be able to continue the upgrade? Thanks.
Activation of sample nametabs with appended fields
06:17:30: Retcode 512: error in DDL statement for ALCCMCUSTP - repea
t
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of ALCCMCUSTP
06:17:42: Retcode 512: error in DDL statement for ALCCMCUSTV - repea
t
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of ALCCMCUSTV
06:17:55: Retcode 512: error in DDL statement for ARC_DESTR_VETO - repea
t
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of ARC_DESTR_VETO
06:18:07: Retcode 512: error in DDL statement for DB6_OPTPROFILE - repea
t
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of DB6_OPTPROFILE
06:18:19: Retcode 512: error in DDL statement for FDT_TRACE_0200 - repea
t
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of FDT_TRACE_0200
06:18:31: Retcode 512: error in DDL statement for FDT_TRACE_0201 - repea
t
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of FDT_TRACE_0201
06:18:43: Retcode 512: error in DDL statement for GE071KF_OLD_NT - repea
t
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of GE071KF_OLD_NT
06:18:55: Retcode 512: error in DDL statement for GTABKEYEXC20 - repea
t
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of GTABKEYEXC20
06:19:07: Retcode 512: error in DDL statement for GTABKEY_CASCADE - repea
t
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of GTABKEY_CASCADE
06:19:19: Retcode 512: error in DDL statement for GTABKEY_COMPEXCL - repea
t
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of GTABKEY_COMPEXCL
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of GTABKEY_COMPSETS
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of GTABKEY_C_SYS
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of GTABKEY_EXT
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLS
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of IACXU
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLS
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of IACXUT
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLS
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of IACXU_C1
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of IACXU_C_TEMP
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of STORE_HELP
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of STORE_LINK_IND
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of SWWOUTBOX
Error -204-SQL0204N when executing ADD-FIELD of is an undefined name. SQLSTA
Error in DDL statement for when executing ADD-FIELD of
(dummy, do not translate)
No DDL commands found for activation of SWWWITEXT
21 shadow nametab activations resulted in errors
Begin: Activation of shadow nametabs with DDL (2014/03/19 06:17:30)
End: Activation of shadow nametabs with DDL (2014/03/19 06:19:31)
Begin: Activation of shadow nametabs with DDL (2014/03/19 06:19:31)
(dummy, do not translate)
Regards,
PhilipHi Philip,
Could you please check the below SAP Note. It is a composite notes which has listing of various errors during upgrade
822379 - Known problems with Support Packages in SAP NW 7.0x AS ABAP
Hope this will be useful
Thanks and Regards
DJ -
MS05 transaction throws "SQL error: error during INSERT (table: &)"
Hi Team,
I am a BASIS engineer on MM system. we have a strange problem from customers we see an error on the MS05 screen with "SQL error: error during INSERT (table: &)" and when the support team runs MS01 transaciton this error gets resolved.
What I would like to know is what could be the likely cause of this error and how we can prevent it.
When I check the SM21 logs i noticed one log with "Transaction cancellation 61 204 ( PLAF )"
and under additional document section is the log I see the below information
Usually, the reason for this error is that an entry already exists
with the same key.
This problem can occur if the client was copied with the movement data
without adjusting the number range intervals.
Please check if the number ranges for this table have been set
correctly and, if necessary, correct the number range interval.
I am from BASIS and I have no clue in how the MM transactions are linked can any MM gurus help in identifying the root cause for this problem.
any help on this is highly appreciated
thanks
VijayHi
Are MS05 & MS01 you're referring is a T-code?. if so, then they are associated with planning and a PP consultant can give a more clear picture on it. Try posting this to a PP forum.
Based on the error log, i guess this may arise because of the number range problem, when the document is getting saved and record is being tried to inserted into a table.
Thanks
E.Avudaiappan
Maybe you are looking for
-
Any way to get rid of email contacts mixed in with phone numbers?
Hi. My email contacts and phone numbers are mixed together and I want just my phone numbers to show. This is found by tapping the green phone icon and going to contacts.
-
When downloading Firefox for mail, when It arrives at drop down widow stateing you may not be authorized user, etc. Two choices are offered: preferred: Administrator or PC user when I select the second choice the download ceases? I have tried every k
-
PR Creation at Inspection lot creation
Dear QM Experts can we generate Purchase requisition with the creation of Inspection lot, Automatically. in my case there are some inspection operation performed by external agency for which he charge some amount for services. for this i created a co
-
Help on Sitecatalyst Integration
All, Need help with Sitecatalyst Integartion. Using AEM 5.6. Referred to the below link, https://dev.day.com/docs/en/cq/5-6/administering/integrating_with_adobe_marketing_cloud/si tecatalyst.html Could someone please guide me with steps . I set up a
-
Has anybody captured an error frame occurence with CAN driver version 2.2
I was very excited about the appearance of the Comm Error Frame Type in version 2.0 of the driver. I have a Series 2 card and was working with the CAN driver version 2.2 to attempt capture error frames with an in house written tool. Currently we have