DB13 on solution manager
Hello Gurus,
When I run TX DB13 on solution manager, I do not get any data on SPACE.
any help?
regards,
Tolulope
Have you looked if SAPOSCOL and standard Job SAP_COLLECTOR_FOR_PERFMONITOR are running, the lastone must be running every hour at or near o´clock.
Similar Messages
-
Background job failing - ECC 6.0, Solution Manager 7.0
Dear All,
Four days back, I have installed the Solution Manager 7.0 and ECC 6.0 on
HPUX IA64 hardware with database as Oracle 10.2.0.2.0 (Unicode).
In both server, latest kernel patch has been applied.
The Support package versions are (both server):
KERNEL (Release 700) 146
SAP_BASIS 0014
SAP_ABA 0014
PI_BASIS(2005_1_700) 0014
ST-PI 0005
SAP_BW 0016
While checking the the jobs from SM37, in both the server,
I am observing that following jobs are always failing with
same reason:
SAP_COLLECTOR_FOR_PERFMONITOR
=============================
Date Time Message text Message class Message no. Message type
========== ======== ====================================================================== ============= =========== ============
15.05.2008 06:25:12 Job started 00 516 S
15.05.2008 06:25:12 Step 001 started (program RSCOLL00, variant , user ID BGDUSER) 00 550 S
15.05.2008 06:25:18 Clean_Plan:Cleanup of DB13 Plannings DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:started by RSDBPREV on server gcbeccd DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:Cleaning up jobs of system RD3 DB6PM 000 S
15.05.2008 06:25:18 Clean_Plan:finished DB6PM 000 S
15.05.2008 06:25:18 Database system not supported S1 101 S
15.05.2008 06:25:36 ABAP/4 processor: DBIF_DSQL2_SQL_ERROR 00 671 A
15.05.2008 06:25:36 Job cancelled 00 518 A
SAP_REORG_UPDATERECORDS
=======================
Date Time Message text Message class Message no. Message type
========== ======== ===================================================================== ============= =========== ============
14.05.2008 00:31:01 Job started 00 516 S
14.05.2008 00:31:01 Step 001 started (program RSM13002, variant SAP&001, user ID BGDUSER) 00 550 S
14.05.2008 00:31:01 Reorganization of update date not allowed in batch 15 100 A
14.05.2008 00:31:02 Job cancelled 00 518 A
SAP_WP_CACHE_RELOAD_FULL
========================
Date Time Message text Message class Message no. Message type
========== ======== ============================================================================================ ============= =========== ============
15.05.2008 00:30:11 Job started 00 516 S
15.05.2008 00:30:11 Step 001 started (program RWP_RUNTIME_CACHE_RELOAD, variant SAP&RELOAD_ALL, user ID BGDUSER) 00 550 S
15.05.2008 00:30:11 No component system chosen URL_GEN_MSGS 031 E
15.05.2008 00:30:11 Job cancelled after system exception ERROR_MESSAGE 00 564 A
Please help to resolve this issue.
Thanks in advance.
Regards
Sudip GhoshHi Markus,
Thanks for the reply.
Below is the dump:
======
======
Runtime Errors DBIF_DSQL2_SQL_ERROR
Date and Time 15.05.2008 06:25:36
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error 3113 occurred in the current database connection "DEFAULT".
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
How to correct the error
Database error text........: "ORA-03113: end-of-file on communication channel"
Database error code........: 3113
Triggering SQL statement...: "FETCH NEXT "
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_DSQL2_SQL_ERROR" " "
"RSORAVSH" or "RSORAVSH"
"FILL_DBVSE"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "gcbeccd"
Network address...... "10.10.4.158"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 15
Shortdump setting.... "full"
Database server... "gcbeccd"
Database type..... "ORACLE"
Database name..... "RD3"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 5 2008 00:55:24"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 1117216
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 695792
MM Free. 400816
User and Transaction
Client.............. 000
User................ "BGDUSER"
Language key........ "E"
Transaction......... " "
Transactions ID..... "482B8A4C89F0442BE10000000A0A049E"
Program............. "RSORAVSH"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "RSORAVSH" - in "FILL_DBVSE".
The main program was "RSORAVSH ".
In the source code you have the termination point in line 48
of the (Include) program "RSORAVSH".
The program "RSORAVSH" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "BGDUSER"
Job Number..... 05251100
Source Code Extract
Line
SourceCde
18
INCLUDE STRUCTURE v_system_event_struc.
19
DATA: END OF v_system_event_tab .
20
21
check sy-dbsys(3) = 'ORA' .
22
23
Get the new snapshots
24
25
PERFORM fill_dbvse TABLES v_system_event_tab.
26
27
28
Get the old snapshots from database table MONI
29
30
startday = sy-datum - days_to_keep .
31
32
33
Save new data now (otherwise these data will be selected twice)
34
35
CONCATENATE 'SYSEVENT' sy-datum sy-uzeit INTO monikey .
36
37
EXPORT sy-datum
38
sy-uzeit
39
v_system_event_tab
40
TO DATABASE moni(db) ID monikey .
41
42
*& Form FILL_DBVSE
43
44
FORM fill_dbvse TABLES v_system_event_tab.
45
date = sy-datum .
46
time = sy-uzeit .
47
EXEC sql performing append_v_system_event .
>>>>>
select event,
49
total_waits,
50
total_timeouts,
51
time_waited * 10,
52
average_wait * 10
53
into :v_system_event_struc
54
from v$system_event
55
ENDEXEC .
56
ENDFORM. " FILL_DBVSE
57
58
59
*& Form APPEND_V_SYSTEM_EVENT
60
61
FORM append_v_system_event.
62
v_system_event_tab-date = date .
63
v_system_event_tab-time = time .
64
65
MOVE-CORRESPONDING v_system_event_struc TO v_system_event_tab.
66
APPEND v_system_event_tab .
67
ENDFORM. " APPEND_V_SYSTEM_EVENT
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
16
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Report for Collecting Data from V$SYSTEM_EVENT Hourly
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080515
SY-UZEIT
062520
SY-XPROG
RSDBRUNT
SY-XFORM
%_INIT_PBO_FIRST
Active Calls/Events
No. Ty. Program Include Line
Name
2 FORM RSORAVSH RSORAVSH 48
FILL_DBVSE
1 EVENT RSORAVSH RSORAVSH 25
START-OF-SELECTION
Chosen variables
Name
Val.
No. 2 Ty. FORM
Name FILL_DBVSE
SY-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
V_SYSTEM_EVENT_STRUC
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222222222222222220000000000000000
0000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
%_SPACE
0
0
2
0
SY
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
No. 1 Ty. EVENT
Name START-OF-SELECTION
SY-LDBPG
SAPDB__S
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454455522222222222222222222222222222222
31042FF300000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
SY-DBSYS+0(6)
ORA
000
000
454
F21
SYST
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
V_SYSTEM_EVENT_TAB[]
Table[initial]
V_SYSTEM_EVENT_TAB
00000000000000 ################
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333322222222222222222222222222222222222222222222222222222222222222220000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
SY-DATUM
20080515
00000000
00000000
33333333
20080515
DAYS_TO_KEEP
30
0001
000E
STARTDAY
00000000
00000000
00000000
33333333
00000000
MONIKEY
0000000000000000000000
0000000000000000000000
2222222222222222222222
0000000000000000000000
SY-UZEIT
062520
000000
000000
333333
062520
SYST-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
MONI-CLUSTR
0
00
00
MONI
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222220022000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "ExecuteCall"
of the SAP kernel, in line 1190 of the module
"//bas/700_REL/src/krn/runt/abexsql.c#2".
The internal operation just processed is "DSQL".
Internal mode was started at 20080515062520.
Internal call code.........: "[DBDS/NEW DSQL]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(0) 0x4000000003b2b450 CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
(1) 0x4000000004d2c470 Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
(2) 0x4000000004d32160 ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
(3) 0x40000000047b51e0 Z10abdbdserriPKtiS0_P9DS_HEADERS0_iPv + 0x470 [dw.sapRD3_DVEBMGS00]
(4) 0x4000000003d777f0 Z11ExecuteCallv + 0x11f0 [dw.sapRD3DVEBMGS00]
(5) 0x4000000003d7e7b0 Z8abjdsqlv + 0x1b0 [dw.sapRD3_DVEBMGS00]
(6) 0x400000000402f190 Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
(7) 0x4000000003f53bc0 Z9abxeventPKt + 0x3c0 at abrunt1.c:339 [dw.sapRD3_DVEBMGS00]
(8) 0x4000000003d9f210 Z8abtriggv + 0x110 at abrunt1.c:58 [dw.sapRD3_DVEBMGS00]
(9) 0x4000000003d9ebe0 ab_run + 0xc0 [dw.sapRD3_DVEBMGS00]
(10) 0x4000000001caa820 N_ab_run + 0x20 at dymainstp.c:4739 [dw.sapRD3_DVEBMGS00]
(11) 0x4000000001cb40f0 dynpmcal + 0x3f0 at dymainstp.c:2281 [dw.sapRD3_DVEBMGS00]
(12) 0x4000000001caf260 dynppai0 + 0xcb0 at dymainstp.c:1107 [dw.sapRD3_DVEBMGS00]
(13) 0x4000000001cb1ec0 dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
(14) 0x4000000001c9dff0 dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
(15) 0x4000000001fea460 Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
(16) 0x4000000001fb54e0 TskhLoop + 0x5520 at thxxhead.c:3945 [dw.sapRD3_DVEBMGS00]
(17) 0x4000000001faae40 ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
(18) 0x4000000001569ec0 DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
(19) 0x4000000002c10630 nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
(20) 0x4000000002c105c0 main + 0x60 [dw.sapRD3_DVEBMGS00]
(21) 0xc00000000002be30 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
RSORAVSH
0
30.03.2005
10:21:59
19456
E
1
Prg
SAPMSSY0
1
17.12.2007
15:41:05
92160
E
2
Prg
SAPMSSYD
1
12.09.2006
11:33:31
21504
E
3
Prg
SAPFSYSCALLS
1
09.09.2004
14:18:32
8192
E
4
Prg
RSDBRUNT
0
17.12.2007
16:04:40
254976
E
5
Typ
RSSCR
0
30.03.2005
10:21:45
5120
6
Prg
RSDBSPBL
0
30.03.2005
10:21:58
72704
E
7
Prg
SAPDB__S
0
30.03.2005
10:22:01
19456
E
8
Prg
RSDBSPMC
0
12.09.2006
11:25:01
79872
E
9
Typ
DDSHDESCR
0
03.09.1997
03:05:16
4096
10
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
11
Prg
SAPLSABE
11
09.09.2004
14:18:36
13312
E
12
Prg
SAPLSECU
12
17.12.2007
15:31:45
87040
E
13
Typ
RSSUBINFO
0
14.10.1999
22:01:03
3072
14
Prg
SAPLSTUP
14
17.12.2007
15:29:58
74752
E
15
Prg
SAPLCNDP
15
11.09.2007
15:24:45
195584
E
16
Prg
SAPLSCNT
16
18.02.2005
14:16:06
30720
E
17
Prg
SAPSHDTV
16
05.01.2005
16:26:16
33792
E
18
Prg
SAPFGUICNTL
1
18.02.2005
14:15:08
24576
E
19
Prg
SAPLOLEA
19
11.09.2007
11:17:30
96256
E
20
Prg
SAPLSGUI
20
17.12.2007
15:41:05
84992
E
21
Prg
SAPLSTTM
21
05.07.2005
13:10:18
69632
E
22
Prg
SAPLSBDC
22
17.12.2007
15:30:54
44032
E
23
Prg
SAPLSFES
23
17.12.2007
16:04:40
260096
E
24
Prg
SAPLTHFB
24
17.12.2007
15:41:05
394240
E
25
Typ
WPINFO
0
26.02.1999
14:49:01
6144
26
Prg
SAPLURFC
26
17.12.2007
15:37:35
22528
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
29
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
30
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
31
Typ
SYST
0
09.09.2004
14:18:12
31744
32
Typ
MONI
0
31.03.2004
16:41:21
5120
Directory of Application Tables
Name Date Time Lngth
Val.
Program RSORAVSH
SYST 09.09.2004 14:18:12 00004612
\0\0\0\0\0\x0010\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
MONI . . : : 00002944
\0\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
71
PAR2
03
0000
0014
002B
RSORAVSH
37
73
PAR2
03
0000
0015
002D
RSORAVSH
37
75
PAR2
03
0000
0016
0026
RSORAVSH
37
77
00
0000
RSORAVSH
37
78
PERP
00
0002
RSORAVSH
44
79
PERP
1C
0000
RSORAVSH
44
80
PERP
04
0000
RSORAVSH
44
81
mvqk
10
0005
0044
04EC
RSORAVSH
45
83
mvqk
0C
0005
0054
052E
RSORAVSH
46
85
DSQL
00
0017
RSORAVSH
48
86
DSQL
01
0018
RSORAVSH
48
87
DSQL
04
0025
RSORAVSH
48
>>>>>
DSQL
16
0025
RSORAVSH
48
89
BRAN
05
0004
RSORAVSH
48
90
perf
00
000A
RSORAVSH
48
91
PERP
80
0000
RSORAVSH
48
92
BRAX
00
FFFC
RSORAVSH
48
93
DSQL
23
0000
RSORAVSH
48
94
ENDF
00
0000
RSORAVSH
56
95
00
0000
RSORAVSH
56
===========
===========
Please check and advise.
Also, I am trying to search for the note 6083 in market place, but not getting the same.
Please advise.
Thanks & Regards
Sudip -
Create a Support Message in Production system showing up in Solution Manage
Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
PaulHi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role. -
Define Service Desk Destination in the Solution Manager System (Dump creen)
hi,
in SPRO when i click on Define Service Desk Destination in the Solution Manager System
i got dump screen with the error below
any help?
Runtime Errors SAPSQL_EMPTY_TABNAME
Except. CX_SY_DYNAMIC_OSQL_SYNTAX
Date and Time 13.07.2008 14:05:57
Short text
A dynamically specified FROM clause has an unexpected format.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSHI2" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SYNTAX', was not
caught in
procedure "STREE_READ_NODE_GENER" "(FUNCTION)", nor was it propagated by a
RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
The running ABAP program attempted to execute an Open SQL statement in
which a FROM clause was specified dynamically in the field "TABLE_NAME". In
this
FROM clause, either a table name after a join operator is missing, or an
alias name after the key name "AS". The field "TABLE_NAME" could be empty as
well.
regardsHi,
I am facing the same problem. What is SP15 ?
Is there any SAP Note that can be applied to correct this ?
Thanks. -
Implementing the Enterprise Support in Solution Manager
Hi Experts,
Can anybody tell me what are the pre requisites to implement Enterprise support in solution manager?
Also let me know what are steps involved in implementing the enterprise support.
Thanks in Advance
HariHello Hari,
In order to implement Enterprise Support your organization should registered as a Value Added Reseller(VAR) with SAP. You can get all the required documentation under https://websmp104.sap-ag.de/solutionmanager --> Information for VARs, ASPs and AHPs which is in the left hand side of the page. However, you need to have a S-user ID of the VAR.
The following are the steps need to perform in implementing the Enterprise Support firmly known as Service Desk for VARs.
1. SAP Solution Manager basic settings (IMG)
a) Initial Configuration Part I
b) Maintain Profile Parameters
c) Maintain Logical Systems
d) Maintain SAP Customer Numbers
e) Initial Configuration Part II
1) Activate BC Set
a) Activate Service Desk BC Set
b) Activate Issue Monitoring BC set
c) Set-up Maintainance optimizer
d) Change online Documentation Settings
e) Activate Solution Manager Services
f) Activate integration with change request Managemnt
g) Define service desk connection in Solution Manager
2)Get components for SAP Service Market place
a) Get SAP Components
3) Get Service Desk Screen Profile
a)generate Business Partener Screen
4)Copy By price list
a)activate Service Desk BC Set
b)Activate Issue Monitoring BC set
c)Set-up Maintainance optimizer
f) Business Add-In for RFC Connections with several SAP customers
g) Business Add-In for RFC Connection of Several SAP Cust. no.
h) Set-Up SAP Support Connection for Customers
i) Assign S-user for SAP Support Portal functionality
j) Schedule Background Jobs
k) Set-Up System Landscape
l) Create Key Users
m) Create Message Processor
2. Multiple SAP Customer Numbers
a) Business Add-In for RFC Connections with several SAP customer numbers
b) Set-Up SAP Support Connection for Customers
3. Data transfer from SAP
a) Data Transfer from SAP
4. Create u201COrganizationu201D Business Partner
5. Service Provider function (IMG)
a) Business Add-In for RFC Connections with several SAP customer numbers
b) Business Add-In for Text Authorization Check
c) Activate BC Set for Service Provider
d) Activate Text Types
e) Adjust Service Desk Roles for Service Provider Menu
6. Service Provider: Value-Added Reseller (VAR)
a) Business Add-In to Process Actions (Post-Processing Framework)
b) Activate BC Sets for Configuration
c) Create Hierarchy and Product Category
d) Set-Up Subcategories
e) Create Business Partner as Person Automatically
f) Set-Up Automatic Confirmation of Messages
g) Maintain Business Partner Call Times
h) Set-Up Incident Management Work Center
7. Work Center (Web UI)
a) Activate Solution Manager Services
b) Assign Work Center Roles to Users
Hope it helps.
Regards,
Satish. -
Install Solution Manager in RedHat Enterprise 6 with Oracle 11
Hello ,
In the marketplace-PAM, RedHat Enterprise 6 is not listed as approved for EHP1 Solution Manager 7.0 64 bit (unicode) with Oracle.
Does anyone have any information on this subject?
Has anyone installed the Solution Manager 7.0/Oracle with RedHat Enterprise 6?
tksYes, you are correct. Apart from PAM, following Note confirms this. RHEL 6 is not supported yet for Oracle, is in planning stage.
Note 1565179 - SAP software and Oracle Linux
Thanks -
System landcape in large enterprise with solution manager
Dear Guru,
Do you have any ideas of how to set up Solution Manager in a big national enterprise? Let's suppose
a big company has a headquarter and serveral branches.
Every branch has its ERP, BW, etc, do you think it is better to set up respective Solution Manager system
for each branch or just create a powerful one centrally in the headquarter. Of course the latter means
less management but more authorization seperation related actions.
Is there any recommendation for this situation? Your opinion and insight is highly appreciated.
Thanks
RayDear Gugu,
I know Solution Manager support some scenarios for multiple customer .e.g VAR in service desk.
But is it possible for hide solution or project infomation, especially content of respective business blueprint
to different customers?
I mean we want to use one single Solution Manager for multiple customers, but customers do not want their
owned document and business process information shared with other customers.
e.g. one customer log on to SOLMAN, then he could view project or solution information of other customer,
furthermore, he could also build up his business blueprint referring to other customer's business blueprint.
Is it possible to segregate this infomation?
Thanks a lot.
Ray -
Logical systems while implementing charm in solution manager
Hello Everybody,
I just wanted to know how many logical systems we need while implementing charm in solution manager 7.0. I have 3 clients in development , 3 clients in Quality and 1 client in production.
Thank you,
vikram.Hi Vikram,
Yes, i1n ChaRM we always work with logical systems, I mean clients.
The standard is:
DEV -> QAS -> PRD
However, you can also use:
- Minimum
DEV -> PRD
- Target groups
DEV -> QAS -> PRD
- > TST
DEV -> QA1 -> QA2 -> PRD
DEV -> QA1 -> PR1
-> QA2 -> PR2
There are a lot of combination possible.
BR
Fernando -
XI 3.0 and BW 3.5 system type/logical component in Solution Manager
We are in the process of performing an upgrade for ERP 2004, XI 3.0 and BW 3.5. Initially this is being done in the sandpits. All systems are configured and connected our Solution Manager to download the packages.
We are unable to determine what type of system the XI 3.0 and BW 3.5 should be configured under. For example, previously we had an issue where ERP was configured as ECC 5.0 rather than ERP 2004. This was causing an issue in MOPZ where the upgrade option wasn't visible in a maintenance transaction. The same issue is now happening for XI and BW.
Please advise on the system type (logical component to use) for XI 3.0 and BW 3.5 in Solution Manager as SAP have made it very confusing. Currently both are under type Netweaver 04.
Regards,
-RohanHi
I believe that SAP hasn't upgrade option for BW 3.5, Check link:
https://service.sap.com/solman-mopz
Upgrade
a "straight" upgrade for SAP Business Suite (upgrade from SAP ERP 2004 to SAP ERP 6.0, for example) is not supported by Maintenance Optimizer
Upgrade with an Installation of an Enhancement Package is supported for SAP ERP, SAP SCM, SAP SRM and SAP CRM
Regards
William Neira -
Using HR data in R/3 to create business partners in Solution Manager
Is it OK for me to setup Solution Manager to automatically download HR data from R/3 to create the Business Partners (employee role) in Solution Manager?
We have setup SAP CRM 4.0 to automatically download the HR data and create Business Partners (employee role) in CRM. Since Solution Manager has the CRM component in it, I assume we can do it as well in Solution Manager.
Regards,
Mel Calucin
Bentley SystemsWe did it, i don't see the problem...
-
SAP GUI 7.10 - Issue reading files from Solution Manager
Hi everyone,
We have just installed SAP GUI 7.10 on our PC and have tried to open documents from Solution Manager.
On both Display and Change mode we are getting "The document cannot be displayed" (SOLAR_DOC021)
Can you suggest anything regarding the source of the problem? Any quick resolution?
Thank you
CorinneFound it myself. Tricky indeed.
http://service.sap.com/patches
- Search for Support Packages and Patches
- Enter Search Term "SAP GUI"
- Select SAP GUI FOR WINDOWS
- Select SAP GUI FOR WINDOWS 7.10 CORE
- Select SAP GUI FOR WINDOWS 7.10 CORE, on the next page also
- Select Win 32
- Arrive at avail. downloads
Regards,
Nathan -
DDIC Password fails in middle of Solution Manager Installation
I'm performing a new install of Solution Manager 7.0 (4.0) on HPUX IA64 11.23. This is a brand new Landscape. The installation has halted at phase 29/47 "Check DDIC password", and reports the error:
Test login to SAP System SMA failed.
SOLUTION: Make sure that the system is started, that the user DDIC exists and that the password of user DDIC is correct.
From the SAPGUI 7.10., I was unable to login as DDIC or SAP. I used the master passwords given in the install. I also tried the default passwords as mention in another thread password '19920706' for DDIC and '06071992' for SAP.
I was able to login with SAP* password PASS after adding login/no_automatic_user_sapstar=0
to the default profile and restarting SAP, but was unable to change the DDIC password because change and transport system not configured.
How do I get past this point in the installation process?This problem is now resolved. The problems of:
1) The "Check DDIC password" phase of sapinst of SM 7.0 was failing with DB-Error 0.
Fix: Install latest kernel patch. Problem was fixed with NW 7.0 kernel patch 133. I installed kernel patch 159. The kernel patch had to be installed via the old method of using SAPCAR to untar the files, backup kernel dir, shutdown sap, and copy files over to kernel dir. See note 19466.
2) The Warning messages
WARNING => IcmJ2EEScheduleFunc: Cannot
access "/sap/public/icman" -
please check node in TA sicf [icxxman_mt.c 2206]
was resolved by TA SICF by SERVICE HOST -> active
to activate the complete default_host subtree. -
Question for installing Solution Manager & ECC 5.0
Any idea for installing Solution Manager 3.2 on Windows server 2003 with Oracle9i problem when install Database Instance. Installation failed when the intallation progress went to Oracle Post-Load Action.
The message from startsap log file is
"running C:\usr\sap\T01\SYS\exe\run/sapstart.exe name=T01 nr=03 SAPDIAHOST=saptest02 -Wait
start service SAP01_03 on machine
saptest02
OpenService of SAPT01_03 failed. Error#: 1060
CreateNamedPipe for
saptest02\pipe\SAP01_03 Failed, Extended Error #2
start service SAP01_03 on machine
saptest02
OpenService of SAPT01_03 failed. Error#: 1060
C:\usr\sap\T01\SYS\exe\run/sapstart.exe=>sapparam(1c): No Profile Used."
Another question is about installing the Oracle database software: should we choose Create Databse or not when install Oracle Server Software only?
Is my installation process as following correct?
->SELECT A PRODUCT TO INSTALL:
Oracle9i Database 9.2.0.1.0
->WHAT TPYE OF INSTALLATION DO YOU WANT:
Enterprise Edition
->SELECT A DATABASE SUITED TO YOUR NEEDS:
Software only
After end of installation
install Oracle9i Client 9.2.0.1.0->Administrator
Thanks a lotHi Shusen, I´m trying to do the same think (Install ECC IDES with Oracle 9i in one computer for educational propose), can you help me with this:
1.I made the same Oracle install process because when I tried with sapserver.cmd nothing happened, for that reason i made:
SELECT A PRODUCT TO INSTALL:
Oracle9i Database 9.2.0.1.0
->WHAT TPYE OF INSTALLATION DO YOU WANT:
Enterprise Edition
->SELECT A DATABASE SUITED TO YOUR NEEDS:
Software only
After end of installation
I did not install client, is this correct?
2.After install this, I run the sapins.exe but show me this error: INSTALL FIRST SAP J2EE ENGINE, I download the JAVA SDK from JAVA page (java_ee_sdk-5-windows) but did not fix the problem: Do you know what file is this? Or, where is it in the DVD installation?
Thanks in advance if you or somebody can help me and excuse me if the answers are obviously, but I´m not a system engineer I´m only try to install IDES for learn SAP WM.
Thanks. -
Solution Manager on Linux x86_64 installation problem
I try to install Solution Manager 4.0 on Linux X86_64 platform. Unfortunately i receive error "the JDK installed in directory /usr/lib/java does not support the 64 bit data model". And there is no J2SDK for Suse linux x86_64 (or at least i can't find it. Please help!!!
OK. I solved the problem by using IBM Java. Also there is an SUSE version of SUN Java 1.4.2 for 64 bit systems.
-
Unable to create tickt in service desk - Solution manage.
Hello,
I have implemented service desk ( Solution manager) and It is working fine for most of the system but i am getting error while creating a ticket in service desk for one system.
Due to some RFC connection problem i have regenerated the RFC ( trusted , Read and TMW) from Solman to Satellite system.
and now I am not bale to create ticket for that system.
Error message :
The URL http://cismp.cargotec.com:8014/sap/bc/bsp/sap/dswpnotifcreate/msg_new.do was not called due to an error.
Note
The following error text was processed in the system SMP : Error SYSTEM_CORE_DUMPED occured. P1=11
The error occurred on the application server cismp_SMP_14 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: DO_HANDLE_EVENT of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DISPATCH_INPUT of program CL_BSP_CONTROLLER2============CP
Method: DO_REQUEST of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DO_REQUEST of program CL_BSP_CTRL_ADAPTER===========CP
Method: ON_REQUEST of program CL_BSP_RUNTIME================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_HTTP_EXT_BSP===============CP
Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
Can any body guide me what should be done to resolve the issue.Hi Prakhar,
As i mentioned workcenter is working fine for all other systems. and user have all roles same as in other systems.
BP is created and we are trying to create ticket from Solman itself so there is no point to maintain bCOS_CUST table.
but still we are not able to create ticket only for one system.
Error Message :
Error when processing your request
What has happened?
The URL http://cismp.cargotec.com:8014/sap/bc/bsp/sap/dswpnotifcreate/msg_new.do was not called due to an error.
Note
The following error text was processed in the system SMP : Error SYSTEM_CORE_DUMPED occured. P1=11
The error occurred on the application server cismp_SMP_14 and in the work process 1 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: MSG_SUBMIT of program CL_DSMOP_BSP_NOTI_MODEL=======CP
Method: DO_HANDLE_EVENT of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DISPATCH_INPUT of program CL_BSP_CONTROLLER2============CP
Method: DO_REQUEST of program CL_DSMOP_BSP_NOTI_CTRL========CP
Method: DO_REQUEST of program CL_BSP_CTRL_ADAPTER===========CP
Method: ON_REQUEST of program CL_BSP_RUNTIME================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_HTTP_EXT_BSP===============CP
Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system SMP in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server cismp_SMP_14 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server cismp_SMP_14 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 011 -u: XABHYABH -l: E -s: SMP -i: cismp_SMP_14 -w: 1 -d: 20091006 -t: 141511 -v: RABAX_STATE -e: SYSTEM_CORE_DUMPED
Regards,
Bhavesh
Maybe you are looking for
-
Hi Gurus, I am having issue with the report (S_ALR_87013611) that is actual/plan line items for Cost Center. When i execute the report for a cost element 510200 the amount is 23,380.13, but when i drill down on it by double click on that amount the
-
WAN MINIPORT ERROR AND TAKES A LONG TIME TO SHUT DOWN
Few days before,my device manager was showing yellow exclamation mark in wan miniport(ikev2),SSTP and another area, which i can't remember.So i searched on forums and use another software to fix this.The link to website is - https://www.vpnhosting.
-
How can I see my music in the icloud?
I lost cover art when I ran itunes Match, also the sound quality doesn't seem any better and can't see music in icloud. What did I pay for?
-
What can I do if I installed the incorrect USB Debug kit, causing my mac to
After irresponisbly not heeding the warning given to me by Apple Developer Connection (http://developer.apple.com/hardwaredrivers/download/usbdebug.html) and installing the incorrect version of IOUSBFamily Debug Kit, my Mac OS X freezes upon starting
-
T61 sudden shut down after I replaced the fan
I was getting a fan error (that was preventing the unit from booting), so I ordered a replacement. On installing it last night, everything seemed fine. Unit ran fine for 20m then Bam! sudden shutdown. This morning, same thing, both witht the battery