I wasn't going to post as I was sure that with perseverence I could fix my problem. I was wrong, it beat me. I've run out of ideas.
I have a x51v with A06, fake server and no exotic software. My PC is a Dell Latitude (laptop) with XP, SP2 and all current updates (automatic).
My problem is that I can't sync. The Ax will connect and just as it's about to sync I get the scary "plonk of death" and a box that says it can't do it. I can close the box and I am still connected but it won't try to sync again.
I have been through the forum and tried the suggestions regarding the firewall and antivirus and even turned them completely off. Have also tried IR with the same result. I have uninstalled and reinstalled AS a few times changing up and down between 4.1 and 4.2. I am currently on 4.1.
Is there any way I can determine whether the problem is with my Axim or my PC ?
Things are so bad that I was even thinking of calling Dell.
All and any suggestions will be gratefully received.
I am in the exact same boat. Same specs (AS 4.1 & 4.2 tried), same computer (Dell Latitude CPx) with the same software (sp2, Winxp pro). It recognizes and connects but will not sync. It then logs me on as a 'guest' and doesn't try and sync again. Tried everything in the book, like you (turned off Firewall & Antivirus). Just thought you should know...your not alone...CAN SOMEONE PLEASE HELP?????
Peace
Rue
__________________ "He is no fool who gives what he cannot keep to gain what he cannot lose" - Jim Elliot
I am in the exact same boat. Same specs (AS 4.1 & 4.2 tried), same computer (Dell Latitude CPx) with the same software (sp2, Winxp pro). It recognizes and connects but will not sync. It then logs me on as a 'guest' and doesn't try and sync again. Tried everything in the book, like you (turned off Firewall & Antivirus). Just thought you should know...your not alone...CAN SOMEONE PLEASE HELP?????
Peace
Rue
Yeah, it's frustrating isn't it. Hopefully someone will take pity or at least point us in the right direction.
I would be happy if I could find out whether it is the Axim or the PC. At least then I would know where to concentrate my efforts.
Well, if you have tried everything else, maybe you could borrow a friends pc and try syncing with it. That would as least confirm or eliminate the Dell laptop.
c3p0
__________________
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
"I'm not as good as I once was, but I'm as good once as I ever was".
(Toby Keith)
Location: Fullerton, California; North Orange County, just south of L.A.
Posts: 27
Device: V220
Carrier: Cingular
Thanked 0 Times in 0 Posts
Have you tried this?
I probably don't have the answer here, but I have a couple thoughts.
Have you taken a look in the hardware manager for your PC and checked to see if the USB ports are all kosher? Do other USB devices function normally? If not, debug the USB connection at your PC and then delete your sync targets and try again with AS.
Also, does your PC run XP Home Edition or the Pro version? I have never used the Home Edition, so I cannot speak to this. On XP Pro however, you can examine the system logs using the MMC snap-in eventvwr.msc. If you have the Pro version, you can enable even greater levels of auditiing by fiddling with Local Policies...unless your XP box lives in a domain where administrators have a domain based policy that is enforced. In this case, security may prevent you from changing the options in your Local Policy.
If you take a close look at the SYSTEM as well as APPLICATION logs, there may very well be error messages there that will help elucidate the foundation of your AS troubles. If the errors are security related, you may also find telltale signs in the SECURITY log, although to really flesh this log out you must be able to set policy.
When you say that your AXIM will connect, then there is a sound of demise from your AXIM. What does AS say at this time? Does AS display your AXIM's name when you are connected? Does the name stay in the AS display AFTER the "plonk of death"? This will indiciate to a pretty meaningful degree the status of your USB bus and the basic connection itself.
I hope my next question will not insult you. Can you tell me, are you sure that tcp/ip is installed on your XP machine, and that the tcp/ip stack is bound to your AS cradle? This means making sure that tcp/ip is loaded for the AS connection and that file and print sharing is also enabled for that connection. You do have a new network connection if you look in the XP machine's 'Start-->Settings-->Network Connections' and looking to see if the AS cradle has a separate network connection here.
The only other thing I can think to have you check is the ip addresses that AS likes to use. The AS program likes to use 192.254.2.1 and 192.254.2.2 for the cradle and AXIM respectively. If you are using these addresses in your LAN someplace this could muck up the synchronization. These addresses can sometimes be unavailable because they are being used for something like ICS (Internet Connection Sharing), or they can be removed from service because they are in a list of reserved addresses being held by a DHCP server. If you have ICS, NAT, DHCP server or the like that has ownership of the addresses, this could mess things up.
I think that the AS software contains it's own DHCP server, and this is reflected in the information one sees if you run ipconfig/all while AS is connected successfully. If I recall correctly, DHCP starts with a client broadcasting a query trying to find a DHCP server. This could give you the impression that the AXIM connects. If the AXIM cannot then get a response from the AS embedded DHCP server, I would expect exactly the sort of ABEND you discribe.
One last thought....even though you have turned off your firewall, is it possible that you enabled IP Filtering in the network conncetion tcp/ip advanced configuration settings? If you turn on IP Filtering for one adapter, you are turning it on for all of them since the setting is adapter global. If you somehow have IP Filtering active, this could yentz you just as you describe.
I am not sure this will help, but I thought about your problem lots and hope that I came up with at least one avenue of debugging that you have not yet been down. Good luck!
__________________
==============================
Robyn Robertson
Ent. Eng./ Proj. Mngr.
Eos Consulting/Concannon Systems
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
Ok, I am in the same boat, but I am on a desktop! I have a feeling it was the 4.2 ActiveSync but going backwards did not solve it.
I went to my second PC that never had 4.2 on and I had NO problems sync'ing.
So now is the question on how to get rid of activesync, without wiping out everything on this hard drive so that I can sync again...
I repluged in the USB cable to a different port (on the problem PC) - still sample problem and the error message is "ActiveSync encoutered a problem on the desktop Support Code: 85010014"
Up to 2 days ago I was having no problems..
Searching the net I found this about the error "# If you are seeing the error 85010014 (a general error) then try uninstalling and reinstalling Outlook. The error in ActiveSync is actually from the Outlook APIs. You will need to reconfigure Outlook unless you backup your settings. To uninstall Outlook click on the Control Panel -> Add or remove Programs -> Office 2003 and chose to modify the installation by adding or removing components. Uncheck Outlook and updated it to remove Outlook from Office 2003. Then click on Office 2003 again and re-check the option to install Outlook to add it back to Office 2003. You may need your Office 2003 CD. Then reboot."
"making sure that tcp/ip is loaded for the AS connection and that file and print sharing is also enabled for that connection. You do have a new network connection if you look in the XP machine's 'Start-->Settings-->Network Connections' and looking to see if the AS cradle has a separate network connection here."
This is the part that I have found causes your problem. As rroberts161 says above, look in the network connections for the new windows mobile device, right click on it and make sure the 3 boxes have a check mark in them. Let us know how it goes.....
Quote:
Originally Posted by rroberts161
"making sure that tcp/ip is loaded for the AS connection and that file and print sharing is also enabled for that connection. You do have a new network connection if you look in the XP machine's 'Start-->Settings-->Network Connections' and looking to see if the AS cradle has a separate network connection here."
Originally Posted by bigdave240
This is the part that I have found causes your problem. As rroberts161 says above, look in the network connections for the new windows mobile device, right click on it and make sure the 3 boxes have a check mark in them. Let us know how it goes.....
Many thanks to "rroberts161", you put a lot of work into your reply and have given me plenty to think about. I will work through the suggestions tonight as I am off to work today (joys of retail) but here are the answers to some of your comments.
I am pretty sure the "Network Connections" are OK and the 3 boxes are ticked.
I am using XP Pro.
After the "plonk of death" I remain connected (USB or IR) and the partnership is intact as AS shows the name of my Axim.
As I have a partnership and a connection are your comments regarding IP addresses still valid?
Your last couple of paragraphs take me a bit out of my depth so I will have to work through them slowly.
Once again, I really appreciate your efforts. I am pretty confident the answer is in there somewhere.
Follow Us
RSS Feed
Follow on Twitter
Facebook
YouTube
Activesync vs me. Score AS 1 me nil
Uber Member
