Configure MOPZ: RFC SAP-OSS and SAP-OSS-LIST-O01 invalide password.

[Former Member]

Hi gurus,

I'm trying to configure MOPZ on a Solution Manager 7.0 system via IMG (tcode SPRO).

->spro->reference IMG->SAP Solution Manager Implementation Guide->SAP Solution Manager->Configuration->Basic Settings->Standard Configuration-of basic settings->Solution Manager->Connection to SAP->Check newly generated RFC connections to SAP

I'm at the step of configuring the RFC connections SAP-OSS and SAP-OSS-LIST-O01,. I'm using the same S-user and password as what I use to login to SMP and this forum. Therefore the user is not locked out. The SAPOSS RFC connection tests OK.

SAP-OSS RFC login&Security:

Language: EN

Client: 001

User: S0005630232

PW Status: is initial

Technical Settings:

Target System: OSS

Msg.Server: /H/<IP SAProuter>/S/sapdp98/H/147.204.2.5/S/sapdp99/H/oss001

Group: EWA

The SAP-OSS and SAP-OSS-LIST-O01 appear to be copies of SAPOSS with only the user/passwd changed.

User: OSS_RFC

PW Status: saved

Does something need to be changed on the internal SAProuter system, like allowing a new S-User thru ?

The dev_rfc0 log shows:

• Trace file opened at 20090421 141508 EDT SAP-REL 700,0,159 RFC-VER U 3 981960

======> Name or password is incorrect. Please re-enter

ABAP Programm: RSRFCPIN (Transaction: SM59)

Called function module: RFC_PING

User: DJI (Client: 001)

Destination: SAP-OSS (handle: 2, 43487095, {49EDD1F4-86EC-0CDA-E100-00001071904B})

[Former Member · Accepted solution]

> PW Status: is initial

Shouldn't that status be 'saved'? Instead of doing just a connection test, try the authorization test:

Utilities > Test > Authorization Test

The SDCC_OSS and SAPOSS RFCs uses group EWA.

But for some reason my SAP-OSS and SAP-OSS-LIST-O01 RFCs use group "1_PUBLIC"

[Former Member · Accepted solution]

The SAP-OSS-LIST-O01 RFC does have PW status "saved".

Authorization test results

Logon: Cancel

Error Details: Name or password is incorrect. Please re-enter

SAP-OSS authorization test results.

Logon: Cancel

Error Details: Name or password is incorrect. Please re-enter

SAPOSS authorization test results:

Logon: 3525msec

Transfer of 0 KB: 311 msec

Transfer of 10KB: 322 msec

Transfer of 20KB 394 msec

Transfer of 30KB 352 msec

I do not have an SDCC_OSS RFC defined.

I turned on RFC tracing for SAP-OSS and ran connection test.

• Trace file opened at 20090422 074741 EDT SAP-REL 700,0,159 RFC-VER U 3 981960

resize I/O buffer to 28000 bytes

>>>> SAP-OSS : R/3 <ac: 1> K /H/16.230.24.163/S/sapdp98/H/147.204.2.5/S/sapdp99/H/oss001 >>> OPEN

>TS> Wed Apr 22 07:47:45 2009

UUID: ab_drvstate create uuid {49ED568C-86EC-0CDA-E100-00001071904B}

CMINIT(lu:147.204.100.52, tp:sapdp01, gwhost:/H/16.230.24.163/S/sapdp98/H/147.204.2.5/S/sapdp99/H/147.204.100.5

2, gws:3301) rc = 0

>>>> SAP-OSS : R/3 <ac: 2> K /H/16.230.24.163/S/sapdp98/H/147.204.2.5/S/sapdp99/H/oss001 >>> 05863999

(05863999)

-{49ED568C-86EC-0CDA-E100-00001071904B}

Send RFCHEADER: 01/BIG/IEEE/SPACE/1100

Send UNICODE-RFCHEADER: cp:4102/ce:IGNORE/et:3/cs:2/rc:0x00000023

UUID: send_rfcuuid {49ED568C-86EC-0CDA-E100-00001071904B}

UUID: RfcCallNew send the uuid to the partner {49ED568C-86EC-0CDA-E100-00001071904B}

>TS> Wed Apr 22 07:47:46 2009

==== Delta 0 1 REG. 00000000000012 ADDR 0xc00000004f433c78 hRfc , ID 0 LOC 0001 l_o 0 XTYP 040

00000000006e0

==== Delta 2 1 REGH 00000000000012 ADDR 0xc00000004f433c78 hRfc , ID 1 LOC 0001 l_o 0 XTYP 040

00000000006e0 (len 0, val 1)

==== Delta 2 1 CONFIRMATION REQUESTED

RFC Info rfctable>: no Compression used

>>>> SAP-OSS : R/3 <ac: 3> K /H/16.230.24.163/S/sapdp98/H/147.204.2.5/S/sapdp99/H/147.204.100.52 >>>

WRITE (05863999)

-{49ED568C-86EC-0CDA-E100-00001071904B}

000000 | D9C6C3F0 F0F0F0F0 F0F0F0E3 01010008 |....|

000010 | 01020101 01010000 01010103 00040000 |................|

000020 | 021B0103 0106000B 04010002 01030200 |................|

000030 | 00002301 06010500 B8312D31 392D322D |..#.....ô¡1-19-2-|

000040 | 3438302D 332D302D 342D342D 352D3136 |480-3-0-4-4-5-16|

000050 | 2E313133 2E313434 2E37352D 362D7361 |.113.144.75-6-sa|

000060 | 70677730 302D372D 31362E32 31332E36 |pgw00-7-16.213.6|

000070 | 352E3230 382D3137 2D31362E 3131332E |5.208-17-16.113.|

000080 | 3134342E 37352D31 382D3136 2E323133 |144.75-18-16.213|

000090 | 2E36352E 3230382D 392D452D 31302D30 |.65.208-9-E-10-0|

0000a0 | 2D31312D 302D3132 2D313334 312D3133 |-11-0-12-1341-13|

0000b0 | 2D302D31 342D312D 31362D53 4D412D31 |-0-14-1-16-SMA-1|

0000c0 | 352D3439 45443532 39373836 45433043 |5-49ED529786EC0C|

0000d0 | 44414531 30303030 30303130 37313930 |DAE1000000107190|

0000e0 | 34422D38 2D616C66 34343633 32337870 |4B-8-alf446323xp|

0000f0 | 00010500 07000F31 362E3131 332E3134 |.......16.113.14|

000100 | 342E3735 20200007 0018002D 31362E31 |4.75 .....-16.1|

000110 | 31332E31 34342E37 35202020 20202020 |13.144.75 |

000120 | 20202020 20202020 20202020 20202020 | |

000130 | 20202020 20202020 20001800 11000133 | ......3|

000140 | 00110012 00043730 30200012 00130004 |......700 ......|

000150 | 37303020 00130008 00207061 78335F53 |700 ..... pax3_S|

. . . .

>>>> SAP-OSS : R/3 <ac: 4> K /H/16.230.24.163/S/sapdp98/H/147.204.2.5/S/sapdp99/H/147.204.100.52 >>>

FLUSH(WRITE) (05863999)

-{49ED568C-86EC-0CDA-E100-00001071904B}

>>>> SAP-OSS : R/3 <ac: 5> K /H/16.230.24.163/S/sapdp98/H/147.204.2.5/S/sapdp99/H/147.204.100.52 >>>

FLUSH(WRITE) (05863999)

-{49ED568C-86EC-0CDA-E100-00001071904B}

>>>> SAP-OSS : R/3 <ac: 6> K /H/16.230.24.163/S/sapdp98/H/147.204.2.5/S/sapdp99/H/147.204.100.52 >>>

WAIT (05863999)

-{49ED568C-86EC-0CDA-E100-00001071904B}

>>>> SAP-OSS : R/3 <ac: 7> K /H/16.230.24.163/S/sapdp98/H/147.204.2.5/S/sapdp99/H/147.204.100.52 >>>

READ WHILE WAITING (05863999)

-{49ED568C-86EC-0CDA-E100-00001071904B}

000000 | 01010008 01010101 01010000 01010103 |................|

000010 | 00040000 020B0103 0106000B 01010000 |................|

. . . .

Received RFCHEADER : 01/LIT/IEEE/SPACE/1100

Received UNICODE-RFCHEADER : cp:1100/ce:IGNORE/et:1/cs:1/rc:0x00000023

UUID: ab_rfccheck_uuid compare uuid's {49ED568C-86EC-0CDA-E100-00001071904B}

======> Name or password is incorrect. Please re-enter

ABAP Programm: RSRFCPIN (Transaction: SM59)

Called function module: RFC_PING

User: DJI (Client: 001)

Destination: SAP-OSS (handle: 2, 05863999, {49ED568C-86EC-0CDA-E100-00001071904B})

>>>> SAP-OSS : R/3 <ac: 8> K /H/16.230.24.163/S/sapdp98/H/147.204.2.5/S/sapdp99/H/147.204.100.52 >>>

FREE abrfcio.c 3458 (05863999)

-{49ED568C-86EC-0CDA-E100-00001071904B}

==== Delta 1 detaching (head) hRfc ID 1

>>>> SAP-OSS : R/3 <ac: 9> K /H/16.230.24.163/S/sapdp98/H/147.204.2.5/S/sapdp99/H/147.204.100.52 >>>

CLOSE abrfcio.c 3161 (05863999)

-{49ED568C-86EC-0CDA-E100-00001071904B}

==== Delta 0 0 LOG DROPPED

End of trace. Let me know if you want to see the buffer content also (which I removed from this trace).

Edited by: Don Isler on Apr 22, 2009 7:05 AM

[Former Member]

For all the RFCs in question, do the authorization tests too.

thanks

Bhudev

[Former Member]

Done. See above entry.

[Former Member]

The authorization test really should pass, and not say "Name or password is incorrect". All I can say is that you should try re-entering it in the RFC logon information. The password is probably case-sensitive.

Sorry I can't be of more help,

Sean

[Former Member]

I have re-entered login and passwd in the SAP-OSS RFC several times. Same error.

[Former Member]

Hi Don Isler,

It clearly indicates that the password is incorrect. So please re-enter the password and save again.

Also can you make sure the s-user id that you use, is entered in table AISUSER.

You can use TCODE: AISUSER.

If that s-user is not entered in AISUSER, then enter the s-user id without "S" in this table and save the entry. Afterthis do connection and authorization test of SAP-OSS and SAP-OSS-LIST-O01.

Hope this should solve your issue.

Regards,

Sanjai

[Former Member]

The AISUSER contains: User: DJI , contact person 5630232.

I tried adding DDIC with contact 0005630232. It gave the warning msg AI_SC_EN093 Partner number 0005630232 was not found in table AICONTACTS. The new entry was added anyway as User DDIC, contact 5630232. The SAP-OSS RFC authentication test still fails when login as user DJI or DDIC.

Job log for REFRESH_ADMIN_DATA_FROM_SUPPORT

|04/22/2009 |13:48:44 |Job started |04/22/2009 |13:48:44 |Step 001 started (program AI_SC_REFRESH_READ_ONLY_DATA, variant , user ID DDIC)

|04/22/2009 |13:48:45 |No systems found in transaction SMSY

|04/22/2009 |13:48:45 |Job cancelled after system exception ERROR_MESSAGE

tcode SMSY under systems show systems SMA and BIF. Don't know why can't locate systems.

The AI_SC_REFRESH_READ_ONLY_DATA job was created by user DDIC. As stated above, I added user DDIC to the AISUSER list. When I select this job and execute it, it just gets marked as scheduled. How do I execute it now?

Isn't there a separate copy of the DB for accounts used by the SMP backend used for SAProuter connections then the accounts used via SMP web? Therefore, an account can be lockout on SMP backend, and yet OK from the web.

[former_member190969]

Hi,

the problem is caused by a wrong password in the RFC-Destination. This is independant of AISUSER. You don't have to maintain it to check if the Destination works and the destination user does not have to be in AISUSER.

Regards

Andreas

[former_member190969]

>

> The AISUSER contains: User: DJI , contact person 5630232. 
> I tried adding DDIC with contact 0005630232. It gave the warning msg AI_SC_EN093 Partner number 0005630232 was not found in table AICONTACTS. The new entry was added anyway as User DDIC, contact 5630232. The SAP-OSS RFC authentication test still fails when login as user DJI or DDIC. 
.

That's bcause the Password is wrong.

> Job log for REFRESH_ADMIN_DATA_FROM_SUPPORT 
> |04/22/2009 |13:48:44 |Job started                                                                                |04/22/2009 |13:48:44 |Step 001 started (program AI_SC_REFRESH_READ_ONLY_DATA, variant , user ID DDIC)  
> |04/22/2009 |13:48:45 |No systems found in transaction SMSY  
> |04/22/2009 |13:48:45 |Job cancelled after system exception ERROR_MESSAGE 
> 
> tcode SMSY under systems show systems SMA and BIF. Don't know why can't locate systems. 

Because the systems have no installation number maintained.

> The AI_SC_REFRESH_READ_ONLY_DATA job was created by user DDIC. As stated above, I added user DDIC to the AISUSER list. When I select this job and execute it, it just gets marked as scheduled. How do I execute it now? 

Probably it is scheduled for a certain start time or you miss some job authorization.

> Isn't there a separate copy of the DB for accounts used by the SMP backend used for SAProuter connections then the accounts used via SMP web? Therefore, an account can be lockout on SMP backend, and yet OK from the web.

Yes, this can happen because because the SAP Backend is split up to separet systems with different databases that synchronize each other. This includes user acounts. Maybe it helps to change the password in SMP, wait for half an hour until the data are synchronized to all backend systems and then try again to do the RFC with the new password. If this doesn't help, create a new S-User or create a ticket to fix this problem.

Regards

Andreas

[Former Member]

I created a ticket to get the S-user account unlocked on OSS. That worked. The SAP-OSS and SAP-OSS-LIST-O01 RFCs now connect OK.

The LANDSCAPE_FETCH job pulled over data and updated the local SLD. I can now see my SolMgr system SMA. Job ran as user DJI.

The REFRESH_ADMIN_DATA_FROM_SUPPORT ran later under user DDIC and still did not find any systems. Log:

4/23/2009 1:47:58 PM Job started

4/23/2009 1:47:58 PM Step 001 started (program AI_SC_REFRESH_READ_ONLY_DATA, variant , user ID DDIC)

4/23/2009 1:48:21 PM No destination for SAP customer number 5630232

4/23/2009 1:48:21 PM No destination for SAP customer number 5630232

4/23/2009 1:48:21 PM System headers will be generated in SMSY from SAP Support Portal

4/23/2009 1:48:21 PM No systems found to generate

4/23/2009 1:48:21 PM SAP customer number unknown for installation number 0020179718

4/23/2009 1:48:21 PM Job finished

I can see from SMP that for installation: 20179718, the customer number is 706822. The 5630232 is my S-user ID.

I used tcode AISUSER to try to add 706822 to the SAP Customer Number field for user: DJI entry, but got the error: entry 706822 does not exist in AISAPCUSTNOS. How do I get this value in the table?

[former_member190969]

HI Don,

check the IMG at

SAP Solution Manager

Basic Settings

Connection to SAP

If additional problems occur always doubelclick the messages in the job log and have a look at my FAQ note 1151450.

Regards

Andreas

[Former Member]

OK, I went thru the IMG basic configuration again. The fix for REFRESH_ADMIN_READ_ONLY_DATA issue of

"No destination for SAP customer number 706822 |AISDK_SP_MESSAGES| 056 "

was to create an RFC desitnation of SM_SP_(customer #). Where is this documented other than forums as a fix? I did not see it anywhere in the IMG steps.

I cleanup a few things:

-Turned off BAdI, since my S-user has the only systems I maintain and I do not manage other customer numbers. Now there are several cu #s for my company, but I manage only the systems under my S-user ID for cu # 706822. So I should be folowing IMG setup for single-customer number. Right?

-I cleanup the AISUER table and removed the cu # from the cu # field. AISUSER now has

User: DDIC & DJI , no SAP Cu #, contact person: <my S-user w/o 'S000'=5630232>

Reran REFRESH_ADMIN_DATA_FROM_SUPPORT and getting error on cu # 5630232.

Job log overview for job: REFRESH_ADMIN_DATA_FROM_SUPPORT / 08393800

-

---

Date

Time

Message text

Message class

Message no.

Message type

-

---

05/14/2009	08:39:38	Job started	00	516	S
05/14/2009	08:39:38	Step 001 started (program AI_SC_REFRESH_READ_ONLY_DATA, variant , user ID DDIC)	00	550	S
05/14/2009	08:40:01	No Businss Partners will be generated from SAP Customer numbers	AI_SC_EN	109	I
05/14/2009	08:40:01	No Businss Partners will be generated from SAP Customer numbers	AI_SC_EN	109	I
05/14/2009	08:40:01	The following error messages have been returned by SAP Support Portal:	AI_SC_EN	207	I
05/14/2009	08:40:01	User S0005630232 - System Data Maintenance authorization not found for customer 0005630232	00	001	I
05/14/2009	08:40:01	System headers will be generated in SMSY from SAP Support Portal	AI_SC_EN	099	I
05/14/2009	08:40:01	No new systems found in SAP Support Portal to generate in SMSY	AI_SC_EN	103	I
05/14/2009	08:40:01	Job finished	00	517	S

-

---

Job is marked as finished OK.

Is this OK? The run should of pickup the data using cu # 706822.

I'm now getting errors when testing RFC connections to satellite systems. I'll open a separate thread on that issue.

Edited by: Don Isler on May 14, 2009 8:50 AM