Windows Vista Vista home sync center just stopped working with DELL Axim

  • Thread starter Thread starter olliejk
  • Start date Start date
O

olliejk

Guest
I have a Dell Axim runnin MS Pocket PC Version 4.20.1081.
It syncs to my XP proffesional desktop just fine and it USED to sync to my
XP Home Premium Laptop happily.

Then suddenly for no appearent reason it stopped syncing to the XP machine
(error below). It "sees" the PDA. It can even browse the device just fine,
but the sync fails. Any ideas?

Problem signature:
Problem Event Name: APPCRASH
Application Name: WmdHost.exe
Application Version: 6.0.6783.0
Application Timestamp: 45b7b21a
Fault Module Name: msvcrt.dll
Fault Module Version: 7.0.6000.16386
Fault Module Timestamp: 4549bd61
Exception Code: c0000005
Exception Offset: 0000999c
OS Version: 6.0.6000.2.0.0.768.3
Locale ID: 1033
Additional Information 1: 8499
Additional Information 2: b1181cca34b415c62d924e4abd3ad6db
Additional Information 3: 356f
Additional Information 4: 204082518061538aa41d61c9deeb5faa



P.S. The Mobile Device Center fails w/ the following error

************** 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.0.0.0
Win32 Version: 6.0.6783.0
CodeBase:
file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceManager.DLL
----------------------------------------
Microsoft.WindowsMobile.Common
Assembly Version: 6.0.0.0
Win32 Version: 6.0.6783.0
CodeBase:
file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Common.DLL
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.WindowsMobile.Rapi
Assembly Version: 6.0.0.0
Win32 Version: 6.0.6783.0
CodeBase:
file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Rapi.DLL
----------------------------------------
Microsoft.WindowsMobile.DeviceCenter
Assembly Version: 6.0.0.0
Win32 Version: 6.0.6783.0
CodeBase:
file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceCenter.DLL
----------------------------------------
AnimationLibrary
Assembly Version: 6.0.0.0
Win32 Version: 6.0.6783.0
CodeBase: file:///C:/Windows/WindowsMobile/AnimationLibrary.DLL
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase:
file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

************** 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.
 
Re: Vista home sync center just stopped working with DELL Axim

System Restore is the best bet.

Control panel/"Sync Center" has a few options for resyncing.

--
Was this helpful? Then click the "Yes" Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales/help/help_en-us.htm#RateAPost

Mark L. Ferguson

..
"olliejk" <olliejk@discussions.microsoft.com> wrote in message
news:7389CB26-BB2E-453C-A315-98B3E1A22A8E@microsoft.com...
>I have a Dell Axim runnin MS Pocket PC Version 4.20.1081.
> It syncs to my XP proffesional desktop just fine and it USED to sync to my
> XP Home Premium Laptop happily.
>
> Then suddenly for no appearent reason it stopped syncing to the XP machine
> (error below). It "sees" the PDA. It can even browse the device just fine,
> but the sync fails. Any ideas?
>
> Problem signature:
> Problem Event Name: APPCRASH
> Application Name: WmdHost.exe
> Application Version: 6.0.6783.0
> Application Timestamp: 45b7b21a
> Fault Module Name: msvcrt.dll
> Fault Module Version: 7.0.6000.16386
> Fault Module Timestamp: 4549bd61
> Exception Code: c0000005
> Exception Offset: 0000999c
> OS Version: 6.0.6000.2.0.0.768.3
> Locale ID: 1033
> Additional Information 1: 8499
> Additional Information 2: b1181cca34b415c62d924e4abd3ad6db
> Additional Information 3: 356f
> Additional Information 4: 204082518061538aa41d61c9deeb5faa
>
>
>
> P.S. The Mobile Device Center fails w/ the following error
>
> ************** 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.0.0.0
> Win32 Version: 6.0.6783.0
> CodeBase:
> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceManager.DLL
> ----------------------------------------
> Microsoft.WindowsMobile.Common
> Assembly Version: 6.0.0.0
> Win32 Version: 6.0.6783.0
> CodeBase:
> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Common.DLL
> ----------------------------------------
> System
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
> ----------------------------------------
> System.Windows.Forms
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
> ----------------------------------------
> System.Drawing
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
> ----------------------------------------
> System.Configuration
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
> ----------------------------------------
> System.Xml
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
> ----------------------------------------
> Microsoft.WindowsMobile.Rapi
> Assembly Version: 6.0.0.0
> Win32 Version: 6.0.6783.0
> CodeBase:
> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Rapi.DLL
> ----------------------------------------
> Microsoft.WindowsMobile.DeviceCenter
> Assembly Version: 6.0.0.0
> Win32 Version: 6.0.6783.0
> CodeBase:
> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceCenter.DLL
> ----------------------------------------
> AnimationLibrary
> Assembly Version: 6.0.0.0
> Win32 Version: 6.0.6783.0
> CodeBase: file:///C:/Windows/WindowsMobile/AnimationLibrary.DLL
> ----------------------------------------
> Accessibility
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
> ----------------------------------------
>
> ************** 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.
>
>
>
>
 
Re: Vista home sync center just stopped working with DELL Axim

Your error log clearly says that the dll msvcrt.dll is corrupted.

WmdHost.exe is not a Vista application but Windows Mobil's. The dll does not
seem to be a Vista dll but it does exist in a few folders apparently for
emulation purposes.

None of the errors your log shows are recognized as Windows errors except
for this one: 0x80040154 which means "Class not registered."

I checked it with errlookup.exe

There is plenty of info on the web, primarily at MS MSDN sites on the issue.
Just google for GUID {89108EE5-18DA-11DB-9617-00E08161165F} (Remove square
brackets when google).

In my Vista Ultimate I found the dll in 5 directories. The first number is
the version. There are 5 versions as you can see.
7.0.6000.16386 (vista_rtm.061101-2205) |||
C:\Windows\winsxs\x86_microsoft-windows-msvcrt_31bf3856ad364e35_6.0.6000.16386_none_cf1e7424a1fb0cd9
||| Windows NT CRT DLL
7.0.2600.0 (xpclient.010817-1148) |||
D:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.0.0_x-ww_2726e76a
||| Windows NT CRT DLL
7.0.2600.2180 (xpsp_sp2_rtm.040803-2158) |||
D:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.2600.2180_x-ww_b2505ed9
||| Windows NT CRT DLL
7.0.3790.1830 (srv03_sp1_rtm.050324-1447 |||
F:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.3790.1830_x-ww_84E4CBAF
||| Windows NT CRT DLL
7.0.3790.3959 (srv03_sp2_rtm.070216-1710 |||
F:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.3790.3959_x-ww_E2727D35
||| Windows NT CRT DLL

If what mark suggested won't work you may try to replace the corrupt dll.
You should have some available on your Vista. The trickiest part will be to
replace the corrupt one with the new one. It may be somehow Vista protected
for security reasons or because it may be a part of your Windows Mobil OS
and therefore in use all the time. The latest case scenario is the worst.
You may use your ingenuity, perhaps try the safe mode or if you have a
second partition (an unlikely case for Pocket PC) that would be the easiest:
to go to the second partition and manipulate the dlls on the partition in
question.

"olliejk" <olliejk@discussions.microsoft.com> wrote in message
news:7389CB26-BB2E-453C-A315-98B3E1A22A8E@microsoft.com...
>I have a Dell Axim runnin MS Pocket PC Version 4.20.1081.
> It syncs to my XP proffesional desktop just fine and it USED to sync to my
> XP Home Premium Laptop happily.
>
> Then suddenly for no appearent reason it stopped syncing to the XP machine
> (error below). It "sees" the PDA. It can even browse the device just fine,
> but the sync fails. Any ideas?
>
> Problem signature:
> Problem Event Name: APPCRASH
> Application Name: WmdHost.exe
> Application Version: 6.0.6783.0
> Application Timestamp: 45b7b21a
> Fault Module Name: msvcrt.dll
> Fault Module Version: 7.0.6000.16386
> Fault Module Timestamp: 4549bd61
> Exception Code: c0000005
> Exception Offset: 0000999c
> OS Version: 6.0.6000.2.0.0.768.3
> Locale ID: 1033
> Additional Information 1: 8499
> Additional Information 2: b1181cca34b415c62d924e4abd3ad6db
> Additional Information 3: 356f
> Additional Information 4: 204082518061538aa41d61c9deeb5faa
>
>
>
> P.S. The Mobile Device Center fails w/ the following error
>
> ************** 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.0.0.0
> Win32 Version: 6.0.6783.0
> CodeBase:
> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceManager.DLL
> ----------------------------------------
> Microsoft.WindowsMobile.Common
> Assembly Version: 6.0.0.0
> Win32 Version: 6.0.6783.0
> CodeBase:
> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Common.DLL
> ----------------------------------------
> System
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
> ----------------------------------------
> System.Windows.Forms
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
> ----------------------------------------
> System.Drawing
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
> ----------------------------------------
> System.Configuration
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
> ----------------------------------------
> System.Xml
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
> ----------------------------------------
> Microsoft.WindowsMobile.Rapi
> Assembly Version: 6.0.0.0
> Win32 Version: 6.0.6783.0
> CodeBase:
> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Rapi.DLL
> ----------------------------------------
> Microsoft.WindowsMobile.DeviceCenter
> Assembly Version: 6.0.0.0
> Win32 Version: 6.0.6783.0
> CodeBase:
> file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceCenter.DLL
> ----------------------------------------
> AnimationLibrary
> Assembly Version: 6.0.0.0
> Win32 Version: 6.0.6783.0
> CodeBase: file:///C:/Windows/WindowsMobile/AnimationLibrary.DLL
> ----------------------------------------
> Accessibility
> Assembly Version: 2.0.0.0
> Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> CodeBase:
> file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
> ----------------------------------------
>
> ************** 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.
>
>
>
>
 
Re: Vista home sync center just stopped working with DELL Axim



"AlexB" wrote:

> Your error log clearly says that the dll msvcrt.dll is corrupted.
>
> WmdHost.exe is not a Vista application but Windows Mobil's. The dll does not
> seem to be a Vista dll but it does exist in a few folders apparently for
> emulation purposes.
>





Old news, but I had to kill the partnership and then re-establish it. Worked
then.
> None of the errors your log shows are recognized as Windows errors except
> for this one: 0x80040154 which means "Class not registered."
>
> I checked it with errlookup.exe
>
> There is plenty of info on the web, primarily at MS MSDN sites on the issue.
> Just google for GUID {89108EE5-18DA-11DB-9617-00E08161165F} (Remove square
> brackets when google).
>
> In my Vista Ultimate I found the dll in 5 directories. The first number is
> the version. There are 5 versions as you can see.
> 7.0.6000.16386 (vista_rtm.061101-2205) |||
> C:\Windows\winsxs\x86_microsoft-windows-msvcrt_31bf3856ad364e35_6.0.6000.16386_none_cf1e7424a1fb0cd9
> ||| Windows NT CRT DLL
> 7.0.2600.0 (xpclient.010817-1148) |||
> D:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.0.0_x-ww_2726e76a
> ||| Windows NT CRT DLL
> 7.0.2600.2180 (xpsp_sp2_rtm.040803-2158) |||
> D:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.2600.2180_x-ww_b2505ed9
> ||| Windows NT CRT DLL
> 7.0.3790.1830 (srv03_sp1_rtm.050324-1447 |||
> F:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.3790.1830_x-ww_84E4CBAF
> ||| Windows NT CRT DLL
> 7.0.3790.3959 (srv03_sp2_rtm.070216-1710 |||
> F:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.3790.3959_x-ww_E2727D35
> ||| Windows NT CRT DLL
>
> If what mark suggested won't work you may try to replace the corrupt dll.
> You should have some available on your Vista. The trickiest part will be to
> replace the corrupt one with the new one. It may be somehow Vista protected
> for security reasons or because it may be a part of your Windows Mobil OS
> and therefore in use all the time. The latest case scenario is the worst.
> You may use your ingenuity, perhaps try the safe mode or if you have a
> second partition (an unlikely case for Pocket PC) that would be the easiest:
> to go to the second partition and manipulate the dlls on the partition in
> question.
>
> "olliejk" <olliejk@discussions.microsoft.com> wrote in message
> news:7389CB26-BB2E-453C-A315-98B3E1A22A8E@microsoft.com...
> >I have a Dell Axim runnin MS Pocket PC Version 4.20.1081.
> > It syncs to my XP proffesional desktop just fine and it USED to sync to my
> > XP Home Premium Laptop happily.
> >
> > Then suddenly for no appearent reason it stopped syncing to the XP machine
> > (error below). It "sees" the PDA. It can even browse the device just fine,
> > but the sync fails. Any ideas?
> >
> > Problem signature:
> > Problem Event Name: APPCRASH
> > Application Name: WmdHost.exe
> > Application Version: 6.0.6783.0
> > Application Timestamp: 45b7b21a
> > Fault Module Name: msvcrt.dll
> > Fault Module Version: 7.0.6000.16386
> > Fault Module Timestamp: 4549bd61
> > Exception Code: c0000005
> > Exception Offset: 0000999c
> > OS Version: 6.0.6000.2.0.0.768.3
> > Locale ID: 1033
> > Additional Information 1: 8499
> > Additional Information 2: b1181cca34b415c62d924e4abd3ad6db
> > Additional Information 3: 356f
> > Additional Information 4: 204082518061538aa41d61c9deeb5faa
> >
> >
> >
> > P.S. The Mobile Device Center fails w/ the following error
> >
> > ************** 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.0.0.0
> > Win32 Version: 6.0.6783.0
> > CodeBase:
> > file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceManager.DLL
> > ----------------------------------------
> > Microsoft.WindowsMobile.Common
> > Assembly Version: 6.0.0.0
> > Win32 Version: 6.0.6783.0
> > CodeBase:
> > file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Common.DLL
> > ----------------------------------------
> > System
> > Assembly Version: 2.0.0.0
> > Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> > CodeBase:
> > file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
> > ----------------------------------------
> > System.Windows.Forms
> > Assembly Version: 2.0.0.0
> > Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> > CodeBase:
> > file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
> > ----------------------------------------
> > System.Drawing
> > Assembly Version: 2.0.0.0
> > Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> > CodeBase:
> > file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
> > ----------------------------------------
> > System.Configuration
> > Assembly Version: 2.0.0.0
> > Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> > CodeBase:
> > file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
> > ----------------------------------------
> > System.Xml
> > Assembly Version: 2.0.0.0
> > Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> > CodeBase:
> > file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
> > ----------------------------------------
> > Microsoft.WindowsMobile.Rapi
> > Assembly Version: 6.0.0.0
> > Win32 Version: 6.0.6783.0
> > CodeBase:
> > file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.Rapi.DLL
> > ----------------------------------------
> > Microsoft.WindowsMobile.DeviceCenter
> > Assembly Version: 6.0.0.0
> > Win32 Version: 6.0.6783.0
> > CodeBase:
> > file:///C:/Windows/WindowsMobile/Microsoft.WindowsMobile.DeviceCenter.DLL
> > ----------------------------------------
> > AnimationLibrary
> > Assembly Version: 6.0.0.0
> > Win32 Version: 6.0.6783.0
> > CodeBase: file:///C:/Windows/WindowsMobile/AnimationLibrary.DLL
> > ----------------------------------------
> > Accessibility
> > Assembly Version: 2.0.0.0
> > Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
> > CodeBase:
> > file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
> > ----------------------------------------
> >
> > ************** 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.
> >
> >
> >
> >
>
>
 

Similar threads

J
just-in-time (JIT) debugging error
Replies
0
Views
263
Jickyboy11
J
C
While trying to update the firmware on a Dell U2718Q monitor, I encounter this "Just-in-Time" debugging error. What do I do???
Replies
0
Views
308
ccunni2020
C
M
connect to detached sql server database using ado.net and error
Replies
0
Views
108
mohammadansari98
M
G
JIT error - Just in Time Error for Deployed Application on windows 10 64 bit
Replies
0
Views
138
G.Albert
G
S
Windows 10 Sysprep and .NET issue
Replies
0
Views
110
Steve S is at work
S
Back
Top