SQL Anywhere ultralite - Windows Mobile 5.0 / ActiveSync 4.0

Author

Windows Mobile 5.0 / ActiveSync 4.0

Madhu Siddalingaiah

2005-11-29, 8:24 pm

I'm running 9.0.2.3198

I had good success synching UL apps on Pocket PC 2003 devices, such as
the iPAQ and Samsung i730, which use ActiveSync 3.7.1

I'm having odd problems with ActiveSync on Dell Axim x51, which runs
Windows Mobile 5.0 and requires ActiveSync 4.0

First, I don't always get the ActiveSyncInvoked event, or at least it
takes a while to show up.

Second, and more importantly, the device can't connect to any servers on
the network. When I try to sync, I get an error: OPEN, 10014,
SOCKET_HOST_NAME_NOT
_FOUND

Does the UL ActiveSync provider work with ActiveSync 4.0?

Is there something I have to do on the device or ActiveSync to enable
network access? I tried some of the obvious things, but no success...

Madhu Siddalingaiah

2005-11-29, 8:24 pm

Update:

I can sync without any problems with the following configuration:

* ActiveSync 4.0.0 (Build 4343)
* HP iPaq

The identical application does not sync on Dell Axim x51.

The error (on the device) is OPEN, 10014, SOCKET_HOST_NAME_NOT
_FOUND

There must be a network or security setting I am missing.

Any ideas??

Madhu Siddalingaiah wrote:
>
> I'm running 9.0.2.3198
>
> I had good success synching UL apps on Pocket PC 2003 devices, such as
> the iPAQ and Samsung i730, which use ActiveSync 3.7.1
>
> I'm having odd problems with ActiveSync on Dell Axim x51, which runs
> Windows Mobile 5.0 and requires ActiveSync 4.0
>
> First, I don't always get the ActiveSyncInvoked event, or at least it
> takes a while to show up.
>
> Second, and more importantly, the device can't connect to any servers on
> the network. When I try to sync, I get an error: OPEN, 10014,
> SOCKET_HOST_NAME_NOT
_FOUND
>
> Does the UL ActiveSync provider work with ActiveSync 4.0?
>
> Is there something I have to do on the device or ActiveSync to enable
> network access? I tried some of the obvious things, but no success...
>

Mike Vander Ploeg

2005-11-30, 1:23 pm

The UL ActiveSync provider does work with ActiveSync 4.0 on the Dell Axim
x51.

A minor fix was made for the default host for ActiveSync 4.0 / Windows
Mobile 5.0 in build 9.0.2.3218, though I don't know if it's available for
download yet.

What UltraLite API are you using? What are your synchronization parameters?

Mike Vander Ploeg
iAnywhere Solutions

"Madhu Siddalingaiah" < msiddalingaiah@bcbsa
l.org> wrote in message
news:438cf770$1@foru
ms-1-dub...[color=darkred]
>
> Update:
>
> I can sync without any problems with the following configuration:
>
> * ActiveSync 4.0.0 (Build 4343)
> * HP iPaq
>
> The identical application does not sync on Dell Axim x51.
>
> The error (on the device) is OPEN, 10014, SOCKET_HOST_NAME_NOT
_FOUND
>
> There must be a network or security setting I am missing.
>
> Any ideas??
>
> Madhu Siddalingaiah wrote:

Madhu Siddalingaiah

2005-11-30, 8:23 pm

I'm using C#, here's the sync code:

string sync_host = (string)
(configOptions["sync_host"] != null ?
configOptions["sync_host"] : "internetdev2");
string sync_stream = (string)
(configOptions["sync_stream"] != null ?
configOptions["sync_stream"] : "http");
string sync_port = (string)
(configOptions["sync_port"] != null ?
configOptions["sync_port"] : "80");
string sync_url = (string)
(configOptions["sync_url"] != null ?
configOptions["sync_url"] : "/scripts/iaredirect.dll/ml/");

// TODO get trusted_certificates
path from command line args
ERx.Conn.SyncParms.AuthenticationParms = authParms;
ERx.Conn.SyncParms.Stream = ULStreamType.ACTIVE_SYNC;
ERx.Conn.SyncParms.Version = "ERx_2.0";
ERx.Conn.SyncParms.StreamParms = "host=" + sync_host +
";stream=" + sync_stream +
";port=" + sync_port +
";url_suffix=" + sync_url +
" ;trusted_certificate
s=\\ePrescribing\\ce
rts\\Thawte Test Root.cer";
statusLbl.Text = ERx.Conn.SyncParms.StreamParms;
statusLbl.Update();

ERx.Conn.SyncParms.UploadOnly = false;
ERx.Conn.Synchronize(new SyncProgListener(thi
s));

Mike Vander Ploeg wrote:
> The UL ActiveSync provider does work with ActiveSync 4.0 on the Dell Axim
> x51.
>
> A minor fix was made for the default host for ActiveSync 4.0 / Windows
> Mobile 5.0 in build 9.0.2.3218, though I don't know if it's available for
> download yet.
>
> What UltraLite API are you using? What are your synchronization parameters?
>
> Mike Vander Ploeg
> iAnywhere Solutions

Mike Vander Ploeg

2005-12-01, 9:23 am

I don't see any problems with your code, so I suggest you upgrade to build
3218 or later. If that doesn't fix the problem, you'll probaby need to work
with tech support to get this resolved.

Mike

"Madhu Siddalingaiah" < msiddalingaiah@bcbsa
l.org> wrote in message
news:438e3e6c$1@foru
ms-1-dub...
>
> I'm using C#, here's the sync code:
>
> string sync_host = (string)
> (configOptions["sync_host"] != null ?
> configOptions["sync_host"] : "internetdev2");
> string sync_stream = (string)
> (configOptions["sync_stream"] != null ?
> configOptions["sync_stream"] : "http");
> string sync_port = (string)
> (configOptions["sync_port"] != null ?
> configOptions["sync_port"] : "80");
> string sync_url = (string)
> (configOptions["sync_url"] != null ?
> configOptions["sync_url"] : "/scripts/iaredirect.dll/ml/");
>
> // TODO get trusted_certificates
path from command line args
> ERx.Conn.SyncParms.AuthenticationParms = authParms;
> ERx.Conn.SyncParms.Stream = ULStreamType.ACTIVE_SYNC;
> ERx.Conn.SyncParms.Version = "ERx_2.0";
> ERx.Conn.SyncParms.StreamParms = "host=" + sync_host +
> ";stream=" + sync_stream +
> ";port=" + sync_port +
> ";url_suffix=" + sync_url +
> " ;trusted_certificate
s=\\ePrescribing\\ce
rts\\Thawte Test Root.cer";
> statusLbl.Text = ERx.Conn.SyncParms.StreamParms;
> statusLbl.Update();
>
> ERx.Conn.SyncParms.UploadOnly = false;
> ERx.Conn.Synchronize(new SyncProgListener(thi
s));
>
>
> Mike Vander Ploeg wrote:
>

Madhu Siddalingaiah

2005-12-05, 8:24 pm

I upgraded to 9.0.2.3221 and that worked :-)

One odd problem remains: on the Dell, the first time I plug in the
device, ActiveSync starts my app, but it doesn't receive the
ActiveSyncInvoked event. After some time, ActiveSync gives up and tries
again, this time, the app does receive the ActiveSyncInvoked event and
sync completes without incident.

If the app is running on the device, it receives the event and syncs
fine. ActiveSync tries to sync the device one more time, the event is
fired, and the sync completes fine.

This double-sync doesn't happen on the iPaq or the Samsung i730 (both
running Windows Mobile 2003), so I must be doing something wrong in my
sync code. It's possible there's a race condition between the app
startup and when the event is fired. What's the best way to handle the
ActiveSyncInvoked event? Right now, when the app starts, I show a login
form (our database is encrypted). When the event shows up, I pop up a
dialog saying "ActiveSync started". I was thinking of showing the login
form only after the event is fired, but how do I wait for an event
without showing a form? Or am I on the wrong track??

BTW, I have not upgraded the Dell to A04 ROM image, which Dell
recommends. I'm still running A03.

Mike Vander Ploeg wrote:
> I don't see any problems with your code, so I suggest you upgrade to build
> 3218 or later. If that doesn't fix the problem, you'll probaby need to work
> with tech support to get this resolved.
>
> Mike

Mike Vander Ploeg

2005-12-07, 11:23 am

I have not seen this kind of behaviour myself. The double sync sounds like
an ActiveSync 4.0 bug. I've never had much confidence in ActiveSync, and
4.0 seems buggier than most. You could try upgrading to 4.1. Also, it
might not hurt to upgrade your device either.

An alternate way of implementing this, is to have the ActiveSync provider
start up your app with a special command line option. If this option is
set, your app would show the login form and then immediately do an
ActiveSync sync without looking for the AcitveSyncInvoked event, and then
automatically shutdown after the sync has completed.

Mike

"Madhu Siddalingaiah" < msiddalingaiah@bcbsa
l.org> wrote in message
news:43949b5b$1@foru
ms-1-dub...[color=darkred]
>
> I upgraded to 9.0.2.3221 and that worked :-)
>
> One odd problem remains: on the Dell, the first time I plug in the device,
> ActiveSync starts my app, but it doesn't receive the ActiveSyncInvoked
> event. After some time, ActiveSync gives up and tries again, this time,
> the app does receive the ActiveSyncInvoked event and sync completes
> without incident.
>
> If the app is running on the device, it receives the event and syncs fine.
> ActiveSync tries to sync the device one more time, the event is fired, and
> the sync completes fine.
>
> This double-sync doesn't happen on the iPaq or the Samsung i730 (both
> running Windows Mobile 2003), so I must be doing something wrong in my
> sync code. It's possible there's a race condition between the app startup
> and when the event is fired. What's the best way to handle the
> ActiveSyncInvoked event? Right now, when the app starts, I show a login
> form (our database is encrypted). When the event shows up, I pop up a
> dialog saying "ActiveSync started". I was thinking of showing the login
> form only after the event is fired, but how do I wait for an event without
> showing a form? Or am I on the wrong track??
>
> BTW, I have not upgraded the Dell to A04 ROM image, which Dell recommends.
> I'm still running A03.
>
> Mike Vander Ploeg wrote:

Madhu Siddalingaiah

2005-12-08, 11:23 am

Yes, I thought about that.

What's problematic is that the command line option doesn't always show
up either!

I think you may be right about ActiveSync, it doesn't appear to be very
robust.

Mike Vander Ploeg wrote:
> I have not seen this kind of behaviour myself. The double sync sounds like
> an ActiveSync 4.0 bug. I've never had much confidence in ActiveSync, and
> 4.0 seems buggier than most. You could try upgrading to 4.1. Also, it
> might not hurt to upgrade your device either.
>
> An alternate way of implementing this, is to have the ActiveSync provider
> start up your app with a special command line option. If this option is
> set, your app would show the login form and then immediately do an
> ActiveSync sync without looking for the AcitveSyncInvoked event, and then
> automatically shutdown after the sync has completed.
>
> Mike

Sponsored Links