SLD fails to connect to Solution Manager

I am trying to populate SMSY with information from my SLD. The SLD appears to be setup properly as I am able to view all of my systems directly within the SLD. However, when I try to view the information in SMSY, The system cannot find anything.
I have configured RZ70, SMSY_SETUP, and SLDAPICUST and have performed numerous SLDCHECK's. I found one error to be with the password in SLDAPICUST as has been mentioned in many threads, however, this only works temporarily. I am still having to unlock user SLDAPIUSER randomly. (It is random). I have checked and reset all my passwords with no luck.
I have looked through all the Solution Manager and SLD manuals I could find and there seems to be very little information regarding the connection of the SLD to Solution Manager (Via SMSY). Could someone please help me. I have been struggling with this for a few weeks now and still nothing appears in SMSY.
Thanks,
Ryan

hi,
problem still unsolved?
maybe any 6.40-systems in your landscape? in these ones you have to input in TAC SLDAPICUST the characters in your password uppercase - because of case-sensitivity...
Message was edited by:
Bjoern Behrens

Similar Messages

Connection from Solution manager to SapNet

Hi,
I want connect from solution manager to sapnet for downloading support packages. What i need to do ?
I think that i need to:
1. official IP address for solution manager host ? Could this ip address be one in all network and routed to solution manager host ?
2. Install sap router on solution manager host ?

Hi Mindaugas,
For getting SAP Solution manager connected to SAP Net the following where mandatory
We Should have a official IP address of the computer on which SAP router can be configured. Its not necessary that you should have it in solution manager server. You can have it in any of the computer within your network and configure SAP router in that machine. This should be an official and registered IP address. You cannot use address such as
10.0.0.0 to 10.255.255.255
172.16.0.0 to 172.31.255.255
192.168.0.0 to 192.168.255.255
Later solution manager can be connected to SAP net using three RFC connections SAPOSS, SAP-OSS, SAP-OSS-LIST-O01. But before starting this make sure that you have configured SAP router correctly. Only then these RFC connections will work.
Also refer Note: 28976
regards,
Anandh

Connection to Solution Manager

Hi All,
I need your knowledge about Solution Manager.
My Request:
I would like to make a connection to Solution Manager, is anyone can help me to do this connection, Is it possible to have or to know what information I can enter to go on the next .
Attach a Snapshot to see what I need.
Thanks in advance,
Regards,
Claude

Hi Claude,
just finishing connection PowerDesigner (16.5) <-> SOLMAN (7.1 SP08). So you will need:
1. Application server (address you can get from SAPGui):
2. Port number - you will need support from your Basis colleagues
3. User ID and Password to access SOLMAN
4. Importing structure from SOLMAN:
a, create new model:
b. change your model language to SOLMAN:
c. this will open possibility to import or export from/to SOLMAN in menu "Language":
d. choosing "Update..." will start Wizard where you will need your data from the beginning:
e. choose a project, processes and import it.
Hopefully helps :-)

HTTP Connection for Solution manager

Dear Experts,
SAP support team asked to create a http connection for solution manager for service check.We already created a R/3 connection for solution manager.why they are asking for HTTP connection? Really they required HTTP connection ?,Is they are any problem with this type of connections.What are the transaction codes which are not run in SAP GUI. Please clarify my doubts.
Thanks and regards,
Patan Thavaheer.

Hi Patan,
Solution Manager transaction codes open in http browser. You can check the behaviour yourself by making a login to solution manager and execute transaction code solman_setup.
For SAP support to open http browser within remote support, they need to have http connection opened along with HTTP url maintained.
Refer to the SAP help link above for the procedure.
Hope this helps.
Regards,
Deepak Kori

Quality Center Adapter - Connecting Multiple Solution Manager Systems

We are running Solution Manager 7/Enhp 1 and Quality Center 10 successfully using the Quality Center Adapter integration. My question is, can we connect multiple Solution Manager systems (i.e. SMP/SMS/SMX) to a single Quality Center server simultaneously? Or is there a one-to-one relationship restriction. Thanks.

I have answered this question in this post below:
http://forums.sdn.sap.com/thread.jspa?threadID=2110531&messageID=10962875#10962875
To quote myself
Each tie up is based on the logical ports at the Solution Manager end and the relationship between the two entities is between Projects. So if you set up the configuration like you would in a normal scenario and at the right moment, connect the projects in SolMans to the corresponding projects in HPQC, you should be fine.
Hope that helps.

XFDesktop not running, FAILED TO CONNECT TO SESSION MANAGER [SOLVED]

Hi all, new to the arch forums, I've recently installed arch with xfce4, and I've been having trouble changing the desktop background as the GUI for it will flash up then close instantly. I tried to reload xfdesktop with xfdesktop --reload, this returns "xfdesktop is not running". Running $ sudo xfdesktop returns:
(xfdesktop:5211): GLib-WARNING **: (gerror.c:381):g_error_new_valist: runtime check failed: (domain != 0)
Failed to connect to session manager: Failed to connect to the session manager: SESSION_MANAGER environment variable not defined
xfdesktop: cairo-scaled-font.c:459: _cairo_scaled_glyph_page_destroy: Assertion `!scaled_font->cache_frozen' failed.
Also, when I look in xfce4-session-settings, all xfce applications are running but xfdesktop isn't there.
Thanks in advance
Last edited by portalin (2015-01-11 15:12:36)

Trilby wrote:
portalin wrote:Running $ sudo xfdesktop returns ...
Prepending sudo to random commands will eventually break your system. Don't do it.
In this case it simply prevents it from working as the session manager is running for your user not for the root user, so this command has nothing to connect to. Remove 'sudo'.
If I run just $ xfdesktop I then get the same error
(xfdesktop:2166): GLib-GObject-CRITICAL **: g_value_get_uint: assertion 'G_VALUE_HOLDS_UINT (value)' failed
xfdesktop: cairo-scaled-font.c:459: _cairo_scaled_glyph_page_destroy: Assertion `!scaled_font->cache_frozen' failed.
Aborted (core dumped)

Question about how to connect two solution manager

Hello experts
one of our clients wants to connect his SOLMAN to our SOLMAN, that way
when they receive a case in his ICM we can monitor the case and respond
It, if the situation requires or they ask for our help.
Can you please tell me if theres a way to connect them and what is the
best way to do that?
Thanks for your help,
Regards,

You are going to connect a Solution Manager to another Solution Manager, so I think it is enough to use the RFC destination on the connection.
I suppose you want to send a message from 7.0 to 7.1, so you may:
In Solman 7.0 system:
1. T-code SM59   > Define an RFC connection to 7.1 system;
2. T-code ICTCONF   > Add an entry for the 7.1 service desk, specify
the RFC Destination as the one you defined   > Activate -> Generate default value mapping (you may find the button on the top of ICTCONF).
In Solman 7.1 system:
1. T-code SM59   > Define an RFC connection to 7.0 system;
2. T-code ICTCONF   > Add an entry for the 7.0 service desk, specify the RFC Destination as the one you defined   > Activate -> Generate default value mapping;
3. Customize your own value mapping including the transaction type. You will find the details in:
    IMG -> SAP Solution Manager -> Capabilities (Optional)    -> Application Incident Management (Service Desk)    -> External Integration -> External Service Desk
Most fields of SIVA and SMIV are the same (for example, priority) so you do not need to care about the value mapping if you do not have special requirement. However, some fields only exist in SIVA category, subject) and others only exist in SMIV (multilevel categories). You may need to implement your own code according to your requirement.
Thanks
Vikram

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 Ghosh

Hi 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

R3load -testconnect failed while installing SAP Solution manager

Hi
I'm trying to install sap solution manager, it gets to "abap import" and then gives an error. I think there is a problem with database connection.
Here is what I get in the log
INFO 2007-03-22 17:03:01
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/DB6/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/DB6/CENTRAL/AS/inifile.2.xml'.
INFO 2007-03-22 17:03:01
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/DB6/CENTRAL/AS/inifile.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/DB6/CENTRAL/AS/inifile.3.xml'.
INFO 2007-03-22 17:03:06
Execute step Component W2K_ServicePack_Check|ind|ind|ind|indPreprocess of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_First_Steps|ind|ind|ind|ind|0|0|W2K_ServicePack_Check|ind|ind|ind|ind|2|0.
INFO 2007-03-22 17:03:18
Copied file 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/DB6/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN/SYSTEM/DB6/CENTRAL/AS/keydb.2.xml'.
INFO 2007-03-22 17:03:18
Execute step testDatabaseConnection of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0.
INFO 2007-03-22 17:03:32
Switched to user: lvtadm.
INFO 2007-03-22 17:03:32
Creating file C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\DB6\CENTRAL\AS\R3load.exe.log.
INFO 2007-03-22 17:03:32
Switched to user: lvtadm.
INFO 2007-03-22 17:03:32
Working directory changed to C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\DB6\CENTRAL\AS.
INFO 2007-03-22 17:03:32
Output of C:\usr\sap\LVT\SYS\exe\uc\NTI386\R3load.exe -testconnect is written to the logfile R3load.exe.log.
WARNING 2007-03-22 17:03:33
Execution of the command "C:\usr\sap\LVT\SYS\exe\uc\NTI386\R3load.exe -testconnect" finished with return code 2. Output: sapparam: sapargv( argc, argv) has not been called.sapparam(1c): No Profile used.sapparam: SAPSYSTEMNAME neither in Profile nor in CommandlineC:\usr\sap\LVT\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070322170332
(DB) ERROR: db_connect rc = 256
DbSl Trace: DbSlConnect to 'SM1' as 'saplvt' failed
(DB) ERROR: DbSlErrorMsg rc = 29
ERROR 2007-03-22 17:03:33
CJS-30023 Process call 'C:\usr\sap\LVT\SYS\exe\uc\NTI386\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.
ERROR 2007-03-22 17:03:33
FCO-00011 The step testDatabaseConnection with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|testDatabaseConnection was executed with status ERROR .
Any assistance will be rewarded.
Thanks in advance

Hi Louis
>>>snip<<<
For details see log file(s) R3load.exe.log.
>>>unsnip<<<
Or logon as <sid>adm and issue
R3trans -x
Then take a look at trans.log
Hth+Best regards
dirk

Connect two Solution Manager systems.

Hello,
We are planning to couple two Solution Manager systems.
We want to get all the alerts ABAP+JAVA(Root Cause) from one Solution Manager to the other.
What are te steps to take?
Connect the SLD's?
Connect the systems thru RFC?
Point all the agents to the 2 Solution Manager systems?
Regards,
Mike Geluk

Hello,
It is possible.
For SLD, two options:
- Each Solution Manager can use its own SLD. Then you must define the other server in the SLD, and vice-versa.
- Each Solution manager can connect to a central SLD where the two are defined.
The rest is just like any other managed system configuration: follow the steps in solman_setup.
Best regards,
Guiilherme

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.

Where has to be defined the SLD? PI/XI or Solution Manager?

Hello,
We have a PI production system, already configured and working. Now we are implementing the solution manager system. In both cases we only have productive systems. In which one should we define the SLD?
Thanks and kind regards,
Ana

Hi
Generally I would not recommend to have a Solution Manager Central SLD also used for Productive PI operations
although this is possible to do
We have seen situations whereby issues on the Solution Manager J2EE could affect PI operations generally the Solution Manager J2EE will be used for different purposes and may require different system administration. The dual purpose may also
have performance or sizing implications - technically any sizing done would have been for separate purposes.
The SLD for PI is needed for productive runtime (although there is a XI cache - even so I have seen situations whereby
this cache has limitations)
Customers often opt for the following
Central SLD running on the Solution Manager J2EE stack
Local PI SLD running on a PI J2EE stack
This is because the SLD service is available on any J2EE installation
You can then sync the local PI SLD to the Central SLD in order to build a full system list of all systems in the landscape
see the SLD planning guide at System Landscape Directory (SLD) for details
Best wishes
Stuart

Connection With Solution Manager!!!!

HI all,
01) Could anyone send me docs on How to connect Solution Manager With the ECC 6.0??
02) How to do Issue tracking with solution manager and use as a repository??
Thanks In advance
Regards,
Ami_Eka

Hi,
check following
How to generate EWAu2019s From Satellite Systems:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0f35bf3-14a3-2910-abb8-89a7a294cedb
SAP Solution Manager service desk:
please refer to the SAP Help Portal (help.sap.com -> SAP Solutions -> SAP Solution Manager -> SAP Solution Manager [current release] [Choose language] -> Service Desk).
https://websmp108.sap-ag.de/~sapdownload/011000358700000509252008E
Maintenance Optimizer:
https://websmp108.sap-ag.de/~sapdownload/011000358700000235502007E
regards,
kaushal
Edited by: kaushal malavia on May 27, 2008 6:12 PM

Connection Between Solution Manager and ECC

Dear Techies,
I would like to install SAP Solution Manager in one laptop and ECC on another laptop. Both the laptops have very good configuration in terms of operating system (both have server editions) , RAM ( 8GB each) and Hard Drive ( 600 GB each). Once the installation is completed, is there any way that I can establish connection between both the laptops over the same internet/wifi ? I would like to ensure connection is established successfully and data transfer is happening between both the systems. Many thanks for your answers in advance.

Hi Arun,
Please check below -
Create A Quick Ad Hoc Wireless Network Connection Between Two Computers In Windows 7/Vista
Best Regards,
Tanmeya

Connection between Solution Manager Testing und Test Workbench

Hello,
I have Problems understanding the connection between the test organization in the solution manager and the test workbench in the corresponding sap system.
The documentation says that the Solution Manager reuses the test workbench functionality. It is not clear for me how this connection works. In the solution manager you define test cases in the configuration of the project. When you create a test plan in the solution manager you can use the testcases of the project. But when you execute the testcases you do it in the corresponding sap system where the transaction of the test case is. Does this mean that the test cases und test plans that you create in the solution manager are transported to the target sap system? If this is true, when is the transport taking place?
Thanks a lot!
Regards, Lars.

Hi Lars,
I think you are confused with solution manager and tools like QTP.
The difference between solution manager and QTP/ECATTT is the eCATT or QTP are used for creating the test scripts or the test cases but solution manager is used for storing all types scripts centrally.
It means say you have manual test scripts eCATT and Ext QTP scripts lying on the R/3 servers but from solution manager you can create a project comprises of all the scenario and linked test cases of various type.
Now at a later time when you start testing a manager login to solution manager enter the test plan project name etc and can check what is the current status of the test
1. how much testing is completed
2. Who is the tester what is the test script where or on which testing took place etc
you can check my weblog to knw how to manage and perform testing via solution manager.
/people/community.user/blog/2006/12/07/organize-and-perform-testing-using-solution-manager
Please reward points for the same.

SLD fails to connect to Solution Manager

Similar Messages

Maybe you are looking for