ChaRM - Logon to System not working

[shaun_kitching]

In ZDMJ and ZDHF we have an action called "Logon to System" where the user can logon to the appropriate system (ie. logon to DR3 to make a change or logon to UR3 for UAT testing).

When we click on this action we are presented with an error:

"OTO information not complete for non ABAP instance of system DR3 in SMSY"

I've had a look at the error in the task list and found this:

Message Text

OTO information not complete for non ABAP instance of system DR3 in SMSY

Technical Data

Message type__________ E (Error)

Message class_________ /TMWFLOW/MISC (Miscellaneous message of Change Request Management)

Message number________ 034

Message variable 1____ DR3

Message variable 2____

Message variable 3____

Message variable 4____

Anyone know what this means? We have ChaRM setup in our maintenance Solution Manager environment and logon to system works fine (same system as Production). Have compared SMSY in Production vs Maintenance and they seem identical.

What could be causing this? Have gone to our Basis team but they are struggling to figure this one out.

Thanks

Shaun

[shaun_kitching]

Restarted System and this fixed the issue!!!

[Former Member]

Thanks to notify. Glad its fixed.

[shaun_kitching]

Hi Vikram,

Thanks for the detailed reply. Unfortunately this is still not working and the same error is appearing when trying to logon via ChaRM.

Our DR3 system is NOT dual stack.

We implemented note 1666845 but this didn't seem to change anything.

As explained in my first post, Logon to System is working in our Maintenance Solution Manager system. We have compared Maintenance vs Production and we can't find anything different.

Any further suggestions?

Thanks

Shaun

[Former Member]

Hi,

The root cause of the whole issue in the non-ABAP instance of system DR3 has not

been configured correctly. see if the ABAP transport system and client are empty.

Is ur System DR3 Dual stack if yes:

Let me explain it to you in this way. Your system DR3 is a dual stack system, which means it is possible to use both ABAP stack and non-ABAP stack in ChaRM. So when you choose the system logon action we will firstly try to get all relevant information, and then give you two choices - you will be able to select ABAP stack or non-ABAP stack as

your logon destination.

We know that in your current project only ABAP stack is used, but from

a general point of view we always have to consider the non-ABAP stack

for dual stack systems. That is the logic behind the logon action.

Now you have to choices to resolve the logon error:

1) Correct the OTO information for non-ABAP stack DR3. Please make

corresponding configurations in STMS and make sure those information is

uploaded to SMSY on SOLMAN system.

2) Unselect the relevant flags for non-ABAP stacks. After that we will

use it as pure stack system so the OTO information won't be checked any

longer.

Also check if product version is missing for systm in SMSY or not?

See also note 1429764.

Check if note: 1666845 implemented?

Thanks

Regards,

Vikram