Mobility Site - View Single Post - ActiveSync works first time then goes to guest

tgerstner · 04-23-03, 10:28 AM

First I will tell you what the problem is, then I will describe what I have done so far to try to fix it.

The Problem:
I have ActiveSync 3.6 both at home and work. My home computer is Windows XP, work is Windows 95. I initially setup the partnership at home to be "Only One Computer". I have had no problems at home. Now I bought a second cradle and I want to also sync at work. Here lies the problem. When setting up the partnership at work, I selected "Two Computers". The sync works for the first time. When I remove the Axim from the cradle then put it back, ActiveSync thinks it is connected to a Guest Partnership. How do I remove the partnership information from the Axim? I believe it stores it somewhere. When I remove the Axim from the cradle again, ActiveSync changes the description from Guest to my actual device name. This tells me that there is something on the device, but what and where?

What I have done so Far:
I have reinstalled ActiveSync 3.6. Did not fix it
I have changed my device name on Axim. Did not fix it
I have deleted the partnership on the PC. Did not fix it.
I have tried to setup work as the only computer. Did not fix it.
And for the biggie, I have done a Hard Reset. Did not fix it.

I have continued looking into this. Here is a clean log just after I have created the partnership and redocked to the cradle. Does anyone know if this looks okay or not.

************ START OF LOG ****************

2003-04-23 11:48:32 FFF6935F - [Ctrl Recv] [0xF0]: Communication socket error 0, returned 0
2003-04-23 11:48:32 FFF5C98B - [Data Recv] [0xFFFFFFFF]: Communication socket error 10038, returned -1
2003-04-23 11:48:32 FFF5058F - [RemSync Recv] [0xFFFFFFFF]: Communication socket error 10038, returned -1
2003-04-23 11:48:32 FFF68C13 - **** ActiveSync session completed

2003-04-23 11:48:39 FFF68C13 - Checking existing partnership on device 0x2A720E75.
2003-04-23 11:48:39 FFF9EA4B - DTPT: Failed first query to find network. Dest={436EF144-B4FB-4863-A041-8F905A62C572}, HR=0x80070057
2003-04-23 11:48:39 FFF9EA4B - DTPT: FAILED to find source network. Dest={436EF144-B4FB-4863-A041-8F905A62C572} fDeviceSrc=0 HR=0x80070057
2003-04-23 11:48:39 FFF9EA4B - ERROR: g_app.SetupDTPT(g_app.GetDTPTNetworkType()) returned 0x80070057, file: d:\medusa\private\apps\conn\repl\wcesmgr\.\partner .cpp, line 2486
2003-04-23 11:48:39 FFF9EA4B - ERROR returned in function CCeSync::CheckPartner. hr: 0x80070057

************ END OF LOG ****************

At this point in the game, I think Windows 95 may be the problem.
Any help here would be greatly appreciated.

04-23-03, 10:28 AM	#1 (permalink)
tgerstner Aximsite Rookie DAP Freshman Join Date: Apr 2003 Location: In a house!! Posts: 36 Thanked 0 Times in 0 Posts	ActiveSync works first time then goes to guest First I will tell you what the problem is, then I will describe what I have done so far to try to fix it. The Problem: I have ActiveSync 3.6 both at home and work. My home computer is Windows XP, work is Windows 95. I initially setup the partnership at home to be "Only One Computer". I have had no problems at home. Now I bought a second cradle and I want to also sync at work. Here lies the problem. When setting up the partnership at work, I selected "Two Computers". The sync works for the first time. When I remove the Axim from the cradle then put it back, ActiveSync thinks it is connected to a Guest Partnership. How do I remove the partnership information from the Axim? I believe it stores it somewhere. When I remove the Axim from the cradle again, ActiveSync changes the description from Guest to my actual device name. This tells me that there is something on the device, but what and where? What I have done so Far: I have reinstalled ActiveSync 3.6. Did not fix it I have changed my device name on Axim. Did not fix it I have deleted the partnership on the PC. Did not fix it. I have tried to setup work as the only computer. Did not fix it. And for the biggie, I have done a Hard Reset. Did not fix it. I have continued looking into this. Here is a clean log just after I have created the partnership and redocked to the cradle. Does anyone know if this looks okay or not. ********** START OF LOG ************ 2003-04-23 11:48:32 FFF6935F - [Ctrl Recv] [0xF0]: Communication socket error 0, returned 0 2003-04-23 11:48:32 FFF5C98B - [Data Recv] [0xFFFFFFFF]: Communication socket error 10038, returned -1 2003-04-23 11:48:32 FFF5058F - [RemSync Recv] [0xFFFFFFFF]: Communication socket error 10038, returned -1 2003-04-23 11:48:32 FFF68C13 - ActiveSync session completed 2003-04-23 11:48:39 FFF68C13 - Checking existing partnership on device 0x2A720E75. 2003-04-23 11:48:39 FFF9EA4B - DTPT: Failed first query to find network. Dest={436EF144-B4FB-4863-A041-8F905A62C572}, HR=0x80070057 2003-04-23 11:48:39 FFF9EA4B - DTPT: FAILED to find source network. Dest={436EF144-B4FB-4863-A041-8F905A62C572} fDeviceSrc=0 HR=0x80070057 2003-04-23 11:48:39 FFF9EA4B - ERROR: g_app.SetupDTPT(g_app.GetDTPTNetworkType()) returned 0x80070057, file: d:\medusa\private\apps\conn\repl\wcesmgr\.\partner .cpp, line 2486 2003-04-23 11:48:39 FFF9EA4B - ERROR returned in function CCeSync::CheckPartner. hr: 0x80070057 ******** END OF LOG ************** At this point in the game, I think Windows 95 may be the problem. Any help here would be greatly appreciated. Last edited by tgerstner; 04-23-03 at 11:54 AM.