WMDC "Windows Mobile Device Center Sync Host has stopped working"

can't get it to work. I've tried all I know to do and searched everywhere
for a solution.

I get the WMDC setup screen. If I click on "Connect without setting up your
device", I can browse my Blackjack just fine.

As soon as I click on "Setup Your Device" , I get an immediate popup
saying"Windows Mobile Device Center Sync Host has stopped working" with a
choice of close or debug.
From that point on, the WMDC will not respond untill I terminate the sync
host process or reboot.

And yes I've got the latest version and tweaked the firewall and even turned
firewall off. Uninstalled and reinstalled a dozen times.

I did an upgrade to Vista so I suspect it has something to do with the
leftovers from the previous installed Activesync in XP

Here are the Event Viewer logs related to the WMDC crash.

The description for Event ID 1000 from source Application Error cannot be
found. Either the component that raises this event is not installed on your
local computer or the installation is corrupted. You can install or repair
the component on the local computer.

If the event originated on another computer, the display information had to
be saved with the event.

The following information was included with the event:

WmdHost.exe

6.0.6783.0

45b7b21a

SPhNS_PC.dll

2.0.0.20

438dbe73

c0000005

0000fa02

--------------------------------------------------------------------------------------

Fault bucket 376918087, type 1

Event Name: APPCRASH

Response: None

Cab Id: 0

Problem signature:

P1: WmdHost.exe

P2: 6.0.6783.0

P3: 45b7b21a

P4: SPhNS_PC.dll

P5: 2.0.0.20

P6: 438dbe73

P7: c0000005

P8: 0000fa02

P9:

P10:

----------------------------------------------------------------------------------------

Faulting application WmdHost.exe, version 6.0.6783.0, time stamp 0x45b7b21a,
faulting module SPhNS_PC.dll, version 2.0.0.20, time stamp 0x438dbe73,
exception code 0xc0000005, fault offset 0x0000fa02, process id 0x1588,
application start time 0x01c74d8579886025

Steven, I am having the exact same experience and i, too, upgraded. When I
click on "My computer" it shows a SGH-i607. However, WIndows MObility Center
shows two devices. one is the i607 but is shows as a music player only. the
other is an unidentified windows mobile device. Therefore, Vista seems to
recognize the device differently in two different programs. there are some
firewall changes you can make at www.pocketpcfaq.com/faqs/wmdc/firewall.htm.
i haven't tried them yet. beyond that i don't know what to do. I have read
some forums where people have not had a problem with the blackjack but i have
been struggling with this for a week.

"StevenW" wrote:

> can't get it to work. I've tried all I know to do and searched everywhere
> for a solution.
>
> I get the WMDC setup screen. If I click on "Connect without setting up your
> device", I can browse my Blackjack just fine.
>
> As soon as I click on "Setup Your Device" , I get an immediate popup
> saying"Windows Mobile Device Center Sync Host has stopped working" with a
> choice of close or debug.
> From that point on, the WMDC will not respond untill I terminate the sync
> host process or reboot.
>
> And yes I've got the latest version and tweaked the firewall and even turned
> firewall off. Uninstalled and reinstalled a dozen times.
>
> I did an upgrade to Vista so I suspect it has something to do with the
> leftovers from the previous installed Activesync in XP
>
> Here are the Event Viewer logs related to the WMDC crash.
>
> The description for Event ID 1000 from source Application Error cannot be
> found. Either the component that raises this event is not installed on your
> local computer or the installation is corrupted. You can install or repair
> the component on the local computer.
>
> If the event originated on another computer, the display information had to
> be saved with the event.
>
> The following information was included with the event:
>
> WmdHost.exe
>
> 6.0.6783.0
>
> 45b7b21a
>
> SPhNS_PC.dll
>
> 2.0.0.20
>
> 438dbe73
>
> c0000005
>
> 0000fa02
>
> --------------------------------------------------------------------------------------
>
> Fault bucket 376918087, type 1
>
> Event Name: APPCRASH
>
> Response: None
>
> Cab Id: 0
>
> Problem signature:
>
> P1: WmdHost.exe
>
> P2: 6.0.6783.0
>
> P3: 45b7b21a
>
> P4: SPhNS_PC.dll
>
> P5: 2.0.0.20
>
> P6: 438dbe73
>
> P7: c0000005
>
> P8: 0000fa02
>
> P9:
>
> P10:
>
> ----------------------------------------------------------------------------------------
>
> Faulting application WmdHost.exe, version 6.0.6783.0, time stamp 0x45b7b21a,
> faulting module SPhNS_PC.dll, version 2.0.0.20, time stamp 0x438dbe73,
> exception code 0xc0000005, fault offset 0x0000fa02, process id 0x1588,
> application start time 0x01c74d8579886025
>

Same exact issue, already called Microsoft Support, they do not support it,
posted in the private partner newsgroup, they don't either support it.
Every time I open the Windows Mobile device center, and click setup your
device, I get a message Windows Mobile Device Center Sync Host has stopped
working, a problem caused the program to stop working correctly. Windows
will close the program and notify you if a solution is available. I have an
option debug and close program.
"Kenwise" <> wrote in message
news:8F1F7800-A931-41C4-B83D-...
> Steven, I am having the exact same experience and i, too, upgraded. When
> I
> click on "My computer" it shows a SGH-i607. However, WIndows MObility
> Center
> shows two devices. one is the i607 but is shows as a music player only.
> the
> other is an unidentified windows mobile device. Therefore, Vista seems to
> recognize the device differently in two different programs. there are
> some
> firewall changes you can make at
> www.pocketpcfaq.com/faqs/wmdc/firewall.htm.
> i haven't tried them yet. beyond that i don't know what to do. I have
> read
> some forums where people have not had a problem with the blackjack but i
> have
> been struggling with this for a week.
>
> "StevenW" wrote:
>
>> can't get it to work. I've tried all I know to do and searched
>> everywhere
>> for a solution.
>>
>> I get the WMDC setup screen. If I click on "Connect without setting up
>> your
>> device", I can browse my Blackjack just fine.
>>
>> As soon as I click on "Setup Your Device" , I get an immediate popup
>> saying"Windows Mobile Device Center Sync Host has stopped working" with a
>> choice of close or debug.
>> From that point on, the WMDC will not respond untill I terminate the sync
>> host process or reboot.
>>
>> And yes I've got the latest version and tweaked the firewall and even
>> turned
>> firewall off. Uninstalled and reinstalled a dozen times.
>>
>> I did an upgrade to Vista so I suspect it has something to do with the
>> leftovers from the previous installed Activesync in XP
>>
>> Here are the Event Viewer logs related to the WMDC crash.
>>
>> The description for Event ID 1000 from source Application Error cannot be
>> found. Either the component that raises this event is not installed on
>> your
>> local computer or the installation is corrupted. You can install or
>> repair
>> the component on the local computer.
>>
>> If the event originated on another computer, the display information had
>> to
>> be saved with the event.
>>
>> The following information was included with the event:
>>
>> WmdHost.exe
>>
>> 6.0.6783.0
>>
>> 45b7b21a
>>
>> SPhNS_PC.dll
>>
>> 2.0.0.20
>>
>> 438dbe73
>>
>> c0000005
>>
>> 0000fa02
>>
>> --------------------------------------------------------------------------------------
>>
>> Fault bucket 376918087, type 1
>>
>> Event Name: APPCRASH
>>
>> Response: None
>>
>> Cab Id: 0
>>
>> Problem signature:
>>
>> P1: WmdHost.exe
>>
>> P2: 6.0.6783.0
>>
>> P3: 45b7b21a
>>
>> P4: SPhNS_PC.dll
>>
>> P5: 2.0.0.20
>>
>> P6: 438dbe73
>>
>> P7: c0000005
>>
>> P8: 0000fa02
>>
>> P9:
>>
>> P10:
>>
>> ----------------------------------------------------------------------------------------
>>
>> Faulting application WmdHost.exe, version 6.0.6783.0, time stamp
>> 0x45b7b21a,
>> faulting module SPhNS_PC.dll, version 2.0.0.20, time stamp 0x438dbe73,
>> exception code 0xc0000005, fault offset 0x0000fa02, process id 0x1588,
>> application start time 0x01c74d8579886025
>>

Hello,

I'm sorry to hear about the problems you're having with WMDC. We've seen
several reports of this nature since we officially launched WMDC. Do you
have any 3rd party software installed on your device? Specifically software
that syncs or used to show settings in ActiveSync 4.x? If so, what are they.

We spent a lot of time trying to ensure that 3rd party applications would
work smoothly with WMDC, but 100% coverage is difficult to acheive. So we
are working with 3rd party vendors to update their code as well as updating
ours to be as robust as possible.

Also, Windows Mobile Device Center is supposed to be fully supported by
Microsoft Product Support. I'll contact a few people to make sure that
customers aren't turned away again.

--
Thanks,
Steve

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



"Moishe Grunstein" wrote:

> Same exact issue, already called Microsoft Support, they do not support it,
> posted in the private partner newsgroup, they don't either support it.
> Every time I open the Windows Mobile device center, and click setup your
> device, I get a message Windows Mobile Device Center Sync Host has stopped
> working, a problem caused the program to stop working correctly. Windows
> will close the program and notify you if a solution is available. I have an
> option debug and close program.
> "Kenwise" <> wrote in message
> news:8F1F7800-A931-41C4-B83D-...
> > Steven, I am having the exact same experience and i, too, upgraded. When
> > I
> > click on "My computer" it shows a SGH-i607. However, WIndows MObility
> > Center
> > shows two devices. one is the i607 but is shows as a music player only.
> > the
> > other is an unidentified windows mobile device. Therefore, Vista seems to
> > recognize the device differently in two different programs. there are
> > some
> > firewall changes you can make at
> > www.pocketpcfaq.com/faqs/wmdc/firewall.htm.
> > i haven't tried them yet. beyond that i don't know what to do. I have
> > read
> > some forums where people have not had a problem with the blackjack but i
> > have
> > been struggling with this for a week.
> >
> > "StevenW" wrote:
> >
> >> can't get it to work. I've tried all I know to do and searched
> >> everywhere
> >> for a solution.
> >>
> >> I get the WMDC setup screen. If I click on "Connect without setting up
> >> your
> >> device", I can browse my Blackjack just fine.
> >>
> >> As soon as I click on "Setup Your Device" , I get an immediate popup
> >> saying"Windows Mobile Device Center Sync Host has stopped working" with a
> >> choice of close or debug.
> >> From that point on, the WMDC will not respond untill I terminate the sync
> >> host process or reboot.
> >>
> >> And yes I've got the latest version and tweaked the firewall and even
> >> turned
> >> firewall off. Uninstalled and reinstalled a dozen times.
> >>
> >> I did an upgrade to Vista so I suspect it has something to do with the
> >> leftovers from the previous installed Activesync in XP
> >>
> >> Here are the Event Viewer logs related to the WMDC crash.
> >>
> >> The description for Event ID 1000 from source Application Error cannot be
> >> found. Either the component that raises this event is not installed on
> >> your
> >> local computer or the installation is corrupted. You can install or
> >> repair
> >> the component on the local computer.
> >>
> >> If the event originated on another computer, the display information had
> >> to
> >> be saved with the event.
> >>
> >> The following information was included with the event:
> >>
> >> WmdHost.exe
> >>
> >> 6.0.6783.0
> >>
> >> 45b7b21a
> >>
> >> SPhNS_PC.dll
> >>
> >> 2.0.0.20
> >>
> >> 438dbe73
> >>
> >> c0000005
> >>
> >> 0000fa02
> >>
> >> --------------------------------------------------------------------------------------
> >>
> >> Fault bucket 376918087, type 1
> >>
> >> Event Name: APPCRASH
> >>
> >> Response: None
> >>
> >> Cab Id: 0
> >>
> >> Problem signature:
> >>
> >> P1: WmdHost.exe
> >>
> >> P2: 6.0.6783.0
> >>
> >> P3: 45b7b21a
> >>
> >> P4: SPhNS_PC.dll
> >>
> >> P5: 2.0.0.20
> >>
> >> P6: 438dbe73
> >>
> >> P7: c0000005
> >>
> >> P8: 0000fa02
> >>
> >> P9:
> >>
> >> P10:
> >>
> >> ----------------------------------------------------------------------------------------
> >>
> >> Faulting application WmdHost.exe, version 6.0.6783.0, time stamp
> >> 0x45b7b21a,
> >> faulting module SPhNS_PC.dll, version 2.0.0.20, time stamp 0x438dbe73,
> >> exception code 0xc0000005, fault offset 0x0000fa02, process id 0x1588,
> >> application start time 0x01c74d8579886025
> >>
>
>

Steve, i've got a program by Syncdata on there. i will uninstall and try
again. FYI, i just had two other friends take my device and connect it to
their Vista machines and it worked fine. i am stumped.

"Steve Spiller [MSFT]" wrote:

> Hello,
>
> I'm sorry to hear about the problems you're having with WMDC. We've seen
> several reports of this nature since we officially launched WMDC. Do you
> have any 3rd party software installed on your device? Specifically software
> that syncs or used to show settings in ActiveSync 4.x? If so, what are they.
>
> We spent a lot of time trying to ensure that 3rd party applications would
> work smoothly with WMDC, but 100% coverage is difficult to acheive. So we
> are working with 3rd party vendors to update their code as well as updating
> ours to be as robust as possible.
>
> Also, Windows Mobile Device Center is supposed to be fully supported by
> Microsoft Product Support. I'll contact a few people to make sure that
> customers aren't turned away again.
>
> --
> Thanks,
> Steve
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
> "Moishe Grunstein" wrote:
>
> > Same exact issue, already called Microsoft Support, they do not support it,
> > posted in the private partner newsgroup, they don't either support it.
> > Every time I open the Windows Mobile device center, and click setup your
> > device, I get a message Windows Mobile Device Center Sync Host has stopped
> > working, a problem caused the program to stop working correctly. Windows
> > will close the program and notify you if a solution is available. I have an
> > option debug and close program.
> > "Kenwise" <> wrote in message
> > news:8F1F7800-A931-41C4-B83D-...
> > > Steven, I am having the exact same experience and i, too, upgraded. When
> > > I
> > > click on "My computer" it shows a SGH-i607. However, WIndows MObility
> > > Center
> > > shows two devices. one is the i607 but is shows as a music player only.
> > > the
> > > other is an unidentified windows mobile device. Therefore, Vista seems to
> > > recognize the device differently in two different programs. there are
> > > some
> > > firewall changes you can make at
> > > www.pocketpcfaq.com/faqs/wmdc/firewall.htm.
> > > i haven't tried them yet. beyond that i don't know what to do. I have
> > > read
> > > some forums where people have not had a problem with the blackjack but i
> > > have
> > > been struggling with this for a week.
> > >
> > > "StevenW" wrote:
> > >
> > >> can't get it to work. I've tried all I know to do and searched
> > >> everywhere
> > >> for a solution.
> > >>
> > >> I get the WMDC setup screen. If I click on "Connect without setting up
> > >> your
> > >> device", I can browse my Blackjack just fine.
> > >>
> > >> As soon as I click on "Setup Your Device" , I get an immediate popup
> > >> saying"Windows Mobile Device Center Sync Host has stopped working" with a
> > >> choice of close or debug.
> > >> From that point on, the WMDC will not respond untill I terminate the sync
> > >> host process or reboot.
> > >>
> > >> And yes I've got the latest version and tweaked the firewall and even
> > >> turned
> > >> firewall off. Uninstalled and reinstalled a dozen times.
> > >>
> > >> I did an upgrade to Vista so I suspect it has something to do with the
> > >> leftovers from the previous installed Activesync in XP
> > >>
> > >> Here are the Event Viewer logs related to the WMDC crash.
> > >>
> > >> The description for Event ID 1000 from source Application Error cannot be
> > >> found. Either the component that raises this event is not installed on
> > >> your
> > >> local computer or the installation is corrupted. You can install or
> > >> repair
> > >> the component on the local computer.
> > >>
> > >> If the event originated on another computer, the display information had
> > >> to
> > >> be saved with the event.
> > >>
> > >> The following information was included with the event:
> > >>
> > >> WmdHost.exe
> > >>
> > >> 6.0.6783.0
> > >>
> > >> 45b7b21a
> > >>
> > >> SPhNS_PC.dll
> > >>
> > >> 2.0.0.20
> > >>
> > >> 438dbe73
> > >>
> > >> c0000005
> > >>
> > >> 0000fa02
> > >>
> > >> --------------------------------------------------------------------------------------
> > >>
> > >> Fault bucket 376918087, type 1
> > >>
> > >> Event Name: APPCRASH
> > >>
> > >> Response: None
> > >>
> > >> Cab Id: 0
> > >>
> > >> Problem signature:
> > >>
> > >> P1: WmdHost.exe
> > >>
> > >> P2: 6.0.6783.0
> > >>
> > >> P3: 45b7b21a
> > >>
> > >> P4: SPhNS_PC.dll
> > >>
> > >> P5: 2.0.0.20
> > >>
> > >> P6: 438dbe73
> > >>
> > >> P7: c0000005
> > >>
> > >> P8: 0000fa02
> > >>
> > >> P9:
> > >>
> > >> P10:
> > >>
> > >> ----------------------------------------------------------------------------------------
> > >>
> > >> Faulting application WmdHost.exe, version 6.0.6783.0, time stamp
> > >> 0x45b7b21a,
> > >> faulting module SPhNS_PC.dll, version 2.0.0.20, time stamp 0x438dbe73,
> > >> exception code 0xc0000005, fault offset 0x0000fa02, process id 0x1588,
> > >> application start time 0x01c74d8579886025
> > >>
> >
> >

If you still hit problems, use the infomation found here to gather debug logs
and send them along to me. This will also help us to make the experience in
these situations better for end-users. (Is anything worse than a fatal
exception??)

http://www.pocketpcfaq.com/faqs/wmdc/debug/index.htm

--
Thanks,
Steve

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



"Kenwise" wrote:

> Steve, i've got a program by Syncdata on there. i will uninstall and try
> again. FYI, i just had two other friends take my device and connect it to
> their Vista machines and it worked fine. i am stumped.
>
> "Steve Spiller [MSFT]" wrote:
>
> > Hello,
> >
> > I'm sorry to hear about the problems you're having with WMDC. We've seen
> > several reports of this nature since we officially launched WMDC. Do you
> > have any 3rd party software installed on your device? Specifically software
> > that syncs or used to show settings in ActiveSync 4.x? If so, what are they.
> >
> > We spent a lot of time trying to ensure that 3rd party applications would
> > work smoothly with WMDC, but 100% coverage is difficult to acheive. So we
> > are working with 3rd party vendors to update their code as well as updating
> > ours to be as robust as possible.
> >
> > Also, Windows Mobile Device Center is supposed to be fully supported by
> > Microsoft Product Support. I'll contact a few people to make sure that
> > customers aren't turned away again.
> >
> > --
> > Thanks,
> > Steve
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> >
> > "Moishe Grunstein" wrote:
> >
> > > Same exact issue, already called Microsoft Support, they do not support it,
> > > posted in the private partner newsgroup, they don't either support it.
> > > Every time I open the Windows Mobile device center, and click setup your
> > > device, I get a message Windows Mobile Device Center Sync Host has stopped
> > > working, a problem caused the program to stop working correctly. Windows
> > > will close the program and notify you if a solution is available. I have an
> > > option debug and close program.
> > > "Kenwise" <> wrote in message
> > > news:8F1F7800-A931-41C4-B83D-...
> > > > Steven, I am having the exact same experience and i, too, upgraded. When
> > > > I
> > > > click on "My computer" it shows a SGH-i607. However, WIndows MObility
> > > > Center
> > > > shows two devices. one is the i607 but is shows as a music player only.
> > > > the
> > > > other is an unidentified windows mobile device. Therefore, Vista seems to
> > > > recognize the device differently in two different programs. there are
> > > > some
> > > > firewall changes you can make at
> > > > www.pocketpcfaq.com/faqs/wmdc/firewall.htm.
> > > > i haven't tried them yet. beyond that i don't know what to do. I have
> > > > read
> > > > some forums where people have not had a problem with the blackjack but i
> > > > have
> > > > been struggling with this for a week.
> > > >
> > > > "StevenW" wrote:
> > > >
> > > >> can't get it to work. I've tried all I know to do and searched
> > > >> everywhere
> > > >> for a solution.
> > > >>
> > > >> I get the WMDC setup screen. If I click on "Connect without setting up
> > > >> your
> > > >> device", I can browse my Blackjack just fine.
> > > >>
> > > >> As soon as I click on "Setup Your Device" , I get an immediate popup
> > > >> saying"Windows Mobile Device Center Sync Host has stopped working" with a
> > > >> choice of close or debug.
> > > >> From that point on, the WMDC will not respond untill I terminate the sync
> > > >> host process or reboot.
> > > >>
> > > >> And yes I've got the latest version and tweaked the firewall and even
> > > >> turned
> > > >> firewall off. Uninstalled and reinstalled a dozen times.
> > > >>
> > > >> I did an upgrade to Vista so I suspect it has something to do with the
> > > >> leftovers from the previous installed Activesync in XP
> > > >>
> > > >> Here are the Event Viewer logs related to the WMDC crash.
> > > >>
> > > >> The description for Event ID 1000 from source Application Error cannot be
> > > >> found. Either the component that raises this event is not installed on
> > > >> your
> > > >> local computer or the installation is corrupted. You can install or
> > > >> repair
> > > >> the component on the local computer.
> > > >>
> > > >> If the event originated on another computer, the display information had
> > > >> to
> > > >> be saved with the event.
> > > >>
> > > >> The following information was included with the event:
> > > >>
> > > >> WmdHost.exe
> > > >>
> > > >> 6.0.6783.0
> > > >>
> > > >> 45b7b21a
> > > >>
> > > >> SPhNS_PC.dll
> > > >>
> > > >> 2.0.0.20
> > > >>
> > > >> 438dbe73
> > > >>
> > > >> c0000005
> > > >>
> > > >> 0000fa02
> > > >>
> > > >> --------------------------------------------------------------------------------------
> > > >>
> > > >> Fault bucket 376918087, type 1
> > > >>
> > > >> Event Name: APPCRASH
> > > >>
> > > >> Response: None
> > > >>
> > > >> Cab Id: 0
> > > >>
> > > >> Problem signature:
> > > >>
> > > >> P1: WmdHost.exe
> > > >>
> > > >> P2: 6.0.6783.0
> > > >>
> > > >> P3: 45b7b21a
> > > >>
> > > >> P4: SPhNS_PC.dll
> > > >>
> > > >> P5: 2.0.0.20
> > > >>
> > > >> P6: 438dbe73
> > > >>
> > > >> P7: c0000005
> > > >>
> > > >> P8: 0000fa02
> > > >>
> > > >> P9:
> > > >>
> > > >> P10:
> > > >>
> > > >> ----------------------------------------------------------------------------------------
> > > >>
> > > >> Faulting application WmdHost.exe, version 6.0.6783.0, time stamp
> > > >> 0x45b7b21a,
> > > >> faulting module SPhNS_PC.dll, version 2.0.0.20, time stamp 0x438dbe73,
> > > >> exception code 0xc0000005, fault offset 0x0000fa02, process id 0x1588,
> > > >> application start time 0x01c74d8579886025
> > > >>
> > >
> > >

when go through the "connect without setting up the device" menu and then try
to sync, here's error detail:
Error message:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.



************** Exception Text **************

System.NullReferenceException: Object reference not set to an instance of an
object.

at System.Runtime.InteropServices.Marshal.ReleaseComO bject(Object o)

at
Microsoft.WindowsMobile.DeviceCenter.NewPartnershi pWizard.Dispose(Boolean
disposing)

at System.ComponentModel.Component.Dispose()

at
Microsoft.WindowsMobile.DeviceCenter.SetupPartners hipFolderItem.OnClick(Object sender, AnimatedControlEventArgs e)

at
Microsoft.WindowsMobile.DeviceCenter.TextFolderIte mWrapper.TextFolderItemWrapper_Click(Object sender, AnimatedControlEventArgs e)

at AnimationLibrary.AnimatedControl.OnClick(Object sender,
AnimatedControlEventArgs e)

at AnimationLibrary.AnimatedControl.OnClick(Object sender,
AnimatedControlEventArgs e)

at AnimationLibrary.AnimatedControl.OnClick(Object sender,
AnimatedControlEventArgs e)

at AnimationLibrary.AnimatedLinkLabel.OnClick(Object sender,
AnimatedControlEventArgs e)

at AnimationLibrary.AnimatedControl.BubbleClick(Mouse EventArgs e)

at AnimationLibrary.AnimationHost.AnimationHost_Mouse Up(Object sender,
MouseEventArgs e)

at System.Windows.Forms.Control.OnMouseUp(MouseEventA rgs e)

at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
button, Int32 clicks)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ScrollableControl.WndProc(Mes sage& m)

at System.Windows.Forms.ContainerControl.WndProc(Mess age& m)

at System.Windows.Forms.UserControl.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)





************** Loaded Assemblies **************

mscorlib

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)

CodeBase:
file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

----------------------------------------

Microsoft.WindowsMobile.DeviceManager

Assembly Version: 6.0.0.0

Win32 Version: 6.0.6783.0

CodeBase:
file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceManager.DLL

----------------------------------------

Microsoft.WindowsMobile.Common

Assembly Version: 6.0.0.0

Win32 Version: 6.0.6783.0

CodeBase:
file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Common.DLL

----------------------------------------

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)

CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)

CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)

CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

System.Configuration

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)

CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

System.Xml

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)

CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

Microsoft.WindowsMobile.Rapi

Assembly Version: 6.0.0.0

Win32 Version: 6.0.6783.0

CodeBase:
file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Rapi.DLL

----------------------------------------

Microsoft.WindowsMobile.DeviceCenter

Assembly Version: 6.0.0.0

Win32 Version: 6.0.6783.0

CodeBase:
file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceCenter.DLL

----------------------------------------

AnimationLibrary

Assembly Version: 6.0.0.0

Win32 Version: 6.0.6783.0

CodeBase: file:///C:/Windows/WindowsMobile/AnimationLibrary.DLL

----------------------------------------

Accessibility

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)

CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

----------------------------------------

System.DirectoryServices

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)

CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.DirectoryServices/2.0.0.0__b03f5f7f11d50a3a/System.DirectoryServices.dll

----------------------------------------



************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.



For example:



<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>



When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.


"Steve Spiller [MSFT]" wrote:

> If you still hit problems, use the infomation found here to gather debug logs
> and send them along to me. This will also help us to make the experience in
> these situations better for end-users. (Is anything worse than a fatal
> exception??)
>
> http://www.pocketpcfaq.com/faqs/wmdc/debug/index.htm
>
> --
> Thanks,
> Steve
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
> "Kenwise" wrote:
>
> > Steve, i've got a program by Syncdata on there. i will uninstall and try
> > again. FYI, i just had two other friends take my device and connect it to
> > their Vista machines and it worked fine. i am stumped.
> >
> > "Steve Spiller [MSFT]" wrote:
> >
> > > Hello,
> > >
> > > I'm sorry to hear about the problems you're having with WMDC. We've seen
> > > several reports of this nature since we officially launched WMDC. Do you
> > > have any 3rd party software installed on your device? Specifically software
> > > that syncs or used to show settings in ActiveSync 4.x? If so, what are they.
> > >
> > > We spent a lot of time trying to ensure that 3rd party applications would
> > > work smoothly with WMDC, but 100% coverage is difficult to acheive. So we
> > > are working with 3rd party vendors to update their code as well as updating
> > > ours to be as robust as possible.
> > >
> > > Also, Windows Mobile Device Center is supposed to be fully supported by
> > > Microsoft Product Support. I'll contact a few people to make sure that
> > > customers aren't turned away again.
> > >
> > > --
> > > Thanks,
> > > Steve
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > >
> > >
> > >
> > > "Moishe Grunstein" wrote:
> > >
> > > > Same exact issue, already called Microsoft Support, they do not support it,
> > > > posted in the private partner newsgroup, they don't either support it.
> > > > Every time I open the Windows Mobile device center, and click setup your
> > > > device, I get a message Windows Mobile Device Center Sync Host has stopped
> > > > working, a problem caused the program to stop working correctly. Windows
> > > > will close the program and notify you if a solution is available. I have an
> > > > option debug and close program.
> > > > "Kenwise" <> wrote in message
> > > > news:8F1F7800-A931-41C4-B83D-...
> > > > > Steven, I am having the exact same experience and i, too, upgraded. When
> > > > > I
> > > > > click on "My computer" it shows a SGH-i607. However, WIndows MObility
> > > > > Center
> > > > > shows two devices. one is the i607 but is shows as a music player only.
> > > > > the
> > > > > other is an unidentified windows mobile device. Therefore, Vista seems to
> > > > > recognize the device differently in two different programs. there are
> > > > > some
> > > > > firewall changes you can make at
> > > > > www.pocketpcfaq.com/faqs/wmdc/firewall.htm.
> > > > > i haven't tried them yet. beyond that i don't know what to do. I have
> > > > > read
> > > > > some forums where people have not had a problem with the blackjack but i
> > > > > have
> > > > > been struggling with this for a week.
> > > > >
> > > > > "StevenW" wrote:
> > > > >
> > > > >> can't get it to work. I've tried all I know to do and searched
> > > > >> everywhere
> > > > >> for a solution.
> > > > >>
> > > > >> I get the WMDC setup screen. If I click on "Connect without setting up
> > > > >> your
> > > > >> device", I can browse my Blackjack just fine.
> > > > >>
> > > > >> As soon as I click on "Setup Your Device" , I get an immediate popup
> > > > >> saying"Windows Mobile Device Center Sync Host has stopped working" with a
> > > > >> choice of close or debug.
> > > > >> From that point on, the WMDC will not respond untill I terminate the sync
> > > > >> host process or reboot.
> > > > >>
> > > > >> And yes I've got the latest version and tweaked the firewall and even
> > > > >> turned
> > > > >> firewall off. Uninstalled and reinstalled a dozen times.
> > > > >>
> > > > >> I did an upgrade to Vista so I suspect it has something to do with the
> > > > >> leftovers from the previous installed Activesync in XP
> > > > >>
> > > > >> Here are the Event Viewer logs related to the WMDC crash.
> > > > >>
> > > > >> The description for Event ID 1000 from source Application Error cannot be
> > > > >> found. Either the component that raises this event is not installed on
> > > > >> your
> > > > >> local computer or the installation is corrupted. You can install or
> > > > >> repair
> > > > >> the component on the local computer.
> > > > >>
> > > > >> If the event originated on another computer, the display information had
> > > > >> to
> > > > >> be saved with the event.
> > > > >>
> > > > >> The following information was included with the event:
> > > > >>
> > > > >> WmdHost.exe
> > > > >>
> > > > >> 6.0.6783.0
> > > > >>
> > > > >> 45b7b21a
> > > > >>
> > > > >> SPhNS_PC.dll
> > > > >>
> > > > >> 2.0.0.20
> > > > >>
> > > > >> 438dbe73
> > > > >>
> > > > >> c0000005
> > > > >>
> > > > >> 0000fa02
> > > > >>
> > > > >> --------------------------------------------------------------------------------------
> > > > >>
> > > > >> Fault bucket 376918087, type 1
> > > > >>
> > > > >> Event Name: APPCRASH
> > > > >>
> > > > >> Response: None
> > > > >>
> > > > >> Cab Id: 0
> > > > >>
> > > > >> Problem signature:
> > > > >>
> > > > >> P1: WmdHost.exe
> > > > >>
> > > > >> P2: 6.0.6783.0
> > > > >>
> > > > >> P3: 45b7b21a
> > > > >>
> > > > >> P4: SPhNS_PC.dll
> > > > >>
> > > > >> P5: 2.0.0.20
> > > > >>
> > > > >> P6: 438dbe73
> > > > >>
> > > > >> P7: c0000005
> > > > >>
> > > > >> P8: 0000fa02
> > > > >>
> > > > >> P9:
> > > > >>
> > > > >> P10:
> > > > >>
> > > > >> ----------------------------------------------------------------------------------------
> > > > >>
> > > > >> Faulting application WmdHost.exe, version 6.0.6783.0, time stamp
> > > > >> 0x45b7b21a,
> > > > >> faulting module SPhNS_PC.dll, version 2.0.0.20, time stamp 0x438dbe73,
> > > > >> exception code 0xc0000005, fault offset 0x0000fa02, process id 0x1588,
> > > > >> application start time 0x01c74d8579886025
> > > > >>
> > > >
> > > >

Ok, i fixed it (Thanks Steve!). I deleted the third party note-syncing
program from my device and laptop. after that, sync went fine.

"Kenwise" wrote:

> when go through the "connect without setting up the device" menu and then try
> to sync, here's error detail:
> Error message:
>
> See the end of this message for details on invoking
>
> just-in-time (JIT) debugging instead of this dialog box.
>
>
>
> ************** Exception Text **************
>
> System.NullReferenceException: Object reference not set to an instance of an
> object.
>
> at System.Runtime.InteropServices.Marshal.ReleaseComO bject(Object o)
>
> at
> Microsoft.WindowsMobile.DeviceCenter.NewPartnershi pWizard.Dispose(Boolean
> disposing)
>
> at System.ComponentModel.Component.Dispose()
>
> at
> Microsoft.WindowsMobile.DeviceCenter.SetupPartners hipFolderItem.OnClick(Object sender, AnimatedControlEventArgs e)
>
> at
> Microsoft.WindowsMobile.DeviceCenter.TextFolderIte mWrapper.TextFolderItemWrapper_Click(Object sender, AnimatedControlEventArgs e)
>
> at AnimationLibrary.AnimatedControl.OnClick(Object sender,
> AnimatedControlEventArgs e)
>
> at AnimationLibrary.AnimatedControl.OnClick(Object sender,
> AnimatedControlEventArgs e)
>
> at AnimationLibrary.AnimatedControl.OnClick(Object sender,
> AnimatedControlEventArgs e)
>
> at AnimationLibrary.AnimatedLinkLabel.OnClick(Object sender,
> AnimatedControlEventArgs e)
>
> at AnimationLibrary.AnimatedControl.BubbleClick(Mouse EventArgs e)
>
> at AnimationLibrary.AnimationHost.AnimationHost_Mouse Up(Object sender,
> MouseEventArgs e)
>
> at System.Windows.Forms.Control.OnMouseUp(MouseEventA rgs e)
>
> at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
> button, Int32 clicks)
>
> at System.Windows.Forms.Control.WndProc(Message& m)
>
> at System.Windows.Forms.ScrollableControl.WndProc(Mes sage& m)
>
> at System.Windows.Forms.ContainerControl.WndProc(Mess age& m)
>
> at System.Windows.Forms.UserControl.WndProc(Message& m)
>
> at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
>
> at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
>
> at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
> IntPtr wparam, IntPtr lparam)
>
>
>
>
>
> ************** Loaded Assemblies **************
>
> mscorlib
>
> Assembly Version: 2.0.0.0
>
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>
> CodeBase:
> file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
>
> ----------------------------------------
>
> Microsoft.WindowsMobile.DeviceManager
>
> Assembly Version: 6.0.0.0
>
> Win32 Version: 6.0.6783.0
>
> CodeBase:
> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceManager.DLL
>
> ----------------------------------------
>
> Microsoft.WindowsMobile.Common
>
> Assembly Version: 6.0.0.0
>
> Win32 Version: 6.0.6783.0
>
> CodeBase:
> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Common.DLL
>
> ----------------------------------------
>
> System
>
> Assembly Version: 2.0.0.0
>
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
>
> ----------------------------------------
>
> System.Windows.Forms
>
> Assembly Version: 2.0.0.0
>
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
>
> ----------------------------------------
>
> System.Drawing
>
> Assembly Version: 2.0.0.0
>
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
>
> ----------------------------------------
>
> System.Configuration
>
> Assembly Version: 2.0.0.0
>
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
>
> ----------------------------------------
>
> System.Xml
>
> Assembly Version: 2.0.0.0
>
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
>
> ----------------------------------------
>
> Microsoft.WindowsMobile.Rapi
>
> Assembly Version: 6.0.0.0
>
> Win32 Version: 6.0.6783.0
>
> CodeBase:
> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Rapi.DLL
>
> ----------------------------------------
>
> Microsoft.WindowsMobile.DeviceCenter
>
> Assembly Version: 6.0.0.0
>
> Win32 Version: 6.0.6783.0
>
> CodeBase:
> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceCenter.DLL
>
> ----------------------------------------
>
> AnimationLibrary
>
> Assembly Version: 6.0.0.0
>
> Win32 Version: 6.0.6783.0
>
> CodeBase: file:///C:/Windows/WindowsMobile/AnimationLibrary.DLL
>
> ----------------------------------------
>
> Accessibility
>
> Assembly Version: 2.0.0.0
>
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
>
> ----------------------------------------
>
> System.DirectoryServices
>
> Assembly Version: 2.0.0.0
>
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.DirectoryServices/2.0.0.0__b03f5f7f11d50a3a/System.DirectoryServices.dll
>
> ----------------------------------------
>
>
>
> ************** JIT Debugging **************
>
> To enable just-in-time (JIT) debugging, the .config file for this
>
> application or computer (machine.config) must have the
>
> jitDebugging value set in the system.windows.forms section.
>
> The application must also be compiled with debugging
>
> enabled.
>
>
>
> For example:
>
>
>
> <configuration>
>
> <system.windows.forms jitDebugging="true" />
>
> </configuration>
>
>
>
> When JIT debugging is enabled, any unhandled exception
>
> will be sent to the JIT debugger registered on the computer
>
> rather than be handled by this dialog box.
>
>
> "Steve Spiller [MSFT]" wrote:
>
> > If you still hit problems, use the infomation found here to gather debug logs
> > and send them along to me. This will also help us to make the experience in
> > these situations better for end-users. (Is anything worse than a fatal
> > exception??)
> >
> > http://www.pocketpcfaq.com/faqs/wmdc/debug/index.htm
> >
> > --
> > Thanks,
> > Steve
> >
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> >
> > "Kenwise" wrote:
> >
> > > Steve, i've got a program by Syncdata on there. i will uninstall and try
> > > again. FYI, i just had two other friends take my device and connect it to
> > > their Vista machines and it worked fine. i am stumped.
> > >
> > > "Steve Spiller [MSFT]" wrote:
> > >
> > > > Hello,
> > > >
> > > > I'm sorry to hear about the problems you're having with WMDC. We've seen
> > > > several reports of this nature since we officially launched WMDC. Do you
> > > > have any 3rd party software installed on your device? Specifically software
> > > > that syncs or used to show settings in ActiveSync 4.x? If so, what are they.
> > > >
> > > > We spent a lot of time trying to ensure that 3rd party applications would
> > > > work smoothly with WMDC, but 100% coverage is difficult to acheive. So we
> > > > are working with 3rd party vendors to update their code as well as updating
> > > > ours to be as robust as possible.
> > > >
> > > > Also, Windows Mobile Device Center is supposed to be fully supported by
> > > > Microsoft Product Support. I'll contact a few people to make sure that
> > > > customers aren't turned away again.
> > > >
> > > > --
> > > > Thanks,
> > > > Steve
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > > >
> > > >
> > > >
> > > > "Moishe Grunstein" wrote:
> > > >

I hard reset my device and I am still having the problem, I don't have any
third party mobile software on my computer, although, activesync may have
had some 3rd party programs on the list prior to the upgrade.
"Kenwise" <> wrote in message
news:89788F02-B9EE-44CB-93EA-...
> Ok, i fixed it (Thanks Steve!). I deleted the third party note-syncing
> program from my device and laptop. after that, sync went fine.
>
> "Kenwise" wrote:
>
>> when go through the "connect without setting up the device" menu and then
>> try
>> to sync, here's error detail:
>> Error message:
>>
>> See the end of this message for details on invoking
>>
>> just-in-time (JIT) debugging instead of this dialog box.
>>
>>
>>
>> ************** Exception Text **************
>>
>> System.NullReferenceException: Object reference not set to an instance of
>> an
>> object.
>>
>> at System.Runtime.InteropServices.Marshal.ReleaseComO bject(Object o)
>>
>> at
>> Microsoft.WindowsMobile.DeviceCenter.NewPartnershi pWizard.Dispose(Boolean
>> disposing)
>>
>> at System.ComponentModel.Component.Dispose()
>>
>> at
>> Microsoft.WindowsMobile.DeviceCenter.SetupPartners hipFolderItem.OnClick(Object
>> sender, AnimatedControlEventArgs e)
>>
>> at
>> Microsoft.WindowsMobile.DeviceCenter.TextFolderIte mWrapper.TextFolderItemWrapper_Click(Object
>> sender, AnimatedControlEventArgs e)
>>
>> at AnimationLibrary.AnimatedControl.OnClick(Object sender,
>> AnimatedControlEventArgs e)
>>
>> at AnimationLibrary.AnimatedControl.OnClick(Object sender,
>> AnimatedControlEventArgs e)
>>
>> at AnimationLibrary.AnimatedControl.OnClick(Object sender,
>> AnimatedControlEventArgs e)
>>
>> at AnimationLibrary.AnimatedLinkLabel.OnClick(Object sender,
>> AnimatedControlEventArgs e)
>>
>> at AnimationLibrary.AnimatedControl.BubbleClick(Mouse EventArgs e)
>>
>> at AnimationLibrary.AnimationHost.AnimationHost_Mouse Up(Object sender,
>> MouseEventArgs e)
>>
>> at System.Windows.Forms.Control.OnMouseUp(MouseEventA rgs e)
>>
>> at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
>> button, Int32 clicks)
>>
>> at System.Windows.Forms.Control.WndProc(Message& m)
>>
>> at System.Windows.Forms.ScrollableControl.WndProc(Mes sage& m)
>>
>> at System.Windows.Forms.ContainerControl.WndProc(Mess age& m)
>>
>> at System.Windows.Forms.UserControl.WndProc(Message& m)
>>
>> at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message&
>> m)
>>
>> at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message&
>> m)
>>
>> at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
>> IntPtr wparam, IntPtr lparam)
>>
>>
>>
>>
>>
>> ************** Loaded Assemblies **************
>>
>> mscorlib
>>
>> Assembly Version: 2.0.0.0
>>
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>
>> CodeBase:
>> file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
>>
>> ----------------------------------------
>>
>> Microsoft.WindowsMobile.DeviceManager
>>
>> Assembly Version: 6.0.0.0
>>
>> Win32 Version: 6.0.6783.0
>>
>> CodeBase:
>> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceManager.DLL
>>
>> ----------------------------------------
>>
>> Microsoft.WindowsMobile.Common
>>
>> Assembly Version: 6.0.0.0
>>
>> Win32 Version: 6.0.6783.0
>>
>> CodeBase:
>> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Common.DLL
>>
>> ----------------------------------------
>>
>> System
>>
>> Assembly Version: 2.0.0.0
>>
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>
>> CodeBase:
>> file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
>>
>> ----------------------------------------
>>
>> System.Windows.Forms
>>
>> Assembly Version: 2.0.0.0
>>
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>
>> CodeBase:
>> file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
>>
>> ----------------------------------------
>>
>> System.Drawing
>>
>> Assembly Version: 2.0.0.0
>>
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>
>> CodeBase:
>> file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
>>
>> ----------------------------------------
>>
>> System.Configuration
>>
>> Assembly Version: 2.0.0.0
>>
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>
>> CodeBase:
>> file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
>>
>> ----------------------------------------
>>
>> System.Xml
>>
>> Assembly Version: 2.0.0.0
>>
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>
>> CodeBase:
>> file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
>>
>> ----------------------------------------
>>
>> Microsoft.WindowsMobile.Rapi
>>
>> Assembly Version: 6.0.0.0
>>
>> Win32 Version: 6.0.6783.0
>>
>> CodeBase:
>> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Rapi.DLL
>>
>> ----------------------------------------
>>
>> Microsoft.WindowsMobile.DeviceCenter
>>
>> Assembly Version: 6.0.0.0
>>
>> Win32 Version: 6.0.6783.0
>>
>> CodeBase:
>> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceCenter.DLL
>>
>> ----------------------------------------
>>
>> AnimationLibrary
>>
>> Assembly Version: 6.0.0.0
>>
>> Win32 Version: 6.0.6783.0
>>
>> CodeBase: file:///C:/Windows/WindowsMobile/AnimationLibrary.DLL
>>
>> ----------------------------------------
>>
>> Accessibility
>>
>> Assembly Version: 2.0.0.0
>>
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>
>> CodeBase:
>> file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
>>
>> ----------------------------------------
>>
>> System.DirectoryServices
>>
>> Assembly Version: 2.0.0.0
>>
>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>
>> CodeBase:
>> file:///C:/Windows/assembly/GAC_MSIL/System.DirectoryServices/2.0.0.0__b03f5f7f11d50a3a/System.DirectoryServices.dll
>>
>> ----------------------------------------
>>
>>
>>
>> ************** JIT Debugging **************
>>
>> To enable just-in-time (JIT) debugging, the .config file for this
>>
>> application or computer (machine.config) must have the
>>
>> jitDebugging value set in the system.windows.forms section.
>>
>> The application must also be compiled with debugging
>>
>> enabled.
>>
>>
>>
>> For example:
>>
>>
>>
>> <configuration>
>>
>> <system.windows.forms jitDebugging="true" />
>>
>> </configuration>
>>
>>
>>
>> When JIT debugging is enabled, any unhandled exception
>>
>> will be sent to the JIT debugger registered on the computer
>>
>> rather than be handled by this dialog box.
>>
>>
>> "Steve Spiller [MSFT]" wrote:
>>
>> > If you still hit problems, use the infomation found here to gather
>> > debug logs
>> > and send them along to me. This will also help us to make the
>> > experience in
>> > these situations better for end-users. (Is anything worse than a fatal
>> > exception??)
>> >
>> > http://www.pocketpcfaq.com/faqs/wmdc/debug/index.htm
>> >
>> > --
>> > Thanks,
>> > Steve
>> >
>> > This posting is provided "AS IS" with no warranties, and confers no
>> > rights.
>> >
>> >
>> >
>> > "Kenwise" wrote:
>> >
>> > > Steve, i've got a program by Syncdata on there. i will uninstall and
>> > > try
>> > > again. FYI, i just had two other friends take my device and connect
>> > > it to
>> > > their Vista machines and it worked fine. i am stumped.
>> > >
>> > > "Steve Spiller [MSFT]" wrote:
>> > >
>> > > > Hello,
>> > > >
>> > > > I'm sorry to hear about the problems you're having with WMDC.
>> > > > We've seen
>> > > > several reports of this nature since we officially launched WMDC.
>> > > > Do you
>> > > > have any 3rd party software installed on your device? Specifically
>> > > > software
>> > > > that syncs or used to show settings in ActiveSync 4.x? If so, what
>> > > > are they.
>> > > >
>> > > > We spent a lot of time trying to ensure that 3rd party applications
>> > > > would
>> > > > work smoothly with WMDC, but 100% coverage is difficult to acheive.
>> > > > So we
>> > > > are working with 3rd party vendors to update their code as well as
>> > > > updating
>> > > > ours to be as robust as possible.
>> > > >
>> > > > Also, Windows Mobile Device Center is supposed to be fully
>> > > > supported by
>> > > > Microsoft Product Support. I'll contact a few people to make sure
>> > > > that
>> > > > customers aren't turned away again.
>> > > >
>> > > > --
>> > > > Thanks,
>> > > > Steve
>> > > >
>> > > > This posting is provided "AS IS" with no warranties, and confers no
>> > > > rights.
>> > > >
>> > > >
>> > > >
>> > > > "Moishe Grunstein" wrote:
>> > > >

debug logs attached.
Thanks,
"Moishe Grunstein" <> wrote in message
news:...
>I hard reset my device and I am still having the problem, I don't have any
>third party mobile software on my computer, although, activesync may have
>had some 3rd party programs on the list prior to the upgrade.
> "Kenwise" <> wrote in message
> news:89788F02-B9EE-44CB-93EA-...
>> Ok, i fixed it (Thanks Steve!). I deleted the third party note-syncing
>> program from my device and laptop. after that, sync went fine.
>>
>> "Kenwise" wrote:
>>
>>> when go through the "connect without setting up the device" menu and
>>> then try
>>> to sync, here's error detail:
>>> Error message:
>>>
>>> See the end of this message for details on invoking
>>>
>>> just-in-time (JIT) debugging instead of this dialog box.
>>>
>>>
>>>
>>> ************** Exception Text **************
>>>
>>> System.NullReferenceException: Object reference not set to an instance
>>> of an
>>> object.
>>>
>>> at System.Runtime.InteropServices.Marshal.ReleaseComO bject(Object o)
>>>
>>> at
>>> Microsoft.WindowsMobile.DeviceCenter.NewPartnershi pWizard.Dispose(Boolean
>>> disposing)
>>>
>>> at System.ComponentModel.Component.Dispose()
>>>
>>> at
>>> Microsoft.WindowsMobile.DeviceCenter.SetupPartners hipFolderItem.OnClick(Object
>>> sender, AnimatedControlEventArgs e)
>>>
>>> at
>>> Microsoft.WindowsMobile.DeviceCenter.TextFolderIte mWrapper.TextFolderItemWrapper_Click(Object
>>> sender, AnimatedControlEventArgs e)
>>>
>>> at AnimationLibrary.AnimatedControl.OnClick(Object sender,
>>> AnimatedControlEventArgs e)
>>>
>>> at AnimationLibrary.AnimatedControl.OnClick(Object sender,
>>> AnimatedControlEventArgs e)
>>>
>>> at AnimationLibrary.AnimatedControl.OnClick(Object sender,
>>> AnimatedControlEventArgs e)
>>>
>>> at AnimationLibrary.AnimatedLinkLabel.OnClick(Object sender,
>>> AnimatedControlEventArgs e)
>>>
>>> at AnimationLibrary.AnimatedControl.BubbleClick(Mouse EventArgs e)
>>>
>>> at AnimationLibrary.AnimationHost.AnimationHost_Mouse Up(Object
>>> sender,
>>> MouseEventArgs e)
>>>
>>> at System.Windows.Forms.Control.OnMouseUp(MouseEventA rgs e)
>>>
>>> at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
>>> button, Int32 clicks)
>>>
>>> at System.Windows.Forms.Control.WndProc(Message& m)
>>>
>>> at System.Windows.Forms.ScrollableControl.WndProc(Mes sage& m)
>>>
>>> at System.Windows.Forms.ContainerControl.WndProc(Mess age& m)
>>>
>>> at System.Windows.Forms.UserControl.WndProc(Message& m)
>>>
>>> at
>>> System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
>>>
>>> at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message&
>>> m)
>>>
>>> at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
>>> IntPtr wparam, IntPtr lparam)
>>>
>>>
>>>
>>>
>>>
>>> ************** Loaded Assemblies **************
>>>
>>> mscorlib
>>>
>>> Assembly Version: 2.0.0.0
>>>
>>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>>
>>> CodeBase:
>>> file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
>>>
>>> ----------------------------------------
>>>
>>> Microsoft.WindowsMobile.DeviceManager
>>>
>>> Assembly Version: 6.0.0.0
>>>
>>> Win32 Version: 6.0.6783.0
>>>
>>> CodeBase:
>>> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceManager.DLL
>>>
>>> ----------------------------------------
>>>
>>> Microsoft.WindowsMobile.Common
>>>
>>> Assembly Version: 6.0.0.0
>>>
>>> Win32 Version: 6.0.6783.0
>>>
>>> CodeBase:
>>> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Common.DLL
>>>
>>> ----------------------------------------
>>>
>>> System
>>>
>>> Assembly Version: 2.0.0.0
>>>
>>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>>
>>> CodeBase:
>>> file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
>>>
>>> ----------------------------------------
>>>
>>> System.Windows.Forms
>>>
>>> Assembly Version: 2.0.0.0
>>>
>>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>>
>>> CodeBase:
>>> file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
>>>
>>> ----------------------------------------
>>>
>>> System.Drawing
>>>
>>> Assembly Version: 2.0.0.0
>>>
>>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>>
>>> CodeBase:
>>> file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
>>>
>>> ----------------------------------------
>>>
>>> System.Configuration
>>>
>>> Assembly Version: 2.0.0.0
>>>
>>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>>
>>> CodeBase:
>>> file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
>>>
>>> ----------------------------------------
>>>
>>> System.Xml
>>>
>>> Assembly Version: 2.0.0.0
>>>
>>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>>
>>> CodeBase:
>>> file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
>>>
>>> ----------------------------------------
>>>
>>> Microsoft.WindowsMobile.Rapi
>>>
>>> Assembly Version: 6.0.0.0
>>>
>>> Win32 Version: 6.0.6783.0
>>>
>>> CodeBase:
>>> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Rapi.DLL
>>>
>>> ----------------------------------------
>>>
>>> Microsoft.WindowsMobile.DeviceCenter
>>>
>>> Assembly Version: 6.0.0.0
>>>
>>> Win32 Version: 6.0.6783.0
>>>
>>> CodeBase:
>>> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceCenter.DLL
>>>
>>> ----------------------------------------
>>>
>>> AnimationLibrary
>>>
>>> Assembly Version: 6.0.0.0
>>>
>>> Win32 Version: 6.0.6783.0
>>>
>>> CodeBase: file:///C:/Windows/WindowsMobile/AnimationLibrary.DLL
>>>
>>> ----------------------------------------
>>>
>>> Accessibility
>>>
>>> Assembly Version: 2.0.0.0
>>>
>>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>>
>>> CodeBase:
>>> file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
>>>
>>> ----------------------------------------
>>>
>>> System.DirectoryServices
>>>
>>> Assembly Version: 2.0.0.0
>>>
>>> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
>>>
>>> CodeBase:
>>> file:///C:/Windows/assembly/GAC_MSIL/System.DirectoryServices/2.0.0.0__b03f5f7f11d50a3a/System.DirectoryServices.dll
>>>
>>> ----------------------------------------
>>>
>>>
>>>
>>> ************** JIT Debugging **************
>>>
>>> To enable just-in-time (JIT) debugging, the .config file for this
>>>
>>> application or computer (machine.config) must have the
>>>
>>> jitDebugging value set in the system.windows.forms section.
>>>
>>> The application must also be compiled with debugging
>>>
>>> enabled.
>>>
>>>
>>>
>>> For example:
>>>
>>>
>>>
>>> <configuration>
>>>
>>> <system.windows.forms jitDebugging="true" />
>>>
>>> </configuration>
>>>
>>>
>>>
>>> When JIT debugging is enabled, any unhandled exception
>>>
>>> will be sent to the JIT debugger registered on the computer
>>>
>>> rather than be handled by this dialog box.
>>>
>>>
>>> "Steve Spiller [MSFT]" wrote:
>>>
>>> > If you still hit problems, use the infomation found here to gather
>>> > debug logs
>>> > and send them along to me. This will also help us to make the
>>> > experience in
>>> > these situations better for end-users. (Is anything worse than a
>>> > fatal
>>> > exception??)
>>> >
>>> > http://www.pocketpcfaq.com/faqs/wmdc/debug/index.htm
>>> >
>>> > --
>>> > Thanks,
>>> > Steve
>>> >
>>> > This posting is provided "AS IS" with no warranties, and confers no
>>> > rights.
>>> >
>>> >
>>> >
>>> > "Kenwise" wrote:
>>> >
>>> > > Steve, i've got a program by Syncdata on there. i will uninstall
>>> > > and try
>>> > > again. FYI, i just had two other friends take my device and connect
>>> > > it to
>>> > > their Vista machines and it worked fine. i am stumped.
>>> > >
>>> > > "Steve Spiller [MSFT]" wrote:
>>> > >
>>> > > > Hello,
>>> > > >
>>> > > > I'm sorry to hear about the problems you're having with WMDC.
>>> > > > We've seen
>>> > > > several reports of this nature since we officially launched WMDC.
>>> > > > Do you
>>> > > > have any 3rd party software installed on your device?
>>> > > > Specifically software
>>> > > > that syncs or used to show settings in ActiveSync 4.x? If so,
>>> > > > what are they.
>>> > > >
>>> > > > We spent a lot of time trying to ensure that 3rd party
>>> > > > applications would
>>> > > > work smoothly with WMDC, but 100% coverage is difficult to
>>> > > > acheive. So we
>>> > > > are working with 3rd party vendors to update their code as well as
>>> > > > updating
>>> > > > ours to be as robust as possible.
>>> > > >
>>> > > > Also, Windows Mobile Device Center is supposed to be fully
>>> > > > supported by
>>> > > > Microsoft Product Support. I'll contact a few people to make sure
>>> > > > that
>>> > > > customers aren't turned away again.
>>> > > >
>>> > > > --
>>> > > > Thanks,
>>> > > > Steve
>>> > > >
>>> > > > This posting is provided "AS IS" with no warranties, and confers
>>> > > > no rights.
>>> > > >
>>> > > >
>>> > > >
>>> > > > "Moishe Grunstein" wrote:
>>> > > >
>