MilkSync/Outlook 2003 Error
With OL and MS icon closed from sys tray, I keep getting the following error:
Detailed technical information follows:
---
Date and Time: 10/28/2010 10:46:10 PM
Machine Name: A-PC
IP Address: 127.0.0.1
Current User: A-PC\A
Application Domain: C:\Users\A\AppData\Local\Remember The Milk\MilkSync for Microsoft Outlook\
Assembly Codebase: file:///C:/Users/A/AppData/Local/Remember The Milk/MilkSync for Microsoft Outlook/AddinExpress.MAPI.DLL
Assembly Full Name: AddinExpress.MAPI, Version=2.3.222.2009, Culture=neutral, PublicKeyToken=4416dd98f0861965
Assembly Version: 2.3.222.2009
Assembly Build Date: 10/26/2010 2:30:54 PM
Exception Source: AddinExpress.MAPI
Exception Type: AddinExpress.MAPI.LogonException
Exception Message: The logon did not succeed, either because one or more of the parameters to MAPILogonEx were invalid or because there were too many sessions open already.
Exception Target Site: MAPIWrapper.Initialize
Object reference not set to an instance of an object.
Any advice or solutions?
Thanks,
Al
Detailed technical information follows:
---
Date and Time: 10/28/2010 10:46:10 PM
Machine Name: A-PC
IP Address: 127.0.0.1
Current User: A-PC\A
Application Domain: C:\Users\A\AppData\Local\Remember The Milk\MilkSync for Microsoft Outlook\
Assembly Codebase: file:///C:/Users/A/AppData/Local/Remember The Milk/MilkSync for Microsoft Outlook/AddinExpress.MAPI.DLL
Assembly Full Name: AddinExpress.MAPI, Version=2.3.222.2009, Culture=neutral, PublicKeyToken=4416dd98f0861965
Assembly Version: 2.3.222.2009
Assembly Build Date: 10/26/2010 2:30:54 PM
Exception Source: AddinExpress.MAPI
Exception Type: AddinExpress.MAPI.LogonException
Exception Message: The logon did not succeed, either because one or more of the parameters to MAPILogonEx were invalid or because there were too many sessions open already.
Exception Target Site: MAPIWrapper.Initialize
Object reference not set to an instance of an object.
Any advice or solutions?
Thanks,
Al
emily (Remember The Milk) says:
Hi Al,
I apologise for the delay -- this issue should now be resolved as of version 1.0.11.
If you do encounter any further issues, please let us know.
Thanks!
I apologise for the delay -- this issue should now be resolved as of version 1.0.11.
If you do encounter any further issues, please let us know.
Thanks!