Error 0x80070057

[Bjarne Riis]

Hello,

Just installed Exchange 2003 RC1 and tried to use the ActiveSync Feature
which always generates the above error.
I have installed a local certificate server, and loaded the root certificate
to the PPC, but as said I get the following error shortly after the Sync
start: Synchronization failed. If the problem continues please contact your
network administrator. Error code: 0x80070057

The funny thing is that I have access to a PPC with the next version of
Windows CE software (4.0) and when running with this PPC, it just works like
a charm against the same server with the same username and password.

I think I have tried all the suggestions in this newsgroup, but none of them
have worked, and the above error doesn't realy point me in any direction.

Regards,
Bjarne Riis

[Heikki Pesonen]

Hi Bjarne,

have you already tried to uppdate your PDA with sertificate disabler
AS_Cert_OFF.CAB?

BR,
Heikki

"Bjarne Riis" <bja...@briis.com> wrote in message
news:uxr4OLuK...@TK2MSFTNGP09.phx.gbl...

[Bjarne Riis]

Yes I have tried that with exactly the same result.

Bjarne

"Heikki Pesonen" <heikki....@pp5.inet.fi> wrote in message
news:OI5pJXGL...@TK2MSFTNGP11.phx.gbl...

[Heikki Pesonen]

Ok, can you access mailbox in exchange 2003 server with OWA or Outlook. You
must first log on to mailbox using OWA and it initializes mailbox correctly.
And after that Mobile access gets data corrrectly from mailbox.

Heikki

"Bjarne Riis" <bja...@briis.com> wrote in message

news:OlZYmyNL...@TK2MSFTNGP11.phx.gbl...

[Heikki Pesonen]

Can you help me with my problem? I have Compaq iPaq H3870 and I use MS
ActiveSync 3.7. I get error message as follows: Synchronization failed due
to a communications failure. Try again. Error code: INTERNET_152? There is
Exchange 2003 RC1 and mailbox works ok from OWA and Outlook from pc where
iPaq is attached with USB cable. I can also log on to mailbox from iPaq with
IE and OWA. I´m totally out of this error.

Heikki

"Bjarne Riis" <bja...@briis.com> wrote in message

news:OlZYmyNL...@TK2MSFTNGP11.phx.gbl...

[Carl Wolz [MSFT]]

There a KB article on this
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B318376

The INTERNET_152 error code comes from Wininet's error 12152
(ERROR_HTTP_INVALID_SERVER_RESPONSE, The server response could not be
parsed. )

Also please check the setting's in the desktop's ActiveSync application's
"Tools->Options->Rules->Pass Through" is set appropriately (usually "Work").

Carl Wolz
This Posting is provided "AS IS" with no warranties, and confers no rights."

"Heikki Pesonen" <heikki....@pp5.inet.fi> wrote in message

news:OcK02UfL...@TK2MSFTNGP11.phx.gbl...

[Victor F]

Hi sorry if I'm jumping into this thread but I have similar problem
that usually ends up with error INTERNET_152.

Using both Exchange server activesync when cradled (via Activesync
3.7) and remotely via GPRS I could synchronise with our Ex2003 RC1
front-end server however the results were inconsistent and at times I
couldn't even browse the internet using the Pocket PC when cradled and
via the pass-thru connection.

This morning I took the devices from scratch and did the following for
each (of PPC and SPV) in turn:

1). Deleted existing Activesync 3.7 partnerships on the PC

2). Hard reset the device (a bit of a hammer to crack a nut but at
least it was clean)

3). Set-up a partnership with Activesync 3.7 on the PC and selected
the sync with Exchange Server (for Inbox, Contacts and Calendar) and
locally for Tasks, Avantgo and (Notes PPC only). Previously the
devices had been set-up with a pernership for the PC only, which I
re-configured for the Server activesync on the fly. In hindsight I
think this has attributed to some of the inconsistent results

4). The first sync would initially fail until I set the Pass Through
option on Activesync on the PC to "The Internet". A previous post
mentions setting this to Work but I don't understand how the two
differ apart from by the connection setting on the PPC and I don't
understand what it does. Anyway this would sync the device through to
the Exchange frontend servers OK and I could also browse to the
internet or the https oma set-up

5).On uncradling the device I would then perform a remote GPRS sync.
On the first time via GPRS each time the device would sit at the
connecting prompt and in the case of the PPC and SPV I was getting
errors such as: INTERNET_2, DEV_10 and primarily INTERNET_152 . When
failures occured I would browse the internet using IE and try
accessing our https oma set-up to prove connection which always worked
. If I tried to sync again the device would usually then make a
connection to the Server Activesync and all would be well.

6) Upon sucessful GPRS sync above I would then re-cradle the device
being used and allow it to automatically sync. On nearly every single
occassion again, the first time this happened the server activesync
on the device would fail with a DEV_10 error but on subsequent tries
it would work.

I can't figure out what it is that is triggering this effect.

I have proved both internal (re-directed to the external server
interface) and external DNS entries for the Exch 2003 front end server
using NSLOOKUP are correct and through browsing thru the device and
the pass-thru via the PC to the internet that the devices (in the case
of the PPC, SPVs cannot browse the internet on pass through using a
cradle) are seeing the front-end servers correctly. I have also looked
at the Activesync server logs but there is nothing noted there.

Any ideas?

"Carl Wolz [MSFT]" <ca...@online.microsoft.com> wrote in message news:<ubwJ2iuL...@TK2MSFTNGP10.phx.gbl>...

[Carl Wolz [MSFT]]

The desktop setting is a hint to the connection manager on the device on how
to connect to a destination network.
On the device there are at least two networks a)Work b)Internet. If in the
server name there is a "." in it,
it maps to "Internet" (does your server have a dot and is not a FQDN?) So an
example, if the device wants
to connect to a server to work and the only way is through a VPN connection.
The connection manager
knows enough to connect to the internet and VPN in to work. This also works
visa-versa. If your connected
to work(LAN) and you can connect to the internet(WAN) then a proxy will be
used.

I don't think #3 was a issue in any of this.

#5
INTERNET_2 = 12002 ERROR_INTERNET_TIMEOUT "The request has timed out."
INTERNET_152 = 12152 ERROR_HTTP_INVALID_SERVER_RESPONSE "The server

response could not be parsed."

Looks like the server isn't responding is the server on the internet or
intranet?

Carl Wolz
This Posting is provided "AS IS" with no warranties, and confers no rights.

"Victor F" <vfle...@yahoo.co.uk> wrote in message
news:1130fa7a.03061...@posting.google.com...