Error: call to messaging system failed

Hi all,
i'm facing this error in a RFC type Communication Channel for every message.
"Error in processing caused by: com.sap.aii.af.mp.module.ModuleException: call to messaging system failed: com.sap.aii.af.ra.ms.api.MessageExpiredException: No response available. caused by: com.sap.aii.af.ra.ms.api.MessageExpiredException: No response available."
Entering the message i got that log:
"Audit Log for Message: 7e223c81-7c6c-11e0-a692-000c292557a5
Time Stamp     Status     Description
2011-05-12 09:50:23     Success     RFC adapter received sRFC for ZXI_GROUNDWORK_START from SM7/100. Attempting to send message synchronously
2011-05-12 09:50:23     Success     MP: Entering module processor
2011-05-12 09:50:23     Success     MP: Processing local module localejbs/RfcAFBean
2011-05-12 09:50:23     Success     Application attempting to send an XI message synchronously using connection RFC_http://sap.com/xi/XI/System.
2011-05-12 09:50:23     Success     Trying to put the message into the call queue.
2011-05-12 09:50:23     Success     Message successfully put into the queue.
2011-05-12 09:50:23     Success     The message was successfully retrieved from the call queue.
2011-05-12 09:50:23     Success     The message status set to DLNG.
2011-05-12 09:55:23     Error     Transmitting the message using connection http://sxsixi118:8000/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.MessageExpiredException: No response available..
2011-05-12 09:55:23     Error     The message status set to FAIL."
Can someone help me i've already verified it's not a timeout problem cause i've increased the timeout to 15 minutes without success.
Thanks in advance.
Daniele

No because i didn't create the scenario and i've to resolve the problem
The log of the message is
"Audit Log for Message: 8e36e2b0-7ca3-11e0-9945-000c292557a5
Time Stamp     Status     Description
2011-05-12 16:24:32     Success     RFC adapter received sRFC for ZXI_GROUNDWORK_START from SM7/100. Attempting to send message synchronously
2011-05-12 16:24:32     Success     MP: Entering module processor
2011-05-12 16:24:32     Success     MP: Processing local module localejbs/RfcAFBean
2011-05-12 16:24:32     Success     Application attempting to send an XI message synchronously using connection RFC_http://sap.com/xi/XI/System.
2011-05-12 16:24:32     Success     Trying to put the message into the call queue.
2011-05-12 16:24:32     Success     Message successfully put into the queue.
2011-05-12 16:24:32     Success     The message was successfully retrieved from the call queue.
2011-05-12 16:24:32     Success     The message status set to DLNG.
2011-05-12 16:34:34     Error     Returning synchronous error notification to calling application: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Timeout.
2011-05-12 16:34:34     Error     Transmitting the message using connection http://sxsixi118:8000/sap/xi/engine?type=entry failed, due to: com.sap.aii.af.ra.ms.api.DeliveryException: Received HTTP response code 500 : Timeout."

Similar Messages

Call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException

hello
I am running an interface RFC2WS sync and recieve this message in the RFC. the message does not get out of the XI and rich the target (WS).
the XI been upgraded lately, and I think this might be the cuase to the problem, becuase the interface been worked before, and still working in PROD environment as is.
what could be the problem and how can I start investigate it to find the problem?
this is what the SAP recieves
call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException
Thanks
Kfir

Hi Kfir,
just check in RWB, in component monitoring, the status of integration server and adapter engine.......if it is red, then ask your basis guys to remove that error................just check your comm channels, i think your comm channels are in error, if they are just edit them, save and activate them again..........i think then your this issue will be resolved.'
Regards,
Rajeev Gupta

"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryExceptio

Hello XI guru,
I am configuring RFC to File scneario where i am using BAPI as Source. When i run this BAPI in se37 it gives me short dump stating "call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:
Please help.
Also I want to know is it necessary to write wrapper for BAPI before configuring. This bapi list all orders created in SCM system.
awaiting ur advises and help
Thanx
Anu

Hello guys,
I am sorry but kind of confuse, please be with me.
I have RFC with following structure:
'Z_BAPI_MOSRVAPS_GETLIST2'
importing parameters
      LOGICAL_SYSTEM = T_LOGICAL_SYSTEM
      START_TIME = T_START_TIME
TABLES
      PRODUCT_SELECTION = T_PRODUCT_SELECTION
      LOCATION_SELECTION = T_LOCATION_SELECTION
      LOCTYPE_SELECTION = T_LOCTYPE_SELECTION
      ORDER_HEADS = T_ORDER_HEADS
      OUTPUT_NODES = T_OUTPUT_NODES.
I put values in logical system/start_time/
product_selection/location_selection/loctype_selection
based on these values order_heads and output_nodes is populated. I want value of these to tables to be sent as file.
Data structure for file is as follows
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:ORDER_MT xmlns:ns0="uri:scm:sql:transaction">
- <ORDER_HEADS>
- <ITEM>
<ORDER_NUMBER />
<ORDER_TYPE />
</ITEM>
</ORDER_HEADS>
- <OUTPUT_NODES>
- <ITEM>
<MASTER_PRODUCT />
<MASTER_PLANT />
</ITEM>
</OUTPUT_NODES>
</ns0:ORDER_MT>
But the payload has value
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:ORDER_MT xmlns:ns0="uri:scm:sql:transaction">
remaining is not seen in sxmb_moni and payload cannot be read error is given.
file structure is dummy structure, please tell me know if it is right or i need to change.
Thanx
Anu

RFC Sender Adapter error " Call to messaging failed"

Hi,
I have been trying the RFC-> XI->File scenario.When I execute RFC using se37 transaction
on R/3 box,it gives the error " Call to messaging failed:
com.sap.aii.af.ra.ms.api.DeliveryException".
I have looked at msg in XI server using SXMB_Moni transaction.I found that,program is unable
to find the interface mapping function (Mapping between RFC and Inbound interface).
I have done the following settings:
For Sender :
1.RFC is being used as outbound Interface.
2.Imported RFC from R/3.
3. The R/3 functionality is to retrieve records.
For Receiver:
1.Defined Inbound ,Async. Interface.
2.Defined Data Type and Msg type
3.Defined Fault Message type
Mappings:
1. Message Mapping is defined for Inbound Message(From RFC) and Outbound Message
2. Source Interface(ZRFC) and target Interface(Inbound Interface) mapping is defined.In this mapping I am unbale to defined Mapping for Response and Fault.I have just deifned for Request as tabs are not gettting enabled after click of 'Read Interface'.
All necessary configurations have been done in Intergration Directory.
I am getting XML message at receiver at without data where rfc retireves two records.Why this is not being done?
As there is no mapping for Fault message of Inbound interface with RFC interface,I think mapping no found error is coming.
PS. I have not done the message mapping between ZRFC.Response and Inbound Message.
Please comment,where I have gone wrong.
Thanks & Regards,
HImanshu

Hi,
I don't know if the info below will solve your problem. Your scenario is an asynch scenario, therefore, the RFC must be executed as a qRFC. SE37 executes the RFC as synch.
To execute the RFC as asynch, you must tested with a report (se38):
The RFC must be executed as a qRFC.
data: DEST LIKE RFCDES-RFCDEST VALUE 'MY_RFC_DEST'.
CALL RFC
     IN BACKGROUND TASK
     DESTINATION DEST
     EXPORTING
COMMIT WORK.
The COMMIT WORK is required to send the RFC.
Regards,
Bill

What does this Adobe Muse error message mean: MuseJSAssert: Error calling slector function:SecurityError: Failed to read the 'contentDocument' property from 'HTMLIFrameElement': Blocked a frame with orign "null" from accessing a cross-origin frame.

So what is up with this error message in Muse?
MuseJSAssert: Error calling slector function:SecurityError: Failed to read the ‘contentDocument’ property from ‘HTMLIFrameElement’: Blocked a frame with orign “null” from accessing a cross-origin frame.

This is a genuine security error generated by the browser when viewing a page with iFrame content locally.
Please refer to Zak's reply in the following thread: https://forums.adobe.com/message/6496180#6496180
Cheers,
Vikas

Error in Local Message System: Error when opening an RFC connection Message

Hi Gurus,
We are not able to create support messages in our ECC production system but it can created in Development and Quality. Support message created appears in solution manager system. ECC System displays error message as
Error in Local Message System: Error when opening
an RFC connection Message was Not Created
I have checked RFC connection between ECC and Solution Manager which displays following message
Logon     Connection Error
Error Details     Error when opening an RFC connection
Error Details     ERROR: partner "local:sapgw00' not reached
Error Details     LOCATION: SAP-Gateway on host local / sapgw05
Error Details     DETAIL: NiPConnect2
Error Details     CALL: connect
Error Details     COMPONENT: NI (network interface)
Error Details     COUNTER: 40142
Error Details     ERROR NUMBER: 10060
Error Details     ERROR TEXT: WSAETIMEDOUT: Connection timed out
Error Details     MODULE: nixxi.cpp
Error Details     LINE: 2835
Error Details     RETURN CODE: -10
Error Details     SUBRC: 0
Error Details     RELEASE: 701
Error Details     TIME: Wed Jan 11 23:26:54 2012
Error Details     VERSION: 38
Kindly Help.....

Hi
Based on the instance number of the servers, you can determine the gateway to be used.
IF your ECC instance number is , 01 then gateway would be , sapgw01 (in ECC system)
So check and change the settings accordingly, in the RFC connection. Also check, if this entry sapgw01 is made in /etc/service file. Also check, in transaction smgw for gateway parameters.
Hope this info helps,
~ Raj

Sapwebdispatcher: ERROR: Connection to message server failed

Hi Team,
We have been facing an issue on the webdispatcher. Web-disaptcher is notable to communicate with the Message Server[PRD-XI].
=====================
Environment: Set-up =
=====================
1. The Webdispatcher is in DMZ. We have opened the port 8100 at the firewall.
==========================================================================
ERROR MESSAGE
==========================================================================
[Thr 2058] Fri Jan 11 18:53:27 2008
[Thr 2058] *** ERROR => NiBufIConnect: non-buffered connect pending after
5000ms (hdl 4;10.1.10.56:8100) [nibuf.cpp 4611]
[Thr 2058] *** ERROR => Connection request from (-1/65535/0) to host:
10.1.10.56, service: 8100 failed (NIECONN_REFUSED)
[icxxconn_mt.c 2738]
[Thr 2058] *** ERROR => IcmConnClientRqCreate() failed (rc=-8)
[icrxx_mt.c 5100]
[Thr 2058] *** ERROR => Could not connect to SAP Message Server at
10.1.10.56. URL=/msgserver/text/logon?version=1.2 [icrxx_mt.c 2459]
[Thr 2058] *** ERROR => rc=-1, HTTP response code: 0 [icrxx_mt.c 2460][Thr 2058] *** ERROR => see also OSS note 552286 [icrxx_mt.c 2461]
==========================================================================
SAPWEBDISPATCHER VERSION DETAILS:
==========================================================================
wd011:wpiadm 73> sapwebdisp -v
SAP Web Dispatcher Version 7.00.10, multithreaded, ASCII, 64 BIT
kernel information
system name =
kernel release = 700
database library =
compiled on = AIX 2 5 005DD9CD4C00
compile time = May 19 2007 01:59:47
update level = 0
patch number = 110
source id = 0.111
supported environment
operating system
AIX 1 5
AIX 2 5
AIX 3 5
=============================================================================
TEST OUTPUT
==========================================================================
wd011:wpiadm 71> sapwebdisp -bootstrap
SAP Web Dispatcher Bootstrap
============================
This bootstrap will perform the following steps:
1. create profile file "sapwebdisp.pfl"for SAP Web Dispatcher (if not
already existing)
2. create user for web based administration in file "icmauth.txt"(if notalready exisiting)
3. start SAP Web Dispatcher with the created profile
After the bootstrap you can use the web based administration
Generating Profile "sapwebdisp.pfl"
Hostname of Message Server (rdisp/mshost): 10.1.10.56
HTTP Port of Message Server (ms/http_port): 8100
Checking connection to message server...
ERROR: Connection to message server failed: NIECONN_REFUSED
Do you want to continue with these settings? no
==========================================================================
BACK-END APPLICATION MESSAGE SERVER DETAILS: SID: PPI [PI/XI]
==========================================================================
icm/server_port_0 PROT=HTTP,PORT=80$$
ms/server_port_0 PROT=HTTP,PORT=81$$
trc file: "dev_ms", trc level: 1, release: "700"
[Thr 1] Thu Jan 3 15:31:05 2008
[Thr 1] WLM Tag 'PPI/MSG' successfully set for this process
[Thr 1] MsSSetTrcLog: trc logging active, max size = 20971520 bytes
systemid 324 (IBM RS/6000 with AIX)
relno 7000
patchlevel 0
patchno 110
intno 20050900
make: multithreaded, Unicode, 64 bit, optimized
pid 2519162
[Thr 1] ***LOG Q01=> MsSInit, MSStart (Msg Server 1 2519162)
[msxxserv_mt. 1824]
[Thr 1] SigISetDefaultAction : default handling for signal 20
[Thr 1] load acl file = /usr/sap/PPI/SYS/global/ms_acl_info
[Thr 1] MsGetOwnIpAddr: my host addresses are :
[Thr 1] 1 : [10.1.10.56] pi100 (HOSTNAME)
[Thr 1] 2 : [127.0.0.1] loopback (LOCALHOST)
[Thr 1] 3 : [10.1.99.4] pi100v (NILIST)
[Thr 1] MsHttpInit: full qualified hostname = pi100
[Thr 1] HTTP logging is switch off
[Thr 1] set HTTP state to LISTEN
[Thr 1] ms/icf_info_server : deleted
[Thr 1] *** I listen to port sapmsPPI (3600) ***
[Thr 1] *** I listen to internal port 3900 (3900) ***
[Thr 1] *** HTTP port 8100 state LISTEN ***
[Thr 1] CUSTOMER KEY: >R1306811094<
[Thr 1] Thu Jan 3 15:31:28 2008
[Thr 1] MsHttpReadUrl2: H-1 url = /sap/public/icf_info/urlprefix (403
Forbidden)
[Thr 1] MsHttpReadUrl2: H-1 url = /sap/public/icf_info/logon_groups (403
Forbidden)
======================+++++++++++++++++++++++++++==============================
Please find the attached file for a better understanding of the trace file.
A quick action on this would be much appreciated.
Please let me know for any information required.
Thank you.
Regards,
~sagar

Vipin,
I don't have access to our firewall myself to confirm what ports and services we opened (I worked with our Network Operations team to get this done), but if I recall correctly, it was pretty limited, just http and https over tcp ports 80, 443, 8100, and 8101. Probably could even restrict that to just https over 443 and 8101. However, from your configuration, you don't yet have your web dispatcher configured to talk to your message server over https, only http. I would recommend that you get the web dispatched completely configured and working in as close to your final desired configuration as possible while keeping it inside your firewall, not your dmz. Then move it to the dmz and see what breaks, and that way you know it's just the firewall that needs configuration at that point.
To configure the SSL termination, the following are the parameters required and the way that I configured them in our scenario (which terminates incoming SSL requests and re-encrypts them when sending them on to the backend, and also uses SSL for message server communication):
rdisp/mshost = mshost.domain.org
ms/https_port = 8101
wdisp/server_info_protocol = https
wdisp/group_info_protocol = https
wdisp/url_map_protocol = https
icm/server_port_1 = PROT=HTTPS,PORT=443,TIMEOUT=30,PROCTIMEOUT=600
icm/server_port_2 = PROT=HTTPS,PORT=8101,TIMEOUT=30,PROCTIMEOUT=600
icm/host_name_full = wdhost.domain.org (note, use the externally visible name as registered on your SSL certificate for web dispatcher here; does not need to match the actual machine hostname, but must be resolvable in external DNS)
icm/HTTP/admin_0 = PREFIX=/sap/admin,DOCROOT=\usr\sap\RW1\W00\data\icmanroot/admin,AUTHFILE=\usr\sap\RW1\SYS\global\security\data\icmauth.txt,PORT=8101
ssl/ssl_lib = $(DIR_EXECUTABLE)\sapcrypto.dll
ssl/server_pse = $(DIR_INSTANCE)\sec\SAPSSLS.pse
ssl/client_pse = $(DIR_INSTANCE)\sec\SAPSSLC.pse
wdisp/ssl_encrypt = 2
wdisp/ssl_auth = 1
is/HTTP/show_detailed_errors = FALSE
wdisp/permission_table = $(DIR_INSTANCE)\sec\ptab
On the backend host I have the following parameters:
sec/libsapsecu = \usr\sap\RP1\DVEBMGS00\exe\sapcrypto.dll
ssl/ssfapi_lib = \usr\sap\RP1\DVEBMGS00\exe\sapcrypto.dll
ssl/ssl_lib = \usr\sap\RP1\DVEBMGS00\exe\sapcrypto.dll
ssf/name = SAPSECULIB
icm/server_port_2 = PROT=HTTPS,PORT=443,PROCTIMEOUT=-1
ms/server_port_1 = PROT=HTTPS,PORT=8101
Naturally, a server certificate is configured on the backend that the web dispatcher trusts (it can be an internally generated certificate; the outside public just needs to trust the web dispatcher's certificate, so that one should come from a recognized CA). Port 8101 is NOT open from the outside, just from the dmz and only to/from the web dispatcher host (this does allow me to use the webadmin interface from the inside). The https service also has to be activated on the backend in SMICM.
There's good advice about security setup for the web dispatcher in Note 870127, and troubleshooting advice in the Note mentioned in your tracefile output, 552286. Fairly complete documentation is in the online help at http://help.sap.com/saphelp_nw70/helpdata/en/de/89023c59698908e10000000a11402f/frameset.htm. Note 538405 is also good, more for performance configuration than security.
I hope you find this helpful.
--Matt

Error in local message system; message 009999000035 not complete

Hello All.
I have configured Service desk in SolMan 7.0 which has patch level 14 and also configured in Satellite systems. I am using SM_...._BACK RFC connection in BCOS_CUST table. The user used by SM_...._BACK have the following roles in SolMan
SAP_SUPPDESK_CREATE,SAP_SV_FDB_NOTIF_BC_ADMIN
and SAP_SV_FDB_NOTIF_BC_CREATE.
However, when I try to create support message (Help --> Create support message) in satellite system, i am getting Error in local message system; message 009999000035 not complete.
I have also checked for Product_ID parameter which is not existing.
One important thing is, I can create support message in satellite system if I give SAP_ALL in that RFC user using in SM_...._BACK connection in SolMan.
So, this shows clearly that it is an issue with role/authorization.
Please suggest me !!
Thanks in advance.
Regards,
Satish.

Hmm not really. Profiles for the roles are also generated?
Those roles/profiles should be sufficient to create support messages.
Even though you assigned SAP_ALL and it worked afterwards I cannot imagine you got an auth. problem here anymore.
When assigning SAP_ALL did you really assign SAP_ALL to the RFC user or did you assign another user (who got SAP_ALL auth.) to the RFC connection?
The user who was logged on to the satellite system when the support messages have been created (with and without SAP_ALL assigned to the RFC user) has always been the same?
Just to make sure: did you set NO_USER_CHECK = X in Sol Man tx: DNO_CUST04?

Service Desk: Error in local message system: You do not have authorization

Hello experts,
i'm configuring support desk scenario. I think all is fine, but, when i try to create a message from satellite (R3 46C) to my SOLMAN the following error appears:
Error in local message system: You do not have authorization to create a notifica Message was not created. (Message no. B~ 088)
The user i use to create the message has the following roles:
SAP_SV_FDB_SUPPORT_LINE_ADMIN
SAP_SV_FDB_SUPPORT_LINE_LEVEL1
SAP_SV_FDB_SUPPORT_LINE_LEVEL2
Z_RFC
and SAP_ALL SAP_NEW profiles.
Anyone knows where is the problem?
Regards
Carlos Calle

Hi Carlos,
Role that allows processing messages is SAP_SUPPDESK_PROCESS. However from what I have understand, once End User enters and submits the message, he/she cannot edit the message anymore. Probably an email will be generated to him/her to notified of the message creation and for futher updates. I think end user should not be required to logon to Solution Manager. Key User i.e. helpdesk or SAP support staff will process(edit/change) the message instead.
If you want something else, I think you need to create a customise role maybe from SAP_SUPPDESK_DISPLAY or PROCESS and change the authorization values.
The below note contains latest authorization info.
Note 834534 - SAP Solution Manager roles in Release 4.0
Experts,
Correct me if I am wrong.
Regards,
Annie

Error in Local Message System: RFC destination MB3AP1039 does not exist.

Error in Local Message System: RFC destination MB3AP1039 does not exist. Message was Not Created
Message no. BCOS088
Hi,
When iam creating a message from any system from HELP-CREATE SUPPORT MESSAGE it is throwing the above error message. Actually i need to send this message to SAP solution Manager Service Desk.
Can anyone help me in resolving the above issue.
Thanks & Regards,
Mirza Kaleemulla Baig.

Dear friend
You have to of following option
1.Define Service Desk destination in the R/3 systems:
Note: for this you need to log in the R/3 system.
Create the RFC between the Solution manager and R/3 system (Login to the R/3 system)
2.a. Go to transaction SM30.
b. In table/view field, enter BCOS_CUST. Then press the Maintain Button. See example below:
c. Press the Continue button in the following screen:
d. You should see the following screen, no entries should be seen in the table. Press the New Entries button:
e. In the next screen, enter the following information:
In the RFC Destination you should point to your Solution Manager destination RFC.
0ss_msg w sm_bsmclnt_back cust620 1.0
shailesh

Error in Local Message System: RFC destination 10.189.98.10 does not exist.

Error in Local Message System: RFC destination 10.189.98.10 does not exist. Message was Not Created
Message no. BCOS088
Hi,
When iam going inside the tcode SM30 in the satellite system and entering the destination ip of solution manager system and after that when iam creating a message from HELP-CREATE SUPPORT MESSAGE, then it is throwing the following error.
Can anyone please help me in the above issue.
Regards,
Mirza Kaleemulla Baig.

Hi Mirza,
For the RFC destination don't enter the IP address,enter the RFC name,somthing like SM_SP1CLNT200_BACK which is maintained in sm59.
Revert for any clarifications.
Thanks and Regards,
Avinash.

Error in Local Message System: Partner function RP is not defined

Hi Team,
I have configured Service Desk in solution manager 4.0 and When I create message from Development server I am able to see in Solution manager. Every thing works fine in Developement server.But in Quality i am not able to create mesage.
I have maintained BCOS_CUST table and defind BACK RFC (SM_SRSCLNT100_BACK)in quality server but When I try to create mesage using Help--> Cretae Support message I am getting error message as " Error in Local Message System: Partner function RP is not defined for notificatio Message was Not Created"
and not able to create message from Quality server.
Please let me know solution to fix this isssue.
Thanks in advance
Regards
Venu

Hi Venu,
This can be related to a configuration on table ( DNOC_USERCFGT ). You can use SM30 or go through IMG (
SAP Solution Manager -> Scenario specific settings -> service desk -> Partner Determination Procedure -> Use of own partner functions )
The parameter NO_USER_CHECK has to be set to 1 which means : No Existence Check for User.
Other point you need to check is wheater the user you are logged on in the QAS has the external identification correctly maintained in the respective BP on the Solution Manager side.
Regards,
Valdecir

Error in Local Message System: No authorization to logon as trusted system

Dear all,
When I am posting the message in Production system which I have configured with my solution manager
I am getting the error like "Error in Local Message System: No authorization to logon as trusted system. So trusted message can not be posted"
I checked with SM59 which I created the RFC destination, in that i selected for both the system ie Solution manager as well Production system 'Trusted System=Y'
Please suggest me how to solve this issue
Regards
Sudharshan

Hi,
please use the search function.
There are ALOT of topics regarding Trusted RFCs, table BCOS_CUST, RFC Back Destination to Sol Man and so on.
/cheers

Error in Local Message System

i wanted to send the messages
from solution manager menu help create support message , here I am
facing the problem when i am creating the message in the menu
HELP -> Create Syupport Message for your reference am attaching the
screen shot.
Error in Local Message System: Syntax program SAPLDNO_OW_SAP Message
was Not Created"
when i execute the Tcode NOTIF_CREATE message displaying that no RFC
authorisataion for user s000****
chers

Hi,
First off, this is a duplicate thread posted by gopal rao!! already two threads for this S000*** error exists.
Please read the rules before posting.
Secondly, I really wonder where the satellite system refers to S000***, S-Number!! accessing Solution Manager??!!
I already replied to gopal rao in another thread saying that he has not done basic configuration.
Follow the SPRO nodes in sequence to configure, It will solve your problem.
Feel free to revert back.
--Ragu

Error in local message system ( message no BCOS03O

MY GURUS
I AM NEW TO SAP AND SOLUTION MANAGER
AM HAVING ISSUES CREATING MESSAGES FROM MY SATELLITE SYSTEM TO SOLUTION MANAGER I GET THIS ERROR MEAASGE = Error in local message system ( message no BCOS03O

Hi
This error occurs if you are not maintaining the BCOS_CUST table entry in your satellite system which comprises of back RFC to solution manager.
if other settings like master data or BP creation done in solman this will resolve ur problem
have you done the required settings in solution manager for service desk setup.
But in case if you have done any setup for service desk please visit below HOW TO guide
https://websmp109.sap-ag.de/~sapdownload/011000358700000776062009E/Howto_ServiceDesk.pdf
Regards
Prakhar
Edited by: Prakhar Saxena on Jun 10, 2011 10:32 AM

Error: call to messaging system failed

Similar Messages

Maybe you are looking for