Solman 3.2
Dear all ,
I had 2 queries regarding the solution manager 3.2 -->
1. I want to implement the business process monitoring in solution manager 3.2 .i had gone throough the sap documentation but it does nt help much . If anybody had done this b4 , please help .
Is this is the paid service . Or we had to take the certification for business pr monitoring .
2. WE are having the our support desk on client 010 of Solutionmanager and change request mgmt is on 099 . Can we change the client of support desk to 099 with all existing messages . Please suggest as this is very urgent
Any kind of suggestions will be helpful.
Warm Regards
Chirag Kohli
Hello Michael
For normal SolMan operations you don't need the java stack (but a windows client! SolMan Transactions don't work with the JavaGui).
If you have a Netweaver04 system with SP-Stack >= 11 you can use the Solution Manager Diagnostics as a separate installation, see the link
http://service.sap.com/~form/sapnet?_SCENARIO=01100035870000000202&_SHORTKEY=01100035870000634682&
I cannot tell more, because have decided to wait for SolMan 4.0 (March 2006) which will have it incorporated.
Similar Messages
-
SOLMAN EHP1 - anyone can create support message in Satellite System's Help?
Hi,
I just curios that why everyone can create support message in satellite system-> help -> create support message?
I tested with restricted profile user and without role SAP_SUPPDESK_CREATE, NO BP created but he still manage to create support message???? Any idea??
Also, same goes to any user can process ticket in SOLMAN with no BP-Employee role and SAP_SUPPDESK_* roles assigned.
Your kind input is very much appreciated.
Thanks,
Nicholas ChangHi Nicholas
If you are using a "Named" user instead of the Trusted Relationship in the RFC maintained in BCOS_CUST for entry OSS_MSG then this is quite possible. In this case the "Named" user will be used to call the interface to create message and the calling user ie the end user creating the ticket will only be used as "Reporter" of the message.
The user entered in the RFC details probably has the authorization to create Support desk messages.
Regards
Amit -
Creating a New Task in SOLMAN Change request Management
Dear all,
We are using SOLMAN 4.0 and scm functionality.In the change request screen we have a create follow up task(+ icon on top left).What is the use of this task,can we asign a task to some particular person?for example can i assign task to tester?If the task has not completed the task,while closing the correction will it give error?
Please give your suggestions.
Thanks in advance,
Avinash.Hi,
Pls click the check button(next to activate button)
see the SLG1 log generated remove the errors shown in red.
One it is done u press the refresh button & thn u cn create the task list
chk
https://websmp202.sap-ag.de/~sapdownload/011000358700000657692007E/ECTS_CHARM_SP12.PDF
/people/dolores.correa/blog/2008/07/26/first-steps-to-work-with-change-request-management-scenario
http://help.sap.com/saphelp_sm32/helpdata/en/0c/5b2160f6fa4b83a3674a210b1cdeb0/content.htm
Regards
Prakhar -
Logical component in SolMan using SMSY
Hi,
What is a logical component and why is it necessary. Why do we create that in our solman system for the landscape.
Also i was going through one tutor in rkt-solman link for creating logical component. It shows for a r/3 system. Is the same selection valid for the Netweaver component also.
Help required and shall be appreciated as well.Hi,
First of all thanks for the reply.
One thing is while i create a new system with assistant, and select the product as netweaver and proceed it asks me to select the main instance. What is this main instance. Say for me the system i am adding is the one having J2ee engine and portal plus trex on it. It doesnot have the ABAP instance. So what should be my selection. Should it be only WebAS Java or java + portal + trex.
Secondly what i did was i selected java and EP and Trex and proceeded. It didn't give me the option of entering the System Number and Message Server. In the next screen the only option i had was to assign logical component. If i select the box then it asks for client but the box for client is disabled.
Don't know what to do. Also RFC anyway is required. In such a case what should be the case. How should i create those RFC's and what RFC's are required for the same.
Lot of questions. Hope to get the detailed reply.
Answers will be rewarded nicely.
Thanks -
Error in installing Solman 4.0 SR2
Hi,
An Error occured during the installation of Solman 4.0 SR2 in import ABAP phase.
Sofware and Hardware configurartion:
Java 1.4.2_12
Database MSSQL 2005 SP2
Solution manager 4.0 SR2
Dual core 2.6 GHZ
2 gb ram
160gb hard drive
Plz find attached the sapinst.log file and import_monitor.log file.
Needfull help in this regard would be highly appreciated. Deserving points will be rewarded.
Best Regards
Omeir.
*import_monior.log*
INFO: 2007-09-21 01:21:36
Import Monitor is started.
CONFIG: 2007-09-21 01:21:36
Application options:
dbCodepage=4103
dbType=MSS
extFiles=no
importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
jobNum=3
loadArgs= -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-09-21 01:21:36
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-09-21 01:21:36
List of packages with views: 'SAPVIEW'.
TRACE: 2007-09-21 01:21:36 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
INFO: 2007-09-21 01:21:36 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2007-09-21 01:21:36
Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2007-09-21 01:21:37
Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
INFO: 2007-09-21 01:21:37
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is started.
TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDIC' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPSDIC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDIC.TSK MSS -l SAPSDIC.log
TRACE: 2007-09-21 01:21:37 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDIC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -loadprocedure fast
INFO: 2007-09-21 01:25:22 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is successfully completed.
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP1\DATA\SAPSSEXC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSEXC.TSK MSS -l SAPSSEXC.log
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPAPPL0.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL0.TSK MSS -l SAPAPPL0.log
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is started.
TRACE: 2007-09-21 01:25:36 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL1' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAPAPPL1.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL1.TSK MSS -l SAPAPPL1.log
TRACE: 2007-09-21 01:25:37 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
TRACE: 2007-09-21 01:25:37 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
TRACE: 2007-09-21 01:25:38 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
INFO: 2007-09-21 13:22:54
Import Monitor is started.
CONFIG: 2007-09-21 13:22:54
Application options:
dbCodepage=4103
dbType=MSS
extFiles=no
importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
jobNum=3
loadArgs= -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-09-21 13:22:54
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-09-21 13:22:54
List of packages with views: 'SAPVIEW'.
TRACE: 2007-09-21 13:22:54 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
INFO: 2007-09-21 13:22:54 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2007-09-21 13:22:54
Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2007-09-21 13:22:58
Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
INFO: 2007-09-21 13:22:58
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is started.
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
TRACE: 2007-09-21 13:23:08 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPAPPL0.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPAPPL1.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-09-21 13:23:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is started.
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is started.
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPAPPL2.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPAPPL2.TSK MSS -l SAPAPPL2.log
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is started.
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSRC' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAPSSRC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSSRC.TSK MSS -l SAPSSRC.log
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPPOOL' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPPOOL.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPPOOL.TSK MSS -l SAPPOOL.log
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPPOOL' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -loadprocedure fast
TRACE: 2007-09-21 13:23:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSRC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -loadprocedure fast
TRACE: 2007-09-21 13:23:25 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2.cmd -dbcodepage 4103 -l SAPAPPL2.log -loadprocedure fast
INFO: 2007-09-21 13:24:19 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is successfully completed.
TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is started.
TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSPROT' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSPROT.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSPROT.TSK MSS -l SAPSPROT.log
TRACE: 2007-09-21 13:24:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSPROT' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -loadprocedure fast
INFO: 2007-09-21 13:25:38 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is successfully completed.
TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is started.
TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDOCU' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP2\DATA\SAPSDOCU.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSDOCU.TSK MSS -l SAPSDOCU.log
TRACE: 2007-09-21 13:25:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDOCU' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -loadprocedure fast
INFO: 2007-09-21 13:26:05 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is successfully completed.
TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is started.
TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLEXC' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSLEXC.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLEXC.TSK MSS -l SAPSLEXC.log
TRACE: 2007-09-21 13:26:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLEXC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -loadprocedure fast
INFO: 2007-09-21 13:26:30 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is successfully completed.
TRACE: 2007-09-21 13:26:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is started.
TRACE: 2007-09-21 13:26:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPCLUST' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPCLUST.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPCLUST.TSK MSS -l SAPCLUST.log
TRACE: 2007-09-21 13:26:56 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPCLUST' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -loadprocedure fast
INFO: 2007-09-21 13:27:12 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is successfully completed.
TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is started.
TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLOAD' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPSLOAD.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPSLOAD.TSK MSS -l SAPSLOAD.log
TRACE: 2007-09-21 13:27:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLOAD' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -loadprocedure fast
INFO: 2007-09-21 13:27:28 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is successfully completed.
INFO: 2007-09-21 13:27:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is successfully completed.
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is started.
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is started.
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDDIM' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDDIM.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDDIM.TSK MSS -l SAPDDIM.log
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDFACT' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDFACT.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDFACT.TSK MSS -l SAPDFACT.log
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDDIM' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -loadprocedure fast
TRACE: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDFACT' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -loadprocedure fast
INFO: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is successfully completed.
INFO: 2007-09-21 13:27:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is successfully completed.
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is started.
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPUSER.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPUSER.TSK MSS -l SAPUSER.log
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDODS' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP3\DATA\SAPDODS.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAPDODS.TSK MSS -l SAPDODS.log
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -loadprocedure fast
TRACE: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -loadprocedure fast
INFO: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is successfully completed.
INFO: 2007-09-21 13:28:24 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is successfully completed.
TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is started.
TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAP0000' import package:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -ctf I E:\Export\EXP4\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL" SAP0000.TSK MSS -l SAP0000.log -o D
TRACE: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAP0000' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -loadprocedure fast
INFO: 2007-09-21 13:28:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
INFO: 2007-09-21 13:34:56 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is successfully completed.
WARNING: 2007-09-21 13:35:24
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2007-09-21 13:35:24
3 error(s) during processing of packages.
INFO: 2007-09-21 13:35:24
Import Monitor is stopped.
INFO: 2007-09-21 13:38:06
Import Monitor is started.
CONFIG: 2007-09-21 13:38:06
Application options:
dbCodepage=4103
dbType=MSS
extFiles=no
importDirs=E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS
jobNum=3
loadArgs= -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-09-21 13:38:06
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-09-21 13:38:06
List of packages with views: 'SAPVIEW'.
TRACE: 2007-09-21 13:38:06 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is started.
INFO: 2007-09-21 13:38:06 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2007-09-21 13:38:06
Data codepage 1100 is determined using TOC file 'E:\Export\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2007-09-21 13:38:06
Version table 'SVERS' is found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
INFO: 2007-09-21 13:38:06
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\Export\EXP2\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is started.
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is started.
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
TRACE: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0' import package into database:
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast
ERROR: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-09-21 13:38:07 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPAPPL1.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: 2007-09-21 13:38:08 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is interrupted with R3load error.
Process 'C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0.cmd -dbcodepage 4103 -l SAPAPPL0.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPAPPL0.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2007-09-21 13:38:36
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2007-09-21 13:38:36
3 error(s) during processing of packages.
INFO: 2007-09-21 13:38:36
Import Monitor is stopped.
sapinst.log
INFO 2007-09-21 13:22:26
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.2.xml'.
INFO 2007-09-21 13:22:27
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/inifile.3.xml'.
INFO 2007-09-21 13:22:29
Execute step
Component W2K_ServicePack_Check|ind|ind|ind|ind
Preprocess of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
INFO 2007-09-21 13:22:40
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/MSS/CENTRAL/AS/keydb.2.xml'.
INFO 2007-09-21 13:22:41
Execute step runMigrationMonitor of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0.
INFO 2007-09-21 13:22:51
Switched to user: prdadm.
INFO 2007-09-21 13:22:51
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\import_monitor.java.log.
INFO 2007-09-21 13:22:51
Switched to user: prdadm.
INFO 2007-09-21 13:22:51
Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS.
INFO 2007-09-21 13:22:51
Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst is written to the logfile import_monitor.java.log.
WARNING 2007-09-21 13:35:24
Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code 103. Output:
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 16, completed 1, failed 0, total 18.
Import Monitor jobs: running 2, waiting 15, completed 1, failed 0, total 18.
Import Monitor jobs: running 3, waiting 14, completed 1, failed 0, total 18.
Loading of 'SAPAPPL0' import package: ERROR
Loading of 'SAPAPPL1' import package: ERROR
Import Monitor jobs: running 1, waiting 14, completed 1, failed 2, total 18.
Import Monitor jobs: running 0, waiting 14, completed 1, failed 3, total 18.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 0, waiting 14, completed 1, failed 3, total 18.
Import Monitor jobs: running 1, waiting 13, completed 1, failed 3, total 18.
Import Monitor jobs: running 2, waiting 12, completed 1, failed 3, total 18.
Import Monitor jobs: running 3, waiting 11, completed 1, failed 3, total 18.
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 2, failed 3, total 18.
Import Monitor jobs: running 3, waiting 10, completed 2, failed 3, total 18.
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 3, failed 3, total 18.
Import Monitor jobs: running 3, waiting 9, completed 3, failed 3, total 18.
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 4, failed 3, total 18.
Import Monitor jobs: running 3, waiting 8, completed 4, failed 3, total 18.
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 5, failed 3, total 18.
Import Monitor jobs: running 3, waiting 7, completed 5, failed 3, total 18.
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 6, failed 3, total 18.
Import Monitor jobs: running 3, waiting 6, completed 6, failed 3, total 18.
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 7, failed 3, total 18.
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 1, waiting 6, completed 8, failed 3, total 18.
Import Monitor jobs: running 2, waiting 5, completed 8, failed 3, total 18.
Import Monitor jobs: running 3, waiting 4, completed 8, failed 3, total 18.
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 9, failed 3, total 18.
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 1, waiting 4, completed 10, failed 3, total 18.
Import Monitor jobs: running 2, waiting 3, completed 10, failed 3, total 18.
Import Monitor jobs: running 3, waiting 2, completed 10, failed 3, total 18.
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 11, failed 3, total 18.
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 1, waiting 2, completed 12, failed 3, total 18.
Import Monitor jobs: running 2, waiting 1, completed 12, failed 3, total 18.
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 13, failed 3, total 18.
Loading of 'SAPAPPL2' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 14, failed 3, total 18.
ERROR 2007-09-21 13:35:24
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-09-21 13:35:24
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
INFO 2007-09-21 13:38:06
An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
INFO 2007-09-21 13:38:06
Switched to user: prdadm.
INFO 2007-09-21 13:38:06
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\import_monitor.java.log.
INFO 2007-09-21 13:38:06
Switched to user: prdadm.
INFO 2007-09-21 13:38:06
Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS.
INFO 2007-09-21 13:38:06
Output of C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst is written to the logfile import_monitor.java.log.
WARNING 2007-09-21 13:38:36
Execution of the command "C:\j2sdk1.4.2_12\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\Export\EXP1;E:\Export\EXP2;E:\Export\EXP3;E:\Export\EXP4 -installDir "C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS" -orderBy "" -r3loadExe C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code 103. Output:
java version "1.4.2_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
Import Monitor jobs: running 1, waiting 3, completed 14, failed 0, total 18.
Import Monitor jobs: running 2, waiting 2, completed 14, failed 0, total 18.
Import Monitor jobs: running 3, waiting 1, completed 14, failed 0, total 18.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 14, failed 1, total 18.
Loading of 'SAPAPPL1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 14, failed 2, total 18.
Loading of 'SAPAPPL0' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 14, failed 3, total 18.
ERROR 2007-09-21 13:38:36
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-09-21 13:38:36
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
INFO 2007-09-21 13:38:40
An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
Edited by: mohammed omeir on Dec 31, 2007 2:30 PMHi Markus,
Its says a previous run may not have finished clearly.
What i need to do now?
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070921132313
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Sep 1 2006 00:38:35
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
Hi Markus,
Its says a previous
(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK.bck already seems to exist
a previous run may not have been finished cleanly
file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK possibly corrupted
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070921132321
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070921133807
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Sep 1 2006 00:38:35
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -loadprocedure fast
(DB) INFO: connected to DB
(TSK) ERROR: file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK.bck already seems to exist
a previous run may not have been finished cleanly
file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\SAPAPPL1.TSK possibly corrupted
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
C:\usr\sap\PRD\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070921133807 -
Installation problem with SolMan on SUSE 9,0 / Oracle
Hi Experts,
I have just started to work with SAP environment. My first challenge is to install Solution Manager on SUSE 9.0 Linux. I have faced quite lot of error messages and managed to solve them with help of support and forum pages. But the last mile seems to be the hardest one. Installation stopped on phase 42 / 45 (Configure System Landscape Directory) with following errors:
WARNING 2007-02-08 09:18:13
Execution of the command "/usr/sap/HSM/DVEBMGS01/exe/jlaunch UserCheck.jlaunch com.sap.security.tools.UserCheck /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/lib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install/sharedlib:/tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/install -c sysnr=01 -c ashost=haukka -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u SLDDSUSER -p XXXXXX -message_file UserCheck.message" finished with return code 4. Output:
Warning: tmpfs at /dev/shm is configured quite small with 1956 MB! Minimum value is 2048 MB.
Recommended size is 75 % of RAM + swap.
Warning: tmpfs at /dev/shm is configured quite small with 1956 MB! Minimum value is 2048 MB.
Recommended size is 75 % of RAM + swap.
Feb 8, 2007 9:18:10 AM Info: User management tool (com.sap.security.tools.UserCheck) called for action "checkCreate"
Feb 8, 2007 9:18:11 AM Error: Exception during execution of the operation
[EXCEPTION]
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=haukka SYSNR=01 GWHOST=haukka GWSERV=sapgw01 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner 'haukka:sapgw01' not reached
TIME Thu Feb 8 09:18:11 2007
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -10
MODULE nixxi.cpp
LINE 2764
DETAIL NiPConnect2
SYSTEM CALL connect
ERRNO 111
ERRNO TEXT Connection refused
COUNTER 2
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:456)
at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:922)
at com.sap.mw.jco.JCO$Client.connect(JCO.java:3171)
at com.sap.security.tools.UserCheck.main(UserCheck.java:172)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Feb 8, 2007 9:18:12 AM Info: Leaving with return code 4
INFO 2007-02-08 09:18:13
Removing file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/dev_UserCheck.
INFO 2007-02-08 09:18:13
Removing file /tmp/sapinst_instdir/SOLMAN/SYSTEM/ORA/CENTRAL/AS/dev_UserCheck.clone.
ERROR 2007-02-08 09:18:13
CJS-30196 Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=haukka SYSNR=01 GWHOST=haukka GWSERV=sapgw01 PCS=1
LOCATION CPIC (TCP/IP) on local host with Unicode
ERROR partner 'haukka:sapgw01' not reached
TIME Thu Feb 8 09:18:11 2007
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -10
MODULE nixxi.cpp
LINE 2764
DETAIL NiPConnect2
SYSTEM CALL connect
ERRNO 111
ERRNO TEXT Connection refused
COUNTER 2
ERROR 2007-02-08 09:18:13
FCO-00011 The step createSLDDSUser with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Configuration|ind|ind|ind|ind|5|0|NW_Usage_Types_Configuration_AS|ind|ind|ind|ind|0|0|NW_CONFIG_SLD|ind|ind|ind|ind|0|0|createSLDDSUser was executed with status ERROR .
I have stopped the installation, rebooted the system and started the installation again. Well that didnt help at all. After that I have to start Oracle database and listener to proceed with old installation.
Can you give me any advices how to solve this problem and finish the installation?
Grateful for help.
JukkaHi Dolores,
Thank you for your advices.
I would appreciate further assistance with this problem because I couldnt work it out jet.
I logged in to the Visual Admin by using go file in usr/sap/HSM/DVEBMGS01/j2ee/admin.
The Visual Administrator screen is opening but I cannot connect in.
The error message popping up is "Cannot open connection on host xx.yy.xx.yy and port 50004".
The login parameters specified are:
Display name: j2ee
User name: Administrator / (J2EE_ADMIN)
Host: localhost
HTTP Port: 50004
Load balancing method: manual
Transport layer: default
I tried with two different username, see above.
I also tried DDIC user logon via ssh command in Shell console, but didnt succeed.
Here is the information in some of those files your mentioned:
trc file: "dev_rd", trc level: 1, release: "700"
Wed Jan 31 10:47:35 2007
***LOG S00=> GwInitReader, gateway started ( 19402) [gwxxrd.c 1677]
systemid 387 (Intel x86 with Linux)
relno 7000
patchlevel 0
patchno 46
intno 20050900
make: single threaded, Unicode, optimized
pid 19402
gateway runs with dp version 210000(ext=109000) (@(#) DPLIB-INT-VERSION-210000-UC)
Wed Jan 31 10:47:37 2007
gw/local_addr : 0.0.0.0
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
Wed Jan 31 10:48:05 2007
Bind service sapgw01 (socket) to port 3301
Wed Jan 31 10:48:06 2007
GwPrintMyHostAddr: my host addresses are :
1 : [192.168.229.131] haukka (HOSTNAME)
2 : [127.0.0.1] localhost (LOCALHOST)
Wed Jan 31 10:48:07 2007
DpSysAdmExtCreate: ABAP is active
DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
Wed Jan 31 10:48:57 2007
DpShMCreate: sizeof(wp_adm) 12744 (1416)
DpShMCreate: sizeof(tm_adm) 4011160 (19956)
DpShMCreate: sizeof(wp_ca_adm) 28800 (96)
DpShMCreate: sizeof(appc_ca_adm) 9600 (96)
DpCommTableSize: max/headSize/ftSize/tableSize=500/8/520056/520064
DpShMCreate: sizeof(comm_adm) 520064 (1032)
DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
DpShMCreate: sizeof(file_adm) 0 (68)
DpShMCreate: sizeof(vmc_adm) 0 (1596)
DpShMCreate: sizeof(wall_adm) (38456/34360/80/184)
DpShMCreate: sizeof(gw_adm) 48
DpShMCreate: SHM_DP_ADM_KEY (addr: 0x457a0000, size: 4663248)
DpShMCreate: allocated sys_adm at 0x457a0000
DpShMCreate: allocated wp_adm at 0x457a1e88
DpShMCreate: allocated tm_adm_list at 0x457a5050
DpShMCreate: allocated tm_adm at 0x457a5080
DpShMCreate: allocated appc_ca_adm at 0x45b7f598
DpShMCreate: allocated comm_adm at 0x45b81b18
DpShMCreate: system runs without file table
DpShMCreate: allocated vmc_adm_list at 0x45c00a98
DpShMCreate: allocated gw_adm at 0x45c00ad8
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 0x45c00b08
Wed Jan 31 10:48:58 2007
MtxInit: -2 0 0
Wed Jan 31 10:49:38 2007
GwDpInit: attached to gw_adm at 0x45c00ad8
Wed Jan 31 10:49:39 2007
***LOG Q0I=> NiIWrite: writev (32: Broken pipe) [nixxi.cpp 3797]
ERROR => NiIWrite: SiSendV failed for hdl 1 / sock 12
(SI_ECONN_BROKEN; UD; ST; 127.0.0.1:0) [nixxi.cpp 3797]
LOCATION SAP-Gateway on host haukka / sapgw01
ERROR connection to partner 'localhost:0' broken
TIME Wed Jan 31 10:49:39 2007
RELEASE 700
COMPONENT NI (network interface)
VERSION 38
RC -6
MODULE nixxi.cpp
LINE 3797
DETAIL NiIWrite
SYSTEM CALL writev
ERRNO 32
ERRNO TEXT Broken pipe
COUNTER 1
ERROR => GwIConnectHandle GwWrite failed (NIECONN_BROKEN) [gwxxrd.c 8689]
C-STACK -
(CTrcStack2+0x78)[0x80c1938]
(SigIGenAction+0x2d1)[0x81e9451]
[0xffffe440]
trc file: "sapstartsrv.log", trc level: 0, release: "700"
Thu Feb 8 09:15:05 2007
<<- ERROR: SapSSLInit(read_profile=1)==SSSLERR_LIB_NOT_FOUND
SapSSLInit failed => https support disabled
Webservice thread started, listening on port 50013
Trusted http connect via Unix domain socket '/tmp/.sapstream50013' enabled.
trc file: "dev_disp.new", trc level: 1, release: "700"
sysno 01
sid HSM
systemid 387 (Intel x86 with Linux)
relno 7000
patchlevel 0
patchno 48
intno 20050900
make: single threaded, Unicode, optimized
pid 19381
Wed Jan 31 10:48:07 2007
CCMS: start to initalize 3.X shared alert area (first segment).
Wed Jan 31 10:48:10 2007
DpMsgAdmin: Set release to 7000, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]
DpMsgAdmin: Set patchno for this platform to 48
Release check o.K.
Wed Jan 31 10:49:57 2007
MBUF state ACTIVE
Wed Jan 31 10:50:11 2007
DpModState: change server state from STARTING to ACTIVE
Wed Jan 31 10:50:18 2007
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ
For some reason the latest files are dated 1.2.2007?
Hopefully You can see the problem from this log file information.
As I mentioned earlier I am a green novice at SAP systems and Linux.
Best regards
Jukka -
Installation Of Solman 7.1 aix Oracle failed with Java Error
Dear All,
We are doing SOLMAN Installation 7.1 SR1 AIX Oracle.
Now the installation stopped at the 19th phase "IMport ABAP"as in the attached screenshot.
OS : AIX 6100-07-02-1150
Database: Oracle 11.2.0.3
Java Version currently maintained: java version "1.4.2"
When i checked in log File import_monitor.java.log ( /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS) ,
[root@solmantrg: /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS] cat import_monitor.java.log
java version "1.6.0_45"
Java(TM) SE Runtime Environment (build 6.1.051)
SAP Java Server VM (build 6.1.051 23.5-b02, May 30 2013 05:04:21 - 61_REL - optU - aix ppc64 - 6 - bas2:197575 (mixed mode))
Required system resources are missing or not available:
Import directory '/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP1' does not exist;
Import directory '/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP2' does not exist;
Import directory '/cddumps/Solman_Export_Cds/51042607_2/DATA_UNITS/EXP3' does not exist;
Import directory '/cddumps/Solman_Export_Cds/51042607_2/DATA_UNITS/EXP4' does not exist.
[root@solmantrg: /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS]
Also i checked all the above import Directories [
'/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP1'
'/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP2'
'/cddumps/Solman_Export_Cds/51042607_2/DATA_UNITS/EXP3'
'/cddumps/Solman_Export_Cds/51042607_2/DATA_UNITS/EXP4'
] and all the above import directories are present in my system.
Later from the above log, i compared the Java Version of our System
[root@solmantrg: /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS] java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build caix64142ifx-20110630 (SR13 FP10) (JIT enabled: jitc))
[root@solmantrg: /tmp/sapinst_instdir/SOLMAN71/SYSTEM/ORA/CENTRAL/AS] which java
/usr/java14_64/jre/bin/java
Kindly clarify the below Queries.
1)Is the above Solman installation error was due to Java version? If so, do we need to install java version "1.6.0_45" in Solman Server to proceed with the installation.
2)Cant we proceed the Solman installation with the current Java version (java version "1.4.2") of our System .
3) What is the actual Prerequistes to be maintained for JAVA. I have downloaded the Installtion guide from SMP.
but in the installation guide, The exact java version to be maintained to proceed with the Solman Installation 7.1 SR1 is not mentioned anywhere.
4)If we install the Java 1.6, do we need to start Solman installation from the scratch . Any reboot required after installing java 1.6?
5)Because of the inconsistencies in java version in our System, The installation shows the Error " Import directory does not exist "?
6)Please tel the cause of the Error
Kindly assist to proceed with the installation
Regards,
Gayathri.KHello Gayathri
The import_monitor.java.log says the JRE used is 1.6 - java version "1.6.0_45"
There must be multiple JRE's installed on the system.
Run the below command and check the output
ls -lad /usr/java*
Few things I would try.
Is the '/cddumps/Solman_Export_Cds/51042607_1/DATA_UNITS/EXP1' an NFS mount ? If yes use a local file system.
Create a directory called /SMINSTALL and move all from /cddumps/Solman_Export_Cds
It should look like /SMINSTALL/51042607_1/DATA_UNITS/EXP1
Start the installation.
Try to use Java 1.4 or 1.5 and see if that helps.
You need to set the environment variable JAVA_HOME before starting the installation.
export JAVA_HOME=/usr/java14_64/jre
Are there any files/directories under 51042607_*/DATA_UNITS/EXP* ?
Regards
RB -
SOLMAN 7.1 SP10 CRM UI Service Desk - How to clear / remove Message Processor on a particular status
Hi Experts,
I have a requirement to remove the stated Message Processor, when the incident / Service Desk ticket is being saved using a particular status (Eg: Sent to Level 1).
Appreciate if someone can guide me how this can be done (whether using simple PPF (tcode SPPFCADM) or we are forced to use BFR+
Thanks in advance
Regards
ShahulThe solution is here
SOLMAN 7.1 CRM UI - "Reported By" Empty
Thanks to Ash. -
"Table VSEOPARENT is not in the database" after SolMan system copy to x64
Hi SDNners,
We've just completed a system copy of our SolMan 3.1 system onto a new
(Xeon x64 based) server. This system copy is part of the process of
moving SolMan 3.1 from an old server onto 64bit hardware and then
upgrading it to SolMan v4 and Oracle 10G.
Although the system appears to start properly in the MMC, we are unable
to log into the system through SAPGUI - we get a SYNTAX_ERROR window
instead of a logon screen.
I've checked the SysLog from within the MMC and noticed a number of
errors stating:
Database: Table VSEOPARENT is not in the database
Database: Table VSEOIFIMPL is not in the database
Database: Table VSEOIFCOMP is not in the database
I tried running SQL command 'select * from "SAPSOL"."VSEOPARENT"; and
it confirmed that the table didn't exist. I then ran the same command
on the source SolMan system and it showed that VSEOPARENT DID exist. I
don't understand how these VSEO* tables could have gone missing between
the source and target systems.
I've searched OSS for VSEO* and cannot find anything. Please help!
Thanks,
Arwel.We have 640 kernel, ECC 5.0 and BASIS patch 23.
For me the problem was with SAPVIEW table wasnt imported from source to target becuase SAPVIEW.STR file was 0 byte. STR files gets created in export preparation phase.
It did happen because on source side master DVD, there was no option for export preparation. I had only option for tablesplit and export db.
I did use ECC 5.0 SR2 Master DVD which had option for export preparation phase and that created SAPVIEW.STR file.
Using migration monitor I did re-export and re-import and this time all views are imported in target.
Regards,
Mamadi. -
unable to delete Role from User ID in SAP SOLMAN production system but able to from DEV with the same authorization, pls suggest
Hi,
For SU01 role removal, you do not need S_USER_AGR with 02, and as you mentioned both authorizations available in production, if so trace should not show you the S_USER_AGR with 02 with RC=04.
I would recommend to do role comparison for the user performing the activity. and then check if you have the S_USER_AGR with 02 in user buffer SU56.
But ideally it should not ask you S_USER_AGR for 02 through SU01, so please take help of abaper to debug it.
Also put trace in non-prd to see if S_USER_AGR is getting checked with 02 for removal through SU01.
BR,
Mangesh -
My SLD is configured in SOLMAN sys, How can I connect it with SAP PI system
Dear Friends
My Basis has configured SLD in Solman, Now I cant use SXMB_IFR tcode in my PI that suggest me some error. saying "error in connection cant read secure connection config" or something like that. Plus SLDCHECK tcode is also not happy. it suggest that RFC connections are missing.
It is clear that My SLD is not linked with PI system. something is missing in technical system part and its not even bridged. but since I am not a BASIS guy I dont know How can I configure it. Not even my BASIS guy understands that I need to bring SOLMAN SLD to PI.
Can anyone suggests me How can I bring my SOLMAN SLD to PI system so I can run SXMB_IFR tcode ? I need to create some rfc connection like LCRSAPRFC and SAPSLDAPI but dont know the connection type like t, or something else. Please englight me by suggesting How can I bring my SOLMAN SLD to PI.
One intresting observation is when I try to run my SLD over url using PI system as host it comes but says SLD is not configured properly and when I did the same practice with SOLMAN host it works fine and I didnt receive any error.
Please reply me. your any help will be appreciated greatly.
Regards
NaeemHi,
Preferebly PI should have it's own SLD. And SOLMAN could use PI's SLD.
Please check Installation guide and SLD Administration Guide from Service Market place before finalizing SLD architecture in your System landscape.
I guess SOLMAN will have only one Instance in system landscape. (Not three system landscape like Dev, Qa, Prod).
If you want to go ahead with your current SLD plan, then Change your SLD hostname in Exchange Profile of PI, to SOLMAN Host name.
Regards
Praveen K
Edited by: Praveen Kurni on Jul 7, 2011 6:12 PM -
SOLMAN monitoring of SAP XI/PI interfaces
Hello! ALL
We have been leveraging SAP XI/PI monitoring capabilities using the Alter Framework: ALRTCATDEF and setting up alert rules in RWB.
However, we would like to start leveraging SOLMAN monitoring features for monitoring SAP XI/PI interfaces.
Please, let us know if anyone has been using SOLMAN for monitoring SAP XI/PI AE & IE interface errors AND how it can be done; so that we can work with Basis in getting this set up in SOLMAN.
Any info - or - documentation and links related to SOLMAN monitoring of SAP XI/PI interfaces would help.
Your help is greatly appreciated!!
Thank you,
RituHi,
Please check below thread. You can use BPM functionality of Sol Man for Monitoring.
[Re: Central monitoring in SOLAM+ALE status]
Regards,
Gouri -
SAPRouter set up in Solman 7.1 sr1 release
Dear All,
we completed the installation Of Solman Server 7.1. Now we are in the process of activity "Configuration Of SOlman Server ".
RFC Destination SAP OSS not working. Connection and Authorization test for SAPOSS is failing with "Connection Error "
Connection test of RFC Destination ( SAPOSS) is failing with below error:
Logon Connection Error
Error Details Error when opening an RFC connection (LB: Hostname or service of the message ser
Error Details ERROR: partner '147.204.2.5:sapdp99' not reached
Error Details LOCATION: SAP-Server solmantrg_SMI_01 on host solmantrg (wp 2)
Error Details DETAIL: NiPConnect2: 147.204.2.5:3299
Error Details CALL: connect
Error Details COMPONENT: NI (network interface)
Error Details COUNTER: 27
Error Details ERROR NUMBER: 79
Error Details ERROR TEXT: Connection refused
Error Details MODULE: nixxi.cpp
Error Details LINE: 3286
Error Details RETURN CODE: -10
Error Details SUBRC: 0
Error Details RELEASE: 720
Error Details TIME: Fri Apr 25 13:04:19 2014
Error Details VERSION: 40
Authorization Test Of RFC Destination ( SAPOSS) IS FAILING WITH below error
Logon Connection Error
Error Details Error when opening an RFC connection (LB: Hostname or service of the message ser
Error Details ERROR: partner '147.204.2.5:sapdp99' not reached
Error Details LOCATION: SAP-Server solmantrg_SMI_01 on host solmantrg (wp 2)
Error Details DETAIL: NiPConnect2: 147.204.2.5:3299
Error Details CALL: connect
Error Details COMPONENT: NI (network interface)
Error Details COUNTER: 34
Error Details ERROR NUMBER: 79
Error Details ERROR TEXT: Connection refused
Error Details MODULE: nixxi.cpp
Error Details LINE: 3286
Error Details RETURN CODE: -10
Error Details SUBRC: 0
Error Details RELEASE: 720
Error Details TIME: Fri Apr 25 13:05:37 2014
Error Details VERSION: 40
In OSS1, parameter of the technical setting is attached. Please check attached screenshot for more details on the error
Please tel how to maintain OSS1 details and help to fix the RFC error of destination SAPOSS
Regards,
Gayathri.KGayathri,
Is your SAProuter installed on the same server as Solution Manager, or on another server? Since you said this was all working before when you were using SolMan 4.0, you must have already had a saprouter registered with SAP. Do you still have that SolMan 4.0 system? Or did you wipe it out before doing the fresh install of SolMan 7.1?
The SAProuter will have two IP addresses: an 'external' one that you have registered with SAP, and an 'internal' one that is on your company's private network. That internal IP address needs to be set up in OSS1 technical settings as the address of your "SAProuter at Customer Site". In your screenshot, you had these fields blank, and as Shkelzen pointed out, this isn't going to work until you fill that in:
Regards,
Matt -
Setting IT performance report in Solman
Hi,
We are trying to set up IT performance reporting in Solution Manager. BI client is same as production client. The Info objects are not getting activated. The job fails with the message to use a different BI client.
SOLMAN SM37 Job log:
Message text
Message class
Message no.
Message type
Job started
00
516
S
Step 001 started (program CCMSBI_SETUP_BATCH, variant , user ID KZHX33)
00
550
S
Incorrect client 025
00
001
S
use BI client 001.
00
001
S
Prerequisites check failed
00
001
A
Job cancelled
00
518
A
If any one faced this issue and resolved, kindly throw some light on it.
Thank you.
Regards,
ManjuHi Manju,
The issue is due to inactive object in the infocube .
Please check the note: 1110013 - ST: Manual activation of BI Content for E2E Diagnostics SP13 attachment . it will help to activate the inactive object.
or
Go to basis configuration -> step 5. configure automatically ->re-excute the Activate BW Source System. so it will reactive the infocube.
Also check the below discussion,
CCMS_BI_SETUP IT Performance Reporting Activation
Error :
20140620 050208[ERROR ]: Activation of InfoCube 0CCMDAY1 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMDAY1 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMDAY2 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMDAY2 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMMIN1 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMMIN1 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMMIN2 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMMIN2 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMMNTH1 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMMNTH1 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMMNTH2 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMMNTH2 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMQTR1 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMQTR1 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMQTR2 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMQTR2 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMVRKF failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMVRKF manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMWEEK1 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMWEEK1 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0CCMWEEK2 failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0CCMWEEK2 manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoCube 0SMD_PE2H failed
20140620 050208[HELP ]: Attempt to activate object CUBE:0SMD_PE2H manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoSet 0CCMIAGGR failed
20140620 050208[HELP ]: Attempt to activate object ISET:0CCMIAGGR manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoSet 0CCMIAVDT failed
20140620 050208[HELP ]: Attempt to activate object ISET:0CCMIAVDT manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of InfoSet 0CCMICURR failed
20140620 050208[HELP ]: Attempt to activate object ISET:0CCMICURR manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of MultiCube 0CCMPDATA failed
20140620 050208[HELP ]: Attempt to activate object MPRO:0CCMPDATA manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of MultiCube 0CCMSDSR failed
20140620 050208[HELP ]: Attempt to activate object MPRO:0CCMSDSR manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of MultiCube 0CCMSMTPH failed
20140620 050208[HELP ]: Attempt to activate object MPRO:0CCMSMTPH manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of MultiCube 0SMD_MPEH failed
20140620 050208[HELP ]: Attempt to activate object MPRO:0SMD_MPEH manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCMAGGR failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCMAGGR manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCMAVDT failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCMAVDT manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCMBUFF failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCMBUFF manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCMCURR failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCMCURR manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCMSDCFG failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCMSDCFG manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCMSYINF failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCMSYINF manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCMTHRS failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCMTHRS manually in transaction RSOR. If this is successful, execute setup again.
20140620 050208[ERROR ]: Activation of DSO 0CCM_SCFG failed
20140620 050208[HELP ]: Attempt to activate object ODSO:0CCM_SCFG manually in transaction RSOR. If this is successful, execute setup again."
Rg,
Karthik -
Using Solman to generate EWA, it came dump SYNTAX_EROR
Hi Experts there,
When I used solman 4.0 to generate satellite system which is ERP 2005's EWA, it came dump SYNTAX_ERROR
Syntax error in program "RDSVASAEA_SQL______________034 ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLDSVAS_PROC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RDSVASAEA_SQL______________034
" in include "RDSVASIEA_SQL______________034 " in
line 37:
"Field "DLD_GLOBALDATA001202" is unknown. It is neither in one of the s"
"pecified tables nor defined by a "DATA" statement. "DATA" statement. ""
"DATA" statement."
but this solman to generate EWA from exactly same systems but is DEV and QUA were ok.
please help me and thank you !
Wei WuHi,
Check this, 851621,863546 - It may solve your problem.
Also please provide if you have any other info, full dump report, support pack level.
Feel free to revert back.
--Ragu -
Error in background job scheduling in Solman 7.0
Hi Experts,
I am working with Solman 7.0 configuration. In the IMG node for Scheduling background jobs (Solution manager-> General Settings), while following the documentation to schedule the jobs, I am facing issues with the following jobs:
1. *SEND_SYSTEM_RELATIONSHIP_TO_SUPPORT *
This job got cancelled on immediate scheduling, however has been scheduled for next day. What could be the reason by which it got cancelled?
2. AI_SDK_FILL_FILE_TYPE_TABLE
I cant find a job of this name in the system (while all other jobs are already available in the system by default). But, there is a program with the same name. Should I schedule the same in SM36?
Regards,
Arun.Hi,
Yes schedule a job with program AI_SDK_FILL_FILE_TYPE_TABLE. Hope this solves your problem.
Feel free to revert back.
--Ragu
Maybe you are looking for
-
Error in schema validation in XI. Please help!
Hi Experts, I have a FILE to proxy scenario. In the sender agreement I have selected schema validation by Adapter. (Other option is by Integration Engine). Now when the file I get an error in sender file communication channel monitoring: Error: co
-
One inspection lot for multiple materials of purchase order line items
Hi All, My client requirement is one inspection lot for multiple materials of purchase order line items. Please share your thoughts. Thanks in advance for early reply. Regards, Jishu
-
How do I get Adobe PDF to show up as a printer option for Illustrator?
How do I get Adobe PDF to show up as a printer option for Illustrator?
-
Probleme mit Offnine-Dateien bei PSE 4
Hallo Community, ich bin neu hier und habe folgendes Problem mit Photoshop Elements 4: Um Speicherplatz freizugeben, habe ich mich entschlossen einen Teil meiner Fotosammlung auf eine DVD zu speichern. Dazu habe ich die Funktion brennen / backup benu
-
Initializing fields in the declaration
Hello, I'm not exactly a newbie on Java (I've been using it since 4 years ago), but today I question has come to my mind: What are the pros/cons of initializing a field directly in its declaration at the top of the class, like... Set<String> setOfStr