Re: O2 xda exec (HTC universal) will sync over wifi not over gprs to exchange

Hi,
Please make sure that the host name (fqdn) is the same for the internal
network as it is for the external network. That way the O2 XDA Exec can
find the Exchange server using the same name in both cases.


--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.tabletpctalk.com
http://www.pocketpctalk.com
http://www.mobilitytalk.com

<> wrote in message
news: ups.com...
> Hi all,
>
> Annoying problem with two new windows mobile 2005 devices. One a pocket
> pc xda exec (htc universal) and one a smartphone (imate sp5).
>
> Talking about the pocketpc here but they both give the same error when
> I try and sync with exchange over gprs.
>
> Result:
> synchronization could not be compelted. try again later
> support code: 0x8503001A
>
> I can't find that support code anywhere on the microsoft site :/ The
> verbose logs on the device don't show anything odd and the logs on the
> exchange server aren't yielding any clues.
>
> I've tried saying dont sync contacts or calendar etc.. all combinations
> to rule out bad data but no luck.
>
> What's even more odd is that a) it works over wifi and b) all my
> windows mobile 2003 devices work absolutely fine with the same settings
> :/
>
> anyone any ideas? at the moment I have to say windows mobile 2005
> syncing seems *very* flaky :/
>

Hi,
Did you enter the FQDN as the name of the server when you setup
synchronization?


--
Chris De Herrera
http://www.pocketpcfaq.com
http://www.tabletpctalk.com
http://www.pocketpctalk.com
http://www.mobilitytalk.com

<> wrote in message
news: ps.com...
> Hi Chris thanks for the reply,
>
> The fqdn is indeed the same internally and externally. Proper old
> fashioned routed IP behind the name.
>
> I'm struggling to see what else could be different between syncing over
> wifi and syncing over gprs unless something changed on wm2005 that the
> gprs providers don't allow through :/
>

With o2 (don't know about Orange) data is optimized as standard over the
Mobile Web GPRS connection. Is it possible that both lots of compression are
conflictiong? If you use bypass as the username and password as the password
for your GPRS connection this will bypass the optimization. aybe this will
solve the issue. I do not have the equipment to test but it is just a thought.
--
Regards,

Andrew Newell


"" wrote:

> ok well after spending all night with several exchange servers trying
> all the options, a colleague sorted it out.
>
> By applying different options and watching the difference between a
> working server and a non-working one, he isolated the settings in
> metabase.xml which when changed, caused this annoying support code.
>
> It was activesync compression enabled via FBA in the first instance...
> so turn compression onto say high on fba, then sync.... worked over
> everything except GPRS (on UK networks O2 and Orange at least, which
> were the only ones we could test with).
>
> Turning both static and dynamic compression to FALSE immediately fixed
> the issue.
>
> It leaves the question why doesn't compression work? could it be a UK
> GPRS network issue perhaps.... don't know yet.
>
> Anyway it all makes sense since compression was something that we know
> ms messed with for wm2005 and will start becoming more important with
> the always on http connection for push email.
>
> So not perhaps fixed, but at least patched for the time being.
>
> Thanks all for the help.... not an easy one to diagnose locally never
> mind remotely
>
>

This should solve the problem.

Ce problème s’applique uniquement aux utilisateurs Windows Mobile 5 qui
veulent synchroniser avec un Exchange 2003 (qui a été mise Ã* jour par le SP2)
et ce via GPRS.. car via Wifi, il n’y a aucun problème.

Le code erreur est 0x8503001A et est du Ã* un problème de compression. La
compression dynamique ainsi que statique étaient désactivées avant
l’application du SP2, mais le SP2 active ça et voilÃ* notre problème !!

Peut-être encore un bug de WM5 d'après ce que j'ai compris, WM5 gère mal la
compression HTTP..

Alors pour contourner le problème, voici la solution :

Tout d’abord, faire un backup de la Metabase
Ouvrir IIS Manager
Cliquez droit sur Server->All Tasks->Backup/Restore Configuration
Cliquez « Create backup »
Entrez un nom style « Backup avant fix »
Cliquez OK, fermez

Ensuite activer la possibilité d’éditer la Metabase pendant qu’IIS tourne :
Ouvrir IIS Manager
Cliquez droit sur Server et choisissez « Properties »
Activez « Enable Direct Metabase Edit »
Cliquez ok

Ouvrir avec Notepad le fichier suivant
C:WINDOWS;SYSTEM32;INETSRV;METABASE.XML

Cherchez <IIsWebVirtualDir
Location="/LM/W3SVC/1/ROOT/Microsoft-Server-ActiveSync">
et juste en dessous vous verrez:

DoDynamicCompression="TRUE"
DoStaticCompression="TRUE"

Changez ces deux parameters en FALSE (attention de ne changer que ces deux
lÃ*, car il y en a d’autres dans ce fichier)

Sauvez le fichier Metabase.xml et redémarrez IIS :
Démarer->executer->IISRESET

Bon amusement
Dirk


"Andrew Newell" wrote:

> With o2 (don't know about Orange) data is optimized as standard over the
> Mobile Web GPRS connection. Is it possible that both lots of compression are
> conflictiong? If you use bypass as the username and password as the password
> for your GPRS connection this will bypass the optimization. aybe this will
> solve the issue. I do not have the equipment to test but it is just a thought.
> --
> Regards,
>
> Andrew Newell
>
>
> "" wrote:
>
> > ok well after spending all night with several exchange servers trying
> > all the options, a colleague sorted it out.
> >
> > By applying different options and watching the difference between a
> > working server and a non-working one, he isolated the settings in
> > metabase.xml which when changed, caused this annoying support code.
> >
> > It was activesync compression enabled via FBA in the first instance...
> > so turn compression onto say high on fba, then sync.... worked over
> > everything except GPRS (on UK networks O2 and Orange at least, which
> > were the only ones we could test with).
> >
> > Turning both static and dynamic compression to FALSE immediately fixed
> > the issue.
> >
> > It leaves the question why doesn't compression work? could it be a UK
> > GPRS network issue perhaps.... don't know yet.
> >
> > Anyway it all makes sense since compression was something that we know
> > ms messed with for wm2005 and will start becoming more important with
> > the always on http connection for push email.
> >
> > So not perhaps fixed, but at least patched for the time being.
> >
> > Thanks all for the help.... not an easy one to diagnose locally never
> > mind remotely
> >
> >

Hi Keith,

We have now tried this with server compression on and o2 GPRS Web
compression off. This worked with no issues. The problem seems to occur when
both lots of compression are on; they must be conflicting. So it works when
you turn either off and leave the other on.

GPRS traffic is compressed as standard when using the mobile.o2.co.uk APN on
the o2 network. To turn it off use 'bypass' as your username and 'password'
as your password in the connection settings for the connection to the APN.

I am fairly sure Orange compress data when using there GPRS connection but I
am not sure how to disable.
--
Regards,

Andrew Newell


"Andrew Newell" wrote:

> With o2 (don't know about Orange) data is optimized as standard over the
> Mobile Web GPRS connection. Is it possible that both lots of compression are
> conflictiong? If you use bypass as the username and password as the password
> for your GPRS connection this will bypass the optimization. aybe this will
> solve the issue. I do not have the equipment to test but it is just a thought.
> --
> Regards,
>
> Andrew Newell
>
>
> "" wrote:
>
> > ok well after spending all night with several exchange servers trying
> > all the options, a colleague sorted it out.
> >
> > By applying different options and watching the difference between a
> > working server and a non-working one, he isolated the settings in
> > metabase.xml which when changed, caused this annoying support code.
> >
> > It was activesync compression enabled via FBA in the first instance...
> > so turn compression onto say high on fba, then sync.... worked over
> > everything except GPRS (on UK networks O2 and Orange at least, which
> > were the only ones we could test with).
> >
> > Turning both static and dynamic compression to FALSE immediately fixed
> > the issue.
> >
> > It leaves the question why doesn't compression work? could it be a UK
> > GPRS network issue perhaps.... don't know yet.
> >
> > Anyway it all makes sense since compression was something that we know
> > ms messed with for wm2005 and will start becoming more important with
> > the always on http connection for push email.
> >
> > So not perhaps fixed, but at least patched for the time being.
> >
> > Thanks all for the help.... not an easy one to diagnose locally never
> > mind remotely
> >
> >