SolMan 7.1 SPS 11: Can not Maintain a solution

[benoit-schmid]

Hello,

I have installed a SolMan 7.1 with SPS 11.

I can not maintain any solution.

When I click on Maintain a solution in System Monitoring -> Setup,

a popup windows opens and close.

In solman_ewa_admin, if I click on a solution, no new window is started.

How should I proceed to find the source of this bad behaviour?

Regards.

[Former Member · Accepted solution]

SAP left a backdoor - you can run the old transaction via SE38 -> RDSMOP_MAIN. I still use this feature, as our system is pretty slow.

[benoit-schmid · Accepted solution]

Daniel Lippmann wrote:

SAP left a backdoor - you can run the old transaction via SE38 -> RDSMOP_MAIN. I still use this feature, as our system is pretty slow.

How do you edit the solution from RDSMOP_MAIN?

[Former Member · Accepted solution]

You should edit solution via smsy using add/delete logical component. Logical component you can maintain via LMDB.

With best regards,

Alexander

[benoit-schmid · Accepted solution]

Please provide the sequence to add logical component.

As I have told you I can not access my solution to add a component.

Alexander Ganishev wrote:


You should edit solution via smsy using add/delete logical component. Logical component you can maintain via LMDB.

With best regards,
Alexander

[Former Member · Accepted solution]

Press Display <-> Edit button

With best regards,

Alexander

[benoit-schmid · Accepted solution]

I do not have this edit buton as I can not go in the solution.

Alexander Ganishev wrote:

Press Display <-> Edit button
With best regards,
Alexander

[Lluis · Accepted solution]

Hi Benoit,

Have you try on other workcenter ?

Solution Manager Administration -> Solutions -> Click on Object ID column -> solman_directory will be open trough sapgui.

On your first post, i can saw your need to open a solution, only that you need to maintain it. on the others comments yo told about to add logical components in a Solution. If it's that I think that you can do that on solman_directory transaction.

I think that if you can see a "ghost" popup that is closed immediately, that can be due to a Internet Browser Security options that block you to download the sap shortcut to acces using sapgui to solman_directory transaction.

Hope that can solve your problem,

Regards,

Lluis

[Former Member · Accepted solution]

Could you please perform following actions:

1. Run SMSY

2. Select System Groups and Logical Components

3. Under Solution Landscapes - Operations select you solution

4. Then select Display <-> Change in Landscape Components menu or click button on toolbar.

With best regards,

Alexander

[benoit-schmid · Accepted solution]

Hello Alexander,

I can not do what you are saying because of the following behaviour.

1. Run SMSY -> OK

2. Select System Groups and Logical Components -> OK

3. Under Solution Landscapes - Operations select you solution -> Error

(Solution XXX has not yet been migrated ro the solution directory)

4. Then select Display <-> Change -> Not possible because of the previous error

Regards,

[benoit-schmid · Accepted solution]

Hello,

Lluis Salvador Suarez wrote:

Have you try on other workcenter ?

If it's that I think that you can do that on solman_directory transaction.

I have tried two different workcenters.

But there is still the problem.

With the transaction solman_directory, the solution folder is empty...

Regards,

[Former Member · Accepted solution]

Hello,

Could you please after step 3 in different session use tcode su53, st22, sm21 for root cause analysis?

With best regards,

Alexander

[benoit-schmid · Accepted solution]

Hello Alexander,

Alexander Ganishev wrote:

Hello,

Could you please after step 3 in different session use tcode su53, st22, sm21 for root cause analysis?

With best regards,
Alexander

SAP works fine. The problem is at the application level and not at the AS level.

st22 -> No dump

sm21-> No log

su53 -> The last authorization check was successfull.

Regards,

[Former Member · Accepted solution]

Hello,

could you please trace it using ST01? Or ST12?

With best regards,

Alexander

[benoit-schmid · Accepted solution]

Alexander Ganishev wrote:


Hello,

could you please trace it using ST01? Or ST12?

With best regards,
Alexander

There is nothing that helps (only 3 Transaction GUID (DSR passport) in the trace).

Regards,

[Former Member · Accepted solution]

Hello,

could you please

1. run RDSMOP_MAIN using sa38 or se38.

2. check existing solutions

3. if yes, try to deactivate or copy or drilldown

4. if no, try to create

use solman_directory to edit solution as described above.

With best regards,

Alexander

[benoit-schmid · Accepted solution]

Hello Alexander,

Alexander Ganishev wrote:

1. run RDSMOP_MAIN using sa38 or se38.

rdsmop_main returns:

This function is obsolete and not supported anymore. 
Use the equivalent functions in the SAP Solution Manager work centers 
See SAP Note 1541013.

Nothing can be performed then.

Regards,

[Former Member · Accepted solution]

Hello,

Use SE38.

With best regards,

Alexander

[benoit-schmid · Accepted solution]

Hello,

By using RDSMOP_MAIN in se38 only I could deactivate/delete/ and recreate the solution.

Thanks.

[Former Member · Accepted solution]

Hello,

After you create solution you can maintain it in solman_directory or via workcenter.

With best regards,

Alexander

[former_member415447]

I've just hit the same problem. New install at 7.1 SPS11, where the only solutions in existence were created by SOLMAN_SETUP.

The problem seems to be that the solution isn't getting assigned a role, and because that field is blank the solution doesn't show up in SOLMAN_DIRECTORY.

Have a look at note 2011353, which describes both the symptoms and the fix, which is to put in a value for that field. After doing that I was able to maintain my solution normally.

[benoit-schmid]

Hello,

Julie Langley wrote:

I've just hit the same problem. New install at 7.1 SPS11, where the only solutions in existence were created by SOLMAN_SETUP.

The problem seems to be that the solution isn't getting assigned a role, and because that field is blank the solution doesn't show up in SOLMAN_DIRECTORY.

Have a look at note 2011353, which describes both the symptoms and the fix, which is to put in a value for that field. After doing that I was able to maintain my solution normally.

I can not apply what is documented in the Note 2011353 because I have solved the problem by

deleting and recreating the problem.

But it seems to be the problem that I have faced.

Regards,

[Former Member]

Hi,

When you use Maintain Solution from System Monitoring -> Setup it will launch SMSY (it may not open when open sessions exceeded). Could you please use SAP Solution Manager Administration -> Solutions.

With best regards,

Alexander

[benoit-schmid]

Hello,

I have the same behaviour with SAP Solution Manager Administration -> Solutions.

If I clik on the solution the popup window exits automatically and I can not edit the solution.

Regards,

[Former Member]

Do you have opened abap sessions of Solman?

Could you please check to use SAP GUI for HTML?

With best regards,

Alexander

[benoit-schmid]

Hello,

Setting abap sessions has you describe does not change the behaviour.

Regards,

[Former Member]

Hi,

Do you have your solution in SMSY->System Groups and Logical Components->Solution Landscapes?

[benoit-schmid]

Hello,

There seems to be a problem.

The solution has been created just after the install.

But smsy reports Solution XXX has not been migrated to the solution directory with

SMSY->System Groups and Logical Components->Solution Landscapes.

Regards,

[Former Member]

Hi,

Go to SOLMAN_SETUP->System Preparation->6 Prepare Landscape Description->6.3 Migrate SMSY Data into LMDB. And 6.4 Configure Automaticaly.

With best regards,

Alexander

[benoit-schmid]

Hello,

I have rerun this but it does not change naything.

For your information, the is a system defined only for the TMS

called MIG.

This is a virtual tms system.

But smsy reports: No active product version assigned to MIG.

It may be related to this system.

Regards,

[Former Member]

Hi,

Go to LMDB and assign product to system/

With best regards,

Alexander

[benoit-schmid]

Hello,

Alexander Ganishev wrote:

Hi,

Go to LMDB and assign product to system/

With best regards,
Alexander

In LMDB -> Product Systems, MIG is not accessible.

How should I proceed?

Regards,

[Former Member]

Press Create button.

With best regards,

Alexander

[benoit-schmid]

After creating the product system in LMDB and run again the sync (SOLMAN_SETUP->System Preparation->6 Prepare Landscape Description->6.3 Migrate SMSY Data into LMDB. And 6.4 Configure Automaticaly), the problem persists.

Alexander Ganishev wrote:

Press Create button.

With best regards,
Alexander