Skip to Content
avatar image
Former Member

UltraLiteJ Error[-1305]: MobiLink communication error -- code: 220, parameter: , system code: 151441510

Hi ,

I am stuck with this past two days. Request if some one can help

com.ianywhere.ultralitejni16.implementation.JniException: UltraLiteJ Error[-1305]: MobiLink communication error -- code: 220, parameter: , system code: 151441510

com.ianywhere.ultralitejni16.implementation.JniConnection.ulcSynchronize(Native Method)

com.ianywhere.ultralitejni16.implementation.JniConnection.synchronize(Unknown Source)

com.mftp.bll.dbaccess.UltraLiteDBAccess.synchronize(UltraLiteDBAccess.java:259)

com.mftp.middleware.dbsynchronizer.hotlist.HotlistSyncHandler.Sync(HotlistSyncHandler.java:51)

com.mftp.middleware.dbsynchronizer.SynchronizationHandler.handleMessage(SynchronizationHandler.java:43)

android.os.Handler.dispatchMessage(Handler.java:99)

android.os.Looper.loop(Looper.java:137)

com.mftp.middleware.dbsynchronizer.DBSynchronizer.run(DBSynchronizer.java:39)

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jun 08, 2016 at 07:44 PM

    What do the logs on the server side of this communication say when you get this error at the remote side?  ML Communication error 220 is an internal error, so the more helpful error is usually on the server side.



    http://dcx.sap.com/index.html#sqla170/en/html/80f0599e6ce21014a6d29de9e700bea0.html


    UltraLiteJ Error[-1305]: MobiLink communication error -- code: 220, parameter: , system code: 151441510

    Reg

    Add comment
    10|10000 characters needed characters exceeded

    • The server side logs show errors with the Outbound Enabler trying to connect to the Relay Server, which is completely separate from the client trying trying to send a request to the Relay Server to be passed to the backend server.  The Relay Server shouldn't respond with an internal error is the backend server you're trying to talk to isn't available, so I think there's a few things going wrong here.

      We'll need to see the "bigger picture" and get a look at the request from start to finish as it travels from the client through the Relay Server and Outbound Enabler to the backend server.

      Can you please reproduce the problem again and provide the following information?

      1. The HTTPERR log from the IIS Machine (typically located at c:\windows\system32\LogFiles\HTTPERR)
      2. The IIS Access Log from the IIS Machine (typically located at c:\inetpub\logs\logfiles\w3svc1)
      3. The applicationHost.config from the IIS Machine (typically located at c:\windows\system32\inetsrv\config).
      4. The output from the "appcmd list config" command, run on the machine where IIS is running.  appcmd isn't always in the path, but is typically located at c:\windows\system32\inetsrv.
      5. The configuration file being used by the Relay Server
      6. A verbosity 5 Relay Server Log from when then problem occurs.  It would be ideal to have a Relay Server log that contains the start-up of the Relay Server and the timeframe from when the problem occurs with nothing removed.
      7. The start line for the Outbound Enabler
      8. The verbosity 5 Outbound Enabler Log from when then problem occurs.  It would be ideal to have an Outbound Enabler log that contains the start-up of the Outbound Enabler and the timeframe from when the problem occurs with with nothing removed.
      9. The time on the machine where IIS is running when you made the request from the client.
      10. The exact URL that the client uses when it makes the request.
      11. The exact error thrown by the client.


      It would be best if you posted all this information to the forum (seriosuly, you can't post ZIP files?).  I'll be off work the rest of the week, so if you email it to me directly (firstname.lastname@sap.com) you will not get a quick response.

      Reg.Domaratzki