You wish to know how to correct issues with the authentication, send and/or receive phases of Connrans.
The guide below details the most common issues that arise in the authentications, send and receive phases of Conntrans, along with the required steps to resolve these issues.
If the Send and Receive are failing together the problem could be with the authentication of the Mobile Client. If one of the phases (Send or Receive) in ConnTrans is successful while the other does not then the problem is not with the authentication but with the specific phase in ConnTrans and this section is not relevant. On such a case the trouble shooting should be done on the specific Transfer Phase.
When you try to access the CRM Server from the Mobile Client a total of three authorization checks are performed. These are:
Access from the client to the Communication Station via: authorization check on the CommStation.
Access from the Communication Station to the CRM Server: Logon by means of an R/3 RFC Destination configured on the Communication Station.
Site Authentication between the Mobile Client and the CRM Server.
Site Authentication between the Mobile Client and the CRM Server is the actual CRM authorization check. On the other two levels, either collective users or Windows users are used that are not linked to the CRM client user. The errors that occur at levels 1) and 2) mentioned above can be replicated with the QmtCnfg.exe program. The following error typically occurs when you try to transfer data from the client to the CRM Server or when the test program (on COM Station or Mobile Client) is processed:
Generally there is the option to assign the required authorizations or to switch off the authorization check. Deactivating the authorization check for the mobile client user in the CommStation does not increase the insecurity for the CRM data access! However, if you want to use additional safety settings like authentication or data encryption between the client and the CommStation,
Security must be configured and cannot be switched off as mentioned below:
See note 169550
This file logs all errors starting from the authentication of Mobile Client on the CommStation and the CRM Server, Sending of messages till the Receive phase of the Message Transfer Service.
In addition to errors, this log also holds statistical data of how many messages were sent or received per call to the CRM Server, authentication status of the Mobile Client with the COM Station and the CRM Server and any errors that might be thrown from the CRM Server or the COM Station. By default, the trace level is set to ‘2’.
If you want to increase the trace level to obtain additional information during errors you may increase the trace level to ‘5’. The QMTCnfg.exe provides a mechanism to alter the trace level of the Transfer Service. Please do not attempt to modify the trace level manually but always use the QMTCnfg.exe. In order to view the TransferService.log file, please run the QMTCnfg.exe.
Using the ‘Tools’ menu click for the “Show QMT Trace File” to view the log file. The location of the TransferService.log can be identified through the QMTCnfg.exe where the path is mentioned at the Current Trace File Settings header.
DotNetQmtClient.log - created in the directory specified in registry key folder HKLM\SOFTWARE\SAP\MSA\MW\TL and registry key "TL_TRACE_DIR".
TL_TRACE.dat and TL_ERROR.dat
In case of any errors during import (like messages not being processed and sent back to the server), two files are created in the directory that can be found under the registry key HKEY_CURRENT_USER\SOFTWARE\SAP\MSA\MW\TL\TL_TRACE_DIR. (TL_ERROR.dat may not be created but it should be checked).
DotNetQmtClient.log – Created in the same location as TL_TRACE file*.*