mobilink: unable to complete the request => what could cause this or how to get more info?

[Former Member]

Hi,

I have this "remoteDB/mobilink/oracle environment" that I'm updating and now that I'm trying to test synchronization I'm getting the message that request cannot be completed without any explanation.

What could cause this?

---

Things I've checked and done:

I can reach the mobilink server and the consolidated database. The mobilink server can also reach the consolidated database.

I've seen this url: http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.sqlanywhere.12.0.1/saerrors/mlsrv...

And I have also checked the mobilink logs on the server with following settnigs and the log shows nothing... there is no indication that any connection was made. These are the settings I use: -v -o C:\\MobilinkLog\\mls.txt -os 10m -cn 5 -zu+ -w 100 -ds 0

And this is what I see in SQL Anywhere Mobilink client:

I. 2015-05-28 14:06:32. Connecting to MobiLink server at 'host=xxx.xxx.xxx.xxx;port=2439' using 'TCPIP' I. 2015-05-28 14:06:32. Begin upload

I. 2015-05-28 14:06:32. Uploading table operations

I. 2015-05-28 14:06:32. Waiting for MobiLink to apply upload

E. 2015-05-28 14:06:32. Error code from MobiLink server: -10368

E. 2015-05-28 14:06:32. Server error: Unable to complete the request

E. 2015-05-28 14:06:32. Error code from MobiLink server: -10368

E. 2015-05-28 14:06:32. Server error: Unable to complete the request

I. 2015-05-28 14:06:32. End synchronizing subscription(s) 'XXXX'

I. 2015-05-28 14:06:32. Disconnecting from MobiLink server

I. 2015-05-28 14:06:32. Synchronization completed

[Breck_Carter]

Look again at the MobiLink server -o log, that is where the error is occurring... it is absolutely impossible that the "log shows nothing"

[Former Member]

I kid you not, I restarted mobilink at 1 o'clock and was trying to synchronize at 2 o'clock... I can only see stuff from the restart, THIS IS THE LAST MESSAGE IN THE LOG FILE:

I. 2015-05-28 13:21:53. Running Windows 2008R2 Build 7601 Service Pack 1 on X86_64
I. 2015-05-28 13:21:53. Server built for X86_64 processor architecture
I. 2015-05-28 13:21:53. <main> Option 1: -c
I. 2015-05-28 13:21:53. <main> Option 2: dsn=cEVD
I. 2015-05-28 13:21:53. <main> Option 3: -v
I. 2015-05-28 13:21:53. <main> Option 4: -o
I. 2015-05-28 13:21:53. <main> Option 5: C:\\MobilinkLog\\mls.txt
I. 2015-05-28 13:21:53. <main> Option 6: -os
I. 2015-05-28 13:21:53. <main> Option 7: 10m
I. 2015-05-28 13:21:53. <main> Option 8: -cn
I. 2015-05-28 13:21:53. <main> Option 9: 5
I. 2015-05-28 13:21:53. <main> Option 10: -zu+
I. 2015-05-28 13:21:53. <main> Option 11: -w
I. 2015-05-28 13:21:53. <main> Option 12: 100
I. 2015-05-28 13:21:53. <main> Option 13: -ds
I. 2015-05-28 13:21:53. <main> Option 14: 0
I. 2015-05-28 13:21:53. <main> Verbose logging: show minimum detail
I. 2015-05-28 13:21:53. <main> Cache size: 52428800 bytes
I. 2015-05-28 13:21:53. <main> Download cache directory size: 0 bytes
I. 2015-05-28 13:21:53. <main> Local file for remote synchronization logs: 'mlsrv.mle'
I. 2015-05-28 13:21:53. <main> Individual database connections will be closed after synchronization errors
I. 2015-05-28 13:21:53. <main> Maximum number of BLOB bytes to compare: 4294967295
W. 2015-05-28 13:21:53. <main> [10001] Maximum number of database connections set to 100 (must be at least the number of database worker threads)
I. 2015-05-28 13:21:53. <main> Maximum number of deadlock retries: 10
I. 2015-05-28 13:21:53. <main> Timeout for inactive database connections: 60 minutes
I. 2015-05-28 13:21:53. <main> Maximum delay between retries after deadlock: 30 seconds
I. 2015-05-28 13:21:53. <main> Rowset size: 10
I. 2015-05-28 13:21:53. <main> Number of database worker threads: 100
W. 2015-05-28 13:21:53. <main> [10064] Unknown users will be added automatically (when there is no authenticate_user script)
I. 2015-05-28 13:21:53. <main> Shared administrative connection connected
I. 2015-05-28 13:21:53. <main> ODBC DBMS Name: Oracle
I. 2015-05-28 13:21:53. <main> ODBC DBMS Version: 11.02.0000
I. 2015-05-28 13:21:53. <main> ODBC DBMS Driver Version: 12.00.0001
I. 2015-05-28 13:21:53. <main> ODBC Version supported by the driver: 3.51
I. 2015-05-28 13:21:53. <main> ODBC DBMS Type: ORACLE
I. 2015-05-28 13:21:53. <main> ODBC isolation set to: Read Committed
I. 2015-05-28 13:21:53. <main> MobiLink server started
I. 2015-05-28 13:21:53. <main> Notifier stage connection connected
I. 2015-05-28 13:21:53. <main> ODBC isolation set to: Read Committed
I. 2015-05-28 13:21:53. <main> Started RTNotifier 'RTNotifier1'

[VolkerBarth]

FWIW, I surrounded the log text with a "pre" tag pair (in angle brackets, of course) to format it as code...

If the log has been renamed currently, what does the previous log tell about the failed sync?

From the docs:

If you specify -v alone, the MobiLink server writes a minimal amount of information about each synchronization.

So you might add more levels to -v to get more output details...

[regdomaratzki · Accepted solution]

The simplest explanation to the ML Client indicating that the ML Server returned error X, but the ML Server having no record of the synchronization is that the ML Client is connecting to a different ML Server.

Are you sure that this is the ML Server running on IP Addres xxx.xxx.xxx.xxx ? Is there any other network infrastructure between the ML Client and ML Server ? If you increase the verbosity of the ML Server to -v+, is there any indication of a synchronization?

Reg

[Former Member · Accepted solution]

Reg's answer is underscored by the fact that your MLSRV12 console log terminates prior to the sync time related to that error: 2015-05-28 14:06:32.

While that could just be due to you not including the whole console log or you are looking for a different ML server.

TIP: requests will show up with their session information between those angle-brackets ... and it won't be the lines with '<main>'.

[Former Member]

My sincere apologies. I was indeed connected to the wrong server. Simple as that. I got the IP of the server from another project of mine and pinged the server to see if I could reach it but offcourse I could since it was a different mobilink server. After your responses I did an ipconfig on the server itself and saw the IP did not match. Sorry !!

[regdomaratzki]

THanks for letting us