AlertRecipient list in Solman 7.1

Hi Experts,
I would like to know whether we can maintain different recepient lists for the different monitoring scenarios in Solman 7.1
Say I have 3 different teams for BI monitoring, PI monitoring and Miscellaneous (handles all other alerts).
Teams should receive their specific alert emails only (E.g: BI monitoring team should NOT receive PI alerts)
I create 3 different mail distribution lists named as BI_ALERT , PI_ALERT & MISC respectively.
Can we configure automatic alerts from :
          . BI Monitoring to be sent to BI_ALERT (only)
          . PI monitoring alerts to be sent to PI_ALERT (only)
          . All other alerts to MISC
Thanks in advance for your help.
Regards,
Pavan.

Hi,
please check below if it helps:
Please review the following chapter in the BPM SEtup Guide:
www.service.sap.com/bpm -> Media Library -> Technical Information
> 4.3.13 Notifications
> 6.3 Workflow Configuration
You can find an additional and more detailed documentation in
http://service.sap.com/bpm -> Media Library -> Technical Information ->
> Setup Guide - Auto-Reaction Messages .
Also check notes:
176492 - Automatic email when an alert occurs (RZ20)
617547 - RZ20: Sending alerts as mail and SMS
796998 - CCMS: Setting titles for alert mails
Regards,
Vikram

Similar Messages

Master list from solman

Dear all
please tell me how to create Buisness Process master List from solman?

Hi gautam,
If you are enquiring about the Buisness Process master list (BPML) creation in Solman..then plz follow the below steps:-
1>Go to the transaction:- SOLAR_EVAL - Project Analysis in ur solman server.
2>Select the Cross Tab Analysis tab under Assignments Section.
3>It will ask for the Project name..Choose ur project.
4>In Display Project Structure..Choose Display Completely radio Button.
5>Then in tab Selection section..Choose the reqd field u want to view in the Master list...like Transaction,..Config..test cases etc..
6>Based on the requirement,we can take full project View or part of also..For the same,In the Project Structure tab,Select Substructure field & in the same..we can select the appropriate Buisness Processes.
7>Choose Execute...
8>Then export it to Excel file..
Now u can view the total BPML file from solman,as reqd by u.
Thanks
JP
+91-9860831112

I need the check list for SOLMAN implementation

Hi gurus ,
i need the check list for solution manager implementation and what are the things to be discuss with the client , i am new to SOLMAN, i have to do this by the evening , any one can help me out
Cheers
Gopal.rao

Hi Gopal,
I am not sure if this thread of yours is in continuation of the other thread you have started which has been replied by two other Forum members.
The checklist depends upon which Scenario(s) of SolMan you are trying to implement.
- Implementation/ Upgrade of ERP systems
- Service Desk
- Change Request Monitoring
- Diagnostics
- Solution Monitoring (includes BPM/ Interface monitoring)
- Delivery of SAP Services (EWA, .....)
Unless you specify the scenario you are seeking information on, it is difficult for anyone to pose a satisfactory reply.
Best regards,
Srini

How to uninstall SAP?

I tried installing Solman 7.0 on the same host as PI 7.1 using multiple oracle homes. But now both installations have got screwed up and I would like to uninstall both before I start a fresh inst.
The status of each is as under:
PI 7.1: Was fully installed alongwith post-inst and in proper working condition until solman inst began. Now I cannot find any processes in the SAP console process list.
SolMan 7.0: Gets stuck on the "Create database" step due to an environment variable error.
In the Add/Remove programs, I am only able to see "SAP Application Server for System SOL". When I go to uninstall it, it says Please use the service Product > Additional software life-cycle tasks > Uninstall on the installation master DVD but I cannot find any such option on the DVD!
Note:
1. I cannot format and reinstall OS/DB since I only have remote desktop access to the server
2. I am using Windows 2003 R2 Enterprise x64
Thanks

Hi Prasad,
SolMan 7.0: Gets stuck on the "Create database" step due to an environment variable error.
If you understand that this installation stuck due to environmental Variable then Why you don't set that variable.
and
If you want to uninstall the system without format then you should have SAP IM cd and follow the sequence.
SAP ERP 6.0 Support Release 3
                --> Software Life-Cycle Options
                       --> Uninstall
                             --> Uninstall - System / Standalone Engine / Optional Standalone Unit
regards,
majamil

Notifications from R/3 4.6c to Solution Manager 3.2

Hello gurus,
Is it possible to transfer notifications from system R/3 4.6c(transaction IQS9) to Solution Manager 3.2. I have checked structure of tables and I found out that they are totally different between systems. Is there any way to transfer notifications to Solution Manager?

Hello Matjaz,
If Solution Manager is the centralized controller in your system, then if you make an entry in the BCOS_CUST table of your satellite system saying that your solman system is the destination of your OSS Messages raised from the satellite system, then those support messages raised in your satellite systems will appear in the notifications list of SolMan.
Hope it helps.
best regds,
Alagammai.

Solman Change Request Management Issue - about create task list

Dears,
We are now using Solman ChangeRM. I have created a maintainance project and maintained its logical component and IMG project. when I want to create a task list for this project, a message"The project is not released. Hence cycle can not be created" poped. The message no. is /TMWFLOW/CONFIG_UI017. Where can I release the project?
Thanks
Roger

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

Error list (solman 4 loading)

hi this is errors from different logs created when loading SOLUTION MANAGER 4
PLZ HELP ME
Install mode does not apply to a Terminal server configured for remote administration.
Could not get thread token.
Last error: 1008. I assume that no thread token exists.
Got process token.
Privileges:
Privilege SeBackupPrivilege, display name: Back up files and directories, not enabled.
Privilege SeRestorePrivilege, display name: Restore files and directories, not enabled.
Privilege SeShutdownPrivilege, display name: Shut down the system, not enabled.
Privilege SeDebugPrivilege, display name: Debug programs, not enabled.
Privilege SeAssignPrimaryTokenPrivilege, display name: Replace a process level token, not enabled.
Privilege SeIncreaseQuotaPrivilege, display name: Adjust memory quotas for a process, not enabled.
Privilege SeSystemEnvironmentPrivilege, display name: Modify firmware environment values, not enabled.
Privilege SeChangeNotifyPrivilege, display name: Bypass traverse checking, enabled.
Privilege SeRemoteShutdownPrivilege, display name: Force shutdown from a remote system, not enabled.
Privilege SeTcbPrivilege, display name: Act as part of the operating system, not enabled.
Privilege SeUndockPrivilege, display name: Remove computer from docking station, not enabled.
Privilege SeSecurityPrivilege, display name: Manage auditing and security log, not enabled.
Privilege SeTakeOwnershipPrivilege, display name: Take ownership of files or other objects, not enabled.
Privilege SeLoadDriverPrivilege, display name: Load and unload device drivers, not enabled.
Privilege SeManageVolumePrivilege, display name: Perform volume maintenance tasks, not enabled.
Privilege SeSystemProfilePrivilege, display name: Profile system performance, not enabled.
Privilege SeImpersonatePrivilege, display name: Impersonate a client after authentication, enabled.
Privilege SeSystemtimePrivilege, display name: Change the system time, not enabled.
Privilege SeCreateGlobalPrivilege, display name: Create global objects, enabled.
Privilege SeProfileSingleProcessPrivilege, display name: Profile single process, not enabled.
Privilege SeIncreaseBasePriorityPrivilege, display name: Increase scheduling priority, not enabled.
Privilege SeCreatePagefilePrivilege, display name:
Create a pagefile, not enabled.
File not found: [C:/DOCUME1/ADMINI1/LOCALS~1/Temp/sapinst_exe.3240.1176320585/msvcp71.dll].
INFO 2007-04-12 01:15:41
File not found: [C:/DOCUME1/ADMINI1/LOCALS~1/Temp/sapinst_exe.3240.1176320585/msvcr71.dll].
File not found: [C:/DOCUME1/ADMINI1/LOCALS~1/Temp/sapinst_exe.3240.1176320585/msvcp71.dll].
INFO       2007-04-12 01:15:41
           CJSlibModule::writeInfo_impl()
File not found: [C:/DOCUME1/ADMINI1/LOCALS~1/Temp/sapinst_exe.3240.1176320585/msvcr71.dll].
F:/Solution Manager & ECC6/BS\IM_WINDOWS_I386/NT/I386/sapinstevents.dll not found.
TRACE      [iaxxejsexp.cpp:188]
           EJS_Installer::writeTraceToLogBook()
./sapinstevents.dll not found.
TRACE      [iaxxejsexp.cpp:188]
           EJS_Installer::writeTraceToLogBook()
2007-04-12 01:16:05.937 STACK factor not empty; value : Java
Loading of 'SAPSDIC'
import package: OK
Import Monitor jobs: running 0, waiting 17, completed 1, failed 0, total 18.12:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/24/200712:46 PM 4/2

Hi, your OS 32 bit , i'm correct?
The main error are
D:Solman - 4.0Solman_Export
you use the blank (spaces) in the directory name for installation files, it's not allowed.
change to D:Solman_4.0Solman_Export (change to all other DVD's paths on your hard disk to )
after restart the installation from the beginning.
https://www.sdn.sap.com/irj/scn/wiki?path=/display/home/rulesofEngagement
Regards.

To view the list of users in Satellite Systems from Solman

Dear Friends,
We wish to view the list of users in a satellite system (say ECC5.0) from solution manager 4.0, can anyone help us to find the same.
Regards
Senthil

Hello Senthil,
You mean the list of BP associated to the satellite users already created? If this is the case
in DSWP, choose a Solution that has your satellite as system and go to Edit->BP
Add the satellite system to the list and if I don´t remember wrong you will get the
BP for the satellite users already created in the righ chart.
Sory if I don´t get the correct question?
Best regards,
Dolores

We need doument attached list order in SOLMAN according to date & time wise

Hi,
we are addding documents to ticket or issue in documents Tab (t-code crm_dno_monitor) But we need to display these file as per date and time wise.
regards
Ganesh
Moderator message: not a proper question, always try to solve problems yourself first, do not just dump specs, please search for available information.
Edited by: Thomas Zloch on May 9, 2011 9:59 AM

Check with badi ME_PROCESS_PO_CUST method PROCESS_HEADER - method SET_DATA

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

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 PM

Hi 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

Error While running Setup Wizard in SolMan Managed Systems

Hello,
I am getting the error listed below while I am trying to setup an Agent in SolMan Diag.
While I am running Setup Wizard, I am giving the message server port (50100) the same as I am getting from the systeminfo page: http://<My Server Name>:50100/sap/monitoring/SystemInfo.
When I change this port with 50104 which is my P4 port, It takes it and then gives me a message that "P4 port is unknown".
Any input?
Regards,
Ray
Failure with Message Server
An error occured while communicating with Message Server <My Server Name>:50100 through the host <My Server Name>: Error to retrieve the process from Message Server (detail: com.sap.bc.proj.jst
artup.impl.JStartupClusterControlExceptionImpl: The message server did not respond within 60 sec. Please check if the message server is running and if the socket connection has been established.); nes
ted exception is:
com.sap.bc.proj.jstartup.impl.JStartupClusterControlExceptionImpl: The message server did not respond within 60 sec. Please check if the message server is running and if the socket connection has bee
n established.(cause=com.sap.bc.proj.jstartup.impl.JStartupClusterControlExceptionImpl The message server did not respond within 60 sec. Please check if the message server is running and if the socket
connection has been established.)
Please check Message Server host/port, or enter the P4 ports in cluster table.

Hi furious
I have the same error , and finally I am find the solution, this error due to the enterprise admin permission, so go to main configuration tree (as shown on screenshot) click properties, click enterprise admin, click advance, again click enterprise
admin, click edit and select "this object and all descendant object" on Applies to option (as per screenshot) and select full control
after that you prepare your organization and It will works
cheers....................

Connection error while performing basic settings SOLMAN 4.0 SP12

Hi All,
We are currently facing a problem while performing Solution Manager 4.0 (SP12) basic configurations through the IMG Wizard. Within the "Initial Configuration Part I" section, an error while connecting to SAP is obtained (This is the full error message "Error creating communication to SAP Service and Support"). After checking at TX SM59, it was noticed that the RFC connections SAP-OSS y SAP-OSS-LIST-O01 (what are supposed to be created in previous steps by copying SAPOSS connection) were no created. We created them both manually (also tested) and everything was ok. We started the Wizard again, and the same error was obtained. However, it was noticed that the SAP-OSS RFC connection had been deleted. The system log shows the following:
00789 - Dialog work process No. 000 - XXXXXX - EQUIPO - 1 - SM_CONFIG_WZ - M_CONFIG_WZ_START - T - Transaction Problem - STSK
The same scenario occurs every time the above wizard is used.
It worth to mention that the SAPOSS connection works fine and also, just to perform a test, I was able to download a note correction through the SNOTE transaction.
Where should I check to see what is causing this connection error? Do I missing a previous configuration step?
Also, would be very helpful for us to get an step by step reference guide for SM configuration. We want to be sure we are no missing or mixed up anything.
Thanks so much for your help.
Regards

>
diego77 wrote:
> We are currently facing a problem while performing Solution Manager 4.0 (SP12) basic configurations through the IMG Wizard.
Why do you start configuration for SP12, although most current version is SolMan 7.0 EhP1 SPS19?
What scenarios / functions are you planning to use?
Best regards,
Ruediger

Error while updating SP's for Solman

Hello ,
I am updating the SP's for Solman. and I have come across these 3 errors, how do I resolve them
1.Function RSDDTREX_INDEX_CHECK (RSDDTREX_CHECK     01) does not fit into the existing function group ((RSDDTREX     06))
2.Table RSBGUI_R_TEST is not in nametab.
3.     Phase ADDON_CONFLICTS_?: Explanation of Errors
     Conflicts were found between the Support Packages that you want to
     import and the Add-Ons installed in the system. To guarantee the
     consistency of your system, the import is interrupted until all Conflict
     Resolution Transports (CRTs) for the listed Support Packages are
     included in the queue.
     To include the CRTs in the queue, proceed as follows:
     #NAME?
     - Leave this screen by choosing 'Cancel' (F12).
     #NAME?
       Service Marketplace or request them from your Add-On supplier.
     #NAME?
     #NAME?
       the beginning.
     If the problem involves an SAP Add-On, see SAP Note 53902, which tells
     you which CRTs resolve the conflicts. Otherwise contact the supplier of
     your Add-On for details on how to proceed.
     The following contains a table of Support Packages for each Add-On for
     which conflicts were detected. The column 'Information on the Conflict
     Resolution' specifies how you can resolve a conflict. For more
     information, select the corresponding 'Information for the Conflict
     Resolution'.
     Note:
     You are importing the queue in the test scenario. As this scenario is
     only used for performing analyses, you can skip the errors and continue
     the import in the next phase.
     In the standard scenario, however, note that the errors have to be
     rectified before importing can be continued in the next phase.
     Conflicts Between Add-On ST-SER 700_2006_1 and Support Packages
     Component     Release     Support Package     Information onConflict Resolution
     ST     400     SAPKITL425     CRT: DUMMY
Thanks Druva

Hi there,
Thank you cauz I did get some lead into the issue with your response.
I missed on some ST's which did give me a CRT error and I downloaded them and the problem is fixed now.
I have another question in my new post please have a look at it.
I am closing this thread.
Thank you
Druva

Invoking SOLMAN WS from a NON-SAP application

Hello All,
Has any one accessed the SAP SolMan web services from a non-sap application ? For my project, I need to talk to solman through its exposed operations as defined in the WSDL file
http://mycompany.com:8003/sap/bc/srt/rfc/sap/ict_service_desk_api?wsdl
When I invoke this WS through eclipse, after taking in the UID & PWD, it is returning appropriate values for:
RequestSystemGuid
RequestGuid
Getpossiblevalues
It fails for all other operations. For e.g. ListUnclosedIncidents returns and error called :
ErrorCode (unsignedByte): 13
Similary for the operation 'ReadCompleteIncident'
What is it that needs to be done to surmount this error ? Any pointers, suggestions ?
Thanks
Karthik

Hi, did you accomplish to solve your problem using the list unclosed incidents operation?
Best Regards
Nasoft

AlertRecipient list in Solman 7.1

Similar Messages

Maybe you are looking for