MONI Message Status as Log Version

Hi Guys,
In MONI few of messages getting status as Log Version..Could any one plesae let me know why ? and what is best way of solution for this...
Thanks,
Siva...

It is the processing instance of the mesg. If you restart the mesg for failure reason, it will version until execute successfully with version numbers.
Refer this link if you have problem in the proxy side
Log version in sxmb_moni in recever system (soap to proxy scenario)

Similar Messages

Moni message status

Hi,
Iam getting message status in moni (Transport acknowledgement ) it tells acknowledgment not possible. So the reason is messages got stucked up. Is that only reason or are there are any reasons? what to do now? Because of that i cannot able to run another interfaces also and they also getting stopped.Do we have to delete the queues or are there anyways to do that? can anybody explain me???

Hi,
if possible correct that error ...so that queues will get released automatically....else you can delete the message blocking queue...so that other entries will be processed....
better try to rectify the error and reprocess the messages..which will release the queue...
HTH
Rajesh

XI monitoring log version

Hello,
Can you please anybody tell me what is log version in SXI_Monitor. I have a HTTP to RFC synchronous scenario. For of my message i can message status as log version and i dodnt see any response in Moni. This is happending for few messages.
Please help me abt this.
Thanks,
Vishal

> Can you please anybody tell me what is log version in SXI_Monitor. I have a HTTP to RFC synchronous scenario. For of my message i can message status as log version and i dodnt see any response in Moni. This is happending for few messages.
>
Hi,
The synchronous scenarios are not stored in XI database (they are not persisted). In order to see them in SXMB_MINI, you have to change the log level to 2. This can be done in SXMB_ADM - Integration Engine Configuration -RUNTIME - LOGGING SYNC to 1.
The status log version shows that the message got processed in IE.
VJ

Log version status in Integration Engine

Hi,
When montioring in Integration engine, couple of my messages are in 'Log version' status. These messages are in this status for the past two days.
We are not able to cancel these messages also.
What is the workaround solution to these messages.
Thanks,
Swapna

It could be due to huge processing of message/data
Do a complete cache refresh and check the same
The solution in this thread points to XI BATCH.
Log version in sxmb_moni in recever system (soap to proxy scenario)
Edited by: Anusha Ramsiva on Aug 6, 2008 2:57 PM

Log version status does not change

Hi,
For a synchronous scenario, I'm getting the status as 'Log Version' in sxmb_moni and the status doesnot change at all. Can you please let me know the reason for this and how the message status can be changed to successful.
Thanks
Sreenivas

HI,
This already explained in above note please do accordingly..
See below..
Symptom
Synchronous messages with message status 001 were made persistent in the database. This can occur, for example, when synchronous messages are being logged. These messages are not deleted by the Delete job.
Other terms
Delete, synchronous messages, message status
Reason and Prerequisites
You use the SAP NetWeaver Exchange Infrastructure.
Solution
Implement the attached correction instructions or import the Support Package listed below.
See the note.. for more details..
Note 930181 - Deletion of synchronous messages with message status 001.
Also see the note
Note 820149 - Deletion of manually changed and terminated messages
Also see the below threads
sxmb_moni, table sxmspmast, Messages with ICON_LED_RED, report RSXMB_SELECT
SXMB_MONI: LogVersion
Points rewarded if it is useful....
Regards
Chilla..

XI messages status "Message scheduled on outbound side" with Green flag

Dear,
          On My XI system , i have too old messages and i want to clear those.
          In moni messages status is "Message scheduled on outbound side" with Green flag .
         When i am trying to cancel these messages i am getting a popup saying
          "Cannot cancel message because of it's status"
          And there is no queue entries for these messsage on smq1 or smq2 (perhaps deleted by someone)
          I just want to cancel these messages, please tell me if there is any way .
Thanks in Advance,
Sandeep

Dear Sunil,
                Thanks, these meesages are neither active nor used anywhere,
                Problem is somebody has manually deleted entries for these messages from SMQ1 and SMQ2.
Regards,
Sandeep

LOG VERSION STATUS IN MONI

Hi Guys,
i am getting synchronous messages status as " TO BE DELIVERD" in Runtime workbench-Integration engine monitoring, i tried to resend this to be deliverd message from Runtime work bench i'm getting error mesaage " Unable to schedule 1 of 1 messages for processing; update the status"
how i will update the status as per above message ?
when i checked with same message id in MONI, its showing as status "LOG VERSION ".
Can any one help me on this how to resolve this issue..
Thanks,
Siva

Hi,
Messages might got blocked in SMQ2.
If you found messages in Queue double click on the queue --> if there is any issue in the messages ---> double click on the messages which redirects you to moni try to rectify the error and reprocess again
Regards,
naveen

Status "log version" in message monitor

Hi,
In a proxy to JDBC scenario, i'm getting status "log version" in sxmb_moni.
I'm trying to insert some records in target JDBC file and recovery JDBC response in a synchronous message interface.
However, i never have ssen JDBC response .
Why?
What does "log version status" means?
Thanks ,
Carme Alentorn

Hi Carme,
The meaning of Log version is " When ever wrong entry field pass to the target end the problem will be raised.
(Spicial chacters or more fields extra)
I think it exatly data will be wrong.check ur data end.
and check the adapter status.
Regards,
Sateesh

SXMB_MONI: Message status: Log Version ?

Hi,
We have a couple synchronous messages that have the "Log Version" status in the integration engine (ABAP stack tcode: sxmb_moni). It is a white circle icon. If we click on the legend (in sxmb_moni), we do not see this status (we see all the others green flag, race flag, etc)
If we click in theses messages, only the following 4 pipeline steps are done (Inbound message + Receiver message + Interface Determination + Message Branching) we do not see all the others (Request message mapping, call adapter).
What is the meaning of this status ?
Thanks !

from help.sap.com
<i>This message version was generated by logging and does not have a particular status.</i>
since yours is a sync scenario most probbaly what happend is that the response system was locked at the time request was send hence no response was received.
we had the same problem and we re-send the message from sender system and it wen't through properly
Thanx
Aamir
Note:i m still unable to figure out if its possible to re-send this from sxmb_moni,may be its not possible,also m not sure why we didn't get timeout error but got this one,may be some expert can shed some light on it.

Log version status for message in PI message monitoring

Hi All,
we send IDocs from ECC to PI and then external systems. It's working fine all the time But third party system did not recieve only one message out of many. This missing message showing in PI is like LOG version when I look at in monitoring.It was happend long back and its still showing as scheduled.
And also there were no pending messages in the queue.
any idea what happend for this message exactly ?
Thanks .

Hello
Check the notes below:
#1471001 PI monitor: Synchronous response is displayed as log version
#1256891 Logging errors in synchronous communication
These may help explain/fix the error.
Regards
Mark

Error Logging in B2B Business Message Status Reports and Error Reports.

Hi,
Could someone please let us know as to how the error messages are being shown up in the b2b frontend in the Business Message Details Report and Error Reports.
In some of the cases the error message logging is not happening properly and even against the valid transaction block the entire iAudit Report or the B2B Analyzer report is getting posted .
In some cases the error message is logged as AIP-51505: General Validation Error (for the transaction block which is valid and having no errors)
Is there any way from the b2b backend these error messages and business messages could be traced or is there any other way wherein the proper and relevant error messages could be tracked from B2B.
Thanks
Sachin.

Hello,
Business message status reports identify business message instance details.These details include the sending and receiving trading partners, exchange protocol,document protocol, business action and its state, message date, and message details.
Error status reports identify error message details. These details include the error code, error text, business message identification, message date, and message details.
Please fix up a telecon to 918041086150 for further discussion on the same.
Rgds,Ramesh

No status assigned to version 0 in FM area MFMA . Message No FMCU

Hi Gurus,
Have been doing the setting of Fund management / Budget. Need advice for 3 issues in this regard.
Issue No. 1 - Is it possible to create period-wise budget in ECC 6.00 ?
Issue No 2 : I selected the standard version of 0 in "OF21" - Define Budget Version.
But, i am not able to assign it with " Set Activation Procedure for Budget version"
Issue No. 3 : I tried to create a budget values in "FMBBC" - Public Sector management > Fund Management > Budgeting > Entry Documents > Create. But system throws a following error.
No status assigned to version 0 in FM area MFMA
Message no. FMCU006
Diagnosis
You want to use version 0 in FM area MFMA but there is no status assigned to version 0 in FM area MFMA.
Procedure
If you want to use this version with this FM area, please maintain the settings under Assignment of Status.
You can also select another version for budgeting in this FM area instead.
Kindly advise me how to rectify all these 3 issues ?
Thanks in advance,
Devi Aparna

Hi,
For period-based budget you can have a work-around, though as from ECC 6.04, you have even specially dedicated object for this: Budget Period.
Regards,
Eli
P.S. Please, respect the rules and don't ask more then one question per thread. Also, try to avoid asking basic questions and search SDN before posting

How to Dal with Log Version in SXMB_MONI

DEAR EXPERTS,
sCENARIO:
FILE-----> PI -
> SAP ECC
Sender - File adapter
Recv - Proxy
Mode_ Sync.
Some of the messages are going to STATUS - *Log Version IN SXMB_MONI. This is happening Intermitently.
How to avoid log version in sxmb_moni..Any SAP Note available.....
Take care,
Pooja

This probelm occurs randomly... There are no data related isues.
there may not be a solution to this problem...may be just a precaution......just check with the end system developers and verify what was the status of the application when they processed the Req from XI (for which you got Log Version).....
Other way to deal with this problem is resend the message.....AFAIK there seems to be no other way out.....if you find any then please let me know
Regards,
Abhishek.

Message Status as scheduled..

Hello All,
I configured scenario which use SOAP as sender and XI Adpter as receiver.
It is syncrnous call. I can see different message status...
intiatially it came as black triangle --> scheduled for outbound processing.
Now, It is showing Green flag which is just sceduled......
What is wrong and how to troubleshoot further....
Thanks,
Srini

See below SAP Note 1118297:
Liang
=====Note 1118297===========
Symptom
You are using the Exchange Infrastructure and you are processing asynchronous messages. These messages are scheduled in queues that are no longer processed. The inbound queue of the qRFC Monitor (transaction SMQ2), for example, contains entries with the status "Running". However, you recognize in the process overview (transaction SM50) that there is no active work process.
Other terms
QRFC, SXMS_ASYNC_EXEC, inbound, running, resource
Reason and Prerequisites
You are using the Exchange Infrastructure and you are processing asynchronous messages. These message are scheduled in the QRFC and are only processed slowly or not at all.
Solution
The asynchronous messages are scheduled in the queues.
Check the following points of your middleware.
Queue configuration:
If the QRFC Inbound Scheduler is configured, see Note
369007.qRFC: Configuration for the QIN Scheduler
Are the XI queues registered and active? In transaction SXMB_ADMIN->Administration->Manage Queues, you can register the queues for the XI runtime.
If the resources are configured for TRFC/QRFC, note the common usage of system resources. For further details, see Notes
74141 Resource management for tRFC and aRFC
527481 tRFC or qRFC calls are not processed
For the qRFC resources see Note
1051445 qRFC scheduler does not use all available
resources
For further information see Unit 3.1 of the "SAP Exchange Infrastructure Tuning Guide", which you can download from the marketplace.
In the XI configuration you can set locks for the processing of XI messages. Note that for many parallel queues there are also sufficient resources for lock objects. At least one enqueue entry is required for each queue, depending on the configuration. For further information see Notes
552289 FAQ: Lock management R/3
654328 Enqueue: System log message GE9
Queue status:
Transaction SMQ2 contains queue entries with the following status
"Running"
If the J2EE engine is downloaded in production mode with the mapping engine or recipient Adapter Framework, processing QRFC entries may not recognize this and remain in the "Running" status. A symptom can be, for example, that the RFC destination "AI_RUNTIME_JCOSERVER" is no longer registered. You can find this information in the Gateway Monitor (transaction SMGW).
Otherwise, the system may reach this status if the application server is downloaded in a controlled manner, and long-running processes can no longer terminate.
The system no longer processes any message. In transaction SMQR, you can activate the queues manually again. You can also schedule the report RSQIWKEX, which automatically restarts the queues. For further information see Notes
620633 Status RUNNING in SMQ2 with XI queues
864333 RSQOWKEX & RSQIWKEX start Running(Executed) queues
"Sysfail"
A queue entry with the status "Sysfail" can have two possible causes.
1. Further processing cannot be carried out on the process for technical reasons (for example, the program terminates with a dump or a system (mapping or recipient system cannot be reached).
2. Queue processing should be stopped, as the message cannot be processed, due to a configuration error. Processing is not permitted for the subsequent messages, as the queue sequence displays the message sequence. You can use the report RSXMB_RESTART_MESSAGES to restart the message processing again. See Note
813029 Automatic processing of failed XI messages
XI-QRFC and IDoc-TRFC processing:
Note that when you use the IDoc adapter this uses the RFC/TRFC resources, which are used together with the QRFC resources. This means an intensive usage of the TRFC can influence the performance of the XI queue message processing. When possible always use the package processing of the IDoc adapter (transport of several IDocs with an RFC call to the recipient system):
1. Package created from an IDoc XML payload with several IDocs
2. Packaging, package created with IDoc package filter
3. Package created with message packaging (queue message package)
(as of NW2004s)
For more information about acknowledgements, see also Note:
1111968 IDoc adapter: Parallel processing of acknowledgements
to reduce the number of acknowledgement queues.
Tuning Balancing parameter :
The BALANCING parameter activates the entries for the parameters B_EO_IN_PARALLEL_SENDER, B_EO_OUT_PARALLEL and B_EO_IN_PARALLEL.
They are used if the number of parallel queues is changed and the messages are distributed to the new queues. A balancing procedure is already used in the Standard System to distribute the messages equally to the queues. If the Balancing parameter is continually active, it has a negative impact on performance (as queue entries are constantly distributed between the queues and this means they cannot be processed). This can cause problems during queue processing.
Its use in the Tuning Guide is not described clearly.
Oracle database:
When using an Oracle database see Note
742950 Performance affected on Oracle DB with supplement 11
if you discover performance problems when processing queue entries. This improves the scheduling process only, and not the processing time of a queue entry.
See also Note
1020260 Delivering Oracle statistics
EO (exactly once) handling of XI-Messages when you restart QRFC entries:
The XI log guarantees the uniqueness of the transfer between the client and server. A restart does not trigger a double execution of messages. Note that a synchronization of the reorganization between client and server is guaranteed. The EO recognition is executed with the message ID. The retention time determines the amount of time this information is retained in the system for.
The individual messages are saved to the database in the system with a key from the message ID and version. This prevents a parallel execution of the same message. A queue entry can be executed in parallel using the report RSQIWKEX or by carrying out a manual start from the queue. We recommend to set the parameter LOCK_MESSAGE (default value is active "1") of the category "RUNTIME" in the XI configuration to the value '0'. More information is contained in Note
1058915 Outbound queue remains in status 'SYSFAIL'
=====End of Note 1118297===========

Log version in SXMB_MONI

what is the meaning of this particular message ?? If this error occurs where and what should we check ?? How to sort out the problem ??
Log version
This message version was generated by logging and does not have a particular status.
thanks
kumar

Hi Palnati
refer the below links
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/003de490-0201-0010-68a4-bf7a1e1fd3a5
http://help.sap.com/saphelp_nw04/helpdata/en/44/f5c3de84056c30e10000000a114a6b/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/0f/80243b4a66ae0ce10000000a11402f/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e01e9400-9e81-2910-20a5-a862945a5e98
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6a90d6aa-0b01-0010-8a83-cf0e6c70dcce
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
Hope this will solve ur issue related to SXMB_MONI
<b>Pls reward if useful</b>

MONI Message Status as Log Version

Similar Messages

Maybe you are looking for