!--a11y-->
Troubleshooting Configuration: Mobile Repository Server 
Reason |
Solution |
The Transport Agent (TA) cannot connect to the CRM server. |
Check and correct the login parameters specified during the TA installation. |
The Mobile Application Repository (MAR) initialization failed. |
See MAR Initialization Failed for possible causes and solutions. |
Reason |
Solution |
Invalid login parameters, such as DSN, user name and password |
· Make sure that the DSN you created is available on the local system and that the user name and password are accurate. · Use the same parameters to logon to the SAP Mobile Application Studio. · You changed the password after configuring TA using Transport Configurator, TA still uses the old password. Update the password in the Transport Configurator on the Service tab. · If you enabled the user management feature, make sure the user name is mapped to a valid profile. |
Invalid DSN |
The DSN does not refer to a valid application repository. Make sure that the default repository in the DSN is set to a valid repository. |
Incompatible database structure version |
Make sure that the version of the ARS.DLL is compatible with the current version of the application repository. For more information, contact your system administrator. |
Unknown error |
· Make sure the files ERRCOMP.DLL, ARS.DLL and LOCKMANAGER.DLL are installed. If they are not installed, install and register them now. If they are installed, register them. · Make sure the Central Service is running. |
Unable to connect to the Central Service component |
· Make sure the Central Service has started and that it is running. · Make sure the entries ServiceMachineName and RemoteSocketPort in the ARS_SYSTABLE are consistent with the Central Service. |
Incompatible build version |
Upgrade to the latest ARS.DLL file. If initialization still fails, contact your system administrator. |
Reason |
Solution |
Password of the user on the CRM server has been changed |
Stop the TA service. Update the user password using the CRM Server Connection option in the Transport Configurator. |
Reason |
Solution |
TA service is not started |
Start the TA service |
CRM server does not recognize the repository |
Check whether or not the repository ID is specified in the CRM server. If not, enter the ID using the SMOBREPMAIN transaction in the CRM server. Check whether or not the repository ID specified in the CRM server is correct. If not, make sure that there is not another repository specified in the CRM server, and then change the ID using the SMOBREPMAIN transaction in the CRM server. |
Connection to the CRM server failed |
See Connection to CRM Server Failed. |

The reasons and solutions provided in this table also apply if the change lists are not moving from the CRM server to the repository.
Reason |
Solution |
You do not have authorization to specify the repository ID in the CRM server |
Contact your system administrator to have your authorization changed to the SAP_MAS_TRANSPORT_ADMIN role authorization, and then repeat this step. |
See also: