Re: Exchange Server AS4.1 Error 85010014
- From: "Carl Wolz [MSFT]" <carlw@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 22 Nov 2005 17:22:50 -0800
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.
<junk@xxxxxxxx> wrote in message news:rIpgf.38339$4n5.37028@xxxxxxxxxxxxx
> 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::DeviceThread : 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
>
.
- Follow-Ups:
- Re: Exchange Server AS4.1 Error 85010014
- From: Fredrik Caesar
- Re: Exchange Server AS4.1 Error 85010014
- Prev by Date: Re: SBS 2003 SP1 Exchange 2003 SP2 can't ActiveSync
- Next by Date: Re: AS 4.1 won't recognize any device
- Previous by thread: Re: Exchange Server AS4.1 Error 85010014
- Next by thread: Re: Exchange Server AS4.1 Error 85010014
- Index(es):
Relevant Pages
|
Loading