WMDC not syncing

I have done lots of research but can't find a solution to this:

A UK Orange E650 (HTC S710). WMDC recognises a device attached but fails
to sync. Device not visible in computer or media player. Device is in
device manager.

Have tried switching to serial. Have reinstalled WMDC several times. In
event log when trying to connect it comes up as a Rapimgr error 8 (WMDC
received a connection from the device, but something failed during the
connection protocol.)

I have enabled suggested ports in the firewall....but the event log seems to
suggest that Rapimgr is causing a problem with the connection. How can I add
the rapimgr.dll to the firewall exceptions? Is it the likely cause of
stopping my phone syncing? The phone connected to XP and Activesync straight
away with no problem...

Cheers,
--
Ben

Hello,

Can you tell me which version of WMDC you're using? The latest is 6.1.

Usually switching to serial will fix the problem. The rapimgr event 8 is
caused when we send a UDP packet to the device asking it to connect back on
port 990 and the device is blocked from doing so.

There's a lot of good information here that may help with troublshooting,
including the Firewall settings:
http://www.pocketpcfaq.com/faqs/wmdc/index.htm


--
Thanks,

Steve Spiller
Development Lead
Windows Mobile Device Center

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

"Ben" <> wrote in message
news:E74F0134-8833-475F-87E5-...
>I have done lots of research but can't find a solution to this:
>
> A UK Orange E650 (HTC S710). WMDC recognises a device attached but fails
> to sync. Device not visible in computer or media player. Device is in
> device manager.
>
> Have tried switching to serial. Have reinstalled WMDC several times. In
> event log when trying to connect it comes up as a Rapimgr error 8 (WMDC
> received a connection from the device, but something failed during the
> connection protocol.)
>
> I have enabled suggested ports in the firewall....but the event log seems
> to
> suggest that Rapimgr is causing a problem with the connection. How can I
> add
> the rapimgr.dll to the firewall exceptions? Is it the likely cause of
> stopping my phone syncing? The phone connected to XP and Activesync
> straight
> away with no problem...
>
> Cheers,
> --
> Ben

Hi Steve. Thanks for your reply. I'm using version 6.1. I have tried
switching the device to serial several times...but to no avail.

I have enabled port 990 on the firewall (along with all other recommended
ports from the website you pointed me at - been there, very useful, but
didn't solve the problem.) It certainly looks like it is being blocked in
some way...WMDC says connecting, then stops and says 'not connected', but has
recognised my device is called Ben...so obviously had some sort of contact.
It just won't initiate the partnership set up. Also now getting a WcesComm
error 4 - even though it is only my phone plugged in to usb...(removed
everything in case of conflict.)

I am considering a hard reset of the device, followed by if necessary (but
not really wanting to) a reinstall of Vista. Would either of these be worth
doing or do you have any other ideas? It is quite frustrating!
--
Ben


"Steve Spiller [MSFT]" wrote:

> Hello,
>
> Can you tell me which version of WMDC you're using? The latest is 6.1.
>
> Usually switching to serial will fix the problem. The rapimgr event 8 is
> caused when we send a UDP packet to the device asking it to connect back on
> port 990 and the device is blocked from doing so.
>
> There's a lot of good information here that may help with troublshooting,
> including the Firewall settings:
> http://www.pocketpcfaq.com/faqs/wmdc/index.htm
>
>
> --
> Thanks,
>
> Steve Spiller
> Development Lead
> Windows Mobile Device Center
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Ben" <> wrote in message
> news:E74F0134-8833-475F-87E5-...
> >I have done lots of research but can't find a solution to this:
> >
> > A UK Orange E650 (HTC S710). WMDC recognises a device attached but fails
> > to sync. Device not visible in computer or media player. Device is in
> > device manager.
> >
> > Have tried switching to serial. Have reinstalled WMDC several times. In
> > event log when trying to connect it comes up as a Rapimgr error 8 (WMDC
> > received a connection from the device, but something failed during the
> > connection protocol.)
> >
> > I have enabled suggested ports in the firewall....but the event log seems
> > to
> > suggest that Rapimgr is causing a problem with the connection. How can I
> > add
> > the rapimgr.dll to the firewall exceptions? Is it the likely cause of
> > stopping my phone syncing? The phone connected to XP and Activesync
> > straight
> > away with no problem...
> >
> > Cheers,
> > --
> > Ben
>
>

Sometimes a hard reset of the device does help, but shouldn't be necessary.
And you should never have to reinstall Vista because of WMDC. Sometimes
uninstalling and reinstalling WMDC helps, though.

Which firewall are you using? You should never get that multiple-devices
connected error unless you have two unique Windows Mobile devices connected.

Also, on that same site is a set of instructions for generating debug logs
for WMDC. Go ahead and do that. Maybe there will be something in there
that points to the issue you're seeing.

--
Thanks,

Steve Spiller
Development Lead
Windows Mobile Device Center

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

"Ben" <> wrote in message
news:65CC48A5-1BFA-435B-84DE-...
> Hi Steve. Thanks for your reply. I'm using version 6.1. I have tried
> switching the device to serial several times...but to no avail.
>
> I have enabled port 990 on the firewall (along with all other recommended
> ports from the website you pointed me at - been there, very useful, but
> didn't solve the problem.) It certainly looks like it is being blocked in
> some way...WMDC says connecting, then stops and says 'not connected', but
> has
> recognised my device is called Ben...so obviously had some sort of
> contact.
> It just won't initiate the partnership set up. Also now getting a
> WcesComm
> error 4 - even though it is only my phone plugged in to usb...(removed
> everything in case of conflict.)
>
> I am considering a hard reset of the device, followed by if necessary (but
> not really wanting to) a reinstall of Vista. Would either of these be
> worth
> doing or do you have any other ideas? It is quite frustrating!
> --
> Ben
>
>
> "Steve Spiller [MSFT]" wrote:
>
>> Hello,
>>
>> Can you tell me which version of WMDC you're using? The latest is 6.1.
>>
>> Usually switching to serial will fix the problem. The rapimgr event 8 is
>> caused when we send a UDP packet to the device asking it to connect back
>> on
>> port 990 and the device is blocked from doing so.
>>
>> There's a lot of good information here that may help with troublshooting,
>> including the Firewall settings:
>> http://www.pocketpcfaq.com/faqs/wmdc/index.htm
>>
>>
>> --
>> Thanks,
>>
>> Steve Spiller
>> Development Lead
>> Windows Mobile Device Center
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Ben" <> wrote in message
>> news:E74F0134-8833-475F-87E5-...
>> >I have done lots of research but can't find a solution to this:
>> >
>> > A UK Orange E650 (HTC S710). WMDC recognises a device attached but
>> > fails
>> > to sync. Device not visible in computer or media player. Device is in
>> > device manager.
>> >
>> > Have tried switching to serial. Have reinstalled WMDC several times.
>> > In
>> > event log when trying to connect it comes up as a Rapimgr error 8 (WMDC
>> > received a connection from the device, but something failed during the
>> > connection protocol.)
>> >
>> > I have enabled suggested ports in the firewall....but the event log
>> > seems
>> > to
>> > suggest that Rapimgr is causing a problem with the connection. How can
>> > I
>> > add
>> > the rapimgr.dll to the firewall exceptions? Is it the likely cause of
>> > stopping my phone syncing? The phone connected to XP and Activesync
>> > straight
>> > away with no problem...
>> >
>> > Cheers,
>> > --
>> > Ben
>>
>>

Steve, have tried several reinstalls of WMDC all to version 6.1. No change.

I am using Zonealarm free. Have enabled all the .exe files and the .dll
files that wmdc seems to want:
wcescomm.dll
rapimgr.dll
ceappmgr.exe
svchost.exe
windowsmobile.rapi.dll
wmdsync.exe
wmdsyncman.dll
wmdhost.exe
wmdc.exe

Not now getting wcescomm error of multiple devices following reboot; still
getting rapimgr error 8 though. Uninstalling/disabling firewalls doesn't
make any difference.

I have tried following the instructions on the website given, but the logs
don't generate as expected by the instructions - no sign of them anywhere...
:-/

Just noticed that the phone is visible for a little while - about 30 seconds
- under computer staight after connecting...can browse the phone too - but
then it just disappears from the menu...at exactly the same time as WMDC says
'not connected'

Cheers Steve,

--
Ben


"Steve Spiller [MSFT]" wrote:

> Sometimes a hard reset of the device does help, but shouldn't be necessary.
> And you should never have to reinstall Vista because of WMDC. Sometimes
> uninstalling and reinstalling WMDC helps, though.
>
> Which firewall are you using? You should never get that multiple-devices
> connected error unless you have two unique Windows Mobile devices connected.
>
> Also, on that same site is a set of instructions for generating debug logs
> for WMDC. Go ahead and do that. Maybe there will be something in there
> that points to the issue you're seeing.
>
> --
> Thanks,
>
> Steve Spiller
> Development Lead
> Windows Mobile Device Center
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Ben" <> wrote in message
> news:65CC48A5-1BFA-435B-84DE-...
> > Hi Steve. Thanks for your reply. I'm using version 6.1. I have tried
> > switching the device to serial several times...but to no avail.
> >
> > I have enabled port 990 on the firewall (along with all other recommended
> > ports from the website you pointed me at - been there, very useful, but
> > didn't solve the problem.) It certainly looks like it is being blocked in
> > some way...WMDC says connecting, then stops and says 'not connected', but
> > has
> > recognised my device is called Ben...so obviously had some sort of
> > contact.
> > It just won't initiate the partnership set up. Also now getting a
> > WcesComm
> > error 4 - even though it is only my phone plugged in to usb...(removed
> > everything in case of conflict.)
> >
> > I am considering a hard reset of the device, followed by if necessary (but
> > not really wanting to) a reinstall of Vista. Would either of these be
> > worth
> > doing or do you have any other ideas? It is quite frustrating!
> > --
> > Ben
> >
> >
> > "Steve Spiller [MSFT]" wrote:
> >
> >> Hello,
> >>
> >> Can you tell me which version of WMDC you're using? The latest is 6.1.
> >>
> >> Usually switching to serial will fix the problem. The rapimgr event 8 is
> >> caused when we send a UDP packet to the device asking it to connect back
> >> on
> >> port 990 and the device is blocked from doing so.
> >>
> >> There's a lot of good information here that may help with troublshooting,
> >> including the Firewall settings:
> >> http://www.pocketpcfaq.com/faqs/wmdc/index.htm
> >>
> >>
> >> --
> >> Thanks,
> >>
> >> Steve Spiller
> >> Development Lead
> >> Windows Mobile Device Center
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Ben" <> wrote in message
> >> news:E74F0134-8833-475F-87E5-...
> >> >I have done lots of research but can't find a solution to this:
> >> >
> >> > A UK Orange E650 (HTC S710). WMDC recognises a device attached but
> >> > fails
> >> > to sync. Device not visible in computer or media player. Device is in
> >> > device manager.
> >> >
> >> > Have tried switching to serial. Have reinstalled WMDC several times.
> >> > In
> >> > event log when trying to connect it comes up as a Rapimgr error 8 (WMDC
> >> > received a connection from the device, but something failed during the
> >> > connection protocol.)
> >> >
> >> > I have enabled suggested ports in the firewall....but the event log
> >> > seems
> >> > to
> >> > suggest that Rapimgr is causing a problem with the connection. How can
> >> > I
> >> > add
> >> > the rapimgr.dll to the firewall exceptions? Is it the likely cause of
> >> > stopping my phone syncing? The phone connected to XP and Activesync
> >> > straight
> >> > away with no problem...
> >> >
> >> > Cheers,
> >> > --
> >> > Ben
> >>
> >>
>
>

Did you try restarting after enabling the logging? If you're getting to the
point of the WMDC UI becoming visible, there will be logging. Without
getting the logs of the error condition I'm stumpped as to what might be
going on. I can honestly say I've never seen this issue before

--
Thanks,

Steve Spiller
Development Lead
Windows Mobile Device Center

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

"Ben" <> wrote in message
news:828D62E5-7F7D-4297-A756-...
> Steve, have tried several reinstalls of WMDC all to version 6.1. No
> change.
>
> I am using Zonealarm free. Have enabled all the .exe files and the .dll
> files that wmdc seems to want:
> wcescomm.dll
> rapimgr.dll
> ceappmgr.exe
> svchost.exe
> windowsmobile.rapi.dll
> wmdsync.exe
> wmdsyncman.dll
> wmdhost.exe
> wmdc.exe
>
> Not now getting wcescomm error of multiple devices following reboot; still
> getting rapimgr error 8 though. Uninstalling/disabling firewalls doesn't
> make any difference.
>
> I have tried following the instructions on the website given, but the logs
> don't generate as expected by the instructions - no sign of them
> anywhere...
> :-/
>
> Just noticed that the phone is visible for a little while - about 30
> seconds
> - under computer staight after connecting...can browse the phone too - but
> then it just disappears from the menu...at exactly the same time as WMDC
> says
> 'not connected'
>
> Cheers Steve,
>
> --
> Ben
>
>
> "Steve Spiller [MSFT]" wrote:
>
>> Sometimes a hard reset of the device does help, but shouldn't be
>> necessary.
>> And you should never have to reinstall Vista because of WMDC. Sometimes
>> uninstalling and reinstalling WMDC helps, though.
>>
>> Which firewall are you using? You should never get that multiple-devices
>> connected error unless you have two unique Windows Mobile devices
>> connected.
>>
>> Also, on that same site is a set of instructions for generating debug
>> logs
>> for WMDC. Go ahead and do that. Maybe there will be something in there
>> that points to the issue you're seeing.
>>
>> --
>> Thanks,
>>
>> Steve Spiller
>> Development Lead
>> Windows Mobile Device Center
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Ben" <> wrote in message
>> news:65CC48A5-1BFA-435B-84DE-...
>> > Hi Steve. Thanks for your reply. I'm using version 6.1. I have tried
>> > switching the device to serial several times...but to no avail.
>> >
>> > I have enabled port 990 on the firewall (along with all other
>> > recommended
>> > ports from the website you pointed me at - been there, very useful, but
>> > didn't solve the problem.) It certainly looks like it is being blocked
>> > in
>> > some way...WMDC says connecting, then stops and says 'not connected',
>> > but
>> > has
>> > recognised my device is called Ben...so obviously had some sort of
>> > contact.
>> > It just won't initiate the partnership set up. Also now getting a
>> > WcesComm
>> > error 4 - even though it is only my phone plugged in to usb...(removed
>> > everything in case of conflict.)
>> >
>> > I am considering a hard reset of the device, followed by if necessary
>> > (but
>> > not really wanting to) a reinstall of Vista. Would either of these be
>> > worth
>> > doing or do you have any other ideas? It is quite frustrating!
>> > --
>> > Ben
>> >
>> >
>> > "Steve Spiller [MSFT]" wrote:
>> >
>> >> Hello,
>> >>
>> >> Can you tell me which version of WMDC you're using? The latest is
>> >> 6.1.
>> >>
>> >> Usually switching to serial will fix the problem. The rapimgr event 8
>> >> is
>> >> caused when we send a UDP packet to the device asking it to connect
>> >> back
>> >> on
>> >> port 990 and the device is blocked from doing so.
>> >>
>> >> There's a lot of good information here that may help with
>> >> troublshooting,
>> >> including the Firewall settings:
>> >> http://www.pocketpcfaq.com/faqs/wmdc/index.htm
>> >>
>> >>
>> >> --
>> >> Thanks,
>> >>
>> >> Steve Spiller
>> >> Development Lead
>> >> Windows Mobile Device Center
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >> "Ben" <> wrote in message
>> >> news:E74F0134-8833-475F-87E5-...
>> >> >I have done lots of research but can't find a solution to this:
>> >> >
>> >> > A UK Orange E650 (HTC S710). WMDC recognises a device attached but
>> >> > fails
>> >> > to sync. Device not visible in computer or media player. Device is
>> >> > in
>> >> > device manager.
>> >> >
>> >> > Have tried switching to serial. Have reinstalled WMDC several
>> >> > times.
>> >> > In
>> >> > event log when trying to connect it comes up as a Rapimgr error 8
>> >> > (WMDC
>> >> > received a connection from the device, but something failed during
>> >> > the
>> >> > connection protocol.)
>> >> >
>> >> > I have enabled suggested ports in the firewall....but the event log
>> >> > seems
>> >> > to
>> >> > suggest that Rapimgr is causing a problem with the connection. How
>> >> > can
>> >> > I
>> >> > add
>> >> > the rapimgr.dll to the firewall exceptions? Is it the likely cause
>> >> > of
>> >> > stopping my phone syncing? The phone connected to XP and Activesync
>> >> > straight
>> >> > away with no problem...
>> >> >
>> >> > Cheers,
>> >> > --
>> >> > Ben
>> >>
>> >>
>>
>>

Steve,

Yes I restarted after doing it. Just to confirm - I copy and save the files
from the website to the windows/windowsmobile folder...? Then restart. Then
I should find the logs in the %temp\ folder...? There is certainly no sign
of them in the temp folder.

With no results, what I did instead was uninstalled WMDC again, deleted all
files I could associated with it (wouldn't let me do some .dlls and some
'MUI' files) then reinstalled wmdc. I then got the log file for installation
of that from windows/inf/setupapi.dev (copied below). Is this of use to you?
I attached the device whilst installing - then detached and re-attached the
device to initiate wmdc. It got to the bit saying 'please wait whilst wmdc
starts' then it hangs as before without getting a connection. Once again the
device appeared under 'computer', then disappeared after about 30 seconds.
HTH.

Ben

Log from windows/inf/setupappi.dev:

>>> [Device Install (Hardware initiated) - ActiveSyncWPDEnumerator\UMB\2&306b293b&0&ACTIVESYN CWPDDEVICE-C5C7610F-6346-E390-B9A5-F7C6113AA174-]
>>> Section start 2007/08/23 21:11:30.276
ump: Creating Install Process: DrvInst.exe 21:11:30.277
ndv: Retrieving device info...
ndv: Setting device parameters...
ndv: Building driver list...
dvi: {Build Driver List} 21:11:30.572
dvi: Searching for hardware ID(s):
dvi: tcpip\windows_mobile_device
dvi: Searching for compatible ID(s):
dvi: tcpip\windows_mobile_device
dvi: Enumerating INFs from path list 'C:\Windows\INF'
inf: Opened PNF:
'C:\Windows\System32\DriverStore\FileRepository\wp drapi.inf_3942e2cb\wpdrapi.inf' ([strings.0409] <src=drvstore>)
dvi: Created Driver Node:
dvi: HardwareID - TCPIP\WINDOWS_MOBILE_DEVICE
dvi: InfName -
C:\Windows\System32\DriverStore\FileRepository\wpd rapi.inf_3942e2cb\wpdrapi.inf
dvi: DevDesc - Windows Mobile device
dvi: DrvDesc - Windows Mobile device
dvi: Provider - Microsoft
dvi: Mfg - (Standard Windows Mobile devices)
dvi: ModelsSec - Microsoft.NTx86
dvi: InstallSec - WINDOWSMOBILE_WPD_DEVICE
dvi: ActualSec - WINDOWSMOBILE_WPD_DEVICE.NT
dvi: Rank - 0x0dff0000
dvi: Signer - microsoft windows
dvi: Signer Score - INBOX
dvi: DrvDate - 06/21/2006
dvi: Version - 6.0.6000.16386
inf: Opened PNF:
'C:\Windows\System32\DriverStore\FileRepository\wp drapi.inf_b2b04810\wpdrapi.inf' ([strings] <src=drvstore>)
dvi: Created Driver Node:
dvi: HardwareID - TCPIP\WINDOWS_MOBILE_DEVICE
dvi: InfName -
C:\Windows\System32\DriverStore\FileRepository\wpd rapi.inf_b2b04810\wpdrapi.inf
dvi: DevDesc - Windows Mobile-based device
dvi: DrvDesc - Windows Mobile-based device
dvi: Provider - Microsoft Corporation
dvi: Mfg - (Standard Windows Mobile devices)
dvi: ModelsSec - Microsoft.NTx86
dvi: InstallSec - WINDOWSMOBILE_WPD_DEVICE
dvi: ActualSec - WINDOWSMOBILE_WPD_DEVICE.NT
dvi: Rank - 0x0dff0000
dvi: Signer - microsoft windows hardware compatibility
publisher
dvi: Signer Score - WHQL
dvi: DrvDate - 05/31/2007
dvi: Version - 6.1.6965.0
inf: Searched 2 potential matches in published INF directory
inf: Searched 29 INFs in directory: 'C:\Windows\INF'
dvi: {Build Driver List - exit(0x00000000)} 21:11:30.737
ndv: Selecting best match...
dvi: {DIF_SELECTBESTCOMPATDRV} 21:11:30.738
dvi: Using exported function 'WpdClassInstaller' in module
'C:\Windows\system32\wpd_ci.dll'.
dvi: Class installer == wpd_ci.dll,WpdClassInstaller
dvi: Using exported function 'CoDeviceInstall' in module
'C:\Windows\system32\WUDFCoInstaller.dll'.
dvi: CoInstaller 1 == WUDFCoInstaller.dll
dvi: CoInstaller 1: Enter 21:11:30.810
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 21:11:30.811
dvi: Class installer: Exit
dvi: Default installer: Enter 21:11:30.813
dvi: {Select Best Driver}
dvi: Selected driver installs from section
[WINDOWSMOBILE_WPD_DEVICE] in
'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf'.
dvi: Class GUID of device remains:
{eec5ad98-8080-425f-922a-dabf3de3f69a}.
dvi: Set selected driver complete.
dvi: Selected:
dvi: Description - [Windows Mobile-based device]
dvi: InfFile -
[c:\windows\system32\driverstore\filerepository\wpd rapi.inf_b2b04810\wpdrapi.inf]
dvi: Section - [WINDOWSMOBILE_WPD_DEVICE]
dvi: Signer - [microsoft windows hardware
compatibility publisher]
dvi: Rank - [0x0dff0000]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 21:11:30.823
ndv: Driver selected, now performing install...
ndv: {Core Device Install}
inf: Opened PNF: 'C:\Windows\INF\oem9.inf' ([strings] <src=oempath>)
inf: Opened PNF: 'C:\Windows\INF\oem9.inf' ([strings] <src=oempath>)
dvi: {DIF_ALLOW_INSTALL} 21:11:30.895
dvi: CoInstaller 1: Enter 21:11:30.895
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 21:11:30.897
dvi: Class installer: Exit
dvi: Default installer: Enter 21:11:30.901
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 21:11:30.903
ndv: Installing files...
dvi: {DIF_INSTALLDEVICEFILES} 21:11:30.904
dvi: CoInstaller 1: Enter 21:11:30.905
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 21:11:30.906
dvi: Class installer: Exit
dvi: Default installer: Enter 21:11:30.908
dvi: {Install FILES}
inf: Opened PNF:
'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf' ([strings] <src=drvstore>)
inf: {Install Inf Section
[WINDOWSMOBILE_WPD_DEVICE.NT]}
inf: CopyFiles=WPDRAPIDRIVER_COMMON.Files.Core
(wpdrapi.inf line 41)
cpy: Open PnpLockdownPolicy: Err=2. This is
OK. Use LockDownPolicyDefault
flq: QueueSingleCopy...
flq: Inf :
'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf'
flq: SourceInf:
'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf'
flq: SourceSection: [sourcedisksfiles]
flq: Source root path based on SourceInf
flq: SourceRootPath:
'C:\Windows\System32\DriverStore\FileRepository\wp drapi.inf_b2b04810'
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x06000000
flq: SourceRootPath -
'C:\Windows\System32\DriverStore\FileRepository\wp drapi.inf_b2b04810'
flq: SourceFilename - 'WpdRapi.dll'
flq: TargetDirectory-
'C:\Windows\system32\DRIVERS\UMDF'
flq: TargetFilename - 'WpdRapi2.dll'
flq: SourceDesc - 'Windows Mobile
Device Center Media'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
inf: {Install Inf Section
[WINDOWSMOBILE_WPD_DEVICE.NT] exit (0x00000000)}
dvi: Processing co-installer registration section
[WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers].
inf: {Install Inf Section
[WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers]}
inf: No (Copy/Ren/Del)Files directives found
inf: {Install Inf Section
[WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers] exit (0x00000000)}
dvi: Co-installers registered.
dvi: {Install INTERFACES}
dvi: Installing section
[WINDOWSMOBILE_WPD_DEVICE.NT.Interfaces]
dvi: {Install INTERFACES exit 00000000}
dvi: {Install FILES exit (0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 21:11:30.935
ndv: Pruning file queue...
dvi: {_SCAN_FILE_QUEUE}
flq: ScanQ flags=620
flq: SPQ_SCAN_PRUNE_COPY_QUEUE
flq: SPQ_SCAN_FILE_COMPARISON
flq: SPQ_SCAN_ACTIVATE_DRP
flq: ScanQ number of copy nodes=1
flq: File 'C:\Windows\system32\DRIVERS\UMDF\WpdRapi2.dll'
pruned from copy.
sig: Using catalog
'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT'.
cpy: DrpSetRegFileProt
'C:\Windows\system32\DRIVERS\UMDF\WpdRapi2.dll' Status=0 Class=OEM OEM
Protected
flq: ScanQ action=200 DoPruning=32
flq: ScanQ end Validity flags=620 CopyNodes=0
dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)}
ndv: Committing file queue...
flq: {_COMMIT_FILE_QUEUE}
flq: CommitQ DelNodes=0 RenNodes=0 BackNodes=0 CopyNodes=0
flq: {_COMMIT_FILE_QUEUE exit(0x00000000)}
ndv: Registering CoInstallers...
dvi: {DIF_REGISTER_COINSTALLERS} 21:11:31.042
dvi: CoInstaller 1: Enter 21:11:31.044
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 21:11:31.045
dvi: Class installer: Exit
dvi: Default installer: Enter 21:11:31.047
inf: Opened PNF:
'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf' ([strings] <src=drvstore>)
inf: {Install Inf Section
[WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers]}
inf: AddReg=CoInstallers_AddReg (wpdrapi.inf line
51)
inf:
HKR,,CoInstallers32,0x00010000,WUDFCoInstaller.dll (wpdrapi.inf line 85)
inf: {Install Inf Section
[WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers] exit (0x00000000)}
dvi: {DIF_DESTROYPRIVATEDATA} 21:11:31.054
dvi: CoInstaller 1: Enter 21:11:31.054
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 21:11:31.056
dvi: Class installer: Exit
dvi: Default installer: Enter 21:11:31.057
dvi: Default installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)}
21:11:31.059
dvi: Co-installers registered.
dvi: Default installer: Exit
dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 21:11:31.061
ndv: Installing interfaces...
dvi: {DIF_INSTALLINTERFACES} 21:11:31.062
dvi: Using exported function 'CoDeviceInstall' in module
'C:\Windows\system32\WUDFCoInstaller.dll'.
dvi: CoInstaller 1 == WUDFCoInstaller.dll
dvi: CoInstaller 1: Enter 21:11:31.065
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 21:11:31.066
dvi: Class installer: Exit
dvi: Default installer: Enter 21:11:31.068
dvi: {Install INTERFACES}
inf: Opened PNF:
'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf' ([strings] <src=drvstore>)
dvi: Installing section
[WINDOWSMOBILE_WPD_DEVICE.NT.Interfaces]
dvi: {Install INTERFACES exit 00000000}
dvi: Default installer: Exit
dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 21:11:31.073
ndv: Installing device...
dvi: {DIF_INSTALLDEVICE} 21:11:31.075
dvi: CoInstaller 1: Enter 21:11:31.075
inf: Opened PNF: 'C:\Windows\INF\oem9.inf' ([strings]
<src=oempath>)
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 21:11:31.163
dvi: {Install DEVICE}
inf: Opened PNF:
'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf' ([strings] <src=drvstore>)
dvi: Processing Registry/Property directives...
inf: {Install Inf Section
[WINDOWSMOBILE_WPD_DEVICE.NT]}
inf: 12,UMDF,wpdrapi2.dll,1 (wpdrapi.inf line
68)
inf: Processing REGISTERDLLS section
[WPDRAPIDRIVER_COMMON.RegisterComServers]. Module: '%12%\UMDF\wpdrapi2.dll',
flags: 0x0001, timeout: 60s, Arguments: '(null)'.
inf: Calling 'DllRegisterServer' in OLE
Control 'C:\Windows\system32\DRIVERS\UMDF\wpdrapi2.dll' succeeded.
inf: {Install Inf Section
[WINDOWSMOBILE_WPD_DEVICE.NT] exit (0x00000000)}
inf: {Install Inf Section
[WINDOWSMOBILE_WPD_DEVICE.NT.Hw]}
inf:
AddReg=WPDRAPIDRIVER_COMMON.AutoPlayRegistration (wpdrapi.inf line 45)
inf:
HKR,,EnableDefaultAutoPlaySupport,0x10001,1 (wpdrapi.inf line 71)
inf: HKR,,EnableLegacySupport,0x10001,1
(wpdrapi.inf line 72)
inf: {Install Inf Section
[WINDOWSMOBILE_WPD_DEVICE.NT.Hw] exit (0x00000000)}
dvi: {Writing Device Properties}
dvi: Provider name=Microsoft Corporation
dvi: DriverDate 05/31/2007
dvi: DriverVersion=6.1.6965.0
dvi: Class name=WPD
dvi: Manufacturer=(Standard Windows Mobile
devices)
dvi: Matching
DeviceID=tcpip\windows_mobile_device
dvi: Strong
Name=oem9.inf:Microsoft.NTx86:WINDOWSMOBILE_WPD_DE VICE:6.1.6965.0:tcpip\windows_mobile_device
dvi: {Writing Device Properties - Complete}
inf: {Install Inf Section
[WINDOWSMOBILE_WPD_DEVICE.NT.Services]}
inf:
AddService=WUDFRd,0x000001fa,WUDFRD_ServiceInstall (wpdrapi.inf line 48)
inf: ServiceType=1 (wpdrapi.inf line 79)
inf: StartType=3 (wpdrapi.inf line 80)
inf: ErrorControl=1 (wpdrapi.inf line 81)
inf:
ServiceBinary=C:\Windows\system32\DRIVERS\WUDFRd.s ys (wpdrapi.inf line 82)
dvi: Add Service: Modified existing service
'WUDFRd'.
inf: {Install Inf Section
[WINDOWSMOBILE_WPD_DEVICE.NT.Services] exit(0x00000000)}
dvi: {Install DEVICE exit (0x00000000)}
dvi: Writing common driver property settings.
dvi: DriverDescription=Windows Mobile-based device
dvi: DeviceDisplayName=Windows Mobile-based device
dvi: Install Device: Restarting device. 21:11:31.255
dvi: Install Device: Restarting device completed.
21:11:43.203
dvi: Class installer: Exit
dvi: CoInstaller 1: Enter (Post Processing) 21:11:43.207
dvi: CoInstaller 1: Exit (Post Processing)
dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 21:11:43.213
dvi: {Build Driver List} 21:11:43.213
! dvi: Driver list already built
dvi: {Build Driver List - exit(0x00000000)} 21:11:43.215
dvi: {DIF_SELECTBESTCOMPATDRV} 21:11:43.215
dvi: CoInstaller 1: Enter 21:11:43.216
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 21:11:43.217
dvi: Class installer: Exit
dvi: Default installer: Enter 21:11:43.219
dvi: {Select Best Driver}
dvi: Selected driver installs from section
[WINDOWSMOBILE_WPD_DEVICE] in
'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf'.
dvi: Class GUID of device remains:
{eec5ad98-8080-425f-922a-dabf3de3f69a}.
dvi: Set selected driver complete.
dvi: Selected:
dvi: Description - [Windows Mobile-based device]
dvi: InfFile -
[c:\windows\system32\driverstore\filerepository\wpd rapi.inf_b2b04810\wpdrapi.inf]
dvi: Section - [WINDOWSMOBILE_WPD_DEVICE]
dvi: Signer - [microsoft windows hardware
compatibility publisher]
dvi: Rank - [0x0dff0000]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 21:11:43.228
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 21:11:43.229
dvi: CoInstaller 1: Enter 21:11:43.230
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 21:11:43.231
dvi: Class installer: Exit
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0x00000000)}
21:11:51.728
ndv: Device install status=0x00000000
ndv: Performing device install final cleanup...
ndv: {Core Device Install - exit(0x00000000)}
dvi: {DIF_DESTROYPRIVATEDATA} 21:11:51.732
dvi: CoInstaller 1: Enter 21:11:51.733
dvi: CoInstaller 1: Exit
dvi: Class installer: Enter 21:11:51.734
dvi: Class installer: Exit
dvi: Default installer: Enter 21:11:51.736
dvi: Default installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 21:11:51.737
ump: Server install process exited with code 0x00000000 21:11:51.766
<<< Section end 2007/08/23 21:11:51.768
<<< [Exit status: SUCCESS]
--
Ben


"Steve Spiller [MSFT]" wrote:

> Did you try restarting after enabling the logging? If you're getting to the
> point of the WMDC UI becoming visible, there will be logging. Without
> getting the logs of the error condition I'm stumpped as to what might be
> going on. I can honestly say I've never seen this issue before
>
> --
> Thanks,
>
> Steve Spiller
> Development Lead
> Windows Mobile Device Center
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Ben" <> wrote in message
> news:828D62E5-7F7D-4297-A756-...
> > Steve, have tried several reinstalls of WMDC all to version 6.1. No
> > change.
> >
> > I am using Zonealarm free. Have enabled all the .exe files and the .dll
> > files that wmdc seems to want:
> > wcescomm.dll
> > rapimgr.dll
> > ceappmgr.exe
> > svchost.exe
> > windowsmobile.rapi.dll
> > wmdsync.exe
> > wmdsyncman.dll
> > wmdhost.exe
> > wmdc.exe
> >
> > Not now getting wcescomm error of multiple devices following reboot; still
> > getting rapimgr error 8 though. Uninstalling/disabling firewalls doesn't
> > make any difference.
> >
> > I have tried following the instructions on the website given, but the logs
> > don't generate as expected by the instructions - no sign of them
> > anywhere...
> > :-/
> >
> > Just noticed that the phone is visible for a little while - about 30
> > seconds
> > - under computer staight after connecting...can browse the phone too - but
> > then it just disappears from the menu...at exactly the same time as WMDC
> > says
> > 'not connected'
> >
> > Cheers Steve,
> >
> > --
> > Ben
> >
> >
> > "Steve Spiller [MSFT]" wrote:
> >
> >> Sometimes a hard reset of the device does help, but shouldn't be
> >> necessary.
> >> And you should never have to reinstall Vista because of WMDC. Sometimes
> >> uninstalling and reinstalling WMDC helps, though.
> >>
> >> Which firewall are you using? You should never get that multiple-devices
> >> connected error unless you have two unique Windows Mobile devices
> >> connected.
> >>
> >> Also, on that same site is a set of instructions for generating debug
> >> logs
> >> for WMDC. Go ahead and do that. Maybe there will be something in there
> >> that points to the issue you're seeing.
> >>
> >> --
> >> Thanks,
> >>
> >> Steve Spiller
> >> Development Lead
> >> Windows Mobile Device Center
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Ben" <> wrote in message
> >> news:65CC48A5-1BFA-435B-84DE-...
> >> > Hi Steve. Thanks for your reply. I'm using version 6.1. I have tried
> >> > switching the device to serial several times...but to no avail.
> >> >
> >> > I have enabled port 990 on the firewall (along with all other
> >> > recommended
> >> > ports from the website you pointed me at - been there, very useful, but
> >> > didn't solve the problem.) It certainly looks like it is being blocked
> >> > in
> >> > some way...WMDC says connecting, then stops and says 'not connected',
> >> > but
> >> > has
> >> > recognised my device is called Ben...so obviously had some sort of
> >> > contact.
> >> > It just won't initiate the partnership set up. Also now getting a
> >> > WcesComm
> >> > error 4 - even though it is only my phone plugged in to usb...(removed
> >> > everything in case of conflict.)
> >> >
> >> > I am considering a hard reset of the device, followed by if necessary
> >> > (but
> >> > not really wanting to) a reinstall of Vista. Would either of these be
> >> > worth
> >> > doing or do you have any other ideas? It is quite frustrating!
> >> > --
> >> > Ben
> >> >
> >> >
> >> > "Steve Spiller [MSFT]" wrote:
> >> >
> >> >> Hello,
> >> >>
> >> >> Can you tell me which version of WMDC you're using? The latest is
> >> >> 6.1.
> >> >>
> >> >> Usually switching to serial will fix the problem. The rapimgr event 8
> >> >> is
> >> >> caused when we send a UDP packet to the device asking it to connect
> >> >> back
> >> >> on
> >> >> port 990 and the device is blocked from doing so.
> >> >>
> >> >> There's a lot of good information here that may help with
> >> >> troublshooting,
> >> >> including the Firewall settings:
> >> >> http://www.pocketpcfaq.com/faqs/wmdc/index.htm
> >> >>
> >> >>
> >> >> --
> >> >> Thanks,
> >> >>
> >> >> Steve Spiller
> >> >> Development Lead
> >> >> Windows Mobile Device Center
> >> >>
> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> >> rights.
> >> >>
> >> >> "Ben" <> wrote in message
> >> >> news:E74F0134-8833-475F-87E5-...
> >> >> >I have done lots of research but can't find a solution to this:
> >> >> >
> >> >> > A UK Orange E650 (HTC S710). WMDC recognises a device attached but
> >> >> > fails
> >> >> > to sync. Device not visible in computer or media player. Device is
> >> >> > in
> >> >> > device manager.
> >> >> >
> >> >> > Have tried switching to serial. Have reinstalled WMDC several
> >> >> > times.
> >> >> > In
> >> >> > event log when trying to connect it comes up as a Rapimgr error 8
> >> >> > (WMDC
> >> >> > received a connection from the device, but something failed during
> >> >> > the
> >> >> > connection protocol.)
> >> >> >
> >> >> > I have enabled suggested ports in the firewall....but the event log
> >> >> > seems
> >> >> > to
> >> >> > suggest that Rapimgr is causing a problem with the connection. How
> >> >> > can
> >> >> > I
> >> >> > add
> >> >> > the rapimgr.dll to the firewall exceptions? Is it the likely cause
> >> >> > of
> >> >> > stopping my phone syncing? The phone connected to XP and Activesync
> >> >> > straight
> >> >> > away with no problem...
> >> >> >
> >> >> > Cheers,
> >> >> > --
> >> >> > Ben
> >> >>
> >> >>
> >>
> >>
>
>

Yes, you save the files in the \windows\windowsmobile folder. The way I get
to the temp folder to do a Start -> Run then type in "%TEMP%". The files
are Wmdc.log and WmdHost.log.

--
Thanks,

Steve Spiller
Development Lead
Windows Mobile Device Center

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

"Ben" <> wrote in message
news:4448339B-00A2-4A17-B1E6-...
> Steve,
>
> Yes I restarted after doing it. Just to confirm - I copy and save the
> files
> from the website to the windows/windowsmobile folder...? Then restart.
> Then
> I should find the logs in the %temp\ folder...? There is certainly no
> sign
> of them in the temp folder.
>
> With no results, what I did instead was uninstalled WMDC again, deleted
> all
> files I could associated with it (wouldn't let me do some .dlls and some
> 'MUI' files) then reinstalled wmdc. I then got the log file for
> installation
> of that from windows/inf/setupapi.dev (copied below). Is this of use to
> you?
> I attached the device whilst installing - then detached and re-attached
> the
> device to initiate wmdc. It got to the bit saying 'please wait whilst
> wmdc
> starts' then it hangs as before without getting a connection. Once again
> the
> device appeared under 'computer', then disappeared after about 30 seconds.
> HTH.
>
> Ben
>
> Log from windows/inf/setupappi.dev:
>
>>>> [Device Install (Hardware initiated) -
>>>> ActiveSyncWPDEnumerator\UMB\2&306b293b&0&ACTIVESYN CWPDDEVICE-C5C7610F-6346-E390-B9A5-F7C6113AA174-]
>>>> Section start 2007/08/23 21:11:30.276
> ump: Creating Install Process: DrvInst.exe 21:11:30.277
> ndv: Retrieving device info...
> ndv: Setting device parameters...
> ndv: Building driver list...
> dvi: {Build Driver List} 21:11:30.572
> dvi: Searching for hardware ID(s):
> dvi: tcpip\windows_mobile_device
> dvi: Searching for compatible ID(s):
> dvi: tcpip\windows_mobile_device
> dvi: Enumerating INFs from path list 'C:\Windows\INF'
> inf: Opened PNF:
> 'C:\Windows\System32\DriverStore\FileRepository\wp drapi.inf_3942e2cb\wpdrapi.inf'
> ([strings.0409] <src=drvstore>)
> dvi: Created Driver Node:
> dvi: HardwareID - TCPIP\WINDOWS_MOBILE_DEVICE
> dvi: InfName -
> C:\Windows\System32\DriverStore\FileRepository\wpd rapi.inf_3942e2cb\wpdrapi.inf
> dvi: DevDesc - Windows Mobile device
> dvi: DrvDesc - Windows Mobile device
> dvi: Provider - Microsoft
> dvi: Mfg - (Standard Windows Mobile devices)
> dvi: ModelsSec - Microsoft.NTx86
> dvi: InstallSec - WINDOWSMOBILE_WPD_DEVICE
> dvi: ActualSec - WINDOWSMOBILE_WPD_DEVICE.NT
> dvi: Rank - 0x0dff0000
> dvi: Signer - microsoft windows
> dvi: Signer Score - INBOX
> dvi: DrvDate - 06/21/2006
> dvi: Version - 6.0.6000.16386
> inf: Opened PNF:
> 'C:\Windows\System32\DriverStore\FileRepository\wp drapi.inf_b2b04810\wpdrapi.inf'
> ([strings] <src=drvstore>)
> dvi: Created Driver Node:
> dvi: HardwareID - TCPIP\WINDOWS_MOBILE_DEVICE
> dvi: InfName -
> C:\Windows\System32\DriverStore\FileRepository\wpd rapi.inf_b2b04810\wpdrapi.inf
> dvi: DevDesc - Windows Mobile-based device
> dvi: DrvDesc - Windows Mobile-based device
> dvi: Provider - Microsoft Corporation
> dvi: Mfg - (Standard Windows Mobile devices)
> dvi: ModelsSec - Microsoft.NTx86
> dvi: InstallSec - WINDOWSMOBILE_WPD_DEVICE
> dvi: ActualSec - WINDOWSMOBILE_WPD_DEVICE.NT
> dvi: Rank - 0x0dff0000
> dvi: Signer - microsoft windows hardware compatibility
> publisher
> dvi: Signer Score - WHQL
> dvi: DrvDate - 05/31/2007
> dvi: Version - 6.1.6965.0
> inf: Searched 2 potential matches in published INF directory
> inf: Searched 29 INFs in directory: 'C:\Windows\INF'
> dvi: {Build Driver List - exit(0x00000000)} 21:11:30.737
> ndv: Selecting best match...
> dvi: {DIF_SELECTBESTCOMPATDRV} 21:11:30.738
> dvi: Using exported function 'WpdClassInstaller' in module
> 'C:\Windows\system32\wpd_ci.dll'.
> dvi: Class installer == wpd_ci.dll,WpdClassInstaller
> dvi: Using exported function 'CoDeviceInstall' in module
> 'C:\Windows\system32\WUDFCoInstaller.dll'.
> dvi: CoInstaller 1 == WUDFCoInstaller.dll
> dvi: CoInstaller 1: Enter 21:11:30.810
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 21:11:30.811
> dvi: Class installer: Exit
> dvi: Default installer: Enter 21:11:30.813
> dvi: {Select Best Driver}
> dvi: Selected driver installs from section
> [WINDOWSMOBILE_WPD_DEVICE] in
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf'.
> dvi: Class GUID of device remains:
> {eec5ad98-8080-425f-922a-dabf3de3f69a}.
> dvi: Set selected driver complete.
> dvi: Selected:
> dvi: Description - [Windows Mobile-based device]
> dvi: InfFile -
> [c:\windows\system32\driverstore\filerepository\wpd rapi.inf_b2b04810\wpdrapi.inf]
> dvi: Section - [WINDOWSMOBILE_WPD_DEVICE]
> dvi: Signer - [microsoft windows hardware
> compatibility publisher]
> dvi: Rank - [0x0dff0000]
> dvi: {Select Best Driver - exit(0x00000000)}
> dvi: Default installer: Exit
> dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 21:11:30.823
> ndv: Driver selected, now performing install...
> ndv: {Core Device Install}
> inf: Opened PNF: 'C:\Windows\INF\oem9.inf' ([strings]
> <src=oempath>)
> inf: Opened PNF: 'C:\Windows\INF\oem9.inf' ([strings]
> <src=oempath>)
> dvi: {DIF_ALLOW_INSTALL} 21:11:30.895
> dvi: CoInstaller 1: Enter 21:11:30.895
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 21:11:30.897
> dvi: Class installer: Exit
> dvi: Default installer: Enter 21:11:30.901
> dvi: Default installer: Exit
> dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 21:11:30.903
> ndv: Installing files...
> dvi: {DIF_INSTALLDEVICEFILES} 21:11:30.904
> dvi: CoInstaller 1: Enter 21:11:30.905
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 21:11:30.906
> dvi: Class installer: Exit
> dvi: Default installer: Enter 21:11:30.908
> dvi: {Install FILES}
> inf: Opened PNF:
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf'
> ([strings] <src=drvstore>)
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT]}
> inf:
> CopyFiles=WPDRAPIDRIVER_COMMON.Files.Core
> (wpdrapi.inf line 41)
> cpy: Open PnpLockdownPolicy: Err=2. This is
> OK. Use LockDownPolicyDefault
> flq: QueueSingleCopy...
> flq: Inf :
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf'
> flq: SourceInf:
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf'
> flq: SourceSection: [sourcedisksfiles]
> flq: Source root path based on SourceInf
> flq: SourceRootPath:
> 'C:\Windows\System32\DriverStore\FileRepository\wp drapi.inf_b2b04810'
> flq: {FILE_QUEUE_COPY}
> flq: CopyStyle - 0x06000000
> flq: SourceRootPath -
> 'C:\Windows\System32\DriverStore\FileRepository\wp drapi.inf_b2b04810'
> flq: SourceFilename - 'WpdRapi.dll'
> flq: TargetDirectory-
> 'C:\Windows\system32\DRIVERS\UMDF'
> flq: TargetFilename - 'WpdRapi2.dll'
> flq: SourceDesc - 'Windows Mobile
> Device Center Media'
> flq: {FILE_QUEUE_COPY exit(0x00000000)}
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT] exit (0x00000000)}
> dvi: Processing co-installer registration section
> [WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers].
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers]}
> inf: No (Copy/Ren/Del)Files directives found
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers] exit (0x00000000)}
> dvi: Co-installers registered.
> dvi: {Install INTERFACES}
> dvi: Installing section
> [WINDOWSMOBILE_WPD_DEVICE.NT.Interfaces]
> dvi: {Install INTERFACES exit 00000000}
> dvi: {Install FILES exit (0x00000000)}
> dvi: Default installer: Exit
> dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 21:11:30.935
> ndv: Pruning file queue...
> dvi: {_SCAN_FILE_QUEUE}
> flq: ScanQ flags=620
> flq: SPQ_SCAN_PRUNE_COPY_QUEUE
> flq: SPQ_SCAN_FILE_COMPARISON
> flq: SPQ_SCAN_ACTIVATE_DRP
> flq: ScanQ number of copy nodes=1
> flq: File 'C:\Windows\system32\DRIVERS\UMDF\WpdRapi2.dll'
> pruned from copy.
> sig: Using catalog
> 'C:\Windows\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\oem9.CAT'.
> cpy: DrpSetRegFileProt
> 'C:\Windows\system32\DRIVERS\UMDF\WpdRapi2.dll' Status=0 Class=OEM OEM
> Protected
> flq: ScanQ action=200 DoPruning=32
> flq: ScanQ end Validity flags=620 CopyNodes=0
> dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)}
> ndv: Committing file queue...
> flq: {_COMMIT_FILE_QUEUE}
> flq: CommitQ DelNodes=0 RenNodes=0 BackNodes=0 CopyNodes=0
> flq: {_COMMIT_FILE_QUEUE exit(0x00000000)}
> ndv: Registering CoInstallers...
> dvi: {DIF_REGISTER_COINSTALLERS} 21:11:31.042
> dvi: CoInstaller 1: Enter 21:11:31.044
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 21:11:31.045
> dvi: Class installer: Exit
> dvi: Default installer: Enter 21:11:31.047
> inf: Opened PNF:
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf'
> ([strings] <src=drvstore>)
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers]}
> inf: AddReg=CoInstallers_AddReg (wpdrapi.inf line
> 51)
> inf:
> HKR,,CoInstallers32,0x00010000,WUDFCoInstaller.dll (wpdrapi.inf line 85)
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.CoInstallers] exit (0x00000000)}
> dvi: {DIF_DESTROYPRIVATEDATA} 21:11:31.054
> dvi: CoInstaller 1: Enter 21:11:31.054
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 21:11:31.056
> dvi: Class installer: Exit
> dvi: Default installer: Enter 21:11:31.057
> dvi: Default installer: Exit
> dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)}
> 21:11:31.059
> dvi: Co-installers registered.
> dvi: Default installer: Exit
> dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 21:11:31.061
> ndv: Installing interfaces...
> dvi: {DIF_INSTALLINTERFACES} 21:11:31.062
> dvi: Using exported function 'CoDeviceInstall' in module
> 'C:\Windows\system32\WUDFCoInstaller.dll'.
> dvi: CoInstaller 1 == WUDFCoInstaller.dll
> dvi: CoInstaller 1: Enter 21:11:31.065
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 21:11:31.066
> dvi: Class installer: Exit
> dvi: Default installer: Enter 21:11:31.068
> dvi: {Install INTERFACES}
> inf: Opened PNF:
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf'
> ([strings] <src=drvstore>)
> dvi: Installing section
> [WINDOWSMOBILE_WPD_DEVICE.NT.Interfaces]
> dvi: {Install INTERFACES exit 00000000}
> dvi: Default installer: Exit
> dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 21:11:31.073
> ndv: Installing device...
> dvi: {DIF_INSTALLDEVICE} 21:11:31.075
> dvi: CoInstaller 1: Enter 21:11:31.075
> inf: Opened PNF: 'C:\Windows\INF\oem9.inf' ([strings]
> <src=oempath>)
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 21:11:31.163
> dvi: {Install DEVICE}
> inf: Opened PNF:
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf'
> ([strings] <src=drvstore>)
> dvi: Processing Registry/Property directives...
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT]}
> inf: 12,UMDF,wpdrapi2.dll,1 (wpdrapi.inf
> line
> 68)
> inf: Processing REGISTERDLLS section
> [WPDRAPIDRIVER_COMMON.RegisterComServers]. Module:
> '%12%\UMDF\wpdrapi2.dll',
> flags: 0x0001, timeout: 60s, Arguments: '(null)'.
> inf: Calling 'DllRegisterServer' in OLE
> Control 'C:\Windows\system32\DRIVERS\UMDF\wpdrapi2.dll' succeeded.
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT] exit (0x00000000)}
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.Hw]}
> inf:
> AddReg=WPDRAPIDRIVER_COMMON.AutoPlayRegistration (wpdrapi.inf line 45)
> inf:
> HKR,,EnableDefaultAutoPlaySupport,0x10001,1 (wpdrapi.inf line 71)
> inf: HKR,,EnableLegacySupport,0x10001,1
> (wpdrapi.inf line 72)
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.Hw] exit (0x00000000)}
> dvi: {Writing Device Properties}
> dvi: Provider name=Microsoft Corporation
> dvi: DriverDate 05/31/2007
> dvi: DriverVersion=6.1.6965.0
> dvi: Class name=WPD
> dvi: Manufacturer=(Standard Windows Mobile
> devices)
> dvi: Matching
> DeviceID=tcpip\windows_mobile_device
> dvi: Strong
> Name=oem9.inf:Microsoft.NTx86:WINDOWSMOBILE_WPD_DE VICE:6.1.6965.0:tcpip\windows_mobile_device
> dvi: {Writing Device Properties - Complete}
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.Services]}
> inf:
> AddService=WUDFRd,0x000001fa,WUDFRD_ServiceInstall (wpdrapi.inf line 48)
> inf: ServiceType=1 (wpdrapi.inf line 79)
> inf: StartType=3 (wpdrapi.inf line 80)
> inf: ErrorControl=1 (wpdrapi.inf line 81)
> inf:
> ServiceBinary=C:\Windows\system32\DRIVERS\WUDFRd.s ys (wpdrapi.inf line
> 82)
> dvi: Add Service: Modified existing service
> 'WUDFRd'.
> inf: {Install Inf Section
> [WINDOWSMOBILE_WPD_DEVICE.NT.Services] exit(0x00000000)}
> dvi: {Install DEVICE exit (0x00000000)}
> dvi: Writing common driver property settings.
> dvi: DriverDescription=Windows Mobile-based device
> dvi: DeviceDisplayName=Windows Mobile-based device
> dvi: Install Device: Restarting device. 21:11:31.255
> dvi: Install Device: Restarting device completed.
> 21:11:43.203
> dvi: Class installer: Exit
> dvi: CoInstaller 1: Enter (Post Processing) 21:11:43.207
> dvi: CoInstaller 1: Exit (Post Processing)
> dvi: {DIF_INSTALLDEVICE - exit(0x00000000)} 21:11:43.213
> dvi: {Build Driver List} 21:11:43.213
> ! dvi: Driver list already built
> dvi: {Build Driver List - exit(0x00000000)} 21:11:43.215
> dvi: {DIF_SELECTBESTCOMPATDRV} 21:11:43.215
> dvi: CoInstaller 1: Enter 21:11:43.216
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 21:11:43.217
> dvi: Class installer: Exit
> dvi: Default installer: Enter 21:11:43.219
> dvi: {Select Best Driver}
> dvi: Selected driver installs from section
> [WINDOWSMOBILE_WPD_DEVICE] in
> 'c:\windows\system32\driverstore\filerepository\wp drapi.inf_b2b04810\wpdrapi.inf'.
> dvi: Class GUID of device remains:
> {eec5ad98-8080-425f-922a-dabf3de3f69a}.
> dvi: Set selected driver complete.
> dvi: Selected:
> dvi: Description - [Windows Mobile-based
> device]
> dvi: InfFile -
> [c:\windows\system32\driverstore\filerepository\wpd rapi.inf_b2b04810\wpdrapi.inf]
> dvi: Section - [WINDOWSMOBILE_WPD_DEVICE]
> dvi: Signer - [microsoft windows
> hardware
> compatibility publisher]
> dvi: Rank - [0x0dff0000]
> dvi: {Select Best Driver - exit(0x00000000)}
> dvi: Default installer: Exit
> dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 21:11:43.228
> dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 21:11:43.229
> dvi: CoInstaller 1: Enter 21:11:43.230
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 21:11:43.231
> dvi: Class installer: Exit
> dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0x00000000)}
> 21:11:51.728
> ndv: Device install status=0x00000000
> ndv: Performing device install final cleanup...
> ndv: {Core Device Install - exit(0x00000000)}
> dvi: {DIF_DESTROYPRIVATEDATA} 21:11:51.732
> dvi: CoInstaller 1: Enter 21:11:51.733
> dvi: CoInstaller 1: Exit
> dvi: Class installer: Enter 21:11:51.734
> dvi: Class installer: Exit
> dvi: Default installer: Enter 21:11:51.736
> dvi: Default installer: Exit
> dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 21:11:51.737
> ump: Server install process exited with code 0x00000000 21:11:51.766
> <<< Section end 2007/08/23 21:11:51.768
> <<< [Exit status: SUCCESS]
> --
> Ben
>
>
> "Steve Spiller [MSFT]" wrote:
>
>> Did you try restarting after enabling the logging? If you're getting to
>> the
>> point of the WMDC UI becoming visible, there will be logging. Without
>> getting the logs of the error condition I'm stumpped as to what might be
>> going on. I can honestly say I've never seen this issue before
>>
>> --
>> Thanks,
>>
>> Steve Spiller
>> Development Lead
>> Windows Mobile Device Center
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Ben" <> wrote in message
>> news:828D62E5-7F7D-4297-A756-...
>> > Steve, have tried several reinstalls of WMDC all to version 6.1. No
>> > change.
>> >
>> > I am using Zonealarm free. Have enabled all the .exe files and the
>> > .dll
>> > files that wmdc seems to want:
>> > wcescomm.dll
>> > rapimgr.dll
>> > ceappmgr.exe
>> > svchost.exe
>> > windowsmobile.rapi.dll
>> > wmdsync.exe
>> > wmdsyncman.dll
>> > wmdhost.exe
>> > wmdc.exe
>> >
>> > Not now getting wcescomm error of multiple devices following reboot;
>> > still
>> > getting rapimgr error 8 though. Uninstalling/disabling firewalls
>> > doesn't
>> > make any difference.
>> >
>> > I have tried following the instructions on the website given, but the
>> > logs
>> > don't generate as expected by the instructions - no sign of them
>> > anywhere...
>> > :-/
>> >
>> > Just noticed that the phone is visible for a little while - about 30
>> > seconds
>> > - under computer staight after connecting...can browse the phone too -
>> > but
>> > then it just disappears from the menu...at exactly the same time as
>> > WMDC
>> > says
>> > 'not connected'
>> >
>> > Cheers Steve,
>> >
>> > --
>> > Ben
>> >
>> >
>> > "Steve Spiller [MSFT]" wrote:
>> >
>> >> Sometimes a hard reset of the device does help, but shouldn't be
>> >> necessary.
>> >> And you should never have to reinstall Vista because of WMDC.
>> >> Sometimes
>> >> uninstalling and reinstalling WMDC helps, though.
>> >>
>> >> Which firewall are you using? You should never get that
>> >> multiple-devices
>> >> connected error unless you have two unique Windows Mobile devices
>> >> connected.
>> >>
>> >> Also, on that same site is a set of instructions for generating debug
>> >> logs
>> >> for WMDC. Go ahead and do that. Maybe there will be something in
>> >> there
>> >> that points to the issue you're seeing.
>> >>
>> >> --
>> >> Thanks,
>> >>
>> >> Steve Spiller
>> >> Development Lead
>> >> Windows Mobile Device Center
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >> "Ben" <> wrote in message
>> >> news:65CC48A5-1BFA-435B-84DE-...
>> >> > Hi Steve. Thanks for your reply. I'm using version 6.1. I have
>> >> > tried
>> >> > switching the device to serial several times...but to no avail.
>> >> >
>> >> > I have enabled port 990 on the firewall (along with all other
>> >> > recommended
>> >> > ports from the website you pointed me at - been there, very useful,
>> >> > but
>> >> > didn't solve the problem.) It certainly looks like it is being
>> >> > blocked
>> >> > in
>> >> > some way...WMDC says connecting, then stops and says 'not
>> >> > connected',
>> >> > but
>> >> > has
>> >> > recognised my device is called Ben...so obviously had some sort of
>> >> > contact.
>> >> > It just won't initiate the partnership set up. Also now getting a
>> >> > WcesComm
>> >> > error 4 - even though it is only my phone plugged in to
>> >> > usb...(removed
>> >> > everything in case of conflict.)
>> >> >
>> >> > I am considering a hard reset of the device, followed by if
>> >> > necessary
>> >> > (but
>> >> > not really wanting to) a reinstall of Vista. Would either of these
>> >> > be
>> >> > worth
>> >> > doing or do you have any other ideas? It is quite frustrating!
>> >> > --
>> >> > Ben
>> >> >
>> >> >
>> >> > "Steve Spiller [MSFT]" wrote:
>> >> >
>> >> >> Hello,
>> >> >>
>> >> >> Can you tell me which version of WMDC you're using? The latest is
>> >> >> 6.1.
>> >> >>
>> >> >> Usually switching to serial will fix the problem. The rapimgr
>> >> >> event 8
>> >> >> is
>> >> >> caused when we send a UDP packet to the device asking it to connect
>> >> >> back
>> >> >> on
>> >> >> port 990 and the device is blocked from doing so.
>> >> >>
>> >> >> There's a lot of good information here that may help with
>> >> >> troublshooting,
>> >> >> including the Firewall settings:
>> >> >> http://www.pocketpcfaq.com/faqs/wmdc/index.htm
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Thanks,
>> >> >>
>> >> >> Steve Spiller
>> >> >> Development Lead
>> >> >> Windows Mobile Device Center
>> >> >>
>> >> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> >> rights.
>> >> >>
>> >> >> "Ben" <> wrote in message
>> >> >> news:E74F0134-8833-475F-87E5-...
>> >> >> >I have done lots of research but can't find a solution to this:
>> >> >> >
>> >> >> > A UK Orange E650 (HTC S710). WMDC recognises a device attached
>> >> >> > but
>> >> >> > fails
>> >> >> > to sync. Device not visible in computer or media player. Device
>> >> >> > is
>> >> >> > in
>> >> >> > device manager.
>> >> >> >
>> >> >> > Have tried switching to serial. Have reinstalled WMDC several
>> >> >> > times.
>> >> >> > In
>> >> >> > event log when trying to connect it comes up as a Rapimgr error 8
>> >> >> > (WMDC
>> >> >> > received a connection from the device, but something failed
>> >> >> > during
>> >> >> > the
>> >> >> > connection protocol.)
>> >> >> >
>> >> >> > I have enabled suggested ports in the firewall....but the event
>> >> >> > log
>> >> >> > seems
>> >> >> > to
>> >> >> > suggest that Rapimgr is causing a problem with the connection.
>> >> >> > How
>> >> >> > can
>> >> >> > I
>> >> >> > add
>> >> >> > the rapimgr.dll to the firewall exceptions? Is it the likely
>> >> >> > cause
>> >> >> > of
>> >> >> > stopping my phone syncing? The phone connected to XP and
>> >> >> > Activesync
>> >> >> > straight
>> >> >> > away with no problem...
>> >> >> >
>> >> >> > Cheers,
>> >> >> > --
>> >> >> > Ben
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>

Ah ha, I have it!

WmdHost:

21/08/2007 23:44:55
C:\Windows\WindowsMobile\WmdHost.exe (6.1.6965.0)
--------- Begin logging ----------
WmdHost Information: 0 : WmdHost.Main
DateTime=2007-08-21T22:44:55.0112130Z
WmdHost Information: 0 : WmdHost.Factory
DateTime=2007-08-21T22:44:55.0592130Z
WmdHost Information: 0 : HostForeman.StartFactories Enter IsRunning:False
DateTime=2007-08-21T22:44:55.1082130Z
WmdHost Information: 0 : HostForeman.Dispose()
DateTime=2007-08-21T22:45:06.4032130Z
WmdHost Information: 0 : HostForeman.StopFactories Enter
DateTime=2007-08-21T22:45:06.4032130Z


21/08/2007 23:59:49
C:\Windows\WindowsMobile\WmdHost.exe (6.1.6965.0)
--------- Begin logging ----------
WmdHost Information: 0 : WmdHost.Main
DateTime=2007-08-21T22:59:49.8933830Z
WmdHost Information: 0 : WmdHost.Factory
DateTime=2007-08-21T22:59:49.9053830Z
WmdHost Information: 0 : HostForeman.StartFactories Enter IsRunning:False
DateTime=2007-08-21T22:59:49.9373830Z
WmdHost Information: 0 : HostForeman.Dispose()
DateTime=2007-08-21T23:00:01.1443830Z
WmdHost Information: 0 : HostForeman.StopFactories Enter
DateTime=2007-08-21T23:00:01.1443830Z


23/08/2007 21:11:54
C:\Windows\WindowsMobile\WmdHost.exe (6.1.6965.0)
--------- Begin logging ----------
WmdHost Information: 0 : WmdHost.Main
DateTime=2007-08-23T20:11:54.4384036Z
WmdHost Information: 0 : WmdHost.Factory
DateTime=2007-08-23T20:11:54.4504036Z
WmdHost Information: 0 : HostForeman.StartFactories Enter IsRunning:False
DateTime=2007-08-23T20:11:54.5644036Z
WmdHost Information: 0 : HostForeman.Dispose()
DateTime=2007-08-23T20:11:54.8364036Z
WmdHost Information: 0 : HostForeman.StopFactories Enter
DateTime=2007-08-23T20:11:54.8364036Z

WMDC:

21/08/2007 23:44:55
C:\Windows\WindowsMobile\wmdc.exe (6.1.6965.0)
--------- Begin logging ----------
wmdc Verbose: 1 : Creating new PartnershipCollection instance
DateTime=2007-08-21T22:44:55.1592130Z
wmdc Information: 0 : Entering PartnershipCollection::Initialize
DateTime=2007-08-21T22:44:55.1652130Z
wmdc Information: 0 : PartnershipCollection::Initialize - Devicemanager
starting with CurrentPartnershipProtocol:3, MinimumPartnershipProtocol:2, and
current DeviceManager version:0x06011b35
DateTime=2007-08-21T22:44:55.1672130Z
wmdc Information: 0 : Updating list of partnersips from the registry
DateTime=2007-08-21T22:44:55.1722130Z
wmdc Information: 0 : Updating list of tombstoned partnerships from the
registry
DateTime=2007-08-21T22:44:55.1812130Z
wmdc Information: 0 : Last connected partnership:
DateTime=2007-08-21T22:44:55.1822130Z
wmdc Information: 4 : Entering PartnershipCollection::OnDeviceConnect
(device
DateTime=2007-08-21T22:45:05.1082130Z
wmdc Information: 0 : Exiting PartnershipCollection::Initialize
DateTime=2007-08-21T22:45:05.1092130Z
wmdc Verbose: 0 : Creating a new partnership object for device
DateTime=2007-08-21T22:45:05.1202130Z
wmdc Verbose: 0 : Creating new Partnership6 object (id:1006302481)
DateTime=2007-08-21T22:45:05.1232130Z
wmdc Information: 0 : Partnership::TagWithCurrentVersion - Tagging current
partnership (0x3bfaf511) with PartnershipProtocol:3 and
PartnershipVersion:0x06011b35
DateTime=2007-08-21T22:45:05.1242130Z
wmdc Information: 0 : PartnershipCollection::ContainsCompatiblePartnersh ip -
Partnership (0x3bfaf511) exists and is compatible
DateTime=2007-08-21T22:45:05.1422130Z
wmdc Information: 0 : Setting current partnership to 3bfaf511
DateTime=2007-08-21T22:45:05.1422130Z
wmdc Verbose: 4 : [3bfaf511] Entering Partnership05::OnDeviceConnected
DateTime=2007-08-21T22:45:05.1432130Z
wmdc Information: 4 : [3bfaf511] Entering Partnership::OnDeviceConnected
DateTime=2007-08-21T22:45:05.1442130Z
wmdc Information: 4 : PartnershipCollection.OnDeviceConnectFailed
DateTime=2007-08-21T22:45:06.1642130Z
wmdc Information: 0 : PartnershipCollection.OnDeviceConnectFailed - Failure
resulted from disconnected device or session failure - setting state to
NotConnected
DateTime=2007-08-21T22:45:06.1642130Z
wmdc Information: 0 : PartnershipCollectionEnumerator::MoveNext -
Partnership (0x3bfaf511) found as next compatible partnership
DateTime=2007-08-21T22:45:06.1642130Z
wmdc Information: 0 : PartnershipCollection.RaiseStateChanged (device:,
state:PartnershipsExistNoDeviceConnected, message
DateTime=2007-08-21T22:45:06.1662130Z
wmdc Information: 0 : WindowsMobileDeviceCollection - Disconnect
DateTime=2007-08-21T22:45:06.1722130Z
wmdc Information: 4 : Entering PartnershipCollection::OnDeviceDisconnect
(device
DateTime=2007-08-21T22:45:06.1762130Z
wmdc Information: 4 : [3bfaf511] Entering Partnership::OnDeviceDisconnect
DateTime=2007-08-21T22:45:06.1772130Z
wmdc Information: 5 : [3bfaf511] Exiting Partnership::OnDeviceDisconnect
DateTime=2007-08-21T22:45:06.1772130Z
wmdc Information: 5 : Exiting Queued Thread in
PartnershipCollection::OnDeviceConnect (device
DateTime=2007-08-21T22:45:06.1892130Z
wmdc Information: 0 : Deleting partnership with id = 1006302481
(hwndOwner:0, options:SkipTombstone
DateTime=2007-08-21T22:45:06.2512130Z
wmdc Verbose: 4 : [3bfaf511] Entering Partnership6:elete (promptOwner:0,
options:SkipTombstone)
DateTime=2007-08-21T22:45:06.2542130Z
wmdc Verbose: 4 : [3bfaf511] Entering Partnership05:elete (promptOwner:0,
options:SkipTombstone, SkipPartnershipConfirmation)
DateTime=2007-08-21T22:45:06.2562130Z
wmdc Verbose: 4 : [3bfaf511] Entering Partnership03:elete (promptOwner:0,
options:SkipTombstone, SkipPartnershipConfirmation
DateTime=2007-08-21T22:45:06.2582130Z
wmdc Verbose: 0 : Deleting partnership data folder
DateTime=2007-08-21T22:45:06.2632130Z
wmdc Error: 0 : [3bfaf511] Error deleting partnership registry key
DateTime=2007-08-21T22:45:06.2772130Z
wmdc Error: 6 : [3bfaf511] Caught exception: System.ArgumentException:
Cannot delete a subkey tree because the subkey does not exist.
at System.ThrowHelper.ThrowArgumentException(Exceptio nResource resource)
at Microsoft.Win32.RegistryKey.DeleteSubKeyTree(Strin g subkey)
at Microsoft.WindowsMobile.DeviceManager.Partnership. Delete(IWin32Window
promptOwner, PartnershipDeletionOptions options)
DateTime=2007-08-21T22:45:06.3232130Z
wmdc Verbose: 5 : [3bfaf511] Exiting Partnership03:elete
DateTime=2007-08-21T22:45:06.3232130Z
wmdc Verbose: 5 : [3bfaf511] Exiting Partnership05:elete
DateTime=2007-08-21T22:45:06.3232130Z
wmdc Verbose: 5 : [3bfaf511] Exiting Partnership6:elete
DateTime=2007-08-21T22:45:06.3232130Z
wmdc Information: 0 : PartnershipCollectionEnumerator::MoveNext -
Partnership (0x3bfaf511) found as next compatible partnership
DateTime=2007-08-21T22:45:06.3262130Z
wmdc Information: 0 : PartnershipCollection.RaiseStateChanged (device:,
state:PartnershipsExistNoDeviceConnected, message
DateTime=2007-08-21T22:45:06.3262130Z
wmdc Information: 0 : PartnershipCollection.RaiseStateChanged - State
changed to same state as before, so not raising any further
DateTime=2007-08-21T22:45:06.3262130Z
wmdc Information: 5 : Exiting PartnershipCollection::OnDeviceDisconnect
(device
DateTime=2007-08-21T22:45:06.3752130Z
wmdc Information: 2 : Disposing of ~SyncCenterStatus
DateTime=2007-08-21T22:45:06.3832130Z
wmdc Information: 0 : Main.Main - Start Windows Mobile Device Center UI
DateTime=2007-08-21T22:51:25.1232130Z
wmdc Information: 0 : Toast::OnPartnershipStateChanged
(PartnershipsExistNoDeviceConnected)
DateTime=2007-08-21T22:51:25.6092130Z
wmdc Verbose: 0 : MainHost.OnPartnershipStateChanged
State:PartnershipsExistNoDeviceConnected
DateTime=2007-08-21T22:51:25.6292130Z
wmdc Verbose: 0 : [3bfaf511] Getting partnership image (iconSize:Size256)
DateTime=2007-08-21T22:51:25.6312130Z
wmdc Verbose: 0 : RightContentStack.Clear()
DateTime=2007-08-21T22:51:25.6492130Z
wmdc Information: 0 : PartnershipCollectionEnumerator::MoveNext -
Partnership (0x3bfaf511) found as next compatible partnership
DateTime=2007-08-21T22:51:25.7092130Z
wmdc Verbose: 0 : RightContentStack.Next() Control:NotConnectedPage -
Name:FolderList - Text:List of Task Folders Size:{Width=0, Height=0}
UserAction:False
DateTime=2007-08-21T22:51:25.7152130Z


21/08/2007 23:59:49
C:\Windows\WindowsMobile\wmdc.exe (6.1.6965.0)
--------- Begin logging ----------
wmdc Verbose: 1 : Creating new PartnershipCollection instance
DateTime=2007-08-21T22:59:49.9883830Z
wmdc Information: 0 : Entering PartnershipCollection::Initialize
DateTime=2007-08-21T22:59:49.9953830Z
wmdc Information: 0 : PartnershipCollection::Initialize - Devicemanager
starting with CurrentPartnershipProtocol:3, MinimumPartnershipProtocol:2, and
current DeviceManager version:0x06011b35
DateTime=2007-08-21T22:59:49.9963830Z
wmdc Information: 0 : Updating list of partnersips from the registry
DateTime=2007-08-21T22:59:50.0033830Z
wmdc Information: 0 : Updating list of tombstoned partnerships from the
registry
DateTime=2007-08-21T22:59:50.0103830Z
wmdc Information: 0 : Last connected partnership:
DateTime=2007-08-21T22:59:50.0103830Z
wmdc Information: 4 : Entering PartnershipCollection::OnDeviceConnect
(device
DateTime=2007-08-21T22:59:59.9553830Z
wmdc Information: 0 : Exiting PartnershipCollection::Initialize
DateTime=2007-08-21T22:59:59.9563830Z
wmdc Verbose: 0 : Creating a new partnership object for device
DateTime=2007-08-21T22:59:59.9663830Z
wmdc Verbose: 0 : Creating new Partnership6 object (id:3825011104)
DateTime=2007-08-21T22:59:59.9683830Z
wmdc Information: 0 : Partnership::TagWithCurrentVersion - Tagging current
partnership (0xe3fd09a0) with PartnershipProtocol:3 and
PartnershipVersion:0x06011b35
DateTime=2007-08-21T22:59:59.9703830Z
wmdc Information: 0 : PartnershipCollection::ContainsCompatiblePartnersh ip -
Partnership (0xe3fd09a0) exists and is compatible
DateTime=2007-08-21T22:59:59.9713830Z
wmdc Information: 0 : Setting current partnership to e3fd09a0
DateTime=2007-08-21T22:59:59.9723830Z
wmdc Verbose: 4 : [e3fd09a0] Entering Partnership05::OnDeviceConnected
DateTime=2007-08-21T22:59:59.9723830Z
wmdc Information: 4 : [e3fd09a0] Entering Partnership::OnDeviceConnected
DateTime=2007-08-21T22:59:59.9743830Z
wmdc Information: 4 : PartnershipCollection.OnDeviceConnectFailed
DateTime=2007-08-21T23:00:01.0253830Z
wmdc Information: 0 : PartnershipCollection.OnDeviceConnectFailed - Failure
resulted from disconnected device or session failure - setting state to
NotConnected
DateTime=2007-08-21T23:00:01.0253830Z
wmdc Information: 0 : PartnershipCollectionEnumerator::MoveNext -
Partnership (0xe3fd09a0) found as next compatible partnership
DateTime=2007-08-21T23:00:01.0263830Z
wmdc Information: 0 : PartnershipCollection.RaiseStateChanged (device:,
state:PartnershipsExistNoDeviceConnected, message
DateTime=2007-08-21T23:00:01.0273830Z
wmdc Information: 0 : WindowsMobileDeviceCollection - Disconnect
DateTime=2007-08-21T23:00:01.0453830Z
wmdc Information: 4 : Entering PartnershipCollection::OnDeviceDisconnect
(device
DateTime=2007-08-21T23:00:01.0483830Z
wmdc Information: 4 : [e3fd09a0] Entering Partnership::OnDeviceDisconnect
DateTime=2007-08-21T23:00:01.0493830Z
wmdc Information: 5 : [e3fd09a0] Exiting Partnership::OnDeviceDisconnect
DateTime=2007-08-21T23:00:01.0493830Z
wmdc Information: 0 : Deleting partnership with id = 3825011104
(hwndOwner:0, options:SkipTombstone
DateTime=2007-08-21T23:00:01.0533830Z
wmdc Verbose: 4 : [e3fd09a0] Entering Partnership6:elete (promptOwner:0,
options:SkipTombstone)
DateTime=2007-08-21T23:00:01.0553830Z
wmdc Information: 5 : Exiting Queued Thread in
PartnershipCollection::OnDeviceConnect (device
DateTime=2007-08-21T23:00:01.0573830Z
wmdc Verbose: 4 : [e3fd09a0] Entering Partnership05:elete (promptOwner:0,
options:SkipTombstone, SkipPartnershipConfirmation)
DateTime=2007-08-21T23:00:01.0613830Z
wmdc Verbose: 4 : [e3fd09a0] Entering Partnership03:elete (promptOwner:0,
options:SkipTombstone, SkipPartnershipConfirmation
DateTime=2007-08-21T23:00:01.0623830Z
wmdc Verbose: 0 : Deleting partnership data folder
DateTime=2007-08-21T23:00:01.0673830Z
wmdc Error: 0 : [e3fd09a0] Error deleting partnership registry key
DateTime=2007-08-21T23:00:01.0683830Z
wmdc Error: 6 : [e3fd09a0] Caught exception: System.ArgumentException:
Cannot delete a subkey tree because the subkey does not exist.
at System.ThrowHelper.ThrowArgumentException(Exceptio nResource resource)
at Microsoft.Win32.RegistryKey.DeleteSubKeyTree(Strin g subkey)
at Microsoft.WindowsMobile.DeviceManager.Partnership. Delete(IWin32Window
promptOwner, PartnershipDeletionOptions options)
DateTime=2007-08-21T23:00:01.1043830Z
wmdc Verbose: 5 : [e3fd09a0] Exiting Partnership03:elete
DateTime=2007-08-21T23:00:01.1053830Z
wmdc Verbose: 5 : [e3fd09a0] Exiting Partnership05:elete
DateTime=2007-08-21T23:00:01.1053830Z
wmdc Verbose: 5 : [e3fd09a0] Exiting Partnership6:elete
DateTime=2007-08-21T23:00:01.1053830Z
wmdc Information: 0 : PartnershipCollectionEnumerator::MoveNext -
Partnership (0xe3fd09a0) found as next compatible partnership
DateTime=2007-08-21T23:00:01.1053830Z
wmdc Information: 0 : PartnershipCollection.RaiseStateChanged (device:,
state:PartnershipsExistNoDeviceConnected, message
DateTime=2007-08-21T23:00:01.1203830Z
wmdc Information: 0 : PartnershipCollection.RaiseStateChanged - State
changed to same state as before, so not raising any further
DateTime=2007-08-21T23:00:01.1203830Z
wmdc Information: 5 : Exiting PartnershipCollection::OnDeviceDisconnect
(device
DateTime=2007-08-21T23:00:01.1253830Z
wmdc Information: 2 : Disposing of ~SyncCenterStatus
DateTime=2007-08-21T23:00:01.1323830Z


23/08/2007 21:11:54
C:\Windows\WindowsMobile\wmdc.exe (6.1.6965.0)
--------- Begin logging ----------
wmdc Verbose: 1 : Creating new PartnershipCollection instance
DateTime=2007-08-23T20:11:54.6744036Z
wmdc Information: 0 : Entering PartnershipCollection::Initialize
DateTime=2007-08-23T20:11:54.7014036Z
wmdc Information: 0 : PartnershipCollection::Initialize - Devicemanager
starting with CurrentPartnershipProtocol:3, MinimumPartnershipProtocol:2, and
current DeviceManager version:0x06011b35
DateTime=2007-08-23T20:11:54.7024036Z
wmdc Information: 0 : Updating list of partnersips from the registry
DateTime=2007-08-23T20:11:54.7084036Z
wmdc Information: 0 : Updating list of tombstoned partnerships from the
registry
DateTime=2007-08-23T20:11:54.7154036Z
wmdc Information: 0 : Last connected partnership:
DateTime=2007-08-23T20:11:54.7164036Z
wmdc Information: 0 : WindowsMobileDeviceCollection - Disconnect
DateTime=2007-08-23T20:11:54.7204036Z
wmdc Information: 2 : Disposing of ~SyncCenterStatus
DateTime=2007-08-23T20:11:54.7284036Z
wmdc Information: 0 : PartnershipCollection.RaiseStateChanged (device:,
state:NoPartnershipsNoDeviceConnected, message
DateTime=2007-08-23T20:11:54.7484036Z
wmdc Information: 0 : Exiting PartnershipCollection::Initialize
DateTime=2007-08-23T20:11:54.8774036Z
wmdc Information: 0 : Main.Main - Start Windows Mobile Device Center UI
DateTime=2007-08-23T22:02:18.7880000Z
wmdc Information: 0 : Toast::OnPartnershipStateChanged
(NoPartnershipsNoDeviceConnected)
DateTime=2007-08-23T22:02:20.9190000Z
wmdc Verbose: 0 : MainHost.OnPartnershipStateChanged
State:NoPartnershipsNoDeviceConnected
DateTime=2007-08-23T22:02:21.0060000Z
wmdc Verbose: 0 : RightContentStack.Clear()
DateTime=2007-08-23T22:02:21.0340000Z
wmdc Verbose: 0 : RightContentStack.Next() Control:NotConnectedPage -
Name:FolderList - Text:List of Task Folders Size:{Width=0, Height=0}
UserAction:False
DateTime=2007-08-23T22:02:21.1650000Z

It looks like I'm disconnecting the device before a partnership is created -
but I am leaving it connected...

Cheers Steve, hope this helps,

--
Ben


"Steve Spiller [MSFT]" wrote:

> Yes, you save the files in the \windows\windowsmobile folder. The way I get
> to the temp folder to do a Start -> Run then type in "%TEMP%". The files
> are Wmdc.log and WmdHost.log.
>
> --
> Thanks,
>
> Steve Spiller
> Development Lead
> Windows Mobile Device Center
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Ben" <> wrote in message
> news:4448339B-00A2-4A17-B1E6-...
> > Steve,
> >
> > Yes I restarted after doing it. Just to confirm - I copy and save the
> > files
> > from the website to the windows/windowsmobile folder...? Then restart.
> > Then
> > I should find the logs in the %temp\ folder...? There is certainly no
> > sign
> > of them in the temp folder.
> >
> > With no results, what I did instead was uninstalled WMDC again, deleted
> > all
> > files I could associated with it (wouldn't let me do some .dlls and some
> > 'MUI' files) then reinstalled wmdc. I then got the log file for
> > installation
> > of that from windows/inf/setupapi.dev (copied below). Is this of use to
> > you?
> > I attached the device whilst installing - then detached and re-attached
> > the
> > device to initiate wmdc. It got to the bit saying 'please wait whilst
> > wmdc
> > starts' then it hangs as before without getting a connection. Once again
> > the
> > device appeared under 'computer', then disappeared after about 30 seconds.
> > HTH.
> >
> > Ben

Steve,

Have you had any luck analysing these log files?

Cheers.
--
Ben


"Ben" wrote:

> Ah ha, I have it!
>
> WmdHost:
>
> 21/08/2007 23:44:55
> C:\Windows\WindowsMobile\WmdHost.exe (6.1.6965.0)
> --------- Begin logging ----------
> WmdHost Information: 0 : WmdHost.Main
> DateTime=2007-08-21T22:44:55.0112130Z
> WmdHost Information: 0 : WmdHost.Factory
> DateTime=2007-08-21T22:44:55.0592130Z
> WmdHost Information: 0 : HostForeman.StartFactories Enter IsRunning:False
> DateTime=2007-08-21T22:44:55.1082130Z
> WmdHost Information: 0 : HostForeman.Dispose()
> DateTime=2007-08-21T22:45:06.4032130Z
> WmdHost Information: 0 : HostForeman.StopFactories Enter
> DateTime=2007-08-21T22:45:06.4032130Z
>
>
> 21/08/2007 23:59:49
> C:\Windows\WindowsMobile\WmdHost.exe (6.1.6965.0)
> --------- Begin logging ----------
> WmdHost Information: 0 : WmdHost.Main
> DateTime=2007-08-21T22:59:49.8933830Z
> WmdHost Information: 0 : WmdHost.Factory
> DateTime=2007-08-21T22:59:49.9053830Z
> WmdHost Information: 0 : HostForeman.StartFactories Enter IsRunning:False
> DateTime=2007-08-21T22:59:49.9373830Z
> WmdHost Information: 0 : HostForeman.Dispose()
> DateTime=2007-08-21T23:00:01.1443830Z
> WmdHost Information: 0 : HostForeman.StopFactories Enter
> DateTime=2007-08-21T23:00:01.1443830Z
>
>
> 23/08/2007 21:11:54
> C:\Windows\WindowsMobile\WmdHost.exe (6.1.6965.0)
> --------- Begin logging ----------
> WmdHost Information: 0 : WmdHost.Main
> DateTime=2007-08-23T20:11:54.4384036Z
> WmdHost Information: 0 : WmdHost.Factory
> DateTime=2007-08-23T20:11:54.4504036Z
> WmdHost Information: 0 : HostForeman.StartFactories Enter IsRunning:False
> DateTime=2007-08-23T20:11:54.5644036Z
> WmdHost Information: 0 : HostForeman.Dispose()
> DateTime=2007-08-23T20:11:54.8364036Z
> WmdHost Information: 0 : HostForeman.StopFactories Enter
> DateTime=2007-08-23T20:11:54.8364036Z
>
> WMDC:
>
> 21/08/2007 23:44:55
> C:\Windows\WindowsMobile\wmdc.exe (6.1.6965.0)
> --------- Begin logging ----------
> wmdc Verbose: 1 : Creating new PartnershipCollection instance
> DateTime=2007-08-21T22:44:55.1592130Z
> wmdc Information: 0 : Entering PartnershipCollection::Initialize
> DateTime=2007-08-21T22:44:55.1652130Z
> wmdc Information: 0 : PartnershipCollection::Initialize - Devicemanager
> starting with CurrentPartnershipProtocol:3, MinimumPartnershipProtocol:2, and
> current DeviceManager version:0x06011b35
> DateTime=2007-08-21T22:44:55.1672130Z
> wmdc Information: 0 : Updating list of partnersips from the registry
> DateTime=2007-08-21T22:44:55.1722130Z
> wmdc Information: 0 : Updating list of tombstoned partnerships from the
> registry
> DateTime=2007-08-21T22:44:55.1812130Z
> wmdc Information: 0 : Last connected partnership:
> DateTime=2007-08-21T22:44:55.1822130Z
> wmdc Information: 4 : Entering PartnershipCollection::OnDeviceConnect
> (device
> DateTime=2007-08-21T22:45:05.1082130Z
> wmdc Information: 0 : Exiting PartnershipCollection::Initialize
> DateTime=2007-08-21T22:45:05.1092130Z
> wmdc Verbose: 0 : Creating a new partnership object for device
> DateTime=2007-08-21T22:45:05.1202130Z
> wmdc Verbose: 0 : Creating new Partnership6 object (id:1006302481)
> DateTime=2007-08-21T22:45:05.1232130Z
> wmdc Information: 0 : Partnership::TagWithCurrentVersion - Tagging current
> partnership (0x3bfaf511) with PartnershipProtocol:3 and
> PartnershipVersion:0x06011b35
> DateTime=2007-08-21T22:45:05.1242130Z
> wmdc Information: 0 : PartnershipCollection::ContainsCompatiblePartnersh ip -
> Partnership (0x3bfaf511) exists and is compatible
> DateTime=2007-08-21T22:45:05.1422130Z
> wmdc Information: 0 : Setting current partnership to 3bfaf511
> DateTime=2007-08-21T22:45:05.1422130Z
> wmdc Verbose: 4 : [3bfaf511] Entering Partnership05::OnDeviceConnected
> DateTime=2007-08-21T22:45:05.1432130Z
> wmdc Information: 4 : [3bfaf511] Entering Partnership::OnDeviceConnected
> DateTime=2007-08-21T22:45:05.1442130Z
> wmdc Information: 4 : PartnershipCollection.OnDeviceConnectFailed
> DateTime=2007-08-21T22:45:06.1642130Z
> wmdc Information: 0 : PartnershipCollection.OnDeviceConnectFailed - Failure
> resulted from disconnected device or session failure - setting state to
> NotConnected
> DateTime=2007-08-21T22:45:06.1642130Z
> wmdc Information: 0 : PartnershipCollectionEnumerator::MoveNext -
> Partnership (0x3bfaf511) found as next compatible partnership
> DateTime=2007-08-21T22:45:06.1642130Z
> wmdc Information: 0 : PartnershipCollection.RaiseStateChanged (device:,
> state:PartnershipsExistNoDeviceConnected, message
> DateTime=2007-08-21T22:45:06.1662130Z
> wmdc Information: 0 : WindowsMobileDeviceCollection - Disconnect
> DateTime=2007-08-21T22:45:06.1722130Z
> wmdc Information: 4 : Entering PartnershipCollection::OnDeviceDisconnect
> (device
> DateTime=2007-08-21T22:45:06.1762130Z
> wmdc Information: 4 : [3bfaf511] Entering Partnership::OnDeviceDisconnect
> DateTime=2007-08-21T22:45:06.1772130Z
> wmdc Information: 5 : [3bfaf511] Exiting Partnership::OnDeviceDisconnect
> DateTime=2007-08-21T22:45:06.1772130Z
> wmdc Information: 5 : Exiting Queued Thread in
> PartnershipCollection::OnDeviceConnect (device
> DateTime=2007-08-21T22:45:06.1892130Z
> wmdc Information: 0 : Deleting partnership with id = 1006302481
> (hwndOwner:0, options:SkipTombstone
> DateTime=2007-08-21T22:45:06.2512130Z
> wmdc Verbose: 4 : [3bfaf511] Entering Partnership6:elete (promptOwner:0,
> options:SkipTombstone)
> DateTime=2007-08-21T22:45:06.2542130Z
> wmdc Verbose: 4 : [3bfaf511] Entering Partnership05:elete (promptOwner:0,
> options:SkipTombstone, SkipPartnershipConfirmation)
> DateTime=2007-08-21T22:45:06.2562130Z
> wmdc Verbose: 4 : [3bfaf511] Entering Partnership03:elete (promptOwner:0,
> options:SkipTombstone, SkipPartnershipConfirmation
> DateTime=2007-08-21T22:45:06.2582130Z
> wmdc Verbose: 0 : Deleting partnership data folder
> DateTime=2007-08-21T22:45:06.2632130Z
> wmdc Error: 0 : [3bfaf511] Error deleting partnership registry key
> DateTime=2007-08-21T22:45:06.2772130Z
> wmdc Error: 6 : [3bfaf511] Caught exception: System.ArgumentException:
> Cannot delete a subkey tree because the subkey does not exist.
> at System.ThrowHelper.ThrowArgumentException(Exceptio nResource resource)
> at Microsoft.Win32.RegistryKey.DeleteSubKeyTree(Strin g subkey)
> at Microsoft.WindowsMobile.DeviceManager.Partnership. Delete(IWin32Window
> promptOwner, PartnershipDeletionOptions options)
> DateTime=2007-08-21T22:45:06.3232130Z
> wmdc Verbose: 5 : [3bfaf511] Exiting Partnership03:elete
> DateTime=2007-08-21T22:45:06.3232130Z
> wmdc Verbose: 5 : [3bfaf511] Exiting Partnership05:elete
> DateTime=2007-08-21T22:45:06.3232130Z
> wmdc Verbose: 5 : [3bfaf511] Exiting Partnership6:elete
> DateTime=2007-08-21T22:45:06.3232130Z
> wmdc Information: 0 : PartnershipCollectionEnumerator::MoveNext -
> Partnership (0x3bfaf511) found as next compatible partnership
> DateTime=2007-08-21T22:45:06.3262130Z
> wmdc Information: 0 : PartnershipCollection.RaiseStateChanged (device:,
> state:PartnershipsExistNoDeviceConnected, message
> DateTime=2007-08-21T22:45:06.3262130Z
> wmdc Information: 0 : PartnershipCollection.RaiseStateChanged - State
> changed to same state as before, so not raising any further
> DateTime=2007-08-21T22:45:06.3262130Z
> wmdc Information: 5 : Exiting PartnershipCollection::OnDeviceDisconnect
> (device
> DateTime=2007-08-21T22:45:06.3752130Z
> wmdc Information: 2 : Disposing of ~SyncCenterStatus
> DateTime=2007-08-21T22:45:06.3832130Z
> wmdc Information: 0 : Main.Main - Start Windows Mobile Device Center UI
> DateTime=2007-08-21T22:51:25.1232130Z
> wmdc Information: 0 : Toast::OnPartnershipStateChanged
> (PartnershipsExistNoDeviceConnected)
> DateTime=2007-08-21T22:51:25.6092130Z
> wmdc Verbose: 0 : MainHost.OnPartnershipStateChanged
> State:PartnershipsExistNoDeviceConnected
> DateTime=2007-08-21T22:51:25.6292130Z
> wmdc Verbose: 0 : [3bfaf511] Getting partnership image (iconSize:Size256)
> DateTime=2007-08-21T22:51:25.6312130Z
> wmdc Verbose: 0 : RightContentStack.Clear()
> DateTime=2007-08-21T22:51:25.6492130Z
> wmdc Information: 0 : PartnershipCollectionEnumerator::MoveNext -
> Partnership (0x3bfaf511) found as next compatible partnership
> DateTime=2007-08-21T22:51:25.7092130Z
> wmdc Verbose: 0 : RightContentStack.Next() Control:NotConnectedPage -
> Name:FolderList - Text:List of Task Folders Size:{Width=0, Height=0}
> UserAction:False
> DateTime=2007-08-21T22:51:25.7152130Z
>
>
> 21/08/2007 23:59:49
> C:\Windows\WindowsMobile\wmdc.exe (6.1.6965.0)
> --------- Begin logging ----------
> wmdc Verbose: 1 : Creating new PartnershipCollection instance
> DateTime=2007-08-21T22:59:49.9883830Z
> wmdc Information: 0 : Entering PartnershipCollection::Initialize
> DateTime=2007-08-21T22:59:49.9953830Z
> wmdc Information: 0 : PartnershipCollection::Initialize - Devicemanager
> starting with CurrentPartnershipProtocol:3, MinimumPartnershipProtocol:2, and
> current DeviceManager version:0x06011b35
> DateTime=2007-08-21T22:59:49.9963830Z
> wmdc Information: 0 : Updating list of partnersips from the registry
> DateTime=2007-08-21T22:59:50.0033830Z
> wmdc Information: 0 : Updating list of tombstoned partnerships from the
> registry
> DateTime=2007-08-21T22:59:50.0103830Z
> wmdc Information: 0 : Last connected partnership:
> DateTime=2007-08-21T22:59:50.0103830Z
> wmdc Information: 4 : Entering PartnershipCollection::OnDeviceConnect
> (device
> DateTime=2007-08-21T22:59:59.9553830Z
> wmdc Information: 0 : Exiting PartnershipCollection::Initialize
> DateTime=2007-08-21T22:59:59.9563830Z
> wmdc Verbose: 0 : Creating a new partnership object for device
> DateTime=2007-08-21T22:59:59.9663830Z
> wmdc Verbose: 0 : Creating new Partnership6 object (id:3825011104)
> DateTime=2007-08-21T22:59:59.9683830Z
> wmdc Information: 0 : Partnership::TagWithCurrentVersion - Tagging current
> partnership (0xe3fd09a0) with PartnershipProtocol:3 and
> PartnershipVersion:0x06011b35
> DateTime=2007-08-21T22:59:59.9703830Z
> wmdc Information: 0 : PartnershipCollection::ContainsCompatiblePartnersh ip -
> Partnership (0xe3fd09a0) exists and is compatible
> DateTime=2007-08-21T22:59:59.9713830Z
> wmdc Information: 0 : Setting current partnership to e3fd09a0
> DateTime=2007-08-21T22:59:59.9723830Z
> wmdc Verbose: 4 : [e3fd09a0] Entering Partnership05::OnDeviceConnected
> DateTime=2007-08-21T22:59:59.9723830Z
> wmdc Information: 4 : [e3fd09a0] Entering Partnership::OnDeviceConnected
> DateTime=2007-08-21T22:59:59.9743830Z
> wmdc Information: 4 : PartnershipCollection.OnDeviceConnectFailed
> DateTime=2007-08-21T23:00:01.0253830Z
> wmdc Information: 0 : PartnershipCollection.OnDeviceConnectFailed - Failure
> resulted from disconnected device or session failure - setting state to
> NotConnected
> DateTime=2007-08-21T23:00:01.0253830Z
> wmdc Information: 0 : PartnershipCollectionEnumerator::MoveNext -
> Partnership (0xe3fd09a0) found as next compatible partnership
> DateTime=2007-08-21T23:00:01.0263830Z
> wmdc Information: 0 : PartnershipCollection.RaiseStateChanged (device:,
> state:PartnershipsExistNoDeviceConnected, message
> DateTime=2007-08-21T23:00:01.0273830Z
> wmdc Information: 0 : WindowsMobileDeviceCollection - Disconnect
> DateTime=2007-08-21T23:00:01.0453830Z
> wmdc Information: 4 : Entering PartnershipCollection::OnDeviceDisconnect
> (device
> DateTime=2007-08-21T23:00:01.0483830Z
> wmdc Information: 4 : [e3fd09a0] Entering Partnership::OnDeviceDisconnect
> DateTime=2007-08-21T23:00:01.0493830Z
> wmdc Information: 5 : [e3fd09a0] Exiting Partnership::OnDeviceDisconnect
> DateTime=2007-08-21T23:00:01.0493830Z
> wmdc Information: 0 : Deleting partnership with id = 3825011104
> (hwndOwner:0, options:SkipTombstone
> DateTime=2007-08-21T23:00:01.0533830Z
> wmdc Verbose: 4 : [e3fd09a0] Entering Partnership6:elete (promptOwner:0,
> options:SkipTombstone)
> DateTime=2007-08-21T23:00:01.0553830Z
> wmdc Information: 5 : Exiting Queued Thread in
> PartnershipCollection::OnDeviceConnect (device
> DateTime=2007-08-21T23:00:01.0573830Z
> wmdc Verbose: 4 : [e3fd09a0] Entering Partnership05:elete (promptOwner:0,
> options:SkipTombstone, SkipPartnershipConfirmation)
> DateTime=2007-08-21T23:00:01.0613830Z
> wmdc Verbose: 4 : [e3fd09a0] Entering Partnership03:elete (promptOwner:0,
> options:SkipTombstone, SkipPartnershipConfirmation
> DateTime=2007-08-21T23:00:01.0623830Z
> wmdc Verbose: 0 : Deleting partnership data folder
> DateTime=2007-08-21T23:00:01.0673830Z
> wmdc Error: 0 : [e3fd09a0] Error deleting partnership registry key
> DateTime=2007-08-21T23:00:01.0683830Z
> wmdc Error: 6 : [e3fd09a0] Caught exception: System.ArgumentException:
> Cannot delete a subkey tree because the subkey does not exist.
> at System.ThrowHelper.ThrowArgumentException(Exceptio nResource resource)
> at Microsoft.Win32.RegistryKey.DeleteSubKeyTree(Strin g subkey)
> at Microsoft.WindowsMobile.DeviceManager.Partnership. Delete(IWin32Window
> promptOwner, PartnershipDeletionOptions options)
> DateTime=2007-08-21T23:00:01.1043830Z
> wmdc Verbose: 5 : [e3fd09a0] Exiting Partnership03:elete
> DateTime=2007-08-21T23:00:01.1053830Z
> wmdc Verbose: 5 : [e3fd09a0] Exiting Partnership05:elete
> DateTime=2007-08-21T23:00:01.1053830Z
> wmdc Verbose: 5 : [e3fd09a0] Exiting Partnership6:elete
> DateTime=2007-08-21T23:00:01.1053830Z
> wmdc Information: 0 : PartnershipCollectionEnumerator::MoveNext -
> Partnership (0xe3fd09a0) found as next compatible partnership
> DateTime=2007-08-21T23:00:01.1053830Z
> wmdc Information: 0 : PartnershipCollection.RaiseStateChanged (device:,
> state:PartnershipsExistNoDeviceConnected, message
> DateTime=2007-08-21T23:00:01.1203830Z
> wmdc Information: 0 : PartnershipCollection.RaiseStateChanged - State
> changed to same state as before, so not raising any further
> DateTime=2007-08-21T23:00:01.1203830Z
> wmdc Information: 5 : Exiting PartnershipCollection::OnDeviceDisconnect
> (device
> DateTime=2007-08-21T23:00:01.1253830Z
> wmdc Information: 2 : Disposing of ~SyncCenterStatus
> DateTime=2007-08-21T23:00:01.1323830Z
>
>
> 23/08/2007 21:11:54
> C:\Windows\WindowsMobile\wmdc.exe (6.1.6965.0)
> --------- Begin logging ----------
> wmdc Verbose: 1 : Creating new PartnershipCollection instance
> DateTime=2007-08-23T20:11:54.6744036Z
> wmdc Information: 0 : Entering PartnershipCollection::Initialize
> DateTime=2007-08-23T20:11:54.7014036Z
> wmdc Information: 0 : PartnershipCollection::Initialize - Devicemanager
> starting with CurrentPartnershipProtocol:3, MinimumPartnershipProtocol:2, and
> current DeviceManager version:0x06011b35
> DateTime=2007-08-23T20:11:54.7024036Z
> wmdc Information: 0 : Updating list of partnersips from the registry
> DateTime=2007-08-23T20:11:54.7084036Z