Any help when Mobile Device Centre 6.1 update crashes connectivity

I have been using Vista with my Dell Axim X51 since Vista Beta 2. I now have
the commercial Ultimate Vista.

There were problems along the way but the worst problem has now occurred
when I installed the latest driver update to Windows Mobile Device Centre 6.1

I get two error messages - one that svchost.exe has closed down and one that
the Windows mobile 2003 based devices service has closed down. These events
occur when I try to connect the device in it's USB cradle.

When the upgrade runs, the first thing it does is install an unknown device
(at first this took ages but after various tries this goes faster now in the
preconfigured folders.)

All I can do now is to choose the device connection type (excluding
Bluetooth) and then the whole Device Centre crashes and generates error
messages when I try to connect.

Vista synced perfectly with the device prior to the upgrade.

I read the blog here and tried uninstalling the upgrade (WMDC) and booting
and then re-installing. No change. I tried uninstalling and then installing
each of two previous upgrades I still had - one from December and one from
February. No change.

Any help available? I could send the ETL log files to
if someone there would receive them and look at them

Forgot to say that the Axim has WM5.

You can send to dcinput or to me directly, just remove "online" from my
address. Also, can you take a look at your Event Log for wcescomm and/or
rapimgr events?

--
Thanks,

Steve Spiller
Development Lead
Windows Mobile Device Center

This posting is provided "AS IS" with no warranties, and confers no rights.

"Copenhagen" <> wrote in message
news:E23D0BD0-958C-4EBF-8933-...
>I have been using Vista with my Dell Axim X51 since Vista Beta 2. I now
>have
> the commercial Ultimate Vista.
>
> There were problems along the way but the worst problem has now occurred
> when I installed the latest driver update to Windows Mobile Device Centre
> 6.1
>
> I get two error messages - one that svchost.exe has closed down and one
> that
> the Windows mobile 2003 based devices service has closed down. These
> events
> occur when I try to connect the device in it's USB cradle.
>
> When the upgrade runs, the first thing it does is install an unknown
> device
> (at first this took ages but after various tries this goes faster now in
> the
> preconfigured folders.)
>
> All I can do now is to choose the device connection type (excluding
> Bluetooth) and then the whole Device Centre crashes and generates error
> messages when I try to connect.
>
> Vista synced perfectly with the device prior to the upgrade.
>
> I read the blog here and tried uninstalling the upgrade (WMDC) and booting
> and then re-installing. No change. I tried uninstalling and then
> installing
> each of two previous upgrades I still had - one from December and one from
> February. No change.
>
> Any help available? I could send the ETL log files to
>
> if someone there would receive them and look at them
>
> Forgot to say that the Axim has WM5.
>

´Many thanks, I have replied to your message, attaching the ETL log files and
the event log entries tyou requested to the @microsoft.com address you
provided. I am looking forward to your reply.

"Steve Spiller [MSFT]" wrote:

> You can send to dcinput or to me directly, just remove "online" from my
> address. Also, can you take a look at your Event Log for wcescomm and/or
> rapimgr events?
>
> --
> Thanks,
>
> Steve Spiller
> Development Lead
> Windows Mobile Device Center

"Steve Spiller [MSFT]" wrote:

> You can send to dcinput or to me directly, just remove "online" from my
> address. Also, can you take a look at your Event Log for wcescomm and/or
> rapimgr events?

Steve and I exchanged some info and it appears that the installer doesn't
clean up properly as the issue was that thre were files of various versions
installed when the installation process was completed. Using the installer
(from the programs applet in the control panel) to remove Mobile Device
Centre 6.1 should leave \Windows\WindowsMobile folder empty (except programs
installed on the device) but it doesn't.

I deleted all this manually and then reinstalled the Mobile Device Centre
6.1 update and this did give me more functionality but connectivity still
doesn't work. There must be some files installed elsewhere that need
upgrading?

This is all very perplexing and annoying. It worked fine before the upgrade
and it seems that there is no way to return to the prior state.

I am having the exact same problem as Copenhagen- my Axim x51 worked
perfectly with WMDC 6.0 but then when I upgraded to 6.1 the computer no
longer recognizes it. The computer will ping everytime the device connects
or turns on or off, but WMDC 6.1 always says it is not connected. I have
uninstalled/installed WMDC several times through add/remove programs,
re-installed 6.0, and uninstalled the Windows Mobile Remote Adapter (even
uninstalling the device driver with it), but still it is a no-go.
The problem I see is that Windows is not even recognizing the Axim in the
"Portable Device" category. When I re-connect after un-installing the Axim
driver Vista will recognize the Axim and install a new driver but after that
it gets dropped from the system again. I have to say I am completely
flummoxed and annoyed by all of this. I need to be able to sync this device
as I use it constantly at work and have updates to programs and databases
that I use constantly. Any help or any workaround would be greatly
appreciated.

"Copenhagen" wrote:

> "Steve Spiller [MSFT]" wrote:
>
> > You can send to dcinput or to me directly, just remove "online" from my
> > address. Also, can you take a look at your Event Log for wcescomm and/or
> > rapimgr events?
>
> Steve and I exchanged some info and it appears that the installer doesn't
> clean up properly as the issue was that thre were files of various versions
> installed when the installation process was completed. Using the installer
> (from the programs applet in the control panel) to remove Mobile Device
> Centre 6.1 should leave \Windows\WindowsMobile folder empty (except programs
> installed on the device) but it doesn't.
>
> I deleted all this manually and then reinstalled the Mobile Device Centre
> 6.1 update and this did give me more functionality but connectivity still
> doesn't work. There must be some files installed elsewhere that need
> upgrading?
>
> This is all very perplexing and annoying. It worked fine before the upgrade
> and it seems that there is no way to return to the prior state.
>
>

Have you recieved any response from anyone here or elsewhere about this
issue? I haven't seen other simialar reports. Maybe the issue is isolated to
Axim x51's ?

"Orion" wrote:

> I am having the exact same problem as Copenhagen- my Axim x51 worked
> perfectly with WMDC 6.0 but then when I upgraded to 6.1 the computer no
> longer recognizes it. The computer will ping everytime the device connects
> or turns on or off, but WMDC 6.1 always says it is not connected. I have
> uninstalled/installed WMDC several times through add/remove programs,
> re-installed 6.0, and uninstalled the Windows Mobile Remote Adapter (even
> uninstalling the device driver with it), but still it is a no-go.
> The problem I see is that Windows is not even recognizing the Axim in the
> "Portable Device" category. When I re-connect after un-installing the Axim
> driver Vista will recognize the Axim and install a new driver but after that
> it gets dropped from the system again. I have to say I am completely
> flummoxed and annoyed by all of this. I need to be able to sync this device
> as I use it constantly at work and have updates to programs and databases
> that I use constantly. Any help or any workaround would be greatly
> appreciated.
>
> "Copenhagen" wrote:
>
> > "Steve Spiller [MSFT]" wrote:
> >
> > > You can send to dcinput or to me directly, just remove "online" from my
> > > address. Also, can you take a look at your Event Log for wcescomm and/or
> > > rapimgr events?
> >
> > Steve and I exchanged some info and it appears that the installer doesn't
> > clean up properly as the issue was that thre were files of various versions
> > installed when the installation process was completed. Using the installer
> > (from the programs applet in the control panel) to remove Mobile Device
> > Centre 6.1 should leave \Windows\WindowsMobile folder empty (except programs
> > installed on the device) but it doesn't.
> >
> > I deleted all this manually and then reinstalled the Mobile Device Centre
> > 6.1 update and this did give me more functionality but connectivity still
> > doesn't work. There must be some files installed elsewhere that need
> > upgrading?
> >
> > This is all very perplexing and annoying. It worked fine before the upgrade
> > and it seems that there is no way to return to the prior state.
> >
> >

nope, no other replies. I don't think this is just related to the Axims
either as I have seen other posts concerning this, or a very similar, issue
on other devices. I keep hoping for either a reply or a patch though as I
have been unable to sync now for over a month and the frustration just mounts.
I will post something here if I ever hear about or find anything that works.

"Copenhagen" wrote:

> Have you recieved any response from anyone here or elsewhere about this
> issue? I haven't seen other simialar reports. Maybe the issue is isolated to
> Axim x51's ?
>

nope, no other replies. I don't think this is just related to the Axims
either as I have seen other posts concerning this, or a very similar, issue
on other devices. I keep hoping for either a reply or a patch though as I
have been unable to sync now for over a month and the frustration just mounts.
I will post something here if I ever hear about or find anything that works.

"Copenhagen" wrote:

> Have you recieved any response from anyone here or elsewhere about this
> issue? I haven't seen other simialar reports. Maybe the issue is isolated to
> Axim x51's ?
>

I downloaded the program and ran it to unlock and delete the
C:/windows/WindowsMobile directory (i did it after uninstalling WMDC and WMDC
driver updates from the control panel), but I could never delete the 5 or 6
files in the en-US folder, however I could delete ALL the others. I turned
off UAC too so it would allow the unlock. however everytime i tried to
unlock and delete those files it would say that they could only be deleted
after a restart but never did delete. I then just renamed the WindowsMobile
folder those were under to something different and reinstalling WMDC. It
still didnt work.

Is there a step I didn't do, or a something you did to delete that folder
(en-US) that I am missing or you, perhaps, didn't mention? man this is
frustrating. thanks.

">
> But, this is what worked:
>
> I found a program named Unlocker 1.8.5 at
> http://ccollomb.free.fr/unlocker/ which gave me the ability to unlock
> and delete the locked files in the Windows Mobil folder. After doing
> so I now attempted to re-install the WMDC Version 6.0, still available on
> the Microsoft website, which had
> worked fine. After the usual legthy delay it installed the "unknown device"
> UMBus enumerator ( why isn't this just included?) and found Pocket PC at
> Windows Update and we were in business again! [If anyone has the Belkin
> Bluetooth F8T009 dongle I suggest uninstalling and reinstalling it before
> doing the above.]

If you have a look at my post later than this one, titled "Sync problem on
WMDC 6.1 fixed by rolling back to WMDC6.0", you will see that I had the same
problem too but simply left that folder intact. It did not prevent me from
rolling back to WMDC6.0.

Regards,
Neville Lang




"Orion" <> wrote in message
news:7F90CB55-3E4C-42E5-9E7B-...
>I downloaded the program and ran it to unlock and delete the
> C:/windows/WindowsMobile directory (i did it after uninstalling WMDC and
> WMDC
> driver updates from the control panel), but I could never delete the 5 or
> 6
> files in the en-US folder, however I could delete ALL the others. I
> turned
> off UAC too so it would allow the unlock. however everytime i tried to
> unlock and delete those files it would say that they could only be deleted
> after a restart but never did delete. I then just renamed the
> WindowsMobile
> folder those were under to something different and reinstalling WMDC. It
> still didnt work.
>
> Is there a step I didn't do, or a something you did to delete that
> folder
> (en-US) that I am missing or you, perhaps, didn't mention? man this is
> frustrating. thanks.
>
> ">
>> But, this is what worked:
>>
>> I found a program named Unlocker 1.8.5 at
>> http://ccollomb.free.fr/unlocker/ which gave me the ability to unlock
>> and delete the locked files in the Windows Mobil folder. After doing
>> so I now attempted to re-install the WMDC Version 6.0, still available on
>> the Microsoft website, which had
>> worked fine. After the usual legthy delay it installed the "unknown
>> device"
>> UMBus enumerator ( why isn't this just included?) and found Pocket PC at
>> Windows Update and we were in business again! [If anyone has the Belkin
>> Bluetooth F8T009 dongle I suggest uninstalling and reinstalling it before
>> doing the above.]
>