Sync Appts with Dell Axim Win7 exception

I recently installed a new computer at a client. it is a32 bit Windows 7
Home OS.
The client is using a Dell Axim Pocket PC, which is running:
Windows Mobile 2003 Second Edition
Version 4.21.1088 (Build 14260.2.0.2)
The client is running Office 2003.

The pocket PC worked fine with Windows XP and ActiveSync
However with Windows 7 it does not work. I have done a hard-reset on the
device.
He is able to register the pocket PC and select the synchronization options.
in fact it can synchronize contacts and email. However, if appointment
synchronization is enabled, the synchronization fails immediately with an
exception. I have included the exception information below.
I have also included the two event log errors (that always appear in pairs)
as well.

According to the documentation I have seen Windows Mobile 2003 SE should
synchronize with Windows Mobile Center.
I have run out of ideas.
Can someone explains to me what the problem is and how to correct it?
Thanks
m

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(RuntimeTyp e 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.ExchangeSourc eSetupFolderItem..ctor(MainHost
mainHost)
at Microsoft.WindowsMobile.DeviceCenter.MobileSetting sPage.Load(Folder
folder)
at Microsoft.WindowsMobile.DeviceCenter.ExpandedListF older..ctor(MainHost
mainHost, IFolderPage page)
at
Microsoft.WindowsMobile.DeviceCenter.DynamicListFo lder.DisplayStack.moreLabel_Click(Object
sender, AnimatedControlEventArgs e)
at AnimationLibrary.AnimatedControl.OnClick(Object sender,
AnimatedControlEventArgs e)
at AnimationLibrary.AnimatedLinkLabel.OnClick(Object sender,
AnimatedControlEventArgs e)
at AnimationLibrary.AnimatedControl.BubbleClick(Mouse EventArgs e)
at AnimationLibrary.AnimationHost.AnimationHost_Mouse Up(Object sender,
MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseUp(MouseEventA rgs 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(Mes sage& m)
at System.Windows.Forms.ContainerControl.WndProc(Mess age& m)
at System.Windows.Forms.UserControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(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.4927 (NetFXspW7.050727-4900)
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.4927 (NetFXspW7.050727-4900)
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.4927 (NetFXspW7.050727-4900)
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.4927 (NetFXspW7.050727-4900)
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.4927 (NetFXspW7.050727-4900)
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.4927 (NetFXspW7.050727-4900)
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.4927 (NetFXspW7.050727-4900)
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.


********EVENT LOGS MESSAGES********

Log Name: Application
Source: Application Error
Date: 12/28/2009 10:44:15 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: user-PC
Description:
Faulting application name: WmdHost.exe, version: 6.1.6965.0, time stamp:
0x465eef4e
Faulting module name: msvcrt.dll, version: 7.0.7600.16385, time stamp:
0x4a5bda6f
Exception code: 0xc0000005
Fault offset: 0x00009f40
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-12-28T08:44:15.000000000Z" />
<EventRecordID>2745</EventRecordID>
<Channel>Application</Channel>
<Computer>user-PC</Computer>
<Security />
</System>
<EventData>
<Data>WmdHost.exe</Data>
<Data>6.1.6965.0</Data>
<Data>465eef4e</Data>
<Data>msvcrt.dll</Data>
<Data>7.0.7600.16385</Data>
<Data>4a5bda6f</Data>
<Data>c0000005</Data>
<Data>00009f40</Data>
</EventData>
</Event>


Log Name: Application
Source: Windows Error Reporting
Date: 12/28/2009 10:44:19 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: user-PC
Description:
Fault bucket 1380445821, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: WmdHost.exe
P2: 6.1.6965.0
P3: 465eef4e
P4: msvcrt.dll
P5: 7.0.7600.16385
P6: 4a5bda6f
P7: c0000005
P8: 00009f40
P9:
P10:

Attached files:
C:\Users\user\AppData\Local\Temp\WER1EB6.tmp.WERIn ternalMetadata.xml

These files may be available here:
C:\Users\user\AppData\Local\Microsoft\Windows\WER\ ReportArchive\AppCrash_WmdHost.exe_e589f7284d2fb6c 271d0fd3dee168ccff955eb0_177d2b05

Analysis symbol:
Rechecking for solution: 0
Report Id: 2d951b91-f38d-11de-a8d6-406186079c13
Report Status: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Windows Error Reporting" />
<EventID Qualifiers="0">1001</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-12-28T08:44:19.000000000Z" />
<EventRecordID>2746</EventRecordID>
<Channel>Application</Channel>
<Computer>user-PC</Computer>
<Security />
</System>
<EventData>
<Data>1380445821</Data>
<Data>1</Data>
<Data>APPCRASH</Data>
<Data>Not available</Data>
<Data>0</Data>
<Data>WmdHost.exe</Data>
<Data>6.1.6965.0</Data>
<Data>465eef4e</Data>
<Data>msvcrt.dll</Data>
<Data>7.0.7600.16385</Data>
<Data>4a5bda6f</Data>
<Data>c0000005</Data>
<Data>00009f40</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
C:\Users\user\AppData\Local\Temp\WER1EB6.tmp.WERIn ternalMetadata.xml</Data>
<Data>C:\Users\user\AppData\Local\Microsoft\Window s\WER\ReportArchive\AppCrash_WmdHost.exe_e589f7284 d2fb6c271d0fd3dee168ccff955eb0_177d2b05</Data>
<Data>
</Data>
<Data>0</Data>
<Data>2d951b91-f38d-11de-a8d6-406186079c13</Data>
<Data>0</Data>
</EventData>
</Event>


****************** Content of
C:\Users\user\AppData\Local\Microsoft\Windows\WER\ ReportArchive\AppCrash_WmdHost.exe
**********

Version=1
EventType=APPCRASH
EventTime=129064634558478513
ReportType=2
Consent=1
UploadTime=129064634559668553
ReportIdentifier=2d951b91-f38d-11de-a8d6-406186079c13
Response.BucketId=1380445821
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=WmdHost.exe
Sig[1].Name=Application Version
Sig[1].Value=6.1.6965.0
Sig[2].Name=Application Timestamp
Sig[2].Value=465eef4e
Sig[3].Name=Fault Module Name
Sig[3].Value=msvcrt.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=7.0.7600.16385
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4a5bda6f
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00009f40
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\Windows\WindowsMobile\WmdHost.exe
UI[3]=Windows Mobile Device Center Sync Host has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Windows\WindowsMobile\WmdHost.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\SYSTEM32\MSCOREE.DLL
LoadedModule[3]=C:\Windows\system32\KERNEL32.dll
LoadedModule[4]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[5]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[6]=C:\Windows\system32\msvcrt.dll
LoadedModule[7]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[8]=C:\Windows\system32\RPCRT4.dll
LoadedModule[9]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[10]=C:\Windows\system32\GDI32.dll
LoadedModule[11]=C:\Windows\system32\USER32.dll
LoadedModule[12]=C:\Windows\system32\LPK.dll
LoadedModule[13]=C:\Windows\system32\USP10.dll
LoadedModule[14]=C:\Windows\system32\IMM32.DLL
LoadedModule[15]=C:\Windows\system32\MSCTF.dll
LoadedModule[16]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\msc orwks.dll
LoadedModule[17]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9 a1e18e3b_8.0.50727.4927_none_d08a205e442db5b5\MSVC R80.dll
LoadedModule[18]=C:\Windows\system32\shell32.dll
LoadedModule[19]=C:\Windows\system32\ole32.dll
LoadedModule[20]=C:\Windows\system32\profapi.dll
LoadedModule[21]=C:\Windows\assembly\NativeImages_v2.0.50727_32\ms corlib\8c1770d45c63cf5c462eeb945ef9aa5d\mscorlib.n i.dll
LoadedModule[22]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\msc orsec.dll
LoadedModule[23]=C:\Windows\system32\WINTRUST.dll
LoadedModule[24]=C:\Windows\system32\CRYPT32.dll
LoadedModule[25]=C:\Windows\system32\MSASN1.dll
LoadedModule[26]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_4211 89da2b7fabfc\COMCTL32.dll
LoadedModule[27]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[28]=C:\Windows\system32\rsaenh.dll
LoadedModule[29]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[30]=C:\Windows\system32\imagehlp.dll
LoadedModule[31]=C:\Windows\system32\ncrypt.dll
LoadedModule[32]=C:\Windows\system32\bcrypt.dll
LoadedModule[33]=C:\Windows\system32\bcryptprimitives.dll
LoadedModule[34]=C:\Windows\system32\USERENV.dll
LoadedModule[35]=C:\Windows\system32\GPAPI.dll
LoadedModule[36]=C:\Windows\system32\cryptnet.dll
LoadedModule[37]=C:\Windows\system32\WLDAP32.dll
LoadedModule[38]=C:\Windows\system32\SensApi.dll
LoadedModule[39]=C:\Windows\system32\Cabinet.dll
LoadedModule[40]=C:\Windows\system32\DEVRTL.dll
LoadedModule[41]=C:\Windows\WindowsMobile\Microsoft.WindowsMobile. Common.dll
LoadedModule[42]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\msc orjit.dll
LoadedModule[43]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Sy stem\5ba3bf5367fc012300c6566f20cb7f54\System.ni.dl l
LoadedModule[44]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Sy stem.Drawing\ead6be8b410d56b5576b10e56af2c180\Syst em.Drawing.ni.dll
LoadedModule[45]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Sy stem.Windows.Forms\fedf1ba58dced4f0b3f8c457648ceed 9\System.Windows.Forms.ni.dll
LoadedModule[46]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Sy stem.Configuration\4b1350e31ff09cc583b34854816d803 6\System.Configuration.ni.dll
LoadedModule[47]=C:\Windows\assembly\NativeImages_v2.0.50727_32\Sy stem.Xml\5dd9f783008543df3e642ff1e99de4e8\System.X ml.ni.dll
LoadedModule[48]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[49]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[50]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[51]=C:\Windows\system32\uxtheme.dll
LoadedModule[52]=C:\Windows\system32\dwmapi.dll
LoadedModule[53]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\Sys tem.EnterpriseServices.Thunk.dll
LoadedModule[54]=C:\Windows\WindowsMobile\wmdsyncproxy.dll
LoadedModule[55]=C:\Windows\system32\sxs.dll
LoadedModule[56]=C:\Windows\WindowsMobile\legacysyncengine.dll
LoadedModule[57]=C:\Windows\system32\WS2_32.dll
LoadedModule[58]=C:\Windows\system32\NSI.dll
LoadedModule[59]=C:\Windows\system32\CEUTIL.dll
LoadedModule[60]=C:\Windows\system32\RAPI.dll
LoadedModule[61]=C:\Windows\system32\WSOCK32.dll
LoadedModule[62]=C:\Windows\system32\wcescommproxy.dll
LoadedModule[63]=C:\Windows\system32\rapistub.dll
LoadedModule[64]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[65]=C:\Windows\system32\rapiproxystub.dll
LoadedModule[66]=C:\Windows\system32\mswsock.dll
LoadedModule[67]=C:\Windows\System32\wshtcpip.dll
LoadedModule[68]=C:\Windows\system32\propsys.dll
LoadedModule[69]=C:\Windows\system32\ntmarta.dll
LoadedModule[70]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[71]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[72]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[73]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[74]=C:\Windows\WindowsMobile\outstore.dll
LoadedModule[75]=C:\Windows\system32\MFC42u.dll
LoadedModule[76]=C:\Windows\system32\ODBC32.dll
LoadedModule[77]=C:\Windows\system32\MAPI32.dll
LoadedModule[78]=C:\Windows\system32\VERSION.dll
LoadedModule[79]=C:\Windows\system32\odbcint.dll
LoadedModule[80]=C:\Windows\WindowsMobile\mailsync.dll
LoadedModule[81]=C:\Windows\WindowsMobile\cefstore.dll
LoadedModule[82]=C:\Windows\WindowsMobile\INetRepl.dll
LoadedModule[83]=C:\Windows\system32\WININET.dll
LoadedModule[84]=C:\Windows\system32\Normaliz.dll
LoadedModule[85]=C:\Windows\system32\urlmon.dll
LoadedModule[86]=C:\Windows\system32\iertutil.dll
LoadedModule[87]=C:\Windows\WindowsMobile\InkStore.dll
LoadedModule[88]=C:\Windows\WindowsMobile\olregdll.dll
LoadedModule[89]=C:\Windows\system32\SspiCli.dll
LoadedModule[90]=C:\Windows\system32\dnsapi.DLL
LoadedModule[91]=C:\Windows\system32\iphlpapi.DLL
LoadedModule[92]=C:\Windows\system32\WINNSI.DLL
LoadedModule[93]=C:\Windows\system32\SFC.DLL
LoadedModule[94]=C:\Windows\system32\sfc_os.DLL
LoadedModule[95]=C:\Program Files\Common
Files\SYSTEM\MSMAPI\1033\MSMAPI32.DLL
LoadedModule[96]=C:\Program Files\Common Files\SYSTEM\MSMAPI\1033\MAPIR.DLL
LoadedModule[97]=C:\Program Files\Common Files\Microsoft
Shared\office11\mso.dll
LoadedModule[98]=C:\Windows\system32\apphelp.dll
LoadedModule[99]=C:\Program Files\Common
Files\SYSTEM\MSMAPI\1033\contab32.dll
LoadedModule[100]=C:\Windows\system32\RICHED20.DLL
LoadedModule[101]=C:\Windows\System32\wship6.dll
LoadedModule[102]=C:\Windows\WindowsMobile\richink.dll
LoadedModule[103]=C:\Windows\WindowsMobile\riresdll.dll
LoadedModule[104]=C:\Program Files\Common
Files\SYSTEM\MSMAPI\1033\mspst32.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=APPCRASH
ConsentKey=APPCRASH
AppName=Windows Mobile Device Center Sync Host
AppPath=C:\Windows\WindowsMobile\WmdHost.exe
ReportDescription=Stopped working


--
__________________________________________________ ______________________
Moshe Raab, Ph.D.
Microsoft Certified Technology Specialist - Microsoft Dynamics CRM 4.0
(USA) Biconix, Inc., private.php?do=newpm&u=, voice +1 (561) 208-3858, fax
+1 (928) 223-3858
(Israel) voice +972( 2) 590-0801, fax +972 (2) 590-0802
If you want to call me click here: https://me.vonage.com/biconix

repair found errors but did not correct the issue.
however, I created a new calendar folder,. moved all the items and it
synchronized OK.
I then added back clumps at a time until I found the event that caused the
sync to choke.
Later, it started to fail again. so I deleted all the events in the calendar
again , removed the PPC connection with the device and then recreated it. it
now synchronized all the events from the PPC to outlook and it all seems to
be working well now
thanks for your help
m

"Todd Allcock" <> wrote in message
news:...
> 2003SE should sync just fine.
>
> Have you tried the Outlook Detect and Repair (or Scan and Repair, or
> whatever they call ScanPST these days!)?
>
> In my experience, Activesync/WMDC is very unforgiving when it comes to any
> errors in Outlook data- even minor ones Outlook itself doesn't seem to
> care about.
>
> If the repair doesn't find anything, the next step is to see if it's a
> particular calendar item causing the issue. First, backup the device's
> PIM data with whatever backup program the Axim includes, (or grab
> PPCPimBackup from dotfred.net) so we can get back to this point if
> something goes wrong.
>
> Now, in Outlook on the PC, select all of your calendar events and move
> them to an empty subfolder (create one if neccessary.) Windows Mobile
> only syncs the default "main" folder, so the computer will have no
> calendar data from the device's standpoint. Now try to sync the device
> with the "empty" default calendar. If that works, the problem is likely
> one of the calendar entries containing some information the device or WMDC
> doesn't like. Now you can move a few calendar items at a time from the
> subfolder back to the main calendar until you find the one that breaks the
> sync. When you find it, retype/copy the relevant data to a new calendar
> event and delete the old one.
>
> Good luck!
>
>
>
>
> "Moshe Raab, Ph.D." <> wrote in message
> news:FB077356-BD03-4582-85D9-...
>>I recently installed a new computer at a client. it is a32 bit Windows 7
>>Home OS.
>> The client is using a Dell Axim Pocket PC, which is running:
>> Windows Mobile 2003 Second Edition
>> Version 4.21.1088 (Build 14260.2.0.2)
>> The client is running Office 2003.
>>
>> The pocket PC worked fine with Windows XP and ActiveSync
>> However with Windows 7 it does not work. I have done a hard-reset on the
>> device.
>> He is able to register the pocket PC and select the synchronization
>> options. in fact it can synchronize contacts and email. However, if
>> appointment synchronization is enabled, the synchronization fails
>> immediately with an exception. I have included the exception information
>> below.
>> I have also included the two event log errors (that always appear in
>> pairs) as well.
>>
>> According to the documentation I have seen Windows Mobile 2003 SE should
>> synchronize with Windows Mobile Center.
>> I have run out of ideas.
>> Can someone explains to me what the problem is and how to correct it?
>> Thanks
>> m
>