Windows Mobile 6.5 and ActiveSync
Darron Chapman
Is anyone else having issues getting ActiveSync on Windows Mobile 6.5 to connect to your CommuniGate server. ActiveSync was working on 6.1 but when I upgraded my phone to 6.5, it stopped working and I get the following error: “Exchange ActiveSync has encountered an error. If this condition persists, please contact your Exchange Administrator.” And then it gives a support code of 0x80070006.
Thanks in advance for any help you can provide.
Darron Chapman
opa...@oxfordms.net
Cheers
############################################################# This message is sent to you because you are subscribed to the mailing list <CGat...@mail.stalker.com>. To unsubscribe, E-mail to: <CGateP...@mail.stalker.com> To switch to the DIGEST mode, E-mail to <CGatePr...@mail.stalker.com> To switch to the INDEX mode, E-mail to <CGatePr...@mail.stalker.com> Send administrative queries to <CGatePro...@mail.stalker.com>
Technical Support
opa...@oxfordms.net wrote:
> What version of CGatePro? We had immediate sync problems with
> ActiveSync devices (and no changes on the mobile devices) after going
> from 5.2.18 to 5.3c so we went back to 5.2.18 and had no problems.
> Upgraded last week from 5.2.18 to 5.3 stable and saw sync problems
> again. We're back down to 5.2.18 again for now.
What kind of problems did you have with CGPro 5.3 and ActiveSync?
> Cheers
>
> On Mon, 04 Jan 2010 17:23:42 -0600
> "Darron Chapman" <dcha...@warrensburg.k12.mo.us> wrote:
> > Is anyone else having issues getting ActiveSync on
> >Windows Mobile 6.5 to connect to your CommuniGate server.
> > ActiveSync was working on 6.1 but when I upgraded my
> >phone to 6.5, it stopped working and I get the following
> >error: "Exchange ActiveSync has encountered an error.
> > If this condition persists, please contact your Exchange
> >Administrator." And then it gives a support code of
> >0x80070006.
> >
> >
> >
> > Thanks in advance for any help you can provide.
> >
> >
> > Darron Chapman
> >
> >
> >
--
Best regards,
Dmitry Akindinov
=======================================================================
When answering to letters sent to you by the tech.support staff, make
sure the original message you have received is included into your
reply.
Robert Opalko
not download email and calendar updates immediately after the upgrade to
5.3. The issues went away when we went back to 5.2.18. From the logs:
00:19:05.541 2 AIRSYNC-018796(someuser/HTCAnd487f70cc) [66.175.144.84]:51160 htcheroc(HTCAnd487f70cc): FolderSync request
00:19:20.181 2 AIRSYNC-018797(someuser/HTCAnd487f70cc) [66.175.144.84]:5027 htcheroc(HTCAnd487f70cc): GetItemEstimate request
00:19:20.186 1 AIRSYNC-018797(someuser/HTCAnd487f70cc) failed to read 'INBOX' synching info. Error Code=unknown mailbox sync ID
00:19:21.509 2 AIRSYNC-018798(someuser/HTCAnd487f70cc) [66.175.144.84]:9059 htcheroc(HTCAnd487f70cc): Sync request
00:19:21.514 1 AIRSYNC-018798(someuser/HTCAnd487f70cc) 'INBOX': updating failed. Error Code=some messages have been deleted
Cheers,
Robert Opalko
Technical Support wrote:
> Hello,
>
> opa...@oxfordms.net wrote:
>> What version of CGatePro? We had immediate sync problems with
>> ActiveSync devices (and no changes on the mobile devices) after going
>> from 5.2.18 to 5.3c so we went back to 5.2.18 and had no problems.
>> Upgraded last week from 5.2.18 to 5.3 stable and saw sync problems
>> again. We're back down to 5.2.18 again for now.
>
> What kind of problems did you have with CGPro 5.3 and ActiveSync?
>
>
>> Cheers
>>
>> On Mon, 04 Jan 2010 17:23:42 -0600
>> "Darron Chapman" <dcha...@warrensburg.k12.mo.us> wrote:
>> > Is anyone else having issues getting ActiveSync on
>> >Windows Mobile 6.5 to connect to your CommuniGate server.
>> > ActiveSync was working on 6.1 but when I upgraded my
>> >phone to 6.5, it stopped working and I get the following
>> >error: "Exchange ActiveSync has encountered an error.
>> > If this condition persists, please contact your Exchange
>> >Administrator." And then it gives a support code of
>> >0x80070006.
>> >
>> >
>> >
>> > Thanks in advance for any help you can provide.
>> >
>> >
>> > Darron Chapman
>> >
>> >
>> >
>
#############################################################
Jason Mader
NotifySync service.
- Contacts not showing up
- Some folders not showing up on the device (which problem messed up Contacts)
On Tue, 5 Jan 2010, Technical Support wrote:
> Hello,
>
> opa...@oxfordms.net wrote:
>> What version of CGatePro? We had immediate sync problems with ActiveSync
>> devices (and no changes on the mobile devices) after going from 5.2.18 to
>> 5.3c so we went back to 5.2.18 and had no problems. Upgraded last week
>> from 5.2.18 to 5.3 stable and saw sync problems again. We're back down to
>> 5.2.18 again for now.
>
> What kind of problems did you have with CGPro 5.3 and ActiveSync?
>
>
>> Cheers
>>
>> On Mon, 04 Jan 2010 17:23:42 -0600
>> "Darron Chapman" <dcha...@warrensburg.k12.mo.us> wrote:
>> > Is anyone else having issues getting ActiveSync on
>> >Windows Mobile 6.5 to connect to your CommuniGate server.
>> > ActiveSync was working on 6.1 but when I upgraded my
>> >phone to 6.5, it stopped working and I get the following
>> >error: "Exchange ActiveSync has encountered an error.
>> > If this condition persists, please contact your Exchange
>> >Administrator." And then it gives a support code of
>> >0x80070006.
>> >
>> >
>> >
>> > Thanks in advance for any help you can provide.
>> >
>> >
>> > Darron Chapman
>> >
>> >
>> >
>
>
---Jason Mader, National Crash Analysis Center,
The George Washington University, Virginia Science and Technology Campus
Darron Chapman
I’m running 5.3.0 right now, but this problem occurred when I was still on 5.2. Our 6.1 phones are working fine even on the new version, but my Windows Mobile 6.5 phone is not connecting at all.
-----------------
What
version of CGatePro? We had immediate sync problems with ActiveSync
devices (and no changes on the mobile devices) after going from 5.2.18 to 5.3c
so we went back to 5.2.18 and had no problems. Upgraded last week from
5.2.18 to 5.3 stable and saw sync problems again. We're back down to
5.2.18 again for now.
Cheers
David Brookfield
about our problem; just recently we have started getting an in-ordinate
number of stalled mail due to DNS timeouts. By this I mean 2 out of 3
will stall in the queue and shows in the logs as below
00:16:18.00 3 SMTPI-42471(bvsig.cput.ac.za) failed to resolve HELO
parameter: DNS transaction timeout. Real address is [198.54.223.71]
00:17:03.00 3 SMTPI-42469(bvsig.cput.ac.za) failed to resolve HELO
parameter: DNS transaction timeout. Real address is [198.54.223.71]
00:17:03.00 3 SMTPI-42470(bvsig.cput.ac.za) failed to resolve HELO
parameter: DNS transaction timeout. Real address is [198.54.223.71]
00:17:03.00 3 SMTPI-42472(bvsig.cput.ac.za) failed to resolve HELO
parameter: DNS transaction timeout. Real address is [198.54.223.71
Now if I look at the queue (I can see it is full of DNS transaction
timeout errors) if I click on the domain and manually release the mail
goes through happily, all e it it takes some time. I wondered if there
was some sort of DNS weirdness on the CGP server but if I do a dig
against any of the domains I get a response I would expect to see and
the same for any of the machines behind our firewall.
We're running 5.0.13 on Ubuntu and I've got DNS setup in the Obscure
setting to look at OpenDNS ( I use this elsewhere and have no problems)
and I also have a final DNS entry of a DNS server in my data centre.
Initial timeout is 3 secs
Concurrent requests is 500 (We do have some mail hosts that squirt out
upwards of 5k of messages throughout the day but no idea if 500 is
problematical)
Retry limit is 6
Log level is currently set to problems but I can change this if need be.
Any ideas
All help gratefully accepted.
David Brookfield
Lyle Giese
running 15 seconds. I think dig times out at 20 or so.
A little bit of congestion at OpenDNS or anywhere in the data/Internet
path between your server and them will more than span 3 seconds.
Lyle Giese
LCR Computer Services, Inc.
David Brookfield
did some digs on domains that were timing out and and was still
receiving response times of between 3 msec and 700msec so assumed that 3
secs was more than enough. As far as I know it's always been 3 seconds.
We've got three DNS servers in our DNS list with the last one being in
the data centre so I still don't have a scoobies why this would happen.
I'll report more when I see it.
Many thanks
David Brookfield
Lyle Giese
server's cache. Then the resolving server will have to crawl the DNS
servers from the root name servers down to the authorative name servers
for that domain. The speed of that resolution can depend on the speed
of many servers out on the Internet.
But once the three servers you have configured have the answer, they
will give you the answer from their cache rather than do a recursive
query. The cached answers SHOULD be fast. Recursive answers can be
slow to come back.
I think that's what you are running into. The recursive queries are
taking more than 3 seconds, CGPro moves on to the next name server until
it runs out of name servers to ask. And by the time you investigate,
the name servers will have the answer in their cache and it appears to
be a fast answer.
Lyle Giese
LCR Computer Services, Inc.
Rob Logan
with Google joining the DNS party along with UltraDNS, OpenDNS and one's
local provider, its a good idea to *test* what's fastest for any
given location on the net.. there are two good tools for this
http://code.google.com/p/namebench/
http://www.grc.com/dns/benchmark.htm
David Brookfield
Timeout to 45 seconds which should be more than ample time for a DNS
query to go though and then some. It looks like the problem hasn't gone
in that now I have more domains in the SMTP sending queue now with
elapsed times of 12 - 14 minutes which makes sense as I've got three DNS
servers in the list and a retry of 6 times.
However if I do manually release the domain it invariably goes. I've
also changed the SMTP sending retry to send every 10 mins and upped the
time it will retry for, but still no joy. All this machine does is CGP
nothing else on it, a quick look at top says that CGP is using less than
1% CPU so more ideas would be great :)
David
Graeme Fowler
David wrote:
> All this machine does is CGP nothing else on it, a quick look at top
> says that CGP is using less than 1% CPU so more ideas would be great
I'd strongly recommend running a local caching resolver on the same machine, then configuring CGP to use that. If necessary you can set that up to forward queries off to OpenDNS, Google, your ISP or elsewhere but it will minimise the disruption if there is any problem with remote DNS resolvers. It will also speed up name resolution as it will pull records from the local cache for most queries, and will reduce the amount of traffic traversing your Internet link.
[note however that you must, must, must ensure that the nameserver is not accessible from external hosts]
Unfortunately I cannot remember the package name for Ubuntu, but it shouldn't be too hard to find with Aptitude or another package manager.
Graeme
David Brookfield
much appreciated.
David
David Brookfield
did the trick nicely, although it doesn't explain why something that was
working stopped working.
Here's the Howto we used if anyone is thinking of doing the same.
Thanks again for the help :)
David
Jason Mader
the number of retries to 1 and extend the timeout.
I use dnscache for my local resolver and have the timeout as 10 minutes,
since dnscache will chug away trying to resolve a query and only return an
answer or that it could not find the answer after it times out (which is
about 960 seconds max).
So you don't want CGP to resend the queries to your local caching resolver
while it is still working on the first query.
And you may also like to increase the number of dns queries in CGP to be
almost what your local caching resolver will handle.
---Jason Mader, National Crash Analysis Center,
The George Washington University, Virginia Science and Technology Campus
#############################################################