Skip to Content
author's profile photo Former Member
Former Member

RE:queue issue

Hi all

i have an issue recently

They are Some standard demos that have worked in DED/DEA for years. Iu2019m not sure what could have changed to affect this

every message is struck in the queue .

A restart may not fix the issue, it looks like the XI cache cannot be refreshed. If you drill into the errors in the queue (transaction SMQ2), all of the issues point to the cache refresh issue.

If you try to run a cache refresh (transaction SXI_CACHE), you get the following message:

Problem during cache refresh.

Problem while updating a receiver agreement with object ID 79F6783DF67A3340BCD2DB8A0811B101. :Destination 4041CDC2F23A3B858D1D941B1124CCA7; HTTP error: Could not generate information for HTTP destination from specified SOAP data

When i used txn smq2. Drilling through some of these, I found the following in Msg ID .......

- http://sap.com/xi/XI/Message/30" xmlns:SOAP=" http://schemas.xmlsoap.org/soap/envelope/">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="XICACHE">UPDATE</SAP:Code>

:

:

<SAP:AdditionalText>No RFC authorization for user XIAPPLUSER.</SAP:AdditionalText>

<SAP:Stack>Error while refreshing the XI runtime cache</SAP:Stack>

Are some more auth needed for the RFC connection user?

now the issue is solved but

1. What could have caused this issue ?

2. Is the issue permanently fixed ?

waiting for your valuable feedback

regards

sravan

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Nov 23, 2011 at 06:34 AM

    there is no permanent solution for CACHE issues(as per my exp), in your case first perfrom full cache refresh then try.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 23, 2011 at 07:12 AM

    Hi Sravan,

    > now the issue is solved but

    > 1. What could have caused this issue ?

    If we have done changes then some times cache doesn't refresh automatically, at this time manually we have to do cache refresh. If some changes happened (RFC dest change....) then at this time if we stop and start the respective communication channel in PI then we can resolve that issue.

    > 2. Is the issue permanently fixed ?

    According to me there is no permanent solution.

    Regards,

    Venkata Ramesh

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.