Exchange Server AS4.1 Error 85010014

Someone from Microsoft - please look and comment

Exchange Server 2003 SP2
Activesync 4.1 - official release
WM5
Certificate installed on the PPC

Credential Authentication must be taking place because when you put in the
WRONG credentials it immediately errors with a bad credentials message. Put
in the correct credentials and you get:.

"Activesync encountered a problem on the SERVER Support Code 85010014"

I've posted before and I see now a few others are coming up on forums with
this problem. NOT an Outlook/85010014 but an Exchange version of the error
and a SLIGHTLY different text in the error dialog - SERVER not DESKTOP.

I've been wading through error logs on the Exchange Server (configured as a
front end) - nothing. But I gleaned this from the error log on the
workstation where ActiveSynch is installed and trying to synch back to the
server.:

11/21/2005 14:13:44.496 p(3440) t(2392) TraceToFile -> ERROR in
CRAPISession::CeRapiUninitInternal : hr = 0x8000ffff - rapisession.cpp(466)
11/21/2005 14:16:55.421 p(3488) t(3028) TraceToFile -> ERROR in
CRAPISession::CeRapiInvokeInternal : hr = 0x80070103 - rapisession.cpp(7145)
11/21/2005 14:16:55.421 p(3488) t(3028) TraceToFile -> ERROR in
CRAPISession::CeRapiInvoke : hr = 0x80070103 - rapisession.cpp(7276)
11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072746 - rapisock.cpp(524)
11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072746 - rapisock.cpp(524)
11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
CRAPISocket::ReceiveBufferSize : hr = 0x80072746 - rapisock.cpp(630)
11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
CByteBuffer::ReceiveFromSocket : hr = 0x80072746 - bytebuf.cpp(314)
11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
CRAPISession::RAPI_EXP_25 : hr = 0x80072746 - rapisession.cpp(10099)
11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
CRAPISocket::ReceiveBuffer : hr = 0x80072746 - rapisock.cpp(690)
11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
CRAPISession::Read : hr = 0x80072746 - rapisession.cpp(10541)
11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
CRAPISocket::WaitForDataToRecv : hr = 0x80072745 - rapisock.cpp(413)
11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072745 - rapisock.cpp(498)
11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
CRAPISocket::ReceiveBuffer : hr = 0x80072745 - rapisock.cpp(690)
11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
CRAPIPacket::ReadPacket : hr = 0x80072745 - rapiconnection.cpp(620)
11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
CRAPIDevicePrivate::HandlePackets : hr = 0x80072745 -
RAPIDevicePriv.cpp(443)
11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
CRAPIDevicePrivate:eviceThread : hr = 0x80072745 - RAPIDevicePriv.cpp(663)
11/21/2005 14:17:59.624 p(3488) t(3844) TraceToFile -> ERROR in
CRAPISession::CeRapiInvokeInternal : hr = 0x80070103 - rapisession.cpp(7145)
11/21/2005 14:17:59.624 p(3488) t(3844) TraceToFile -> ERROR in
CRAPISession::CeRapiInvoke : hr = 0x80070103 - rapisession.cpp(7276)

There is little in the KB on these error codes - and what there is doesn't
relate to AS - anyone got any ideas?

TIA

I have absolutely no inkling of a solution for this problem, but I have
to say, the session descriptors in your error log do speak volumes about
the situation. <ROTFLMAO>

As to the error codes, we are trying to pry some loose, but it was
mentioned somewhere that sql error codes could be used in a high
percentage of the numeric codes. (I could be totally wrong on this, so
approach is as research rather than a solution path)

Beverly Howard [MS MVP-Mobile Devices]

On Mon, 21 Nov 2005 15:01:58 -0500, <> wrote:

>Someone from Microsoft - please look and comment
>
>Exchange Server 2003 SP2
>Activesync 4.1 - official release
>WM5
>Certificate installed on the PPC
>
>Credential Authentication must be taking place because when you put in the
>WRONG credentials it immediately errors with a bad credentials message. Put
>in the correct credentials and you get:.
>
>"Activesync encountered a problem on the SERVER Support Code 85010014"
>
>I've posted before and I see now a few others are coming up on forums with
>this problem. NOT an Outlook/85010014 but an Exchange version of the error
>and a SLIGHTLY different text in the error dialog - SERVER not DESKTOP.

Can you try deleting the server from the device, then readd it and see
if it helps any?

--
Rob Borek
Microsoft MVP - Mobile Devices
Want *ONE ON ONE* support? http://www.pocketpcone2one.com
Please place all replies into the newsgroup so that others can benefit.

I guess I should have been a little more specific in my original post.

Have also:

Recreated Partnership - numerous times when trying other things.

Recreated Server on Device - numerous times

Tried a totally different "vanilla" test workstation running XP SP2 fully
patched and not a lot else and put in AS4.1 and synched back to the server.
Same error - so it is probably something server side - I just can't find
it..

Tried a "vanilla" Exchange Server used for testing. SBS 2003 fully patched
and updated. With a "vanilla" client. Same problem.

These vanilla machines are test non-production machines that are kept in a
"latest patch" state and used for compatibilitiy testing before we deploy
software in the production environment. Basically we ghost the drives
before trying something and then ghost them back to original state ready for
the next test.

A synch from client to desktop copy of Outlook works just fine. So it is a
workaround but the lack of live email from the Exchange Server is a total
pain and is really supposed to be the point of this exercise.

BTW - Real name is Graeme - the address is an anti-spam measure.





"Rob Borek [MS MVP]" <> wrote in message
news:...
> On Mon, 21 Nov 2005 15:01:58 -0500, <> wrote:
>
>>Someone from Microsoft - please look and comment
>>
>>Exchange Server 2003 SP2
>>Activesync 4.1 - official release
>>WM5
>>Certificate installed on the PPC
>>
>>Credential Authentication must be taking place because when you put in the
>>WRONG credentials it immediately errors with a bad credentials message.
>>Put
>>in the correct credentials and you get:.
>>
>>"Activesync encountered a problem on the SERVER Support Code 85010014"
>>
>>I've posted before and I see now a few others are coming up on forums with
>>this problem. NOT an Outlook/85010014 but an Exchange version of the
>>error
>>and a SLIGHTLY different text in the error dialog - SERVER not DESKTOP.
>
> Can you try deleting the server from the device, then readd it and see
> if it helps any?
>
> --
> Rob Borek
> Microsoft MVP - Mobile Devices
> Want *ONE ON ONE* support? http://www.pocketpcone2one.com
> Please place all replies into the newsgroup so that others can benefit.

Hi,

I'm unfortunately not offering any help, but rather posting looking for
assistance with same problems. Brand new install Dell Axim X51v, WM5 and 4.0
of ActiveSync. Same issues with being able to sync with Outlook no problem
at all, but "Activesync encountered a problem on the SERVER Support Code
85010014" error is all I am getting. Checked event logs on both Exchange
Server (2003, sp1) and workstation (XP, SP2) and nothing in those.

Mike

"" wrote:

> I guess I should have been a little more specific in my original post.
>
> Have also:
>
> Recreated Partnership - numerous times when trying other things.
>
> Recreated Server on Device - numerous times
>
> Tried a totally different "vanilla" test workstation running XP SP2 fully
> patched and not a lot else and put in AS4.1 and synched back to the server.
> Same error - so it is probably something server side - I just can't find
> it..
>
> Tried a "vanilla" Exchange Server used for testing. SBS 2003 fully patched
> and updated. With a "vanilla" client. Same problem.
>
> These vanilla machines are test non-production machines that are kept in a
> "latest patch" state and used for compatibilitiy testing before we deploy
> software in the production environment. Basically we ghost the drives
> before trying something and then ghost them back to original state ready for
> the next test.
>
> A synch from client to desktop copy of Outlook works just fine. So it is a
> workaround but the lack of live email from the Exchange Server is a total
> pain and is really supposed to be the point of this exercise.
>
> BTW - Real name is Graeme - the address is an anti-spam measure.
>
>
>
>
>
> "Rob Borek [MS MVP]" <> wrote in message
> news:...
> > On Mon, 21 Nov 2005 15:01:58 -0500, <> wrote:
> >
> >>Someone from Microsoft - please look and comment
> >>
> >>Exchange Server 2003 SP2
> >>Activesync 4.1 - official release
> >>WM5
> >>Certificate installed on the PPC
> >>
> >>Credential Authentication must be taking place because when you put in the
> >>WRONG credentials it immediately errors with a bad credentials message.
> >>Put
> >>in the correct credentials and you get:.
> >>
> >>"Activesync encountered a problem on the SERVER Support Code 85010014"
> >>
> >>I've posted before and I see now a few others are coming up on forums with
> >>this problem. NOT an Outlook/85010014 but an Exchange version of the
> >>error
> >>and a SLIGHTLY different text in the error dialog - SERVER not DESKTOP.
> >
> > Can you try deleting the server from the device, then readd it and see
> > if it helps any?
> >
> > --
> > Rob Borek
> > Microsoft MVP - Mobile Devices
> > Want *ONE ON ONE* support? http://www.pocketpcone2one.com
> > Please place all replies into the newsgroup so that others can benefit.
>
>
>

Sorry, I left out that I was getting that error when trying to sync with my
Exchange server. Read elsewhere that the server must be external fqdn, so
that's what I'm using. I know the server resolves and is accessible. Able
to access internet with Axim as well.

"BlueGreenOrange" wrote:

> Hi,
>
> I'm unfortunately not offering any help, but rather posting looking for
> assistance with same problems. Brand new install Dell Axim X51v, WM5 and 4.0
> of ActiveSync. Same issues with being able to sync with Outlook no problem
> at all, but "Activesync encountered a problem on the SERVER Support Code
> 85010014" error is all I am getting. Checked event logs on both Exchange
> Server (2003, sp1) and workstation (XP, SP2) and nothing in those.
>
> Mike
>
> "" wrote:
>
> > I guess I should have been a little more specific in my original post.
> >
> > Have also:
> >
> > Recreated Partnership - numerous times when trying other things.
> >
> > Recreated Server on Device - numerous times
> >
> > Tried a totally different "vanilla" test workstation running XP SP2 fully
> > patched and not a lot else and put in AS4.1 and synched back to the server.
> > Same error - so it is probably something server side - I just can't find
> > it..
> >
> > Tried a "vanilla" Exchange Server used for testing. SBS 2003 fully patched
> > and updated. With a "vanilla" client. Same problem.
> >
> > These vanilla machines are test non-production machines that are kept in a
> > "latest patch" state and used for compatibilitiy testing before we deploy
> > software in the production environment. Basically we ghost the drives
> > before trying something and then ghost them back to original state ready for
> > the next test.
> >
> > A synch from client to desktop copy of Outlook works just fine. So it is a
> > workaround but the lack of live email from the Exchange Server is a total
> > pain and is really supposed to be the point of this exercise.
> >
> > BTW - Real name is Graeme - the address is an anti-spam measure.
> >
> >
> >
> >
> >
> > "Rob Borek [MS MVP]" <> wrote in message
> > news:...
> > > On Mon, 21 Nov 2005 15:01:58 -0500, <> wrote:
> > >
> > >>Someone from Microsoft - please look and comment
> > >>
> > >>Exchange Server 2003 SP2
> > >>Activesync 4.1 - official release
> > >>WM5
> > >>Certificate installed on the PPC
> > >>
> > >>Credential Authentication must be taking place because when you put in the
> > >>WRONG credentials it immediately errors with a bad credentials message.
> > >>Put
> > >>in the correct credentials and you get:.
> > >>
> > >>"Activesync encountered a problem on the SERVER Support Code 85010014"
> > >>
> > >>I've posted before and I see now a few others are coming up on forums with
> > >>this problem. NOT an Outlook/85010014 but an Exchange version of the
> > >>error
> > >>and a SLIGHTLY different text in the error dialog - SERVER not DESKTOP.
> > >
> > > Can you try deleting the server from the device, then readd it and see
> > > if it helps any?
> > >
> > > --
> > > Rob Borek
> > > Microsoft MVP - Mobile Devices
> > > Want *ONE ON ONE* support? http://www.pocketpcone2one.com
> > > Please place all replies into the newsgroup so that others can benefit.
> >
> >
> >

The error code indicates that there was a error on the Exchange Server
Front-end. I would concentrate your effort there.



The error codes below are winsock error codes coming from RAPI, and happen
when one side closes there socket. This is normal and doesn't affect
Exchange Server Sync.



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



<> wrote in message news:rIpgf.38339$4n5.37028@dukeread01...
> Someone from Microsoft - please look and comment
>
> Exchange Server 2003 SP2
> Activesync 4.1 - official release
> WM5
> Certificate installed on the PPC
>
> Credential Authentication must be taking place because when you put in the
> WRONG credentials it immediately errors with a bad credentials message.
> Put in the correct credentials and you get:.
>
> "Activesync encountered a problem on the SERVER Support Code 85010014"
>
> I've posted before and I see now a few others are coming up on forums with
> this problem. NOT an Outlook/85010014 but an Exchange version of the
> error and a SLIGHTLY different text in the error dialog - SERVER not
> DESKTOP.
>
> I've been wading through error logs on the Exchange Server (configured as
> a front end) - nothing. But I gleaned this from the error log on the
> workstation where ActiveSynch is installed and trying to synch back to the
> server.:
>
> 11/21/2005 14:13:44.496 p(3440) t(2392) TraceToFile -> ERROR in
> CRAPISession::CeRapiUninitInternal : hr = 0x8000ffff -
> rapisession.cpp(466)
> 11/21/2005 14:16:55.421 p(3488) t(3028) TraceToFile -> ERROR in
> CRAPISession::CeRapiInvokeInternal : hr = 0x80070103 -
> rapisession.cpp(7145)
> 11/21/2005 14:16:55.421 p(3488) t(3028) TraceToFile -> ERROR in
> CRAPISession::CeRapiInvoke : hr = 0x80070103 - rapisession.cpp(7276)
> 11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
> CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072746 - rapisock.cpp(524)
> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
> CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072746 - rapisock.cpp(524)
> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
> CRAPISocket::ReceiveBufferSize : hr = 0x80072746 - rapisock.cpp(630)
> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
> CByteBuffer::ReceiveFromSocket : hr = 0x80072746 - bytebuf.cpp(314)
> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
> CRAPISession::RAPI_EXP_25 : hr = 0x80072746 - rapisession.cpp(10099)
> 11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
> CRAPISocket::ReceiveBuffer : hr = 0x80072746 - rapisock.cpp(690)
> 11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
> CRAPISession::Read : hr = 0x80072746 - rapisession.cpp(10541)
> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
> CRAPISocket::WaitForDataToRecv : hr = 0x80072745 - rapisock.cpp(413)
> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
> CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072745 - rapisock.cpp(498)
> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
> CRAPISocket::ReceiveBuffer : hr = 0x80072745 - rapisock.cpp(690)
> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
> CRAPIPacket::ReadPacket : hr = 0x80072745 - rapiconnection.cpp(620)
> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
> CRAPIDevicePrivate::HandlePackets : hr = 0x80072745 -
> RAPIDevicePriv.cpp(443)
> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
> CRAPIDevicePrivate:eviceThread : hr = 0x80072745 -
> RAPIDevicePriv.cpp(663)
> 11/21/2005 14:17:59.624 p(3488) t(3844) TraceToFile -> ERROR in
> CRAPISession::CeRapiInvokeInternal : hr = 0x80070103 -
> rapisession.cpp(7145)
> 11/21/2005 14:17:59.624 p(3488) t(3844) TraceToFile -> ERROR in
> CRAPISession::CeRapiInvoke : hr = 0x80070103 - rapisession.cpp(7276)
>
> There is little in the KB on these error codes - and what there is doesn't
> relate to AS - anyone got any ideas?
>
> TIA
>

But please, have you at all read the posts in this forum? ActiveSync 4 is a
REAL PROBLEM for Microsoft. Everyone are having problems! I can't get it to
work either, even in an isolated test environment.

You MUST act on this, or people will loose al confidence in your products. I
have never EVER seen so many problems concentrated to one single product in
so little time

Please. How can we get help? Who should we call?

Just my .05...

"Carl Wolz [MSFT]" <> wrote in message
news:%...
> The error code indicates that there was a error on the Exchange Server
> Front-end. I would concentrate your effort there.
>
>
>
> The error codes below are winsock error codes coming from RAPI, and happen
> when one side closes there socket. This is normal and doesn't affect
> Exchange Server Sync.
>
>
>
> --
> Carl Wolz [MSFT]
> This Posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
>
> <> wrote in message news:rIpgf.38339$4n5.37028@dukeread01...
>> Someone from Microsoft - please look and comment
>>
>> Exchange Server 2003 SP2
>> Activesync 4.1 - official release
>> WM5
>> Certificate installed on the PPC
>>
>> Credential Authentication must be taking place because when you put in
>> the WRONG credentials it immediately errors with a bad credentials
>> message. Put in the correct credentials and you get:.
>>
>> "Activesync encountered a problem on the SERVER Support Code 85010014"
>>
>> I've posted before and I see now a few others are coming up on forums
>> with this problem. NOT an Outlook/85010014 but an Exchange version of
>> the error and a SLIGHTLY different text in the error dialog - SERVER not
>> DESKTOP.
>>
>> I've been wading through error logs on the Exchange Server (configured as
>> a front end) - nothing. But I gleaned this from the error log on the
>> workstation where ActiveSynch is installed and trying to synch back to
>> the server.:
>>
>> 11/21/2005 14:13:44.496 p(3440) t(2392) TraceToFile -> ERROR in
>> CRAPISession::CeRapiUninitInternal : hr = 0x8000ffff -
>> rapisession.cpp(466)
>> 11/21/2005 14:16:55.421 p(3488) t(3028) TraceToFile -> ERROR in
>> CRAPISession::CeRapiInvokeInternal : hr = 0x80070103 -
>> rapisession.cpp(7145)
>> 11/21/2005 14:16:55.421 p(3488) t(3028) TraceToFile -> ERROR in
>> CRAPISession::CeRapiInvoke : hr = 0x80070103 - rapisession.cpp(7276)
>> 11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
>> CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072746 - rapisock.cpp(524)
>> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
>> CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072746 - rapisock.cpp(524)
>> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
>> CRAPISocket::ReceiveBufferSize : hr = 0x80072746 - rapisock.cpp(630)
>> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
>> CByteBuffer::ReceiveFromSocket : hr = 0x80072746 - bytebuf.cpp(314)
>> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
>> CRAPISession::RAPI_EXP_25 : hr = 0x80072746 - rapisession.cpp(10099)
>> 11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
>> CRAPISocket::ReceiveBuffer : hr = 0x80072746 - rapisock.cpp(690)
>> 11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
>> CRAPISession::Read : hr = 0x80072746 - rapisession.cpp(10541)
>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>> CRAPISocket::WaitForDataToRecv : hr = 0x80072745 - rapisock.cpp(413)
>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>> CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072745 - rapisock.cpp(498)
>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>> CRAPISocket::ReceiveBuffer : hr = 0x80072745 - rapisock.cpp(690)
>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>> CRAPIPacket::ReadPacket : hr = 0x80072745 - rapiconnection.cpp(620)
>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>> CRAPIDevicePrivate::HandlePackets : hr = 0x80072745 -
>> RAPIDevicePriv.cpp(443)
>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>> CRAPIDevicePrivate:eviceThread : hr = 0x80072745 -
>> RAPIDevicePriv.cpp(663)
>> 11/21/2005 14:17:59.624 p(3488) t(3844) TraceToFile -> ERROR in
>> CRAPISession::CeRapiInvokeInternal : hr = 0x80070103 -
>> rapisession.cpp(7145)
>> 11/21/2005 14:17:59.624 p(3488) t(3844) TraceToFile -> ERROR in
>> CRAPISession::CeRapiInvoke : hr = 0x80070103 - rapisession.cpp(7276)
>>
>> There is little in the KB on these error codes - and what there is
>> doesn't relate to AS - anyone got any ideas?
>>
>> TIA
>>
>
>

Everyone? Please provide proof of such a broad statement.

I'll start it by saying I had no problems using it.




"Fredrik Caesar" <fredrik AT caesar DOT dyns DOT net> wrote in message
news:...
> But please, have you at all read the posts in this forum? ActiveSync 4 is
> a REAL PROBLEM for Microsoft. Everyone are having problems! I can't get it
> to work either, even in an isolated test environment.
>
> You MUST act on this, or people will loose al confidence in your products.
> I have never EVER seen so many problems concentrated to one single product
> in so little time
>
> Please. How can we get help? Who should we call?
>
> Just my .05...
>
> "Carl Wolz [MSFT]" <> wrote in message
> news:%...
>> The error code indicates that there was a error on the Exchange Server
>> Front-end. I would concentrate your effort there.
>>
>>
>>
>> The error codes below are winsock error codes coming from RAPI, and
>> happen when one side closes there socket. This is normal and doesn't
>> affect Exchange Server Sync.
>>
>>
>>
>> --
>> Carl Wolz [MSFT]
>> This Posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>>
>> <> wrote in message news:rIpgf.38339$4n5.37028@dukeread01...
>>> Someone from Microsoft - please look and comment
>>>
>>> Exchange Server 2003 SP2
>>> Activesync 4.1 - official release
>>> WM5
>>> Certificate installed on the PPC
>>>
>>> Credential Authentication must be taking place because when you put in
>>> the WRONG credentials it immediately errors with a bad credentials
>>> message. Put in the correct credentials and you get:.
>>>
>>> "Activesync encountered a problem on the SERVER Support Code 85010014"
>>>
>>> I've posted before and I see now a few others are coming up on forums
>>> with this problem. NOT an Outlook/85010014 but an Exchange version of
>>> the error and a SLIGHTLY different text in the error dialog - SERVER not
>>> DESKTOP.
>>>
>>> I've been wading through error logs on the Exchange Server (configured
>>> as a front end) - nothing. But I gleaned this from the error log on the
>>> workstation where ActiveSynch is installed and trying to synch back to
>>> the server.:
>>>
>>> 11/21/2005 14:13:44.496 p(3440) t(2392) TraceToFile -> ERROR in
>>> CRAPISession::CeRapiUninitInternal : hr = 0x8000ffff -
>>> rapisession.cpp(466)
>>> 11/21/2005 14:16:55.421 p(3488) t(3028) TraceToFile -> ERROR in
>>> CRAPISession::CeRapiInvokeInternal : hr = 0x80070103 -
>>> rapisession.cpp(7145)
>>> 11/21/2005 14:16:55.421 p(3488) t(3028) TraceToFile -> ERROR in
>>> CRAPISession::CeRapiInvoke : hr = 0x80070103 - rapisession.cpp(7276)
>>> 11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
>>> CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072746 -
>>> rapisock.cpp(524)
>>> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
>>> CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072746 -
>>> rapisock.cpp(524)
>>> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
>>> CRAPISocket::ReceiveBufferSize : hr = 0x80072746 - rapisock.cpp(630)
>>> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
>>> CByteBuffer::ReceiveFromSocket : hr = 0x80072746 - bytebuf.cpp(314)
>>> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
>>> CRAPISession::RAPI_EXP_25 : hr = 0x80072746 - rapisession.cpp(10099)
>>> 11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
>>> CRAPISocket::ReceiveBuffer : hr = 0x80072746 - rapisock.cpp(690)
>>> 11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
>>> CRAPISession::Read : hr = 0x80072746 - rapisession.cpp(10541)
>>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>>> CRAPISocket::WaitForDataToRecv : hr = 0x80072745 - rapisock.cpp(413)
>>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>>> CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072745 -
>>> rapisock.cpp(498)
>>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>>> CRAPISocket::ReceiveBuffer : hr = 0x80072745 - rapisock.cpp(690)
>>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>>> CRAPIPacket::ReadPacket : hr = 0x80072745 - rapiconnection.cpp(620)
>>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>>> CRAPIDevicePrivate::HandlePackets : hr = 0x80072745 -
>>> RAPIDevicePriv.cpp(443)
>>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>>> CRAPIDevicePrivate:eviceThread : hr = 0x80072745 -
>>> RAPIDevicePriv.cpp(663)
>>> 11/21/2005 14:17:59.624 p(3488) t(3844) TraceToFile -> ERROR in
>>> CRAPISession::CeRapiInvokeInternal : hr = 0x80070103 -
>>> rapisession.cpp(7145)
>>> 11/21/2005 14:17:59.624 p(3488) t(3844) TraceToFile -> ERROR in
>>> CRAPISession::CeRapiInvoke : hr = 0x80070103 - rapisession.cpp(7276)
>>>
>>> There is little in the KB on these error codes - and what there is
>>> doesn't relate to AS - anyone got any ideas?
>>>
>>> TIA
>>>
>>
>>
>
>

Alan,

I'm not out to get in a p*ssing match over the word "everyone"

But I would tend to agree with Fredrick that Activesync 4 is significantly
worse in terms of introductory problems than many pieces of software. There
are many other fora (to be strictly correct about the plural of "forum")
that have a significant number of issues with this software getting
discussed.

If we can't even get it to work in a pretty vanilla test environment then
"summat's up" - though I agree not with "everyone"

Graeme



"Alan" <> wrote in message
news:dm5cs9$s62$...
> Everyone? Please provide proof of such a broad statement.
>
> I'll start it by saying I had no problems using it.
>
>
>
>
> "Fredrik Caesar" <fredrik AT caesar DOT dyns DOT net> wrote in message
> news:...
>> But please, have you at all read the posts in this forum? ActiveSync 4 is
>> a REAL PROBLEM for Microsoft. Everyone are having problems! I can't get
>> it to work either, even in an isolated test environment.
>>
>> You MUST act on this, or people will loose al confidence in your
>> products. I have never EVER seen so many problems concentrated to one
>> single product in so little time
>>
>> Please. How can we get help? Who should we call?
>>
>> Just my .05...
>>
>> "Carl Wolz [MSFT]" <> wrote in message
>> news:%...
>>> The error code indicates that there was a error on the Exchange Server
>>> Front-end. I would concentrate your effort there.
>>>
>>>
>>>
>>> The error codes below are winsock error codes coming from RAPI, and
>>> happen when one side closes there socket. This is normal and doesn't
>>> affect Exchange Server Sync.
>>>
>>>
>>>
>>> --
>>> Carl Wolz [MSFT]
>>> This Posting is provided "AS IS" with no warranties, and confers no
>>> rights.
>>>
>>>
>>>
>>> <> wrote in message
>>> news:rIpgf.38339$4n5.37028@dukeread01...
>>>> Someone from Microsoft - please look and comment
>>>>
>>>> Exchange Server 2003 SP2
>>>> Activesync 4.1 - official release
>>>> WM5
>>>> Certificate installed on the PPC
>>>>
>>>> Credential Authentication must be taking place because when you put in
>>>> the WRONG credentials it immediately errors with a bad credentials
>>>> message. Put in the correct credentials and you get:.
>>>>
>>>> "Activesync encountered a problem on the SERVER Support Code 85010014"
>>>>
>>>> I've posted before and I see now a few others are coming up on forums
>>>> with this problem. NOT an Outlook/85010014 but an Exchange version of
>>>> the error and a SLIGHTLY different text in the error dialog - SERVER
>>>> not DESKTOP.
>>>>
>>>> I've been wading through error logs on the Exchange Server (configured
>>>> as a front end) - nothing. But I gleaned this from the error log on
>>>> the workstation where ActiveSynch is installed and trying to synch back
>>>> to the server.:
>>>>
>>>> 11/21/2005 14:13:44.496 p(3440) t(2392) TraceToFile -> ERROR in
>>>> CRAPISession::CeRapiUninitInternal : hr = 0x8000ffff -
>>>> rapisession.cpp(466)
>>>> 11/21/2005 14:16:55.421 p(3488) t(3028) TraceToFile -> ERROR in
>>>> CRAPISession::CeRapiInvokeInternal : hr = 0x80070103 -
>>>> rapisession.cpp(7145)
>>>> 11/21/2005 14:16:55.421 p(3488) t(3028) TraceToFile -> ERROR in
>>>> CRAPISession::CeRapiInvoke : hr = 0x80070103 - rapisession.cpp(7276)
>>>> 11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
>>>> CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072746 -
>>>> rapisock.cpp(524)
>>>> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
>>>> CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072746 -
>>>> rapisock.cpp(524)
>>>> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
>>>> CRAPISocket::ReceiveBufferSize : hr = 0x80072746 - rapisock.cpp(630)
>>>> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
>>>> CByteBuffer::ReceiveFromSocket : hr = 0x80072746 - bytebuf.cpp(314)
>>>> 11/21/2005 14:17:15.968 p(3440) t(3820) TraceToFile -> ERROR in
>>>> CRAPISession::RAPI_EXP_25 : hr = 0x80072746 - rapisession.cpp(10099)
>>>> 11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
>>>> CRAPISocket::ReceiveBuffer : hr = 0x80072746 - rapisock.cpp(690)
>>>> 11/21/2005 14:17:15.968 p(3488) t(3220) TraceToFile -> ERROR in
>>>> CRAPISession::Read : hr = 0x80072746 - rapisession.cpp(10541)
>>>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>>>> CRAPISocket::WaitForDataToRecv : hr = 0x80072745 - rapisock.cpp(413)
>>>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>>>> CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072745 -
>>>> rapisock.cpp(498)
>>>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>>>> CRAPISocket::ReceiveBuffer : hr = 0x80072745 - rapisock.cpp(690)
>>>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>>>> CRAPIPacket::ReadPacket : hr = 0x80072745 - rapiconnection.cpp(620)
>>>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>>>> CRAPIDevicePrivate::HandlePackets : hr = 0x80072745 -
>>>> RAPIDevicePriv.cpp(443)
>>>> 11/21/2005 14:17:15.968 p(1996) t(576) TraceToFile -> ERROR in
>>>> CRAPIDevicePrivate:eviceThread : hr = 0x80072745 -
>>>> RAPIDevicePriv.cpp(663)
>>>> 11/21/2005 14:17:59.624 p(3488) t(3844) TraceToFile -> ERROR in
>>>> CRAPISession::CeRapiInvokeInternal : hr = 0x80070103 -
>>>> rapisession.cpp(7145)
>>>> 11/21/2005 14:17:59.624 p(3488) t(3844) TraceToFile -> ERROR in
>>>> CRAPISession::CeRapiInvoke : hr = 0x80070103 - rapisession.cpp(7276)
>>>>
>>>> There is little in the KB on these error codes - and what there is
>>>> doesn't relate to AS - anyone got any ideas?
>>>>
>>>> TIA
>>>>
>>>
>>>
>>
>>
>
>