Troubleshooting the Groupware
Adapter 
The errors that may occur when the Groupware Adapter processes messages are listed in the following table along with information to resolve them:
Error Messages |
Description |
MapBox not registered |
MapBox Instance is not registered as an RFC Destination. Resolution: Refer to the activity Define RFC Destination for the MapBox in the SAP Implementation Guide under Customer Relationship Management ® CRM Middleware and Related Components ® Internal SyncPoint. |
External MapBox commit failed |
This error can occur if there is a network failure or the MapBox service is shut down during message processing. Resolution: Select the message and choose F8 to reprocess the message in the queue. |
Error Parsing XML document |
This error occurs when the XML document (BDoc) is invalid. The transformer validates the BDoc document against the corresponding ABAP Dictionary structure of the BDoc. The non-validity is possibly due to: ● The data in certain fields in the BDoc segment exceeds the field length of the corresponding field in the ABAP Dictionary structure. ● The SAP MapBox is corrupting the output XML document by adding extra attributes. These attributes make the BDoc document invalid. Resolution: Delete the message from the queue. If you find a field that exceeds the maximum length, reduce the size of the content. Otherwise, edit some of the values and resend the message. |
Unspecified Error in SyncPoint |
SyncPoint was unable to process the message. Resolution: Switch on the trace function for the SyncPoint and monitor the performance data. Execute the program CMW_ISPTRACE_DISPLAY. For information on how to enable the SyncPoint trace, see the Enabling the SyncPoint Trace section below. |
Timeout during allocation of registered program |
SyncPoint could not process this message because the SAP MapBox was processing another message. Resolution: Try to reprocess this message later, when MapBox is not processing other messages. |
MapBox raised exception |
The SAP MapBox has raised an exception during the processing of the message. Resolution: Refer to the MapBox log to find out the details of the error. |
MapBox RFC destination not maintained in table ISPCFG |
MapBox Instance is not registered as an RFC Destination. Resolution: Refer to the activity Define RFC Destination for the MapBox in the SAP Implementation Guide under Customer Relationship Management ® CRM Middleware and Related Components ® Internal SyncPoint. |
ISP RC 94: MapBox raised exception 'MAPCASEEXCEPTION’ |
The MapBox has raised a map case exception. This means that the map case for the Groupware Adapter may contain errors or that the XSLT stylesheet contains a syntax error. Resolution: Check the MapBox log to rectify this error. |
Message Edited in target system |
If messages in the outbound queues still have the status “Message edited in target system”, they have not been accepted (confirmed) by the client. The following error codes can be returned to the client: ● 0 - Success ● 1 - Success / Inbound queue created dynamically. ● 2 - Not used ● 3 - Read queue (session mode = 0/1) not available. ● 4 - Session for same queue already established ● 5 - Invalid session handling ● 6 - Invalid parameter specified ● 7 - Unknown property ● 8 - Not used ● 9 - Severe error, for example, database problems ● 10 - Queue empty ● 11 - Wrong session mode ● 12 - Illegal operation: Only post to read-only queues ● 13 - Concurrent logon to same queue not allowed Resolution: Check the log file of the connector to get detailed information regarding this error. |
If the inbound queue is not receiving messages, it implies that the subscriptions are not properly assigned to the site of the Groupware Adapter. For information on subscriptions related to the Groupware Adapter, see Creating Subscriptions for the Groupware Integration.
Enabling the SyncPoint Trace
The trace is used to analyze the performance of the internal SyncPoint.It is activated by assigning X to the parameter TRACE in the table ISPCFG. Tracing is activated per site type.The trace shows the following information for each message sent to the SAP MapBox:
● Start date
● Start time
● qRFC TID
● Internal MapBox Job ID (GUID)
● Return value of SAP MapBox
● Return value of internal SyncPoint processing
● Size (in bytes) of message
● Number of resulting upstream messages
● Number of resulting downstream messages
● Total processing duration
● Duration of internal SyncPoint processing (without SAP MapBox)
● Duration of MapBox processing
● Duration of MapBox Commit
● Duration of R/3 Commit Work
● End time
● Application server
To view the trace file information, run the program CMW_ISPTRACE_DISPLAY by using transaction SE38. Enter the Site Type ID as GWA_01, enter the time range, select inbound to get trace information regarding inbound message processing and outbound for outbound message processing. The trace file can contain the trace from all the application servers.
With some older 6.20 versions, some parameters may be lost in the SOAP implementation. If the client receives error codes when logging on, the payload interface trace must be switched on. You can then check if the parameters are being completely transferred to the server. If not, ensure that the patch level of version 6.20 is at least 589.
Enabling the Payload Interface Trace
For each call, the trace of the payload interface displays the parameters passed from the client as well as the resulting return values.
In table ISPCFG enter the value X for the parameter PIF_TRACE. The site type must remain empty.
To view trace file information, run the program CMW_PIFTRACE_DISPLAY by using transaction SE38.
Verifying MapBox Connection Status
To check the connection status of the SAP MapBox, enter transaction SM59 and under TCP/IP Connections, click on the MapBox instance. Choose Test Connection This displays the connection status of the SAP MapBox.
Queue Naming Convention for the Groupware Adapter
Internal SyncPoint frequently uses the qRFC queues with the following naming conventions:
Queue Name |
Description |
ISP_I_* |
Inbound queue filled by PLIF. |
ISP_S_* |
Secondary inbound queue filled after MapBox processing. |
ISP_U_* |
Site-type-dependent Inbound queue (for thrust reversing). |
ISP_D_* |
Site-type-dependent Outbound queue (technically inbound queue). |
ISP_O_* |
Outbound queue filled by the pay load interface. |