Wednesday, August 27, 2014

SMQS scheduler status shows RES_LACK

Today I was confronted with the fact that our BI system wasn't reciving data from our R3. After a short investigation, I found that the IDOCs were not processed. Manually processing them sent them to the tRFC queue. However, from here they just ended in "transaction recorded".
From past experience I knew to check the registrations in the SMQS. However, today I was met with a weird situation. The registration was fine, but the scheduler had a weird status.


After a while of looking, I noticed that the "host ID" was that of another system (!)
My suspicions immediately went to last weeks homogenous system copy. So I went through every step of the RFC process, from data creation to the REF destinations. And lo and behold.... the RFC logon groups (RZ12) had not been configured. Simple fix, furtunately.
Posted by at

3 comments:

  1. UnknownJune 15, 2015 at 3:48 AM

    Hi,
    I got the same issue but in my case the Host ID is correct.
    Could you tell me more precisely what you have done ?
    thanks
    Pierrick

    ReplyDelete
    Replies
    1. HasseNovember 23, 2016 at 4:57 AM

      You may still face a problem with the RFC logon groups not being correctly defined. Go to RZ12 and ensure that the logon groups are pointing to the currently running system (or even recreate them totally)

      Delete
  2. UnknownJune 15, 2015 at 3:48 AM

    This comment has been removed by a blog administrator.

    ReplyDelete

Subscribe to: Post Comments (Atom)