Vista Sync Center Error

[dxk7874]

This is the error message I am getting when I am trying to open "File Management" in Sync Center.
"Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.
Driver failed to load in the time allotted."

When I clicked on "continue", the Sync Center closed.
Thanks,
Dan

[JonathanD]

There is a problem with the path to the Quedirectory in the system.cfg file.
Locate the system.cfg file in the shared Sysdata directory, then verify that the path to the Quedirectory is correct with either map drive or UNC pathing.

Or

The problem occurs because Microsoft Data Access Components (MDAC) is not installed on the computer. The .NET application uses MDAC to access the data from the database.

To resolve this problem, install MDAC on the computer. You can download MDAC from the following Microsoft Developer Network (MSDN) Web site:
Data Access downloads : http://msdn.microsoft.com/en-us/data/aa937695.aspx

[Glenny]

Sync Errors are more dangerous than conflicts and warnings. The cause of errors is mainly due to -
a device is not available
a device loses its wireless connection
a battery of the device runs flat.

Whatever reason may be -- if one partner is unavailable, synchronization fails, and that triggers an error report.

Please follow this tip to avoid this : synchronize your files before your start working on them in the second location. This reduces the annoying situation where both versions of the files have changed since the last synchronization.

[chroma]

Sync errors usually occur when there is a problem with the device, computer, folder, or web service you are trying to sync with. Errors are different and more serious than conflicts and warnings. The commonest cause of errors is that a device is not available, perhaps it loses its wireless connection, or its battery runs flat. Sync errors usually block sync from completing. If you don't fix them, some or all of your files will not be in sync.

Sync warnings usually don't prevent sync from completing, so it is not imperative that you fix or even notice every warning. However, it is a good idea to check occasionally for warnings on the Sync Results screen when you sync. Warnings might notify you of problems that will lead to sync errors if you don't take action to fix them, such as recharging a battery that is almost dead or plugging in a cable that has come loose.

[dxk7874]

Thanks to all of you for caring.
I should have provided more specific details......................
I am able to sync my phone but I am not able to open "File Management" to add files like I used to in the past.
This is the error message I am getting when I am trying to open "File Management" in Sync Center.
The box Header: Unidentified Device Installed
Searching for preconfigured driver folders
"Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.
Driver failed to load in the time allotted."

When I clicked on "continue", the Sync Center closed.

I got the following message when opening "details".

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
Microsoft.WindowsMobile.DeviceManager.WpdException: Driver failed to load in the time allotted.
at Microsoft.WindowsMobile.DeviceManager.Wpd.WaitDriverLoad()
at Microsoft.WindowsMobile.DeviceManager.Wpd.get_Id()
at Microsoft.WindowsMobile.DeviceManager.WindowsMobileDevice.Explore()
at Microsoft.WindowsMobile.DeviceCenter.ExploreFolderItem.OnClick(Object sender, AnimatedControlEventArgs e)
at Microsoft.WindowsMobile.DeviceCenter.TextFolderItemWrapper.TextFolderItemWrapper_Click(Object sender, AnimatedControlEventArgs e)
at AnimationLibrary.AnimatedControl.OnClick(Object sender, AnimatedControlEventArgs e)
at AnimationLibrary.AnimatedControl.OnClick(Object sender, AnimatedControlEventArgs e)
at AnimationLibrary.AnimatedControl.OnClick(Object sender, AnimatedControlEventArgs e)
at AnimationLibrary.AnimatedLinkLabel.OnClick(Object sender, AnimatedControlEventArgs e)
at AnimationLibrary.AnimatedControl.BubbleClick(MouseEventArgs e)
at AnimationLibrary.AnimationHost.AnimationHost_MouseUp(Object sender, MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.UserControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3074 (QFE.050727-3000)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Microsoft.WindowsMobile.DeviceManager
Assembly Version: 6.1.0.0
Win32 Version: 6.1.6965.0
CodeBase: file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceManager.DLL
----------------------------------------
Microsoft.WindowsMobile.Common
Assembly Version: 6.1.0.0
Win32 Version: 6.1.6965.0
CodeBase: file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Common.DLL
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3074 (QFE.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.WindowsMobile.Rapi
Assembly Version: 6.1.0.0
Win32 Version: 6.1.6965.0
CodeBase: file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Rapi.DLL
----------------------------------------
Microsoft.WindowsMobile.DeviceCenter
Assembly Version: 6.1.0.0
Win32 Version: 6.1.6965.0
CodeBase: file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceCenter.DLL
----------------------------------------
AnimationLibrary
Assembly Version: 6.1.0.0
Win32 Version: 6.1.6965.0
CodeBase: file:///C:/Windows/WindowsMobile/AnimationLibrary.DLL
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

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

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


Thanks for your time and kind assistance.
Hope to hear from you soon.
Dan

[dxk7874]

I followed the link but I am not sure which one to download.
Thanks,
Dan

Originally Posted by JonathanD

There is a problem with the path to the Quedirectory in the system.cfg file.
Locate the system.cfg file in the shared Sysdata directory, then verify that the path to the Quedirectory is correct with either map drive or UNC pathing.

Or

The problem occurs because Microsoft Data Access Components (MDAC) is not installed on the computer. The .NET application uses MDAC to access the data from the database.

To resolve this problem, install MDAC on the computer. You can download MDAC from the following Microsoft Developer Network (MSDN) Web site:
Data Access downloads : http://msdn.microsoft.com/en-us/data/aa937695.aspx

[dxk7874]

Good Afternoon Jonathan.
From the error message I posted, do you think I still need the MDAC files?
Thanks,
Dan

Originally Posted by JonathanD

There is a problem with the path to the Quedirectory in the system.cfg file.
Locate the system.cfg file in the shared Sysdata directory, then verify that the path to the Quedirectory is correct with either map drive or UNC pathing.

Or

The problem occurs because Microsoft Data Access Components (MDAC) is not installed on the computer. The .NET application uses MDAC to access the data from the database.

To resolve this problem, install MDAC on the computer. You can download MDAC from the following Microsoft Developer Network (MSDN) Web site:
Data Access downloads : http://msdn.microsoft.com/en-us/data/aa937695.aspx

[dxk7874]

I am not able to locate the system.cfg etc to fix the problem.
What third party software would you recommend for me to use instead of trying to fix the sync center?
I appreciate your time and help.
Thanks.

Originally Posted by JonathanD

There is a problem with the path to the Quedirectory in the system.cfg file.
Locate the system.cfg file in the shared Sysdata directory, then verify that the path to the Quedirectory is correct with either map drive or UNC pathing.

Or

The problem occurs because Microsoft Data Access Components (MDAC) is not installed on the computer. The .NET application uses MDAC to access the data from the database.

To resolve this problem, install MDAC on the computer. You can download MDAC from the following Microsoft Developer Network (MSDN) Web site:
Data Access downloads : http://msdn.microsoft.com/en-us/data/aa937695.aspx

[Raiz]

See this microsoft help about vista sync center : http://www.microsoft.com/windows/win...nc-center.aspx

And also refer to following similar kind of issues to grab more info :

Problem with Sync Center and Mobile Device Center after upgrade
Windows Vista Sync Center - "Access Denied"
http://forums.techarena.in/vista-adm...on/1067100.htm
Sync Center has gone mad!

[Macarenas]

Error's are normally generated when the connection between two devices are not setup properly. The most common cause is that when device is not available or it loses the contact via wireless or cable. I will advice you to first check out that the connection is proper and then you try to sync the device back again.