I've installed ME 2.1 SP03. Test synchronisation in webbrowser works fine. When I try to synchronize from the client (on Windows) it doesn't get a device ID and reports no error either.
When I examine the MeSync Log on the J2EE server, it contains the message that the mandatory servlet parameter ~login is missing. The client trace states a httpPost like this, which in fact doesn't contain a ~logon parameter.
It seems that the problem is not in the gateway or the other settings on the MI client. The client uses a new kind of communication - it does not include the login name and the password as arguments in the cgi form (i.e. "&login=username&password=userpass"), but sets them as request parameters.
It is pretty lovely, but the server still expects that data as arguments in the cgi form. So an internal servlet error 500 is generated (with explanation "~login missing"), and the syncronization fails.
In my opinion there is a client/server misversioning. May please someone confirm or disprove this? I haven't yet idea how to resolve the problem..
@Matthew: thanks, but it doesn't work either. Message is still the same. The properties file exists and seems to be correct (as test sync call via browser is working fine)
@Meesum: The file is called misync.txt - use search function.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.