on 07-10-2008 3:44 AM
hi everyone,
I am trying to re configure my Solution manager 4.0. I have deleted my previous business client 100, and created a new one using
client copy 000. I now have a fresh client 100 in my solman, SOLCLNT100. My problem now is, in tcode SMSY, there is still
existing systems which i cannot delete. Whenever i try to delete my QAS in the systems tab, it shows me this message,
You cannot delete the system as long as it is still used in logical components. How do i delete this logical component assignment if
i have deleted everything already including my systems in tcode DSWP/SOLUTION_MANAGER? I want to delete this logical assignment
so i can re configure my SOLMAN.
many thanks
Hi,
SMSY is client independant, so no wonder that your old smsy is still intact.
To delete Logical components, go to SMSY, and select the tab system groups and logical components. Expand the your product go in change mode and press F4 in the system that is maintained for logical component. Select No System Empty space there and save it.
Now try to delete the system.
This will solve your problem.
Feel free to revert back.
--Ragu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, i was able to select the empty system and was able to delete my QAS server in the landscape components tab. but i am getting errors that the deletion is not complete and gives me the message, The deletion could not be completely performed. I tried to disregard the error and continued to create new server in the Landscape component tab and still had an error saving it. this is the error log after saving,
"You have edited a component (component name 'LBPSOLMAN'; component type ' Server') in the system landscape, and saved your changes.
An error occurred while you were saving your changes.
Your changes were saved consistently in the Solution Manager system landscape maintenance data repository. The changes are replicated into the SLD (System Landscape Directory), depending on the settings which you made when setting-up the system landscape maintenance (transaction SMSY_SETUP, Edit -> Expert Settings menu). The error could have occurred while replicating the changes into SLD.
The SLD server connection is inactive"
i am not using any SLD.
thanks for your help
Hi,
Perfectly fine. The error message clearly mentions
Your changes were saved consistently in the Solution Manager system landscape maintenance data repository
The system is trying the access SLD, which actually does not exist.
The SLD server connection is inactive
So I don't see any problem as such. Everything is ok, you can go ahead.
This solves your problem.
Feel free to revert back.
--Ragu
Edited by: Raguraman C on Jul 10, 2008 4:21 AM
Hi, i have deleted everything again and restarted my solman server. Now, if i try to create a new system or server i get a runtime error. OBJECTS_OBJREF_NOT_ASSIGNED, Exception CX_SY_REF_IS_INITIAL. Access via 'NULL' object reference not possible. This runtime error occurs if i try to save a newly created server or system in smsy. have you encountered this type of error? i just want my solman server to be clean as possible delete everything and reconfigure again.
this is my current system level:
System SOL:
ST-PI 0006
ST 0011
ST-A/PI 01K_CRM560
Satellite system QAS:
ST-PI 0006
ST-A/PI 01K_ECC600
many thanks!
hi, here is the dump that i am getting from my system SOL.
Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED
Exception CX_SY_REF_IS_INITIAL
Date and Time 14.07.2008 10:32:48
Short text
Access via 'NULL' object reference not possible.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSMSY_ACTUALIZE_DATA" had to be terminated because
it has
come across a statement that unfortunately cannot be executed.
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.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "UPDATE_SYSTEM_LCR" "(FORM)", 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:
You attempted to use a 'NULL' object reference (points to 'nothing')
Information on where terminated
Termination occurred in the ABAP program "SAPLSMSY_ACTUALIZE_DATA" - in
"UPDATE_SYSTEM_LCR".
The main program was "CL_SMSYED_SYSTEM==============CP ".
In the source code you have the termination point in line 445
of the (Include) program "LSMSY_ACTUALIZE_DATAF01".
The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in
procedure "UPDATE_SYSTEM_LCR" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "SAPLSMSY_ACTUALIZE_DATA "; its source code begins
in line
414 of the (Include program "LSMSY_ACTUALIZE_DATAF01 ".
hope u can help.. thanks!
Dear Raguraman,
I m getting same error in Solman.I m trying to implimnet that note in solman but giving message This note is note valid correction instruction.
i m pasting the dump here.
Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED
Exception CX_SY_REF_IS_INITIAL
Date and Time 07.06.2010 13:00:37
-
-
Short text |
Access via 'NULL' object reference not possible. |
-
-
What happened? |
Error in the ABAP Application Program |
The current ABAP program "SAPLSMSY_ACTUALIZE_DATA" had to be terminated because |
it has |
come across a statement that unfortunately cannot be executed. |
-
-
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. |
-
-
Error analysis |
An exception occurred that is explained in detail below. |
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not |
caught in |
procedure "SMSYAD_GET_DATA_FROM_LCR" "(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: |
You attempted to use a 'NULL' object reference (points to 'nothing') |
access a component (variable: "ACCESSOR"). |
An object reference must point to an object (an instance of a class) |
before it can be used to access components. |
Either the reference was never set or it was set to 'NULL' using the |
CLEAR statement. |
-
-
How to correct the error |
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: |
"OBJECTS_OBJREF_NOT_ASSIGNED" "CX_SY_REF_IS_INITIAL" |
"SAPLSMSY_ACTUALIZE_DATA" or "LSMSY_ACTUALIZE_DATAU14" |
"SMSYAD_GET_DATA_FROM_LCR" |
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. |
The exception must either be prevented, caught within proedure |
"SMSYAD_GET_DATA_FROM_LCR" "(FUNCTION)", or its possible occurrence must be |
declared in the |
RAISING clause of the procedure. |
| To prevent the exception, note the following:
Please suggest me how to solve this.
Regards
Ashok
any help?
thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.