Re: Mobile Device Center / Sync Center and Windows Mobile 5.0

JasperM

On May 21, 12:56 pm, Steve Spiller [MSFT]
<> wrote:
> Great! One thing... You need to remove the "online" part from the email
> address shown in my profile.
>
> --
> Thanks,
>
> Steve Spiller
> Development Lead
> Windows Mobile Device Center
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Sandra" wrote:
> > Excellent, thanks!
>
> > I just emailed you privately with the two logs.
>
> > "Steve Spiller [MSFT]" wrote:
>
> > > On that page linked below, right click on the two file links (wmdc.exe.config
> > > and wmdhost.exe.config) and choose to save them to your WindowsMobile folder.
> > > This is in your Windows folder, usually C:\WINDOWS\WINDOWSMOBILE.
>
> > > Once you've save those two files reboot your machine and try to use WMDC.
> > > This time when it fails it will have created some log files.
>
> > > If you do Start->Run (or WindowKey + R) and type in %TEMP%, it will open a
> > > folder with WMDC.LOG and WMDHOST.LOG. Those are the files we need.
>
> > > Hope that's more clear for you!
>
> > > --
> > > Thanks,
>
> > > Steve Spiller
> > > Development Lead
> > > Windows Mobile Device Center
>
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
>
> > > "Sandra" wrote:
>
> > > > I swear, I'm not computer-dumb, but I really don't understand these
> > > > instructions. Can you please elaborate on them in a little more detail? What
> > > > exactly am I "file --> save as"'ing in the Windows Mobile folder? I'm
> > > > confused.
>
> > > > Thanks!
> > > > Sandra
>
> > > > "Steve Spiller [MSFT]" wrote:
>
> > > > > You can find instructions on how to generate logs for WMDC here:
> > > > >
>
> > > > > You can post the logs here or send them to me directly. The red "x" after
> > > > > trying to connect is usually caused by a handled exception that the software
> > > > > can't recover from.
>
> > > > > --
> > > > > Thanks,
>
> > > > > Steve Spiller
> > > > > Development Lead
> > > > > Windows Mobile Device Center
>
> > > > > This posting is provided "AS IS" with no warranties, and confers no rights.
>
> > > > > "Sandra" wrote:
>
> > > > > > Still nothing.
>
> > > > > > *sigh*
>
> > > > > > I tried rebooting, deleting the drivers and starting from scratch - then
> > > > > > followed your directions. The same thing occirred - it was "connecting" for
> > > > > > about half a minute before it stopped and showed "error" with no further
> > > > > > explanation.
>
> > > > > > Any other suggestions????
>
> > > > > > Thanks!
> > > > > > S.
>
> > > > > > "R. Kbs" wrote:
>
> > > > > > > I think I have a solution for your problem, I have pretty much the same sync
> > > > > > > problem.
>
> > > > > > > 1. Unplug your PDA from the USB (cradle)
> > > > > > > 2. Go to Services (right click computer - manage - services and
> > > > > > > applications - services)
> > > > > > > 3. right click Windows Mobile-based device connectivity and click Stop
> > > > > > > 4. next screen click yes (windows mobile 2003-based device connectivity)
> > > > > > > 5. wait a few seconds..........
> > > > > > > 6. right click Windows Mobile-based device connectivity and click Start
> > > > > > > 7. right click windows mobile 2003-based device connectivity and click Start
> > > > > > > 8. start windows mobile device center through start menu
> > > > > > > 9. wait 5 seconds and plug in your PDA in the USB (cradle)
> > > > > > > 10. now the PDA will connect to WMDC
>
> > > > > > > Good luck
>
> > > > > > > Rob
>
> > > > > > > "Sandra" <San...@discussions.microsoft.com> wrote in message
> > > > > > >news:67BE386C-B5BF-4F34-9E64-E8D3D4DAF3D0@microsoft.com...
> > > > > > > > I've scoured message boards everywhere, and I'm not really getting much
> > > > > > > > help.
> > > > > > > > Hopefully I'll get more here.
>
> > > > > > > > I had a Moto Q running Windows Mobile 5.0. I bought a new computer with
> > > > > > > > Vista Home Premium and had only a little trouble before I was able to get
> > > > > > > > my
> > > > > > > > phone synched with Vista.
>
> > > > > > > > Then I ran into problems with the phone (the internal charging mechanism
> > > > > > > > died) and my vendor (Telus in Canada) gave me a new phone. Same model,
> > > > > > > > etc.
>
> > > > > > > > I deleted the previous partnership with Sync Center and my old phone, and
> > > > > > > > tried to create a new one. For some reason, Sync Center is only
> > > > > > > > recognizing
> > > > > > > > the phone as an MP3 player (although it's labelled as a "Motorola Q") and
> > > > > > > > only allows me to "Sync with Windows Media Player". Windows Mobile Device
> > > > > > > > Center shows it as "connecting" briefly before ending with "error".
>
> > > > > > > > I've tried uninstalling and reinstalling WMDC (and deleting all the
> > > > > > > > inherant
> > > > > > > > drivers), I've unchecked the option on the phone itself that says "enable
> > > > > > > > advanced connectivity" as I was told on other forums. I just can't get
> > > > > > > > Windows to recognize my Windows Mobile-based device as anything other than
> > > > > > > > a
> > > > > > > > simple storage card.
>
> > > > > > > > Is there a way to force this recognition? Has anyone else run into the
> > > > > > > > same
> > > > > > > > problem and was able to fix it? I see a lot of forum members here saying
> > > > > > > > "WMDC is just ActiveSync with a new skin" but there's no way. I've had
> > > > > > > > nothing but problems trying to sync a Windows-based mobile device!!!
>
> > > > > > > > Please help! I've promised a year's supply of Pocky by post to anyone who
> > > > > > > > can get this working for me. I'm determined to NOT re-enter my 250+
> > > > > > > > contacts
> > > > > > > > back into the phone manually.
>
> > > > > > > > Thanks,
> > > > > > > > Sandra

Steve,

Are there any release notes about reading the WMDC log files? Working
in a support role myself, it would be nice to have something that
would describe what is in those files and perhaps how to read them?
Are they additional log files that were not present in A/S 4.x,
something besides cryptic Exchange Sync errors?

-JasperM