Synchronization Fails

After synchronization, either a synchronization log appears with error messages or a message appears that the synchronization was successful, but no data was synchronized (for example, no device ID with the first synchronization).

Prerequisites

-

Main Tools

Text editor

Analysis

The following figure gives you an overview of the steps:

1.   Check if MI is still running

Depending on the MI variant on the client, check if the MI is running:

• MI Tomcat:
  • Open an Internet browser, delete all temporary Internet files and enter the following URL (if you installed the MI on a port other than 4444, replace 4444 in the following link with the port on which you installed the MI):

    http://127.0.0.1:4444/

  • If either the Mobile Infrastructure logon screen or the Mobile Infrastructure home screen is displayed, then the MI is still running and you can continue with Step 2.
  • If neither of the screens specified above is displayed and you get an error such as The page cannot be displayed , then the MI is no longer running. This may be due to an OutOfMemoryError. Further investigation is required, but this is not part of this problem analysis scenario.
• MI AWT:
  • If an MI window is still open and you can open the MI menu, then the MI is still running and you can continue with Step 2.
  • Otherwise the MI is no longer running and further investigation is required, but this is not part of this problem analysis scenario.

2.   Check the MI client (synchronization) settings

You must maintain the following settings:

• MI 2.5:
  • Client: the client of the MI server system
  • Protocol: Select either HTTP or HTTPS. If you select HTTPS, make sure that the MI client and MI server (J2EE Engine) support HTTPS (see SAP NetWeaver Security Guide ).
  • Host: the IP address or host name of the J2EE Engine to be used for synchronization
  • Port: the port on which the J2EE Engine can be accessed
  • System: the ID of the MI server system
• ME 2.1:
  • Gateway: This setting must have the following format:
    • <PROTOCOL>://<HOST>:<PORT>/meSync/servlet/meSync?~sysid=<SYSTEM>&
    • You must replace <PROTOCOL>, <HOST>, <PORT> and <SYSTEM> with the correct values
  • Client: the client of the MI server system
    Note

    See the Installation Guide for further details.

The relevant fields are marked red in the screenshots.

 

Settings MI 2.5 (Tomcat)

Settings ME 2.1 (Tomcat)

The AWT version of the MI contains dialogs with the corresponding input fields:

• ME 2.1: Settings → Connection
• MI 2.5: Settings → Connection (for client; gateway can also be maintained) and / or Settings → Gateway (for protocol, host, port and system)

If the settings were maintained properly, continue with step 3. Otherwise adjust the synchronization settings and start the synchronization again.

3.   Check the user name and (synchronization) password

Check if the user can log on to the corresponding Web AS.

If a synchronization password was prompted, enter the user name and synchronization password to log on to Web AS; the synchronization password was introduced with MI 2.5. (See SAP NetWeaver Security Guide .)

Otherwise, enter the user name and MI client logon password to log on to Web AS.

If the logon was successful, continue with Step 4.

Otherwise, adjust the user password. For example:

• Administrator sets a new password for the user on Web AS
• Depending on the security settings on the client, the user can either
  • Press Sync, enter the new synchronization password (if a synchronization password is prompted before each synchronization)
  • Log off, log on again, press Sync, enter the new synchronization password (if the synchronization password is prompted once)
  • Change the local password to a new password (if a synchronization password is not prompted)
  • Synchronize again.

4.   Check if the sync servlet is working

4.1. Check if the J2EE Engine is running

Open a Web browser and enter the following URL, replacing <HOST> and <PORT> with the corresponding host and port of the J2EE Engine to be used for synchronization:

http://<HOST>:<PORT>/

The welcome screen of the J2EE Engine should be displayed. If this is the case, continue with Step 4.2.

Otherwise check the host and port, and restart the J2EE Engine.

4.2. Check if the MI sync servlet is deployed

Open a Web browser and enter the following URL, replacing <HOST> and <PORT> with the corresponding host and port of the J2EE Engine to be used for synchronization:

http://<HOST>:<PORT>/meSync/

If a directory listing or an error message such as You are not authorized to view the content of the requested directory is displayed, you know that the MI sync servlet application has been deployed on this J2EE Engine. If this is the case, continue with Step 4.3.

Otherwise deploy the MI sync servlet to the J2EE Engine.

See also:

Installation Guide.

4.3. Check if the system properties file is installed and if it has the right content

Create a corresponding property file for each system against which a MI client should be able to synchronize.

For example, if a client wants to synchronize against a system XYZ, then a XYZ.props file has to be created in the System_Properties folder of the MI sync servlet installation.

There are two ways to check if the required property file is available:

1. If you have access to the file system on which the corresponding J2EE Engine is installed, you can navigate directly to the System_Properties folder of the MI sync servlet application.
2. If you do not have access to the file system of the J2EE Engine, you can check it by opening the following link in a Web browser:

   http://<HOST>:<PORT>/meSync/System_Properties/<SYSTEM_ID>.props

   for example:

   http://pwdf1234:55000/meSync/System_Properties/XYZ.props

   Since the J2EE Engine handles this request case-sensitively, you may need to correct the case of the letters in the system ID. Only lowercase or only uppercase is usually used in the system ID.

   If this file is available, a browser download dialog is opened. Save the property file on your local disk.

If no such property file exists, you have to create one. See the Installation Guide.

Open the property file with a simple text editor (such as Notepad) and check the application host and system number.

Content of a sample system properties file

If the settings are correct, continue with Step 4.4.

Otherwise you have to change these settings. See the Installation Guide.

4.4. Execute test URL

Open a Web browser and enter the following URL:

http://<HOST>:<PORT>/meSync/servlet/meSync?~sysid=<SYSTEM_ID>&~login=<USERNAME>&~password=<PASSWORD>&~client=<CLIENT>&~language=<LANGUAGE>&~acknowledge=X&~test=true&

replacing <HOST>, <PORT>, <SYSTEM_ID>, <USERNAME>, <PASSWORD>, <CLIENT> and <LANGUAGE> with the correct values.

For example, if you want to check if the MI sync servlet on pwdf1234, port 55000, is working for system XYZ (client 100), user MAIER (password TEST) and language English, you have to enter the following URL:

http://pwdf1234.wdf.sap.corp:55000/meSync/servlet/meSync?~sysid=XYZ&~login=MAIER&~password=TEST&~client=100&~language=EN&~acknowledge=X&~test=true&

If you get one of the following results, the sync servlet is working properly:

&WAF_SYNC&STATUS=&Execution Time= & HeaderType = MEREPLICATION &MORE_PACKAGES_WAITING = & SyncCounter = 0 &

Or

&WAF_SYNC&STATUS=&Execution Time= 143629& HeaderType = MEREPLICATION &MORE_PACKAGES_WAITING = &

If you get one of the above results, report the problem to SAP and enclose all gathered information.

If you get an empty page, there is an error in the connection to the ABAP stack.

• SAP NetWeaver Security Guide Security Guide
• MI Installation Guide:
  • ME 2.1: http://service.sap.com/instguides → SAP Components → SAP ME 2.1
  • MI 2.5: http://service.sap.com/instguides → SAP NetWeaver → Release 04 → Installation