Self-Monitoring solman SP16 error

Hi gurus,
I need your help with Solution Manager Diagnostic configuration. I installed Solution Mananger 7.0 SP16 with Willy Introscope 7.2 and SMD in solution Manager.
When I run the wizard for Diagnostics Setup --> Managed Systems --> Managed Systems for Self-Monitoring (solman) I've this error and I understand this problem.
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (host01:6000) no Wilyhost Agent was detected from host host01. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
Step Wilyhost Agent Details
Created destination SM1_DVEBMGS00_server0
Created destination SM1|host01_SM1_00
Created action SAP GC|SM1_DVEBMGS00_server0 - SAP GC|SM1_DVEBMGS00_server0
Created action SM1 - SM1 AbapSystem
Created action SM1|host01_SM1_00 - SM1|host01_SM1_00 AbapInstance
Created 3 action(s).
0 Wilyhost Agent(s) and 0 EP Agent(s) from host host01 are connected to the EM.
Wilyhost Agent configuration finished without errors, but on Enterprise Manager (host01:6000) no Wilyhost Agent was detected from host host01. Please check the log file jvm_smdagent.out whether the Wilyhost Agent could connect to the Enterprise Manager. If the Enterprise Manager configuration has been changed recently please restart the SMD Agent on OS level.
Please, can someone helpme for this error. Any suggest is welcome.
Regards,
Sergio.

Hi:
Try to walk through this configuration guide, it may help you.
/people/federico.babelis2/blog/2006/04/25/system-monitoring-configuration-guide-for-dummies
Regards,
Federico

Similar Messages

How to change Self Monitoring Thresholds in SOLMAN 7.1 SP8?

Hello Expert,
I'm wondering if there is an option to change Self Monitoring Thresholds in SOLMAN 7.1 SP8? I'm getting so many SOLMAN Self Monitoring alert's emails, so looking forward to adjust the thresholds (if this is possible at all)?
Your help is always appreciated.
Thanks & regards,
MM

Hi Roland,
Thanks a lot for advice!
Sorry, how are you getting to this screen where you can create a custom template?
Somehow I can't find any option to create a custom template in step 3.2 of the Self-Mon in my system.
When I press 'Configure and Activate' button it's just activating the Self-Mon, without any option to create a custom template.
In Alerting Directory Browser I can see SAP Standard Template for Self-Mon,...
...but I'm struggeling to find where I can create the custom template a copy of this standard one?
Probably I'm missing something.
I'm on SP08.
You help is much appreciated.
Best,
MM

Various errors on self-monitoring (non-Prod) evironment

Hi all, i do have few issues that i see on the app srv log for PPM, any idea whats causing this errors:
- Component Performance metric calculations may be inaccurate or incomplete (usually getting this)
- Errors in AppServ log "Communication to Monitor Servlet failed" (always)
- Component objects not fully cached (rarely)
- No Component PeopleCode trace information (always)
I do get data populated in current and history tbls for PPM.
thanks

thx for the reply Nicolas
answers to your questions;
Peopletools version, ;8.48
database used (with version), Oracle 9i
OS (with version) :GENERIC (All Platforms)
what configuration setting has been done or not: its a self monitoring PPM setup
proper extract from your appserver/webserver log would be useful: im working on getting that from the customer
let me know your thoughts...

SAP on V6R1 - ABAP Import:Program 'Migration Monitor' exits with error code

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_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 .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

Hello,
We are doing an installation of SAP NW 7.01 SR1 on V6R1.
 
We were getting error in SAPAPPL2.TSK.bck we merged the files with following command:R3load --merge_only <TSK file> and refering sap note:Note 455195 - R3load: Use of TSK files.
 
We are again getting error in following steps:
 
sapinst.log
 
 WARNING 2009-09-30 23:25:28.477
Execution of the command "Y:\QOpenSys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 OS400 ppc64-64 j9ap64142sr13-20090310 (JIT enabled)
J9VM - 20090309_31291_BHdSMr
JIT - 20090210_1447ifx1_r8
GC - 200902_24)
I mport Monitor jobs: running 1, waiting 27, completed 0, failed 0, total 28.
 Loading of 'SAPNTAB' import package: OK
 Import Monitor jobs: running 0, waiting 27, completed 1, failed 0, total 28.
Import Monitor jobs: running 1, waiting 26, completed 1, failed 0, total 28. 
Import Monitor jobs: running 2, waiting 25, completed 1, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 24, completed 1, failed 0, total 28. 
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 2, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 23, completed 2, failed 0, total 28. 
Loading of 'SAPAPPL1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 3, failed 0, total 28. 
Import Monitor jobs: running 3, waiting 22, completed 3, failed 0, total 28. 
Loading of 'SAPAPPL2' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 3, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 21, completed 3, failed 1, total 28. 
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28. 
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 20, completed 5, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 19, completed 5, failed 1, total 28. 
Loading of 'SAPSDIC' import package: OK
Import Monitor jobs: running 2, waiting 19, completed 6, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 18, completed 6, failed 1, total 28. 
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 2, waiting 18, completed 7, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 17, completed 7, failed 1, total 28. 
Loading of 'SAPSSRC' import package: OK
Import Monitor jobs: running 2, waiting 17, completed 8, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 16, completed 8, failed 1, total 28. 
Loading of 'FUPARAREF' import package: OK
Import Monitor jobs: running 2, waiting 16, completed 9, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 15, completed 9, failed 1, total 28. 
Loading of 'TODIR' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 10, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 14, completed 10, failed 1, total 28. 
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 14, completed 11, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 13, completed 11, failed 1, total 28. 
Loading of 'E071K' import package: OK
Import Monitor jobs: running 2, waiting 13, completed 12, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 12, completed 12, failed 1, total 28. 
Loading of 'SAPPOOL' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 13, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 11, completed 13, failed 1, total 28. 
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 11, completed 14, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 10, completed 14, failed 1, total 28. 
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 2, waiting 10, completed 15, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 9, completed 15, failed 1, total 28. 
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 2, waiting 9, completed 16, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 8, completed 16, failed 1, total 28. 
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 2, waiting 8, completed 17, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 7, completed 17, failed 1, total 28. 
Loading of 'SAPSLEXC' import package: OK
Import Monitor jobs: running 2, waiting 7, completed 18, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 6, completed 18, failed 1, total 28. 
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 6, completed 19, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 5, completed 19, failed 1, total 28. 
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 5, completed 20, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 4, completed 20, failed 1, total 28. 
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 2, waiting 4, completed 21, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 3, completed 21, failed 1, total 28. 
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 22, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 2, completed 22, failed 1, total 28. 
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 23, failed 1, total 28. 
Import Monitor jobs: running 3, waiting 1, completed 23, failed 1, total 28. 
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 2, waiting 1, completed 24, failed 1, total 28. 
Loading of 'SAPAPPL0' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 25, failed 1, total 28. 
Loading of 'SAPSSEXC' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 26, failed 1, total 28. 
 
WARNING[E] 2009-09-30 23:25:28.524
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log,
 
ERROR 2009-09-30 23:25:28.914
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_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 .
 
 import_monitor.log.
 ****************************************************************************************************************************************************
 INFO: 2009-09-30 23:26:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
 
INFO: 2009-09-30 23:30:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0' import package is successfully completed.
 
INFO: 2009-09-30 23:31:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
 
WARNING: 2009-09-30 23:31:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2009-09-30 23:31:31
1 error(s) during processing of packages.
INFO: 2009-09-30 23:31:31
Import Monitor is stopped.
 *************************************************************************************************************************************************
 SAPAPPL02.LOG
 **************************************************************************************************************************************************
 TVV1 in *LIBL type *FILE not found. MSGID= Job=015908/SAPINST/QJVAEXEC
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) INFO: TVV1 created #20091001110304
 
(DB) INFO: TVV1 deleted/truncated #20091001110304
 
(IMP) INFO: import of TVV1 completed (0 rows) #20091001110304
 
(DB) ERROR: DDL statement failed 
(ALTER TABLE "TVV1" DROP PRIMARY KEY ) 
DbSlExecute: rc = 99 
(SQL error -539) 
error message returned by DbSl:
Table TVV1 in R3E04DATA does not have a primary or unique key. MSGID= Job=015908/SAPINST/QJVAEXEC
Your inputs will help a lot.
Regards,
Prasad

SAP ECC error:'Migration Monitor' exits with error code 103.

Hi All,
I am doing SAP ECC installation for windows 32 bit with MAXDB as backend.
I am stuck at the import ABAP.Getting error
ERROR 2008-08-08 16:10:53
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
1) imort_monitor.java.log-->contains
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 0, completed 18, failed 0, total 19.
Loading of 'SAPVIEW' import package: ERROR
Import Monitor jobs: running 0, waiting 0, completed 18, failed 1, total 19.
2)import_monitor.log
ERROR: 2008-08-08 16:10:36 com.sap.inst.migmon.LoadTask run
Loading of 'SAPVIEW' import package is interrupted with R3load error.
Process 'D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPVIEW.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
INFO: 2008-08-08 16:10:52
All import packages are processed.
WARNING: 2008-08-08 16:10:52
1 error(s) during processing of packages.
INFO: 2008-08-08 16:10:52
Import Monitor is stopped.
3)SAPVIEW.log
error message returned by DbSl:
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE VIEW "Z_T_CO_BW" ( "KOKRS" , "KOSTL" , "VERSN" , "KSTAR" , "WOG001" , "MEG001" ) AS SELECT T0002."KOKRS", T0002."KOSTL", T0001."VERSN", T0001."KSTAR", T0001."WOG001", T0001."MEG001" FROM "COSS" T0001, "CSKS" T0002 WHERE T0002."MANDT" = T0001."MANDT")
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
(DB) INFO: disconnected from DB
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: job finished with 3108 error(s)
D:\usr\sap\EC6\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20080808174211
Only SAPDB: SAPSID srvice of SAP DB is only up.
No other services of database are up.And i am not able to up the other services also.
Is it required to up the other services?
If not?
Why this error is occuring?
Any help will be appreciated.
Thanks&Regards
Manisha das

Hello Manisha,
The one of the possible reasons for this is due to lack of H/W.
Increase your RAM size to atleast 2GB and utilise the same while you are installing ECC in database parameters step..
If the issue is with H/W, then this should fix the issue.
Hope it helps,
Regards,
Satish.

For IDOC monitoring, analysis and error handling in ALE & idoc

Hello...experts..can u please tell me about idoc monitoring,analysis and error handling..and can u please tell as per interview point of view in this area..if availble can u send material about this...
thx
Message was edited by:
durga kottapalli

Hi,
Reprocessing IDocs with errors
Outbound (BD88)
Once the error has been determined and corrected it is not necessary to resend the IDoc again. You simply resend the IDocs that have already been generated.
Using the IDoc overview screen you need to take note of the following for each IDoc that was not processed:
Error number: 2, 4, 5, 25, 29
Error number: 30 (Execute Check IDoc dispatch to process)
IDoc number
Using the Error number, the IDoc number and the transaction BD88 , with the required message type you can resend the IDoc. Match the error number with this transaction and execute the function for the IDocs incorrectly processed.
Just check the below link, u will get all IDOC related Interview questions
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sappoint.com/abap.html
http://www.sap-img.com/
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://www.sappoint.com/abap.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sap-img.com/
http://www.allsaplinks.com/
Regards,
Suresh.
Message was edited by:
SureshKumar Ramamoorthy

How to monitor the alerts(error handling) in seerburger adapter?

hi,
is it like normal moniotoring for any scenario..i have to do the monitoring in seeburger adapter.
any other specific thing i have to take care to do monitoring the alerts (error handling) in seeburger adapter for AS2 and FTP adapters..
plz give other ways to monitor interfaces for seeburger adapter.
Regards
Raja

Hi Raja,
All Seeburger adapters have option of some kind of acknowledgement to be sent to the sender or any partner... u need to check the respective adapter documention....
for eg: FTP adapter can be configured for Message protocol - FTP-REPORTS
for sending various types of reports to any Business Partner,,,reports like dispatch report, transmission reports,,....etc
and for monitoring errors in XI... u can configure alerts as u normally do.....
*Reward points if useful*
Regards,
Sushil.

10gR2 - Self monitoring

Hi,
i am using oracle 10gR2 without the EM.
i am intrested in using the database self-monitoring abilities like the alert log.
how can i do it from the SQLPLUS and not from the EM?
Thx,
Doron

The alert log is an operating system file. It has been with the database for many versions, not just 10g. You look at it using any operating system viewer or editor that can handle text files.
(Also, please refer to the 2 Day DBA manual in the doc set.)

System Monitoring - Solman 7 EHP1

Hi
Solution Manager 7.0 EHP1 / Windows 2008 / Oracle
Satellite System R/3 Enterprise extn set 110 / Solaris on Sparc / Oracle
I am having trouble configuring System monitoring on solution Manager. Here is what I have done
Added the satellite system to SLD, Configured data collector (RZ70) in the satellite system, Pushed data from SLD to SMSYS (automatic transfer).
Installed CCMS agent + CCMSPING agent in satellite system. Checked connectivity in solman with RZ21. Connectivity is fine.
Created Monitor sets and monitors in CCMS for monitoring satellite system. Client data is visible in CCMS.
Created a solution in DSWP. Created logical component in SMSY. Assigned the logical component to the solution. Now I can see the data in DSWP.
Here are my questions
==================
1. In DSWP, everytime I have to view data, I have to click on "Setup System Monitoring" to view the alerts in the satellite system
I see a red alert reading for instance availability. Similarly,
In the system monitoring workcenter, I see the status of both the solution manager and the satellite system greyed out with a cross. When I move my mouse over it, it reads, no CCMSPING data available.
Any idea as to why this happens?
2. For what I see after I click on "Setup System Monitoring" I have parameters which I can configure. I see default values for these parameters. Is there like a recommendation or a template which can be used to setup these monitoring parameter values?
3. I have configured the ccmsping in the solution manager (for the solution manager) however the ccmsping service refuses to run. It throws a error reading "The system could not find the file specified". The ccmsping exe file is present in the location stated. Are there other files that this is looking for?
4. While registering the agent in the satellite system, I first registered with the CSMREG id. It failed with the message,
INFO: [SMG:040:CSMREG] connected to SMG, host sapsm.NA.XXX.NET, System Nr. 00, traceflag [ ]
INFO: SMG release is 701 , (kernel release 701 )
        RFC Error Info:
         message:
         status: EXCEPTION AUTHORITY_NOT_AVAILABLE RAISED
         intstat:
      Go Ahead anyway? n/[y] :
INFO: handling destination SAPCCM4X.SAPR3PR1.00
ERROR: can't register at SMG. RfcRc = 2, AUTHORITY_NOT_AVAILABLE
RFC Error Info for SALF_CSM_AGENT_REGISTER
message:
status: EXCEPTION AUTHORITY_NOT_AVAILABLE RAISED
intstat:
I then did this with a dialog user. That worked. Agent was registered in solution manager. Any idea on why this error would show up with the CSMREG? I am concerned about issues which can come up when the password for the dialog user changes.
I am not sure how to upload screenshots of what i see, probably if i do that, it will be easy to relate to the issue which I am mentioning here. Is there a way I can do that?
Let me know if you need any more information from my side to understand this.
Ideas will be appreciated.
thanks
Ravi

Hello Ravi,
Additionally you will want to look at SAP Note 1175058 - Problems with CCMSPING in SAP Solution Manager, especially
c) Ensure that the message server host name in the monitoring options of CCMSPING and the message server of the corresponding main instance of the relevant system is the same in the SAP Solution Manager landscape
(SMSY). Important: The monitoring options of CCMSPING must not be configured using an IP address.
Regards,
Paul

Solman 4 error

my solman 4 running since 3 days at import abap 16 phase of 42.
plz help me
following error in log
INFO: 2007-04-19 20:36:17 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2' import package is successfully completed.
INFO: 2007-04-19 21:40:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is successfully completed.
WARNING: 2007-04-19 21:40:22
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2007-04-19 21:40:22
1 error(s) during processing of packages.
INFO: 2007-04-19 21:40:22
Import Monitor is stopped.
and
TRACE      [iaxxejsexp.cpp:188]
           EJS_Installer::writeTraceToLogBook()
Returncode of C:\j2sdk1.4.2_12\bin\jar.exe: 0
TRACE      [iaxxejsexp.cpp:188]
           EJS_Installer::writeTraceToLogBook()
Jar file local_policy.jar is not included in zip file F:\sldprofile.zip, returning false
TRACE      [iaxxdlghnd.cpp:657]
           CDialogHandler::doHandleDoc()

Hi Mina,
I guess you're part of RampUp phase, in this case the best way should be to open a customer message into OSS.
Note that with UME and ABAP as datasource the client is very important, so please check the ABAP client (UME datasource) and the indicated on SLD, this should be sufficient to solve this.
For inconsistences you allways can use the tool mentioned on SAP Note 818947, but as this SolMan release is quite new and not officially released the answer must be provided directly by the developers, so don't hesitate to open a message in http://service.sap.com/message
Cheers,
Luis

Adapter Engine self-test status red / Error

Hi.
Im having trouble figuring out what to do about this error.
In Runtime Workbench --> Component Monitoring --> Integration Server --> Adapter Engine, the Adapter Engine self-test (and ping status) are in error.
The error message is: HTTP Request failed. Error code: "403". Error Message: "Forbidden [http://<server>:<port>/AdapterFramework/rtc]".
Anyone have an idea?
Regards...
Peter

Hi again.
Looking in the default trace I get this Info:
Hope it contribute to a solution.
Regards...
Peter
ACCESS.ERROR:
Authorization check for caller assignment to J2EE security role [sap.com/com.sap.aii.af.app*AdapterFramework : xi_af_rtc].
Exception when reading settings:
Thrown:
MESSAGE ID: com.sap.aii.rwb.exceptions.rb_CommunicationException.HttpReqFailed
com.sap.aii.rwb.exceptions.RequestFailedException: HTTP request failed. Error code: "403". Error message: "Forbidden [http://<server>:<port>/AdapterFramework/rtc]"
at com.sap.aii.rwb.exceptions.RequestFailedException.forHttpErrorCode(RequestFailedException.java:79)
at com.sap.aii.rwb.rtcheck.rtcclient.GrmgConnector.request(GrmgConnector.java:238)
at com.sap.aii.rwb.rtcheck.rtcclient.GrmgConnector.getSettings(GrmgConnector.java:105)
at com.sap.aii.rwb.core.XIRTCComponent.refreshConfigParameters(XIRTCComponent.java:279)
at com.sap.aii.rwb.web.componentmonitoring.model.CmMainModel.getConfigParameterCategoriesForSelectedXIComponent(CmMainModel.java:424)
at jsp_component_monitoring1209546798419._jspService(jsp_component_monitoring1209546798419.java:579)
at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:68)
at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at jsp_FC_Secure1209546795341._jspService(jsp_FC_Secure1209546795341.java:15)
at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:566)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:190)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
User XIRWBUSER, IP address
HTTP request processing failed. HTTP error [403] will be returned. The error is [You are not authorized to view the requested resource.No details available].

Solution Manager Self check gives an error

Hi all,
After installing diagnostics on SM 4.0 SPS 13 i have run a self check.
Everything is ok except for one issue. This is an issue with a task from the task scheduler:
3084] The Task Collect Configuration Data (nw01) failed during its processing!
[EXCEPTION]
com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: 1 error(s) occured during abap configuration data collect on monitored host [nw01]. Check logs for details.
     at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process_AbapConfiguration(ConfigGatherTask.java:340)
     at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process(ConfigGatherTask.java:148)
     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.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)
     at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
     at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:266)
     at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)
     at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
     at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.Exception: Error collecting abap system [sid:NW1] [install:0020255009].
     at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfigurationContent(AbapConfigurationProvider.java:332)
     at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfiguration(AbapConfigurationProvider.java:266)
     at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAndStoreAbapConfiguration(AbapConfigurationProvider.java:199)
     at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process_AbapConfiguration(ConfigGatherTask.java:287)
     ... 11 more
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Table does not exist in database.
     at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
     at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1442)
     at com.sap.mw.jco.JCO$Client.execute(JCO.java:3979)
     at com.sap.mw.jco.JCO$Client.execute(JCO.java:3416)
     at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfigurationContent(AbapConfigurationProvider.java:321)
     ... 14 more
Category: /Applications/AdminConsole/Scheduler
Location: com.sap.sup.admin.scheduler.JmsScheduler
Application: sap.com/tcwebadministratorscheduler~ejb
Thread: SAPEngine_Application_Thread[impl:3]_33
Data Source: D:\usr\sap\SO1\DVEBMGS01\j2ee\cluster\server0\log\defaultTrace.trc
Message ID: 00188BF8D663002D0000002B00000BC0000443721D1DD31C
Argument Objects: com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: 1 error(s) occured during abap configuration data collect on monitored host [nw01]. Check logs for details.
at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process_AbapConfiguration(ConfigGatherTask.java:340)
at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process(ConfigGatherTask.java:148)
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.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)
at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:266)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.Exception: Error collecting abap system [sid:NW1] [install:0020255009].
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfigurationContent(AbapConfigurationProvider.java:332)
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfiguration(AbapConfigurationProvider.java:266)
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAndStoreAbapConfiguration(AbapConfigurationProvider.java:199)
at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process_AbapConfiguration(ConfigGatherTask.java:287)
... 11 more
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Table does not exist in database.
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1442)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3979)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3416)
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfigurationContent(AbapConfigurationProvider.java:321)
... 14 more
Arguments: com.sap.sup.admin.scheduler.exception.FatalTaskExecutionException: 1 error(s) occured during abap configuration data collect on monitored host [nw01]. Check logs for details.
at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process_AbapConfiguration(ConfigGatherTask.java:340)
at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process(ConfigGatherTask.java:148)
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.smd.server.exec.asio.AsioInvocationHandler$1.call(AsioInvocationHandler.java:87)
at com.sap.smd.server.util.concurrent.FutureResult$1.run(FutureResult.java:90)
at com.sap.smd.server.exec.asio.AsioInvocationHandler$AsioRunner.run(AsioInvocationHandler.java:266)
at com.sap.smd.server.exec.TaskRunner.run(TaskRunner.java:45)
at com.sap.smd.server.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:785)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.Exception: Error collecting abap system [sid:NW1] [install:0020255009].
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfigurationContent(AbapConfigurationProvider.java:332)
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfiguration(AbapConfigurationProvider.java:266)
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAndStoreAbapConfiguration(AbapConfigurationProvider.java:199)
at com.sap.sup.admin.scheduler.task.remote.config.ConfigGatherTask.process_AbapConfiguration(ConfigGatherTask.java:287)
... 11 more
Caused by: com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Table does not exist in database.
at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:455)
at com.sap.mw.jco.MiddlewareJRfc$Client.execute(MiddlewareJRfc.java:1442)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3979)
at com.sap.mw.jco.JCO$Client.execute(JCO.java:3416)
at com.sap.sup.admin.upload.abapconfig.provider.AbapConfigurationProvider.collectAbapConfigurationContent(AbapConfigurationProvider.java:321)
... 14 more
DSR Component: n/a
DSR Transaction: 36b0a6f2c04711dca06700188bf8d663
DSR User: n/a
Message Code: n/a
Session: 0
Transaction: n/a
User: J2EE_GUEST
Host: so1
System: SO1
Instance: 01
Node: Server 0 1_17087
Regards,
Koen Engelen

Hi All,
Can anybody please help me with my question?
Regards,
Koen

Solman Configuration Error

Hi
Hi
I have installed Solman on test server and patched to SP16. while tring to configure workcenter getting the following error.
SAP web application server
NO switch to https occured so it is not secured to send the password.
SSO logon not possible invalid hostname for issuing cookies
choose logon to continue a dailog box appears in which you can enter user id and password, we have given the credentials
'still we are not getting further screen
As a part of preconfiguration
1:we have activate WebDynpro applications (services).
/sap/bc/webdynpro/sap/ags_work_incident_man
/sap/bc/webdynpro/sap/ags_workcenter
/sap/bc/ags_workcenter/ags_work_appln
/sap/bc/ags_workcenter/ags_work_webgui
/sap/bc/webdynpro/sap/ags_work_trans_print
/sap/bc/webdynpro/sap/ags_work_incident_create_app
/sap/bc/webdynpro/sap/ags_work_change_man
/sap/bc/webdynpro/sap/ags_work_setup
/sap/bc/webdynpro/sap/ags_work_job_sch_man
/sap/bc/webdynpro/sap/ags_work_implementation
/sap/bc/webdynpro/sap/ags_work_bp_iterf_mon
/sap/bc/webdynpro/sap/ags_work_services
/sap/bc/webdynpro/sap/ags_rbe
/sap/bc/solman/nwbc/solmanwork
/sap/bc/webdynpro/sap/ags_work_gui_selection
/sap/bc/dal/demoA
/sap/bc/webdynpro/sap/wdc_wba_rfc_monitoring
/sap/bc/bsp/sap/wba_start_smdia
/sap/bc/webdynpro/sap/ags_work_gui_default_set
2:Assigned the user with following roles
Z:SAP_SMWORK_BASIC
Z:SAP_SMWORK_SETUP
Z:SAP_SM_BASIC_SETTINGS
3:Maintained the parameter in RZ10
Login/create_sso2_ticket
login/accept_sso2_ticket
Could any can throw more light on why we are getting this problem
Note:As error stating "SSO logon not possible invalid hostname for issuing cookies"
hostname is fine we are able to ping it and in host file it is configured in the right manner
Regards
Uday

Hi
Its a fresh standalone solman system installed and patched to SP16,we have maintained parameter Login/create_sso2_ticket;Login/create_sso2_ticket in RZ10 and started configuring workcentes and we are getting this problem
SSO config with like #1083421
Do i need to do this
your FQDN might be wrongly maintained in SMICM
As i said it a standalone system installed on loopback adaptor with out any networkconnection
my host file name intel and i have configured as icm/host_name_full=intel in RZ10 and bouced the sytem for parameter to take effect
In etc/host its mentioned as intel
Regards
Uday

Query regarding handling and monitoring of OSB Errors in a specific manner

Hi,
I'm using
- OSB 10gR3 (10.3.1)
Context
To give some context, the setup I currently have a proprietory frontend client that is making XML/HTTP requests to OSB
which in turn is getting info from downstream systems.
I have no control over the behaviour/logic of the frontend client .. apart from knowing that it has a specific
request/response format.
So now to the issue..
The issue I'm facing is regarding handling of errors. Based on my knowledge of OSB, the error handling of the transaction has been
built along these lines
(Within the stage) If an error scenario's occurred, error is being thrown
(Within the error handler stage) Logging the error (using the 'Log' function .. with severity 'Error')
(Within the error handler stage) The response payload is being built .. so that the error can be reported to the frontend client
(Within the error handler stage) I'm doing a 'Reply with Success'
Now this does give me the expected behavior from the frontend client's perspective (... i.e. it receives the payload and displays whatever error that's occurred)
However from OSB's perspective, because I have done a 'Reply with success', the OSB Service Health Page ... (screenshot below) does not
increment the 'Errors' count for the respective proxy service ....
[OSB Service Health Page|http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/operations/monitoring.html#wp1107685] (Looking at Figure 3-8)
The only way I could achieve this was to set the error handler stage to 'Reply with Failure' (which would return HTTP 500) ...
The issue however is that, the proprietory frontend simply sees the incoming HTTP 500 code and doesn't read the return XML payload (containing the error details ..)
which beats the whole idea of being able to maintain some sort of traceability for the failed transactions.
So what I'm basically trying to find is .. that when an error occurs
- Some 'call' to make the during the error handler stage so that it registers as an error in the OSB Service Health Page.. and I can clearly
see the error count, etc for each of the proxy services
- After that being able to still use 'Reply with Success' ... so that the payload is being returned with HTTP 500 code...
so the frontend can read the payload ...
............. in essence, the idea being to register errors so that they can be monitored via the Service Health Dashboard ..but at the same time
being able to return the 'error details' payload successfully
With my limited (but growing) knowledge of OSB .. I've tried quite a few ways to achieve this with no success...
Would very much appreciate any help here ...
Lastly, if there is some way of achieving what I'm trying to get to above through different means, I'm open
to trying out alternate stuff.
Regards,
Himanshu

Hi Atheek,
Many thanks for the reply. Does appear to be a pretty neat way of doing it ..
One more clarification I'd like on this however ....
Given that I have a set up like this below
[External frontend client] <------> (1 Parent Service) <------> (2 Child Service)
(1 Parent Service) .... has error handler .. and all it does is 'Reply with success'
(2 Child Service) .... has error handler for particular stage
so...
2 Child Service - is doing the actual work (has error handler where custom error msg is being populated in $body)
1 Parent Service - is the one that is getting called by the external client (has error handler .. and all it does is 'Reply with success')
What I currently have is ..once the error occurs, I'm populating $body ... with the custom error message within the error handler
Previously I had 'Reply with Success' in the 2 Child Service's error handler and the custom error message would get returned to the external client.
Now, with the error handler only creating the custom error msg.... and 1 Parent service doing the 'Reply with Success' .. it doesn't appear
to return the $body .. with the custom msg that I'd populated .. in 2 Child Service's error handler.
Are the $body contents populated in 2 Child Service's error handler lost ...once the error propagates up to 1 Parent service's error handler ?
If yes... is there way of getting around it ? I could see for instance that the $fault message context has a 'user populated' Details variable
but the documentation covering this is sparse.
Regards,

In Message Monitoring Message showing Error:Message

Hi
Can anyone solve this problem.Its urgent for me.
My scenario is IDoc->XI->FILE
The file i am trying to generate is an xml file which i am dropping in XI application server using File system.
The problem is when i am going to see the message using transaction SXMB_MONI the perticular message interface is showing waiting for acknowladgement status .
But in message monitoring in runtime workbench the it is showing following status:
Adapter Engine
Holding
18.11.2005 05:42:09
CORP_SAP_DR2_030 http://limited.com/usa/sap_appl/retail/VendorsSAPAPOToMANU
MIIA_Create
BS_MANU
I am in SP14.
Also the output xml file is not getting created in the XI application server.
Please let me know the solution.
Thanks
Debraj Roy

hi debraj..
is ur mesage ie sxmb_moni in red staus or scheduled status...??
if in scheduled cud be errors with queues ...delete ur queues with tcodes : smq1 and smq2...
and also hopefully u must have configured ur idoc correctly..
https://websmp101.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
regards..
vishal

Self-Monitoring solman SP16 error

Similar Messages

Maybe you are looking for