Comments

1. Mary Poole

   
   Posted on: December 23, 2007 at 2:26PM  

   I have had the same problem for 3 months and have never found the answer. My phone shows connected in device center but WMDC never has shown connection, I therfore am unable to get mail or calendar to synch
2. viroid

   
   Posted on: January 02, 2008 at 2:26PM  

   I'm new here, are users able to start new threads or only post comments on threads started by MS people?

   This thread looks like a good place to place this comment..  I've experience similar issues as the people above, if I connect my phone (Cingular 8125) to Vista, I see the "Sync Center" icon appear in the system tray and it says connected but it does not sync.  However, if I launch the Mobile Device Center, the phone is immidiately connected and everything sync's just fine.  As long as the Device Center is open, I dont have any problems.  Hopefully someone can resolve this issue, it's sort of annoying.  I sometimes forget to launch the Mobile Device Center and so nothing gets sync'ed and then I leave the office and my notes are in the appointment (such as directions to a client) etc etc.
3. bbe_fox

   
   Posted on: January 09, 2008 at 10:47AM  

   I have Windows Vista Home Premium 32 bit version with office 2003 including outlook 2003.  My mobile device is an HP iPaq H6325.

   Microsoft Windows Device Center 6.1 (edited)

   This is the error message I get every time when I try to "Set up your device" to sync everything. I have to connect without setting up the device. It also errors when it debugs.

   I have already tried to reinstalling it many times and I get the same error. I have never been able to run this program on this PC.  ActiveSync works fine on Windows XP.

   Does anyone know how to help me on this please?

   Update: I had active sync 4.0 installed which was causing part of the error. I unisnalled it. now I can set up the device but I cannot sync it and I get the following error:

   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.

   Retreiving the COM class factory component with CLSID {89108ee-18da-11db-9617-00e08161165f} failed due to the following error: 80040154.

   Details:

   See the end of this message for details on invoking

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

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

   System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {89108EE5-18DA-11DB-9617-00E08161165F} failed due to the following error: 80040154.

     at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)

     at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)

     at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)

     at System.Activator.CreateInstance(Type type, Boolean nonPublic)

     at Microsoft.WindowsMobile.OutlookInfo.get_Instance()

     at Microsoft.WindowsMobile.DeviceCenter.ExchangeSourceSetupFolderItem..ctor(MainHost mainHost)

     at Microsoft.WindowsMobile.DeviceCenter.MobileSettingsPage.Load(Folder folder)

     at Microsoft.WindowsMobile.DeviceCenter.FolderList.AddFolder(IFolderPage page)

     at Microsoft.WindowsMobile.DeviceCenter.ConnectedPage..ctor(MainHost mainHost)

     at Microsoft.WindowsMobile.DeviceCenter.PartneredPage..ctor(MainHost mainHost)

     at Microsoft.WindowsMobile.DeviceCenter.MainHost.OnPartnershipStateChanged(State s, String message)

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

   mscorlib

      Assembly Version: 2.0.0.0

      Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)

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

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

   Microsoft.WindowsMobile.DeviceManager

      Assembly Version: 6.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.312 (rtmLHS.050727-3100)

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

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

   System.Windows.Forms

      Assembly Version: 2.0.0.0

      Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)

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

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

   System.Drawing

      Assembly Version: 2.0.0.0

      Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)

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

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

   System.Configuration

      Assembly Version: 2.0.0.0

      Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)

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

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

   System.Xml

      Assembly Version: 2.0.0.0

      Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)

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

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

   Microsoft.WindowsMobile.Rapi

      Assembly Version: 6.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.312 (rtmLHS.050727-3100)

      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.
4. drme

   
   Posted on: April 06, 2008 at 7:18AM  

   Ive just spent the last 8.5 hours trying to get my vista contacts to my new phone. Theres only one thing I can say. Microsoft puts a chimp in one room and a monkey in the next and gives them each a computer and tells them, Here design a windows mobile sync system.

   Then the chimp says, "aaahhiiii?

   then they sell it.!!!

   Thanks for nothing
5. ciroyong

   
   Posted on: May 25, 2008 at 10:38PM  

   hello!

   I am trying to connect my Pocket PC Phone with windows mobile 5 on my Vista desktop. It doesnt connect and the evern viewer has the following error

   Source  - RapiMgr

   Windows Mobile-based USB device is plugged in but is unable to make a network connection to the desktop.

   Help me!Thanks!
6. charlescollins

   
   Posted on: July 15, 2008 at 4:02AM  

   Hi there

   have been using WMDC for a while with no problem using Vista home to sync with my pocket pc [Vodafone pda3]. Now I am getting the message;

   Retrieving the COM class factory for component with CLSID {89108EE5-18DA-11DB-9617-00E08161165F}

   and in the details window it says

   See the end of this message for details on invoking

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

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

   System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {89108EE5-18DA-11DB-9617-00E08161165F} failed due to the following error: 80040154.

     at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)

     at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)

     at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)

     at System.Activator.CreateInstance(Type type, Boolean nonPublic)

     at Microsoft.WindowsMobile.OutlookInfo.get_Instance()

     at Microsoft.WindowsMobile.DeviceCenter.ExchangeSourceSetupFolderItem..ctor(MainHost mainHost)

     at Microsoft.WindowsMobile.DeviceCenter.MobileSettingsPage.Load(Folder folder)

     at Microsoft.WindowsMobile.DeviceCenter.FolderList.AddFolder(IFolderPage page)

     at Microsoft.WindowsMobile.DeviceCenter.ConnectedPage..ctor(MainHost mainHost)

     at Microsoft.WindowsMobile.DeviceCenter.PartneredPage..ctor(MainHost mainHost)

     at Microsoft.WindowsMobile.DeviceCenter.MainHost.OnPartnershipStateChanged(State s, String message)

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

   mscorlib

      Assembly Version: 2.0.0.0

      Win32 Version: 2.0.50727.1434 (REDBITS.050727-1400)

      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.1434 (REDBITS.050727-1400)

      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.1434 (REDBITS.050727-1400)

      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.1434 (REDBITS.050727-1400)

      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.1434 (REDBITS.050727-1400)

      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.1434 (REDBITS.050727-1400)

      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.1434 (REDBITS.050727-1400)

      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.

   And help appreciated
7. SuperSean

   
   Posted on: July 24, 2008 at 11:06AM  

   It has now been about a year since the 'launch' of WMDC 6.1 and I am completely stunned by shear THOUSANDS of forum and blog posts I have read containing people requesting help getting WMDC to sync their Mobile devices to their vista based computers.

   Isn’t it about time that we received an official response to the issues that these people are having?

   Don't we have a right to expect the devices to simply do what they are advertised to do?

   For heaven’s sake, if the developer's would simply do a quick search of the net and you will be faced with the fact that this software simply DOESN'T WORK and when it does, it's rarely stable.  Surely the volume of requests for help would show that there is more than an isolated few problems?

   I and I'm sure TENS IF NOT HUNDREDS OF THOUSANDS of others are disappointed with their choice of device/operating system and now wish they went with another system.  I myself settled on a Windows Mobile based phone over a Nokia N95 solely based on the operating systems and advertised ease of communication with my Vista based computer.

   Up to the time my phone and computer stopped working together – as is the case with most of the problems I have read about – I was a strong proponent of and defended Windows Vista to all those who would dare trash it.  Unfortunately, these last few months trolling through the mounds of posts and blogs on WMDC, after countless installs and uninstalls, soft resets and hard resets, I have finally had to face defeat and have been forced to eat my words.

   For once and for all – PLEASE- get your heads out of the sand and fix this issue.  Or at the very least acknowledge that the software is faulty!

   As this is my first post on this blob, I don’t know if this comment will be canceled by the moderators, and if it is, I guess they are the only ones who will ever read it, but in either case, please, take these comments seriously, because Vista, Windows Mobile, and the millions/billions in development Microsoft has sunk into these technologies will all be in jeopardy when yet more people turn away in search of something faster, more stable, cheaper, and more in touch with their customer’s needs.
8. rsx

   
   Posted on: July 26, 2008 at 7:26PM  

   I must agree with SuperSean.

   I have used PocketPC, then Windows Mobile for many years. I just upgraded from WM6 to WM6.1. And guess what - once again, I cannot get a sync to complete.

   Earlier today, no problem syncing with WM6 on this same Vista computer.

   Now, same phone, same computer, now with WM6.1, the sync goes part way through then stops.

   Why can't Windows software work flawlessly? My wife's Palm software, my friend's iPhone software, work fine, they don't give it a second thought.

   My WM6.1 with Windows Vista, you would think they would work perfectly together.

   But NO. Why can't MS deal with this ongoing problem?

   When I first got WM6 I had same trouble. It took hours of my time to get it straight. Now again.
9. osanchez

   
   Posted on: August 01, 2008 at 12:58AM  

   Hi : after breaking my head for about 8 days with this problem I finally found the solution on another forum.

   The problem is that the first and only time I had sync my Samsung Phone I choose to install the Golf game and some notes application on my device. That apps are incompatible with windows-mobile-device-center and make it to crash.

   You have to uninstall those applications both from the device and from the vista computer, remember, uninstall from both sides. After doing that my samsung came back to life and like to sync again as if nothing has happened before (except for a whole week of lost work and time).

   I hope this helps somebody ,
10. theresa

    
    Posted on: October 31, 2008 at 1:52PM  

    Does anyone know how to override the device when syncing to windows mobile center using vista? My device has no contacts but I want to sync it to my outlook without wiping out my contacts info on my outlook.