Windows Mobile Device Center Connects then Disconnects

[davenash]

I'm having a problems syncing my Athena with my laptop. It's a T-Mobile Ameo with PK3.0. I think the problems may have occurred when I upgraded to PK3.0 (about a month ago).

I'm running Vista - on two laptops, a Dell D610 and a D630. I can't sync by cable with either or bluetooth to the D630 (not supported on D610).

What happens (whether by cable or bluetooth) is often you can get the phone to connect and Windows Mobile Device Center says 'connecting'. Then I am connected - for about 5 seconds. Then, I am just disconnected.

I've tried everything - disabling advanced USB functionality, reinstalling WMDC numerous times, different laptops, bluetooth/usb and nothing's working. I suspect it happened when I installed PK 3.0 but I can't be sure. I've tried hard resetting and the 'clear storage' utility.

I have no memory card and no way of connecting a memory card to my laptop so I can't really reflash that way.

Has anyone come across this before? Do you have any ideas how I can fix this?

Many, many thanks in advance.

[WiZaxx]

Do you have a personal firewall installed?
By your description looks as if you have one active. TrenMicro anti-virus instals one by default and I believe others do too.


Cheers,
--M

[davenash]

no no firewalls and have also disabled all the stuff in the Windows Firewall.

sorry, forgot to say that.

[Confucious]

Had you synced before you flashed? If so, delete any existing partnerships and try again. Also, why AP3? AP4 is out now. I have had no probs syncing with either,

[davenash]

this is the whole point....

I can't install AP4 because I can't get the F*ing thing to connect to the F*ing computer. This is driving me up the wall, I have tried absolutely everything.

Most recently:

Bought memory card and adapter. Came to about £30 what a waste.
Put Tmobile WM5 NBH on SD card and installed that via boot manager.

Following that I could now sync by bluetooth.

But you can't upgrade the ROM via bluetooth, that must be by cable, and that's not working.

New error now though. WMDC shows connecting for around 5-10 seconds, and then tells me 'Error'. Well that's really useful.

Investigating the event viewer reveals error 0x80072745. Full log at bottom of post.

A google of 'wmdc 0x80072745' reveals lots of other people who have this problem.

The generally suggested solution is uninstall/reinstall WMDC. Well that doesn't work. (and a load of silly things like disabled advanced network functionality which ive obviously already tried).

Most people seem to think this problem exists because they upgraded to WMDC 6.1. In that case, how do I completely remove that from my system? Obviously not just uninstall restart etc.

No-one on the internet seems to have yet found a solution to this. All the forums end with 'I still haven't sorted this'. I really hate Microsoft. Its over 6 months since they released 6.1 and STILL NO FIX??!

And I can't even decompile the 'athena updater' EXE file to get the NBH for AP4 and put that on an SD card because according to the wiki, the SPL structure is changed for the upgrade to AP4 and obviously I can't do that by myself and presumably it is not the NBH that controls this but some other part of the .exe package.


GRRR all I want is AP4.

Please, anyone any ideas?





- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
+ <System>
<Provider Name="RapiMgr" />
<EventID Qualifiers="49152">8</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2008-05-09T18:30:17.000Z" />
<EventRecordID>4724</EventRecordID>
<Channel>Application</Channel>
<Computer>DaveD630</Computer>
<Security />
</System>
- <EventData>
<Data>communication (0x80072745)</Data>
</EventData>
</Event>

[johnwalk]

Like Confusious said, if you where syncing before you upgraded, then you will need to delete all partnerships, and then set them up again.
out of all the roms, I used 6.1 the longest, with no problems

[davenash]

I'd tried that as far as I could.

Problem now solved!

Thanks to this genius:

http://www.tech-archive.net/Archive/PocketPC/microsoft.public.pocketpc.activesync/2007-09/msg00101.html

I'm not sure if doing all these manual steps helped to delete partnerships properly. I'd tried as far as possible to do this already, by deleting c:\windows\windows mobile, but I hadn't looked at the stuff in reg edit or in c:\users\dave\appdata\.....

So perhaps that solved it. I think more it was a problem with WMDC 6.1 as a search for 'wmdc 0x80072745' in Google reveals everyone moaning about 6.1.

Anyway hopefully this will help anyone who has this problem in the future - I had tried literally everything (like you probably have so far) and this really worked.

You need to download WMDC 6.0, the link at Microsoft is:

http://www.microsoft.com/downloads/details.aspx?familyid=83D513EA-9DF9-4920-AF33-3A0E2E4E7BEB&displaylang=en

(you can check with install file you have easily, as 6.0 is 10.3mb and 6.1 is 12mb).

Thanks to everyone for their help. I love the way how when MS release an upgrade it is breaks things for so many users (but yes I'm sure things are fine for others...).

Sidenote: AP4.0 seems verrrry slow at writing text messages. I wonder if it's snapvue that's slowing it down (seeing as that was designed for the shift).