No love with WMDC 6.1 and Vista x64

Just installed Windows Mobile Device Center 6.1 onto a clean copy of Vista
Ultimate x64 and Outlook 2007 (pst empty). WMDC was installed meticulously
following the steps outlined on the WMDC website and consequently my USB Dell
Axim (X5 with PocketPC 2003) appears in Device Manager under Mobile devices
as well as does the Windows Mobile-based device node under Portable Devices.

What first appears is the popup "Changes to synchronization settings with
Server ActiveSync cannot be made at this time." The UI only shows a red X
and the word "Error." If I close the program, disconnect the Axim, and start
only the program I get the same popup but the UI now has the word Axim in the
lower left corner accompanied by Not Connected and I get a Mobile Device
Settings dialog which I did not have before. Underneath that I get only
Connection Settings in which I cleared the Bluetooth checkbox but allowed the
USB connections and device authentication to remain checked (tried unchecking
that but it didn't help either).

Now if I plug in the Axim with WMDC open, I get the same "Changes to
synchronization settings..." popup and red X but now I get a new option under
Mobile Device Settings, "Backup and Restore" which does allow me to backup
the device. At no time do I get an option to setup a partnership.

I looked at the other posts on this and tried reinstalling but that didn't
help. From a non Microsoft forum it was suggested to drop in the debugging
logger into /Windows/WindowsMobile but Windows denies me access saying I
don't have sufficient permissions. This is certainly strange being the only
user and administrator of a clean copy of Windows and it may or may not be a
clue to the problem. The security tab shows I have full permissions on the
folder but CREATOR OWNER and TrustedInstaller do not.

Another possibility is that I may have declined VB scripting support in the
installation of Outlook. I don't know if that would have any impact but I
know I've done that on my other machines for security reasons. I can say
that ActiveSync, Outlook 2000, and the Axim worked fine together on XP.

Any suggestions? or just another curious vista x64 incompatibility?
--
Brad

Hello,

Vista has an oddity with saving files from the internet directly to a folder
that requires you to elevate to access. Try saving the .config files for
logging to your desktop first, then copying them into
\windows\windowsmobile. It sounds like the call the desktop makes to the
device to get it's sync configuration is failing for some reason, but
without the logs it's hard to say.

--
Thanks,

Steve Spiller
Development Lead
Windows Mobile Device Center

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

"Brad" <> wrote in message
news:7EEE763C-B09C-45D9-B0B4-...
> Just installed Windows Mobile Device Center 6.1 onto a clean copy of Vista
> Ultimate x64 and Outlook 2007 (pst empty). WMDC was installed
> meticulously
> following the steps outlined on the WMDC website and consequently my USB
> Dell
> Axim (X5 with PocketPC 2003) appears in Device Manager under Mobile
> devices
> as well as does the Windows Mobile-based device node under Portable
> Devices.
>
> What first appears is the popup "Changes to synchronization settings with
> Server ActiveSync cannot be made at this time." The UI only shows a red X
> and the word "Error." If I close the program, disconnect the Axim, and
> start
> only the program I get the same popup but the UI now has the word Axim in
> the
> lower left corner accompanied by Not Connected and I get a Mobile Device
> Settings dialog which I did not have before. Underneath that I get only
> Connection Settings in which I cleared the Bluetooth checkbox but allowed
> the
> USB connections and device authentication to remain checked (tried
> unchecking
> that but it didn't help either).
>
> Now if I plug in the Axim with WMDC open, I get the same "Changes to
> synchronization settings..." popup and red X but now I get a new option
> under
> Mobile Device Settings, "Backup and Restore" which does allow me to backup
> the device. At no time do I get an option to setup a partnership.
>
> I looked at the other posts on this and tried reinstalling but that didn't
> help. From a non Microsoft forum it was suggested to drop in the
> debugging
> logger into /Windows/WindowsMobile but Windows denies me access saying I
> don't have sufficient permissions. This is certainly strange being the
> only
> user and administrator of a clean copy of Windows and it may or may not be
> a
> clue to the problem. The security tab shows I have full permissions on
> the
> folder but CREATOR OWNER and TrustedInstaller do not.
>
> Another possibility is that I may have declined VB scripting support in
> the
> installation of Outlook. I don't know if that would have any impact but I
> know I've done that on my other machines for security reasons. I can say
> that ActiveSync, Outlook 2000, and the Axim worked fine together on XP.
>
> Any suggestions? or just another curious vista x64 incompatibility?
> --
> Brad

Steve,

Thanks for your response. Did so and the log files went to
\Brad\AppData\Local\Temp (not \Windows\Temp), if that is important. I don't
know if it is appropriate to post the results here but they may mean more to
you than to me. Also, I got the usual server ActiveSync error popup but I
didn't get the same UI as I did before - it now hangs at the waiting to
connect green screen (if it means anything). I can also send the pertinent
portion of the setupdev log if you like. It has quite a few triple bangs
(but you learn to tolerate those in Linux).


10/22/2007 12:36:36 PM
C:\Windows\WindowsMobile\WmdHost.exe (6.1.6965.0)
--------- Begin logging ----------
WmdHost Information: 0 : WmdHost.Main
DateTime=2007-10-22T17:36:36.0530461Z
WmdHost Information: 0 : WmdHost.Factory
DateTime=2007-10-22T17:36:36.1624211Z
WmdHost Information: 0 : HostForeman.StartFactories Enter IsRunning:False
DateTime=2007-10-22T17:36:36.6311711Z
WmdHost Information: 0 : HostForeman.Dispose()
DateTime=2007-10-22T17:39:27.9483616Z
WmdHost Information: 0 : HostForeman.StopFactories Enter
DateTime=2007-10-22T17:39:27.9503146Z


10/22/2007 12:36:36 PM
C:\Windows\WindowsMobile\wmdc.exe (6.1.6965.0)
--------- Begin logging ----------
wmdc Verbose: 1 : Creating new PartnershipCollection instance
DateTime=2007-10-22T17:36:37.0374211Z
wmdc Information: 0 : Entering PartnershipCollection::Initialize
DateTime=2007-10-22T17:36:37.1780461Z
wmdc Information: 0 : PartnershipCollection::Initialize - Devicemanager
starting with CurrentPartnershipProtocol:3, MinimumPartnershipProtocol:2, and
current DeviceManager version:0x06011b35
DateTime=2007-10-22T17:36:37.1936711Z
wmdc Information: 0 : Updating list of partnersips from the registry
DateTime=2007-10-22T17:36:37.2561711Z
wmdc Information: 0 : Updating list of tombstoned partnerships from the
registry
DateTime=2007-10-22T17:36:37.3030461Z
wmdc Information: 0 : Last connected partnership:
DateTime=2007-10-22T17:36:37.3030461Z
wmdc Information: 4 : Entering PartnershipCollection::OnDeviceConnect
(device:Microsoft.WindowsMobile.DeviceManager.Wind owsMobileDevice2003)
DateTime=2007-10-22T17:36:37.3186711Z
wmdc Information: 0 : Exiting PartnershipCollection::Initialize
DateTime=2007-10-22T17:36:37.3186711Z
wmdc Verbose: 0 : Creating a new partnership object for device
Microsoft.WindowsMobile.DeviceManager.WindowsMobil eDevice2003
DateTime=2007-10-22T17:36:37.4749211Z
wmdc Verbose: 0 : Creating new Partnership03 object (id:3623739192)
DateTime=2007-10-22T17:36:37.5061711Z
wmdc Information: 0 : Partnership::TagWithCurrentVersion - Tagging current
partnership (0xd7fddf38) with PartnershipProtocol:3 and
PartnershipVersion:0x06011b35
DateTime=2007-10-22T17:36:37.5217961Z
wmdc Information: 0 : PartnershipCollection::ContainsCompatiblePartnersh ip -
Partnership (0xd7fddf38) exists and is compatible
DateTime=2007-10-22T17:36:37.5374211Z
wmdc Information: 0 : Setting current partnership to d7fddf38
DateTime=2007-10-22T17:36:37.5374211Z
wmdc Information: 4 : [d7fddf38] Entering Partnership::OnDeviceConnected
DateTime=2007-10-22T17:36:37.5530461Z
wmdc Information: 0 : Processing guest partnership
DateTime=2007-10-22T17:36:37.5530461Z
wmdc Information: 0 : Config XML to device:
<wap-provisioningdoc><characteristic type="Sync" ><characteristic-query
recursive="false" type="Settings"
></characteristic-query></characteristic></wap-provisioningdoc>
DateTime=2007-10-22T17:36:37.9436711Z
wmdc Information: 4 : PartnershipCollection.OnDeviceConnectFailed
DateTime=2007-10-22T17:36:40.8839776Z
wmdc Error: 6 : Caught exception:
Microsoft.WindowsMobile.Rapi.ConfigurationExceptio n: CeProcessConfig Failed,
result: 0x80042008, returning: <wap-provisioningdoc><characteristic
type="Sync"><characteristic recursive="false" type="Settings"><parm
name="ConflictResolution" value="1"/><parm name="DisconnectWhenDone"
value="1"/><parm name="BodyTruncation" value="5120"/><parm
name="AutoSyncWhenCradled" value="1"/><parm name="SyncAfterTimeWhenCradled"
value="0"/><parm name="AutoSync" value="0"/><parm name="SyncAfterTime"
value="30"/><parm name="PeakStartTime" value="0800"/><parm name="PeakEndTime"
value="1800"/><parm name="PeakFrequency" value="0"/><parm
name="OffPeakFrequency" value="0"/><parm name="SyncWhenRoaming"
value="0"/><parm name="RadioEnabledDevice" value="0"/><parm
name="DeviceSMSAddress" value=""/><parm name="NotificationsSupported"
value="0"/><parm name="SyncWhenRoaming" value="0"/><parm
name="ClientProtocolVersion" value="1.0"/><parm name="OutboundMailDelay"
value="0"/><parm name="SendMailItemsImmediately" value="0"/><parm
name="DevicePhoneReadOnly" value="0"/><parm name="DevicePhoneNumber"
value=""/><parm name="CarrierConnector" value=""/><parm
name="DeviceAddressingMethod" value="1"/><parm name="VersionMajor"
value="1"/><parm name="VersionMinor" value="1"/><characteristic
type="PeakDays"><parm name="Sun" value="0"/><parm name="Mon" value="1"/><parm
name="Tue" value="1"/><parm name="Wed" value="1"/><parm name="Thr"
value="1"/><parm name="Fri" value="1"/><parm name="Sat"
value="0"/></characteristic><characteristic
type="CarrierConnectorList"/></characteristic></characteristic></wap-provisioningdoc>

at Microsoft.WindowsMobile.Rapi.Session.ThrowErrorFor Code(UInt32 err,
String message)
at Microsoft.WindowsMobile.Rapi.Device.<>c__DisplayCl ass1.<Configure>b__0()
at Microsoft.WindowsMobile.Rapi.RapiManager.Invoke(Me thodInvoker method)
at Microsoft.WindowsMobile.Rapi.Device.Configure(IntP tr input)
at
Microsoft.WindowsMobile.DeviceManager.Configuratio nManager.ProcessStatic(IDevice
device, ConfigurationOptions request, Action operationType, Int64 promptOwner)
at
Microsoft.WindowsMobile.DeviceManager.Partnership2 003.UpdateServerVersion()
at
Microsoft.WindowsMobile.DeviceManager.Partnership2 003.ReadFromDevice(Boolean
updateServerVersion)
at
Microsoft.WindowsMobile.DeviceManager.Partnership. <>c__DisplayClass1.<OnDeviceConnected>b__0()
at Microsoft.WindowsMobile.Rapi.RapiManager.Invoke(Me thodInvoker method)
at
Microsoft.WindowsMobile.DeviceManager.Partnership. OnDeviceConnected(WindowsMobileDevice device)
at
Microsoft.WindowsMobile.DeviceManager.PartnershipC ollection.<>c__DisplayClass7.<OnDeviceConnect>b__6 (Object )
DateTime=2007-10-22T17:36:41.0187346Z
wmdc Information: 0 : PartnershipCollection.RaiseStateChanged (device:,
state:ConnectFailed, message
DateTime=2007-10-22T17:36:41.0402186Z
wmdc Information: 5 : Exiting Queued Thread in
PartnershipCollection::OnDeviceConnect
(device:Microsoft.WindowsMobile.DeviceManager.Wind owsMobileDevice2003)
DateTime=2007-10-22T17:36:41.0714686Z
wmdc Information: 0 : WindowsMobileDeviceCollection - Disconnect
DateTime=2007-10-22T17:39:27.5821531Z
wmdc Information: 4 : Entering PartnershipCollection::OnDeviceDisconnect
(device:Microsoft.WindowsMobile.DeviceManager.Wind owsMobileDevice2003)
DateTime=2007-10-22T17:39:27.6759031Z
wmdc Information: 4 : [d7fddf38] Entering Partnership::OnDeviceDisconnect
DateTime=2007-10-22T17:39:27.6759031Z
wmdc Information: 5 : [d7fddf38] Exiting Partnership::OnDeviceDisconnect
DateTime=2007-10-22T17:39:27.6759031Z
wmdc Information: 0 : Deleting partnership with id = 3623739192
(hwndOwner:0, options:SkipTombstone
DateTime=2007-10-22T17:39:27.7384031Z
wmdc Verbose: 4 : [d7fddf38] Entering Partnership03:elete (promptOwner:0,
options:SkipTombstone
DateTime=2007-10-22T17:39:27.7384031Z
wmdc Verbose: 0 : Deleting partnership data folder
DateTime=2007-10-22T17:39:27.7540281Z
wmdc Error: 0 : [d7fddf38] Error deleting partnership registry key
DateTime=2007-10-22T17:39:27.7852781Z
wmdc Error: 6 : [d7fddf38] Caught exception: System.ArgumentException:
Cannot delete a subkey tree because the subkey does not exist.
at Microsoft.Win32.RegistryKey.DeleteSubKeyTree(Strin g subkey)
at Microsoft.WindowsMobile.DeviceManager.Partnership. Delete(IWin32Window
promptOwner, PartnershipDeletionOptions options)
DateTime=2007-10-22T17:39:27.8321531Z
wmdc Verbose: 5 : [d7fddf38] Exiting Partnership03:elete
DateTime=2007-10-22T17:39:27.8321531Z
wmdc Information: 0 : PartnershipCollectionEnumerator::MoveNext -
Partnership (0xd7fddf38) found as next compatible partnership
DateTime=2007-10-22T17:39:27.8321531Z
wmdc Information: 0 : PartnershipCollection.RaiseStateChanged (device:,
state:PartnershipsExistNoDeviceConnected, message
DateTime=2007-10-22T17:39:27.8321531Z
wmdc Information: 5 : Exiting PartnershipCollection::OnDeviceDisconnect
(device:Microsoft.WindowsMobile.DeviceManager.Wind owsMobileDevice2003)
DateTime=2007-10-22T17:39:27.8477781Z
wmdc Information: 2 : Disposing of ~SyncCenterStatus
DateTime=2007-10-22T17:39:27.8790281Z

--
Brad


"Steve Spiller [MSFT]" wrote:

> Hello,
>
> Vista has an oddity with saving files from the internet directly to a folder
> that requires you to elevate to access. Try saving the .config files for
> logging to your desktop first, then copying them into
> \windows\windowsmobile. It sounds like the call the desktop makes to the
> device to get it's sync configuration is failing for some reason, but
> without the logs it's hard to say.
>
> --
> Thanks,
>
> Steve Spiller
> Development Lead
> Windows Mobile Device Center
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Brad" <> wrote in message
> news:7EEE763C-B09C-45D9-B0B4-...
> > Just installed Windows Mobile Device Center 6.1 onto a clean copy of Vista
> > Ultimate x64 and Outlook 2007 (pst empty). WMDC was installed
> > meticulously
> > following the steps outlined on the WMDC website and consequently my USB
> > Dell
> > Axim (X5 with PocketPC 2003) appears in Device Manager under Mobile
> > devices
> > as well as does the Windows Mobile-based device node under Portable
> > Devices.
> >
> > What first appears is the popup "Changes to synchronization settings with
> > Server ActiveSync cannot be made at this time." The UI only shows a red X
> > and the word "Error." If I close the program, disconnect the Axim, and
> > start
> > only the program I get the same popup but the UI now has the word Axim in
> > the
> > lower left corner accompanied by Not Connected and I get a Mobile Device
> > Settings dialog which I did not have before. Underneath that I get only
> > Connection Settings in which I cleared the Bluetooth checkbox but allowed
> > the
> > USB connections and device authentication to remain checked (tried
> > unchecking
> > that but it didn't help either).
> >
> > Now if I plug in the Axim with WMDC open, I get the same "Changes to
> > synchronization settings..." popup and red X but now I get a new option
> > under
> > Mobile Device Settings, "Backup and Restore" which does allow me to backup
> > the device. At no time do I get an option to setup a partnership.
> >
> > I looked at the other posts on this and tried reinstalling but that didn't
> > help. From a non Microsoft forum it was suggested to drop in the
> > debugging
> > logger into /Windows/WindowsMobile but Windows denies me access saying I
> > don't have sufficient permissions. This is certainly strange being the
> > only
> > user and administrator of a clean copy of Windows and it may or may not be
> > a
> > clue to the problem. The security tab shows I have full permissions on
> > the
> > folder but CREATOR OWNER and TrustedInstaller do not.
> >
> > Another possibility is that I may have declined VB scripting support in
> > the
> > installation of Outlook. I don't know if that would have any impact but I
> > know I've done that on my other machines for security reasons. I can say
> > that ActiveSync, Outlook 2000, and the Axim worked fine together on XP.
> >
> > Any suggestions? or just another curious vista x64 incompatibility?
> > --
> > Brad
>
>

Clarification to above, the UI presented at device insertion says "Please
wait while Windows Mobile Device Center starts" and remains after ejection.
It can only be killed through task manager.
--
Brad


"Steve Spiller [MSFT]" wrote:

> Hello,
>
> Vista has an oddity with saving files from the internet directly to a folder
> that requires you to elevate to access. Try saving the .config files for
> logging to your desktop first, then copying them into
> \windows\windowsmobile. It sounds like the call the desktop makes to the
> device to get it's sync configuration is failing for some reason, but
> without the logs it's hard to say.
>
> --
> Thanks,
>
> Steve Spiller
> Development Lead
> Windows Mobile Device Center
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Brad" <> wrote in message
> news:7EEE763C-B09C-45D9-B0B4-...
> > Just installed Windows Mobile Device Center 6.1 onto a clean copy of Vista
> > Ultimate x64 and Outlook 2007 (pst empty). WMDC was installed
> > meticulously
> > following the steps outlined on the WMDC website and consequently my USB
> > Dell
> > Axim (X5 with PocketPC 2003) appears in Device Manager under Mobile
> > devices
> > as well as does the Windows Mobile-based device node under Portable
> > Devices.
> >
> > What first appears is the popup "Changes to synchronization settings with
> > Server ActiveSync cannot be made at this time." The UI only shows a red X
> > and the word "Error." If I close the program, disconnect the Axim, and
> > start
> > only the program I get the same popup but the UI now has the word Axim in
> > the
> > lower left corner accompanied by Not Connected and I get a Mobile Device
> > Settings dialog which I did not have before. Underneath that I get only
> > Connection Settings in which I cleared the Bluetooth checkbox but allowed
> > the
> > USB connections and device authentication to remain checked (tried
> > unchecking
> > that but it didn't help either).
> >
> > Now if I plug in the Axim with WMDC open, I get the same "Changes to
> > synchronization settings..." popup and red X but now I get a new option
> > under
> > Mobile Device Settings, "Backup and Restore" which does allow me to backup
> > the device. At no time do I get an option to setup a partnership.
> >
> > I looked at the other posts on this and tried reinstalling but that didn't
> > help. From a non Microsoft forum it was suggested to drop in the
> > debugging
> > logger into /Windows/WindowsMobile but Windows denies me access saying I
> > don't have sufficient permissions. This is certainly strange being the
> > only
> > user and administrator of a clean copy of Windows and it may or may not be
> > a
> > clue to the problem. The security tab shows I have full permissions on
> > the
> > folder but CREATOR OWNER and TrustedInstaller do not.
> >
> > Another possibility is that I may have declined VB scripting support in
> > the
> > installation of Outlook. I don't know if that would have any impact but I
> > know I've done that on my other machines for security reasons. I can say
> > that ActiveSync, Outlook 2000, and the Axim worked fine together on XP.
> >
> > Any suggestions? or just another curious vista x64 incompatibility?
> > --
> > Brad
>
>

This is what I wanted. I've got my team taking a look at the error now.

--
Thanks,

Steve Spiller
Development Lead
Windows Mobile Device Center

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

"Brad" <> wrote in message
news:F3C6DF03-5029-48EE-A432-...
> Steve,
>
> Thanks for your response. Did so and the log files went to
> \Brad\AppData\Local\Temp (not \Windows\Temp), if that is important. I
> don't
> know if it is appropriate to post the results here but they may mean more
> to
> you than to me. Also, I got the usual server ActiveSync error popup but I
> didn't get the same UI as I did before - it now hangs at the waiting to
> connect green screen (if it means anything). I can also send the
> pertinent
> portion of the setupdev log if you like. It has quite a few triple bangs
> (but you learn to tolerate those in Linux).
>
>
> 10/22/2007 12:36:36 PM
> C:\Windows\WindowsMobile\WmdHost.exe (6.1.6965.0)
> --------- Begin logging ----------
> WmdHost Information: 0 : WmdHost.Main
> DateTime=2007-10-22T17:36:36.0530461Z
> WmdHost Information: 0 : WmdHost.Factory
> DateTime=2007-10-22T17:36:36.1624211Z
> WmdHost Information: 0 : HostForeman.StartFactories Enter IsRunning:False
> DateTime=2007-10-22T17:36:36.6311711Z
> WmdHost Information: 0 : HostForeman.Dispose()
> DateTime=2007-10-22T17:39:27.9483616Z
> WmdHost Information: 0 : HostForeman.StopFactories Enter
> DateTime=2007-10-22T17:39:27.9503146Z
>
>
> 10/22/2007 12:36:36 PM
> C:\Windows\WindowsMobile\wmdc.exe (6.1.6965.0)
> --------- Begin logging ----------
> wmdc Verbose: 1 : Creating new PartnershipCollection instance
> DateTime=2007-10-22T17:36:37.0374211Z
> wmdc Information: 0 : Entering PartnershipCollection::Initialize
> DateTime=2007-10-22T17:36:37.1780461Z
> wmdc Information: 0 : PartnershipCollection::Initialize - Devicemanager
> starting with CurrentPartnershipProtocol:3, MinimumPartnershipProtocol:2,
> and
> current DeviceManager version:0x06011b35
> DateTime=2007-10-22T17:36:37.1936711Z
> wmdc Information: 0 : Updating list of partnersips from the registry
> DateTime=2007-10-22T17:36:37.2561711Z
> wmdc Information: 0 : Updating list of tombstoned partnerships from the
> registry
> DateTime=2007-10-22T17:36:37.3030461Z
> wmdc Information: 0 : Last connected partnership:
> DateTime=2007-10-22T17:36:37.3030461Z
> wmdc Information: 4 : Entering PartnershipCollection::OnDeviceConnect
> (device:Microsoft.WindowsMobile.DeviceManager.Wind owsMobileDevice2003)
> DateTime=2007-10-22T17:36:37.3186711Z
> wmdc Information: 0 : Exiting PartnershipCollection::Initialize
> DateTime=2007-10-22T17:36:37.3186711Z
> wmdc Verbose: 0 : Creating a new partnership object for device
> Microsoft.WindowsMobile.DeviceManager.WindowsMobil eDevice2003
> DateTime=2007-10-22T17:36:37.4749211Z
> wmdc Verbose: 0 : Creating new Partnership03 object (id:3623739192)
> DateTime=2007-10-22T17:36:37.5061711Z
> wmdc Information: 0 : Partnership::TagWithCurrentVersion - Tagging current
> partnership (0xd7fddf38) with PartnershipProtocol:3 and
> PartnershipVersion:0x06011b35
> DateTime=2007-10-22T17:36:37.5217961Z
> wmdc Information: 0 :
> PartnershipCollection::ContainsCompatiblePartnersh ip -
> Partnership (0xd7fddf38) exists and is compatible
> DateTime=2007-10-22T17:36:37.5374211Z
> wmdc Information: 0 : Setting current partnership to d7fddf38
> DateTime=2007-10-22T17:36:37.5374211Z
> wmdc Information: 4 : [d7fddf38] Entering Partnership::OnDeviceConnected
> DateTime=2007-10-22T17:36:37.5530461Z
> wmdc Information: 0 : Processing guest partnership
> DateTime=2007-10-22T17:36:37.5530461Z
> wmdc Information: 0 : Config XML to device:
> <wap-provisioningdoc><characteristic type="Sync" ><characteristic-query
> recursive="false" type="Settings"
>></characteristic-query></characteristic></wap-provisioningdoc>
> DateTime=2007-10-22T17:36:37.9436711Z
> wmdc Information: 4 : PartnershipCollection.OnDeviceConnectFailed
> DateTime=2007-10-22T17:36:40.8839776Z
> wmdc Error: 6 : Caught exception:
> Microsoft.WindowsMobile.Rapi.ConfigurationExceptio n: CeProcessConfig
> Failed,
> result: 0x80042008, returning: <wap-provisioningdoc><characteristic
> type="Sync"><characteristic recursive="false" type="Settings"><parm
> name="ConflictResolution" value="1"/><parm name="DisconnectWhenDone"
> value="1"/><parm name="BodyTruncation" value="5120"/><parm
> name="AutoSyncWhenCradled" value="1"/><parm
> name="SyncAfterTimeWhenCradled"
> value="0"/><parm name="AutoSync" value="0"/><parm name="SyncAfterTime"
> value="30"/><parm name="PeakStartTime" value="0800"/><parm
> name="PeakEndTime"
> value="1800"/><parm name="PeakFrequency" value="0"/><parm
> name="OffPeakFrequency" value="0"/><parm name="SyncWhenRoaming"
> value="0"/><parm name="RadioEnabledDevice" value="0"/><parm
> name="DeviceSMSAddress" value=""/><parm name="NotificationsSupported"
> value="0"/><parm name="SyncWhenRoaming" value="0"/><parm
> name="ClientProtocolVersion" value="1.0"/><parm name="OutboundMailDelay"
> value="0"/><parm name="SendMailItemsImmediately" value="0"/><parm
> name="DevicePhoneReadOnly" value="0"/><parm name="DevicePhoneNumber"
> value=""/><parm name="CarrierConnector" value=""/><parm
> name="DeviceAddressingMethod" value="1"/><parm name="VersionMajor"
> value="1"/><parm name="VersionMinor" value="1"/><characteristic
> type="PeakDays"><parm name="Sun" value="0"/><parm name="Mon"
> value="1"/><parm
> name="Tue" value="1"/><parm name="Wed" value="1"/><parm name="Thr"
> value="1"/><parm name="Fri" value="1"/><parm name="Sat"
> value="0"/></characteristic><characteristic
> type="CarrierConnectorList"/></characteristic></characteristic></wap-provisioningdoc>
>
> at Microsoft.WindowsMobile.Rapi.Session.ThrowErrorFor Code(UInt32 err,
> String message)
> at
> Microsoft.WindowsMobile.Rapi.Device.<>c__DisplayCl ass1.<Configure>b__0()
> at Microsoft.WindowsMobile.Rapi.RapiManager.Invoke(Me thodInvoker method)
> at Microsoft.WindowsMobile.Rapi.Device.Configure(IntP tr input)
> at
> Microsoft.WindowsMobile.DeviceManager.Configuratio nManager.ProcessStatic(IDevice
> device, ConfigurationOptions request, Action operationType, Int64
> promptOwner)
> at
> Microsoft.WindowsMobile.DeviceManager.Partnership2 003.UpdateServerVersion()
> at
> Microsoft.WindowsMobile.DeviceManager.Partnership2 003.ReadFromDevice(Boolean
> updateServerVersion)
> at
> Microsoft.WindowsMobile.DeviceManager.Partnership. <>c__DisplayClass1.<OnDeviceConnected>b__0()
> at Microsoft.WindowsMobile.Rapi.RapiManager.Invoke(Me thodInvoker method)
> at
> Microsoft.WindowsMobile.DeviceManager.Partnership. OnDeviceConnected(WindowsMobileDevice
> device)
> at
> Microsoft.WindowsMobile.DeviceManager.PartnershipC ollection.<>c__DisplayClass7.<OnDeviceConnect>b__6 (Object
> )
> DateTime=2007-10-22T17:36:41.0187346Z
> wmdc Information: 0 : PartnershipCollection.RaiseStateChanged (device:,
> state:ConnectFailed, message
> DateTime=2007-10-22T17:36:41.0402186Z
> wmdc Information: 5 : Exiting Queued Thread in
> PartnershipCollection::OnDeviceConnect
> (device:Microsoft.WindowsMobile.DeviceManager.Wind owsMobileDevice2003)
> DateTime=2007-10-22T17:36:41.0714686Z
> wmdc Information: 0 : WindowsMobileDeviceCollection - Disconnect
> DateTime=2007-10-22T17:39:27.5821531Z
> wmdc Information: 4 : Entering PartnershipCollection::OnDeviceDisconnect
> (device:Microsoft.WindowsMobile.DeviceManager.Wind owsMobileDevice2003)
> DateTime=2007-10-22T17:39:27.6759031Z
> wmdc Information: 4 : [d7fddf38] Entering Partnership::OnDeviceDisconnect
> DateTime=2007-10-22T17:39:27.6759031Z
> wmdc Information: 5 : [d7fddf38] Exiting Partnership::OnDeviceDisconnect
> DateTime=2007-10-22T17:39:27.6759031Z
> wmdc Information: 0 : Deleting partnership with id = 3623739192
> (hwndOwner:0, options:SkipTombstone
> DateTime=2007-10-22T17:39:27.7384031Z
> wmdc Verbose: 4 : [d7fddf38] Entering Partnership03:elete
> (promptOwner:0,
> options:SkipTombstone
> DateTime=2007-10-22T17:39:27.7384031Z
> wmdc Verbose: 0 : Deleting partnership data folder
> DateTime=2007-10-22T17:39:27.7540281Z
> wmdc Error: 0 : [d7fddf38] Error deleting partnership registry key
> DateTime=2007-10-22T17:39:27.7852781Z
> wmdc Error: 6 : [d7fddf38] Caught exception: System.ArgumentException:
> Cannot delete a subkey tree because the subkey does not exist.
> at Microsoft.Win32.RegistryKey.DeleteSubKeyTree(Strin g subkey)
> at Microsoft.WindowsMobile.DeviceManager.Partnership. Delete(IWin32Window
> promptOwner, PartnershipDeletionOptions options)
> DateTime=2007-10-22T17:39:27.8321531Z
> wmdc Verbose: 5 : [d7fddf38] Exiting Partnership03:elete
> DateTime=2007-10-22T17:39:27.8321531Z
> wmdc Information: 0 : PartnershipCollectionEnumerator::MoveNext -
> Partnership (0xd7fddf38) found as next compatible partnership
> DateTime=2007-10-22T17:39:27.8321531Z
> wmdc Information: 0 : PartnershipCollection.RaiseStateChanged (device:,
> state:PartnershipsExistNoDeviceConnected, message
> DateTime=2007-10-22T17:39:27.8321531Z
> wmdc Information: 5 : Exiting PartnershipCollection::OnDeviceDisconnect
> (device:Microsoft.WindowsMobile.DeviceManager.Wind owsMobileDevice2003)
> DateTime=2007-10-22T17:39:27.8477781Z
> wmdc Information: 2 : Disposing of ~SyncCenterStatus
> DateTime=2007-10-22T17:39:27.8790281Z
>
> --
> Brad
>
>
> "Steve Spiller [MSFT]" wrote:
>
>> Hello,
>>
>> Vista has an oddity with saving files from the internet directly to a
>> folder
>> that requires you to elevate to access. Try saving the .config files for
>> logging to your desktop first, then copying them into
>> \windows\windowsmobile. It sounds like the call the desktop makes to the
>> device to get it's sync configuration is failing for some reason, but
>> without the logs it's hard to say.
>>
>> --
>> Thanks,
>>
>> Steve Spiller
>> Development Lead
>> Windows Mobile Device Center
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Brad" <> wrote in message
>> news:7EEE763C-B09C-45D9-B0B4-...
>> > Just installed Windows Mobile Device Center 6.1 onto a clean copy of
>> > Vista
>> > Ultimate x64 and Outlook 2007 (pst empty). WMDC was installed
>> > meticulously
>> > following the steps outlined on the WMDC website and consequently my
>> > USB
>> > Dell
>> > Axim (X5 with PocketPC 2003) appears in Device Manager under Mobile
>> > devices
>> > as well as does the Windows Mobile-based device node under Portable
>> > Devices.
>> >
>> > What first appears is the popup "Changes to synchronization settings
>> > with
>> > Server ActiveSync cannot be made at this time." The UI only shows a
>> > red X
>> > and the word "Error." If I close the program, disconnect the Axim, and
>> > start
>> > only the program I get the same popup but the UI now has the word Axim
>> > in
>> > the
>> > lower left corner accompanied by Not Connected and I get a Mobile
>> > Device
>> > Settings dialog which I did not have before. Underneath that I get
>> > only
>> > Connection Settings in which I cleared the Bluetooth checkbox but
>> > allowed
>> > the
>> > USB connections and device authentication to remain checked (tried
>> > unchecking
>> > that but it didn't help either).
>> >
>> > Now if I plug in the Axim with WMDC open, I get the same "Changes to
>> > synchronization settings..." popup and red X but now I get a new option
>> > under
>> > Mobile Device Settings, "Backup and Restore" which does allow me to
>> > backup
>> > the device. At no time do I get an option to setup a partnership.
>> >
>> > I looked at the other posts on this and tried reinstalling but that
>> > didn't
>> > help. From a non Microsoft forum it was suggested to drop in the
>> > debugging
>> > logger into /Windows/WindowsMobile but Windows denies me access saying
>> > I
>> > don't have sufficient permissions. This is certainly strange being the
>> > only
>> > user and administrator of a clean copy of Windows and it may or may not
>> > be
>> > a
>> > clue to the problem. The security tab shows I have full permissions on
>> > the
>> > folder but CREATOR OWNER and TrustedInstaller do not.
>> >
>> > Another possibility is that I may have declined VB scripting support in
>> > the
>> > installation of Outlook. I don't know if that would have any impact
>> > but I
>> > know I've done that on my other machines for security reasons. I can
>> > say
>> > that ActiveSync, Outlook 2000, and the Axim worked fine together on XP.
>> >
>> > Any suggestions? or just another curious vista x64 incompatibility?
>> > --
>> > Brad
>>
>>

I sure hope you got it. I have wasted numerous hours with your India support
team going round and round and back to zero.
As you can see, basically everybody with PDA will have problem syncing under
Vista and Mobile Device Center 6.1.

"Steve Spiller [MSFT]" wrote:

> Hello,
>
> Vista has an oddity with saving files from the internet directly to a folder
> that requires you to elevate to access. Try saving the .config files for
> logging to your desktop first, then copying them into
> \windows\windowsmobile. It sounds like the call the desktop makes to the
> device to get it's sync configuration is failing for some reason, but
> without the logs it's hard to say.
>
> --
> Thanks,
>
> Steve Spiller
> Development Lead
> Windows Mobile Device Center
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Brad" <> wrote in message
> news:7EEE763C-B09C-45D9-B0B4-...
> > Just installed Windows Mobile Device Center 6.1 onto a clean copy of Vista
> > Ultimate x64 and Outlook 2007 (pst empty). WMDC was installed
> > meticulously
> > following the steps outlined on the WMDC website and consequently my USB
> > Dell
> > Axim (X5 with PocketPC 2003) appears in Device Manager under Mobile
> > devices
> > as well as does the Windows Mobile-based device node under Portable
> > Devices.
> >
> > What first appears is the popup "Changes to synchronization settings with
> > Server ActiveSync cannot be made at this time." The UI only shows a red X
> > and the word "Error." If I close the program, disconnect the Axim, and
> > start
> > only the program I get the same popup but the UI now has the word Axim in
> > the
> > lower left corner accompanied by Not Connected and I get a Mobile Device
> > Settings dialog which I did not have before. Underneath that I get only
> > Connection Settings in which I cleared the Bluetooth checkbox but allowed
> > the
> > USB connections and device authentication to remain checked (tried
> > unchecking
> > that but it didn't help either).
> >
> > Now if I plug in the Axim with WMDC open, I get the same "Changes to
> > synchronization settings..." popup and red X but now I get a new option
> > under
> > Mobile Device Settings, "Backup and Restore" which does allow me to backup
> > the device. At no time do I get an option to setup a partnership.
> >
> > I looked at the other posts on this and tried reinstalling but that didn't
> > help. From a non Microsoft forum it was suggested to drop in the
> > debugging
> > logger into /Windows/WindowsMobile but Windows denies me access saying I
> > don't have sufficient permissions. This is certainly strange being the
> > only
> > user and administrator of a clean copy of Windows and it may or may not be
> > a
> > clue to the problem. The security tab shows I have full permissions on
> > the
> > folder but CREATOR OWNER and TrustedInstaller do not.
> >
> > Another possibility is that I may have declined VB scripting support in
> > the
> > installation of Outlook. I don't know if that would have any impact but I
> > know I've done that on my other machines for security reasons. I can say
> > that ActiveSync, Outlook 2000, and the Axim worked fine together on XP.
> >
> > Any suggestions? or just another curious vista x64 incompatibility?
> > --
> > Brad
>
>