Re: My Logs (Was: Re: Three Weeks and Counting...No Sync)

You could try sending those logs to astell <at> microsoft <dot> com.
Nothing just jumps out at me except the socket error, which is WSAEShutdown,
which could, conceivably indicate that some network routing/blocking service
on the PC is sending AS packets either into a black hole or off onto the
wrong network.

Paul T.

"Keith Russell" <5hub-> wrote in message
news:...
> FWIW, here are the logs from my last two sessions.
>
> The first time, I didn't get the usual error message. ActiveSync
> simply said it was connected and stayed that way--but it wasn't
> actually connected.
>
> The second time, it behaved in the usual way and gave me the
> "Synchronization cannot be completed" error.
>
> =============================================
> WCESCOMM.LOG:
> 07/27/2006 23:51:34.015 - Windows CE Services (4.2.0)
> Communication Logging.
> 07/27/2006 23:51:34.015 - IrUtil: IrDA socket cannot be created,
> error code 10093.
> 07/27/2006 23:51:34.031 - Windows CE Services Communication
> started.
> 07/27/2006 23:51:38.281 - Started desktop passthru TCP2UDP
> component
> 07/27/2006 23:51:38.281 - Connection: Prep for a new socket
> connection.
> 07/27/2006 23:53:56.046 - USB: RNDIS device id
> \\?\USB#Vid_413c&Pid_4011#050d1d20-0602-1113-7800-0050bfe45ce5#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
> 07/27/2006 23:53:56.187 - USB: found RNDIS device id
> USB\Vid_413c&Pid_4011&Rev_0000
> 07/27/2006 23:54:11.406 - USB RNDIS: Device Arrival notification
> 07/28/2006 00:45:17.406 - USB RNDIS: Device Removal notification
> 07/28/2006 00:45:17.750 - USB: RNDIS device id
> \\?\USB#Vid_413c&Pid_4011#050d1d20-0602-1113-7800-0050bfe45ce5#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
> 07/28/2006 00:45:18.093 - USB: found RNDIS device id
> USB\Vid_413c&Pid_4011&Rev_0000
> 07/28/2006 00:45:28.468 - USB: RNDIS device id
> \\?\USB#Vid_413c&Pid_4011#050d1d20-0602-1113-7800-0050bfe45ce5#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
> 07/28/2006 00:45:28.500 - USB: found RNDIS device id
> USB\Vid_413c&Pid_4011&Rev_0000
> 07/28/2006 00:45:36.843 - USB RNDIS: Device Arrival notification
>
>
> ===========================================
> WCESMgr.log
> 07/27/2006 23:54:13.750 **************** Logging Started
> ****************
> 07/27/2006 23:54:13.750 Process C:\Program Files\Microsoft
> ActiveSync\WCESMgr.exe p(3712)
> 07/27/2006 23:54:13.750
> **** ActiveSync (4.2.4876 RETAIL) started, Cmd line: '/onconnect'
> 07/28/2006 00:45:17.765 ERROR: returned 0x8014503B
> 07/28/2006 00:45:17.765 CCeConnect::Connect Failed with Error
> 0x80145110
> 07/28/2006 00:45:17.765 ERROR returned in function
> CCeConnect::Connect. hr: 0x80145110
> 07/28/2006 00:45:37.671 Checking existing partnership on device
> 0x78C459BB.
> 07/28/2006 00:45:38.171 **************** Logging Started
> ****************
> 07/28/2006 00:45:38.171 Process C:\Program Files\Microsoft
> ActiveSync\WCESMgr.exe p(920)
> 07/28/2006 00:45:38.171 ActiveSync second instance started, Cmd
> line: '/onconnect'
> 07/28/2006 00:45:38.171 ActiveSync second instance exiting
> 07/28/2006 00:45:38.171 **************** Logging Stopped
> ****************
> 07/28/2006 00:45:37.671 DTPT: Setting DTPT network to
> {ADB0B001-10B5-3F39-27C6-9742E785FCD4}
> 07/28/2006 00:45:38.734 DTPT: Send DTPT
> Network={ADB0B001-10B5-3F39-27C6-9742E785FCD4}. Result=0x00000000
> 07/28/2006 00:45:44.281 *** Http listener loaded
> 07/28/2006 00:45:44.281 Connected to device 0x78C459BB (PocketPC,
> MiniMe) [partner 0]
> 07/28/2006 00:45:44.281 **** Starting synchronization engine
> 07/28/2006 00:50:44.593 ERROR: Connection to ActiveSync on the
> device failed. Error: 0x80145001 Socket Error: 0x274A
> 07/28/2006 00:50:44.593 ERROR returned in function
> CCeComm::Connect. hr: 0x80145001
> 07/28/2006 00:50:44.593 ERROR: returned 0x80145001
> 07/28/2006 00:50:44.593 ERROR returned in function
> CCeSync::ConnectThrd. hr: 0x80145001
> 07/28/2006 00:50:44.593 ERROR: returned 0x8014503A
> 07/28/2006 00:51:38.109 p(3712) t(2664) AirSyncStatusXML ->
> Process XML: <SyncBegin Partner="" Datatype=""/> -
> ASStatus.cpp(617)
> 07/28/2006 00:51:38.109 p(3712) t(2664) AirSyncStatusXML ->
> Process XML: <SyncBegin
> Partner="{66C04E4A-0FFF-4E67-B908-7E76728B49A6}" Datatype=""/> -
> ASStatus.cpp(617)
> 07/28/2006 00:51:38.109 p(3712) t(2664) AirSyncStatusXML ->
> Process XML: <SyncEnd
> Partner="{66C04E4A-0FFF-4E67-B908-7E76728B49A6}" Datatype=""/> -
> ASStatus.cpp(617)
> 07/28/2006 00:51:38.109 p(3712) t(2664) AirSyncStatusXML ->
> Process XML: <SyncEnd Partner="" Datatype=""/> -
> ASStatus.cpp(617)
> 07/28/2006 00:57:38.656 p(3712) t(2664) AirSyncStatusXML ->
> Process XML: <SyncBegin Partner="" Datatype=""/> -
> ASStatus.cpp(617)
> 07/28/2006 00:57:38.656 p(3712) t(2664) AirSyncStatusXML ->
> Process XML: <SyncBegin
> Partner="{66C04E4A-0FFF-4E67-B908-7E76728B49A6}" Datatype=""/> -
> ASStatus.cpp(617)
> 07/28/2006 00:57:38.656 p(3712) t(2664) AirSyncStatusXML ->
> Process XML: <SyncEnd
> Partner="{66C04E4A-0FFF-4E67-B908-7E76728B49A6}" Datatype=""/> -
> ASStatus.cpp(617)
> 07/28/2006 00:57:40.343 p(3712) t(2664) AirSyncStatusXML ->
> Process XML: <SyncEnd Partner="" Datatype=""/> -
> ASStatus.cpp(617)
>
> ==================================
> WCESLog.log
> 07/27/2006 23:54:14.390 **************** Logging Started
> ****************
> 07/27/2006 23:54:14.390 Process C:\Program Files\Microsoft
> ActiveSync\WCESMgr.exe p(3712)
> 07/27/2006 23:54:17.218 **************** Logging Started
> ****************
> 07/27/2006 23:54:17.218 Process F:\PPC\dotPocket\dpDesktop.exe
> p(3756)
> 07/28/2006 00:12:12.281 **************** Logging Started
> ****************
> 07/28/2006 00:12:12.281 Process F:\PPC\dotPocket\dpDesktop.exe
> p(2576)
> 07/28/2006 00:42:38.500 **************** Logging Started
> ****************
> 07/28/2006 00:42:38.500 Process C:\WINDOWS\explorer.exe p(3940)
> 07/28/2006 00:42:50.171 **************** Logging Started
> ****************
> 07/28/2006 00:42:50.171 Process C:\Program Files\Microsoft
> ActiveSync\CEAppMgr.exe p(3360)
> 07/28/2006 00:45:17.359 p(3392) t(1616) TraceToFile -> ERROR in
> CRAPISocket::WaitForDataToRecv : hr = 0x80072745 -
> rapisock.cpp(413)
> 07/28/2006 00:45:17.359 p(3392) t(1616) TraceToFile -> ERROR in
> CRAPISocket::ReceiveBufferNoDecrypt : hr = 0x80072745 -
> rapisock.cpp(498)
> 07/28/2006 00:45:17.359 p(3392) t(1616) TraceToFile -> ERROR in
> CRAPISocket::ReceiveBuffer : hr = 0x80072745 - rapisock.cpp(690)
> 07/28/2006 00:45:17.359 p(3392) t(1616) TraceToFile -> ERROR in
> CRAPIPacket::ReadPacket : hr = 0x80072745 -
> rapiconnection.cpp(620)
> 07/28/2006 00:45:17.359 p(3392) t(1616) TraceToFile -> ERROR in
> CRAPIDevicePrivate::HandlePackets : hr = 0x80072745 -
> RAPIDevicePriv.cpp(447)
> 07/28/2006 00:45:17.359 p(3392) t(544) TraceToFile -> ERROR in
> CRAPIDevicePrivate::RequestSessionSocketFromDevice : hr =
> 0x800704b1 - RAPIDevicePriv.cpp(1090)
> 07/28/2006 00:45:17.359 p(3392) t(544) TraceToFile -> ERROR in
> CRAPIDevicePrivate::CreateSessionSocket : hr = 0x800704b1 -
> RAPIDevicePriv.cpp(1762)
> 07/28/2006 00:45:17.359 p(3392) t(1616) TraceToFile -> ERROR in
> CRAPIDevicePrivate:eviceThread : hr = 0x80072745 -
> RAPIDevicePriv.cpp(667)
> 07/28/2006 00:45:17.359 p(3392) t(4064) TraceToFile -> ERROR in
> CRAPIDevicePrivate::GetConnectionInfo : hr = 0x80070490 -
> RAPIDevicePriv.cpp(1552)
> 07/28/2006 00:45:17.359 p(3392) t(1580) TraceToFile -> ERROR in
> CRAPISocket::SendBuffer : hr = 0x8000ffff - rapisock.cpp(737)
> 07/28/2006 00:45:17.359 p(3392) t(1580) TraceToFile -> ERROR in
> CRAPIPacket::WritePacket : hr = 0x8000ffff -
> rapiconnection.cpp(697)
> 07/28/2006 00:45:17.359 p(3392) t(1580) TraceToFile -> ERROR in
> CRAPIDevicePrivate::RequestSessionSocketFromDevice : hr =
> 0x8000ffff - RAPIDevicePriv.cpp(1076)
> 07/28/2006 00:45:17.359 p(3392) t(1580) TraceToFile -> ERROR in
> CRAPIDevicePrivate::CreateSessionSocket : hr = 0x8000ffff -
> RAPIDevicePriv.cpp(1762)
> 07/28/2006 00:45:17.625 p(3712) t(3444) TraceToFile -> ERROR in
> CRAPIDevice::CreateSession : hr = 0x800704b1 -
> RAPIDevice.cpp(433)
> 07/28/2006 00:45:17.359 p(3392) t(652) TraceToFile -> ERROR in
> CRAPISocket::SendBuffer : hr = 0x8000ffff - rapisock.cpp(737)
> 07/28/2006 00:45:17.359 p(3392) t(652) TraceToFile -> ERROR in
> CRAPIPacket::WritePacket : hr = 0x8000ffff -
> rapiconnection.cpp(697)
> 07/28/2006 00:45:17.359 p(3392) t(652) TraceToFile -> ERROR in
> CRAPIDevicePrivate::RequestSessionSocketFromDevice : hr =
> 0x8000ffff - RAPIDevicePriv.cpp(1076)
> 07/28/2006 00:45:17.359 p(3392) t(652) TraceToFile -> ERROR in
> CRAPIDevicePrivate::CreateSessionSocket : hr = 0x8000ffff -
> RAPIDevicePriv.cpp(1762)
> 07/28/2006 00:45:17.359 p(3392) t(1216) TraceToFile -> ERROR in
> CRAPISocket::SendBuffer : hr = 0x8000ffff - rapisock.cpp(737)
> 07/28/2006 00:45:17.359 p(3392) t(1216) TraceToFile -> ERROR in
> CRAPIPacket::WritePacket : hr = 0x8000ffff -
> rapiconnection.cpp(697)
> 07/28/2006 00:45:17.359 p(3392) t(1216) TraceToFile -> ERROR in
> CRAPIDevicePrivate::RequestSessionSocketFromDevice : hr =
> 0x8000ffff - RAPIDevicePriv.cpp(1076)
> 07/28/2006 00:45:18.031 p(2576) t(3236) TraceToFile -> ERROR in
> CRAPIDevice::CreateSession : hr = 0x8000ffff -
> RAPIDevice.cpp(433)
> 07/28/2006 00:45:17.359 p(3392) t(1216) TraceToFile -> ERROR in
> CRAPIDevicePrivate::CreateSessionSocket : hr = 0x8000ffff -
> RAPIDevicePriv.cpp(1762)
> 07/28/2006 00:45:17.359 p(3392) t(4020) TraceToFile -> ERROR in
> CRAPISocket::SendBuffer : hr = 0x8000ffff - rapisock.cpp(737)
> 07/28/2006 00:45:17.359 p(3392) t(4020) TraceToFile -> ERROR in
> CRAPIPacket::WritePacket : hr = 0x8000ffff -
> rapiconnection.cpp(697)
> 07/28/2006 00:45:17.359 p(3392) t(4020) TraceToFile -> ERROR in
> CRAPIDevicePrivate::RequestSessionSocketFromDevice : hr =
> 0x8000ffff - RAPIDevicePriv.cpp(1076)
> 07/28/2006 00:45:18.046 p(3940) t(3172) TraceToFile -> ERROR in
> CRAPIDevice::CreateSession : hr = 0x8000ffff -
> RAPIDevice.cpp(433)
> 07/28/2006 00:45:17.359 p(3392) t(4020) TraceToFile -> ERROR in
> CRAPIDevicePrivate::CreateSessionSocket : hr = 0x8000ffff -
> RAPIDevicePriv.cpp(1762)
> 07/28/2006 00:45:18.046 **************** Logging Stopped
> ****************
> 07/28/2006 00:45:43.843 **************** Logging Started
> ****************
> 07/28/2006 00:45:43.843 Process C:\Program Files\Microsoft
> ActiveSync\WCESMgr.exe p(3712)
> 07/28/2006 00:50:59.593 **************** Logging Started
> ****************
> 07/28/2006 00:50:59.593 Process C:\WINDOWS\explorer.exe p(3244)
> 07/28/2006 00:51:07.484 **************** Logging Started
> ****************
> 07/28/2006 00:51:07.484 Process C:\Program Files\Microsoft
> ActiveSync\CEAppMgr.exe p(3912)
> 07/28/2006 00:51:37.734 **************** Logging Started
> ****************
> 07/28/2006 00:51:37.734 Process C:\PROGRAM FILES\MICROSOFT
> ACTIVESYNC\WCESMGR.EXE p(3712)
> 07/28/2006 00:51:46.156 **************** Logging Started
> ****************
> 07/28/2006 00:51:46.156 Process C:\Program Files\Microsoft
> ActiveSync\CEAppMgr.exe p(3900)
>
> ======================================
> WcesView.Log:
> 7/28/2006 12:42:37 AM -
> 7/28/2006 12:42:38 AM -
> 7/28/2006 12:42:38 AM - Entering connect threadproc
> 7/28/2006 12:42:38 AM - OnLogActive
> 7/28/2006 12:42:38 AM - ÀB"
> |ØÀ
> 7/28/2006 12:42:38 AM - |ØÀ
> 7/28/2006 12:44:46 AM -
> 7/28/2006 12:44:46 AM -
> 7/28/2006 12:44:46 AM -
> 7/28/2006 12:45:18 AM - OnLogDisconnection
> 7/28/2006 12:45:18 AM - CConnectThread::ThreadProc() Calling
> CeRapiUninit.
> 7/28/2006 12:45:18 AM - Ç?,ÙÀ
> 7/28/2006 12:45:18 AM -
> 7/28/2006 12:45:18 AM -
> 7/28/2006 12:50:59 AM -
> 7/28/2006 12:50:59 AM -
> 7/28/2006 12:50:59 AM - Entering connect threadproc
> 7/28/2006 12:50:59 AM - OnLogActive
> 7/28/2006 12:50:59 AM - ðC"
> |ØÀ
> 7/28/2006 12:50:59 AM - |ØÀ
> 7/28/2006 12:51:28 AM -
> 7/28/2006 12:51:28 AM -
> 7/28/2006 12:51:28 AM -
>
>
>
> Can someone who understands these better than I tell me what's
> going on here? Thank you VERY much.
> --
> Keith

Yes, that's a means of possibly getting on the to-do list, but it's unlikely
to generate any sort of an immediate fix.

Understandable. You can push from the device OEM end for some sort of
support, but that's about all I can recommend. If it is some network
component causing the problem, you could uninstall everything that could
conceivably be a network component (delete VPN settings, etc.), but you'd
want to have a solid backup.

Paul T.

"Keith Russell" <5hub-> wrote in message
news...
> On Fri, 28 Jul 2006 10:33:54 -0700, "Paul G. Tobey [eMVP]" <p
> space tobey no spam AT no instrument no spam DOT com> wrote:
>
>>You could try sending those logs to astell <at> microsoft <dot> com.
>>Nothing just jumps out at me except the socket error, which is
>>WSAEShutdown,
>>which could, conceivably indicate that some network routing/blocking
>>service
>>on the PC is sending AS packets either into a black hole or off onto the
>>wrong network.
>
> Thanks, Paul. Your message gave me hope. I forwarded the
> information to the astell address, but received an autoresponse
> saying that they review submissions but do not reply. :-(
>
> So I guess I'm back at square one again. My second PC has now
> suffered a horrible death, going from BSODs to displaying nothing
> at all when I boot it now. So I truly do have no way to
> synchronize. I am not happy.
> --
> Keith