Remove dead code
Source code checked in, #111668
↧
↧
Source code checked in, #111669
Problem: NULL pointer in unicode
Fix: Don't convert null to wstring
↧
Source code checked in, #111672
Problem: Inconisistent declaration of MrMAPILogonEx
Fix: Fix it
↧
Source code checked in, #111675
Problem: I feel the need. The need for speed.
Fix: Based on profiling, identified several high volume places in the code we can get minor speed boosts.
Including: Adding const& to high traffic wstring functions
Rearranging string building code to minimize wstring constructors
Eliminating some high cost MAPIFreeBuffer calls when the target is NULL
Moving \r stripping code only to paths that require it (in the process fixing several line ending bugs in mrmapi output)
↧
Source code checked in, #111676
Problem: We can parse PR_CHANGE_KEY
Fix: Do it
↧
↧
Source code checked in, #111677
Problem: Can't request obscure properties on multiple stores.
Fix: Reading props from multiple stores depended on the prop being available in the store table. New code spots MAPI_E_NOT_FOUND and opens the store to find the prop.
↧
Source code checked in, #111678
Problem: Update build#
Fix: Do it
↧
Source code checked in, #111679
Add missing smartview parser files
↧
New Post: .MSG to .EML conversion error
Hi, I'm trying to use MFCMAPI to convert a standard Outlook .msg file to .eml so I can share it with another party.
When I use the "Advanced > Import/Export > Convert .msg to .eml" function, choose the .msg file, give a name to the desired .eml and then click Open, I get the following three errors:
Error: IConverterSession not found. This interface is only supported by Outlook 2003 and higher.
Code: REGDB_E_CLASSNOTREG == 0x80040154
Function CoCreateInstance(CLSID_IConverterSession, NULL, CLSCTX_INPROC_SERVER, IID_IConverterSession, (LPVOID*)&lpConverter)
File MapiMime.cpp
Line 84
Error:
Code: REGDB_E_CLASSNOTREG == 0x80040154
Function ExportIMessageToEML( pMessage, lpszEMLFile, ulConvertFlags, et, mst, ulWrapLines, lpAdrBook)
File MapiMime.cpp
Line 211
Error:
Code: REGDB_E_CLASSNOTREG == 0x80040154
Function ConvertMSGToEML( dlgFilePickerMSG.GetFileName(), dlgFilePickerEML.GetFileName(), ulConvertFlags, et, mst, ulWrapLines, lpAdrBook)
File MainDlg.cpp
Line 1756
I'm using a 32-bit version of Outlook 2013 from Office 365.
Any chance this will work?
Thanks!
Greg
When I use the "Advanced > Import/Export > Convert .msg to .eml" function, choose the .msg file, give a name to the desired .eml and then click Open, I get the following three errors:
Error: IConverterSession not found. This interface is only supported by Outlook 2003 and higher.
Code: REGDB_E_CLASSNOTREG == 0x80040154
Function CoCreateInstance(CLSID_IConverterSession, NULL, CLSCTX_INPROC_SERVER, IID_IConverterSession, (LPVOID*)&lpConverter)
File MapiMime.cpp
Line 84
Error:
Code: REGDB_E_CLASSNOTREG == 0x80040154
Function ExportIMessageToEML( pMessage, lpszEMLFile, ulConvertFlags, et, mst, ulWrapLines, lpAdrBook)
File MapiMime.cpp
Line 211
Error:
Code: REGDB_E_CLASSNOTREG == 0x80040154
Function ConvertMSGToEML( dlgFilePickerMSG.GetFileName(), dlgFilePickerEML.GetFileName(), ulConvertFlags, et, mst, ulWrapLines, lpAdrBook)
File MainDlg.cpp
Line 1756
I'm using a 32-bit version of Outlook 2013 from Office 365.
Any chance this will work?
Thanks!
Greg
↧
↧
New Post: .MSG to .EML conversion error
↧
New Post: .MSG to .EML conversion error
I figured it was something like that. Thanks!
Greg
Greg
↧
Updated Release: September 2015 Release (Sep 02, 2015)
Build: 15.0.0.1043
Full release notes at SGriffin's blog.
If you just want to run the MFCMAPI or MrMAPI, get the executables. If you want to debug them, get the symbol files and the source.
The 64 bit builds will only work on a machine with Outlook 2010/2013 64 bit installed. All other machines should use the 32 bit builds, regardless of the operating system.
![Facebook Badge]( "Facebook Badge")
Full release notes at SGriffin's blog.
If you just want to run the MFCMAPI or MrMAPI, get the executables. If you want to debug them, get the symbol files and the source.
The 64 bit builds will only work on a machine with Outlook 2010/2013 64 bit installed. All other machines should use the 32 bit builds, regardless of the operating system.
↧
Updated Wiki: Home
Project Description
MFCMAPI provides access to MAPI stores to facilitate investigation of Exchange and Outlook issues and to provide developers with a sample for MAPI development.
September 2015 Release of MFCMAPI and MrMAPI
Help/Feedback
For assistance using MFCMAPI, developing add-ins, or general MAPI development, consult thedocumentation. Find a bug? Need help? Have a suggestion? Use theDiscussions or
Issue Tracker tabs or contact me through my blog:
http://blogs.msdn.com/stephen_griffin/contact.aspx.
Become a fan on Facebook!
Interested in Exchange Web Services (EWS)? Try
EWSEditor!
↧
↧
Released: September 2015 Release (Sep 02, 2015)
Build: 15.0.0.1043
Full release notes at SGriffin's blog.
If you just want to run the MFCMAPI or MrMAPI, get the executables. If you want to debug them, get the symbol files and the source.
The 64 bit builds will only work on a machine with Outlook 2010/2013 64 bit installed. All other machines should use the 32 bit builds, regardless of the operating system.
![Facebook Badge]( "Facebook Badge")
Full release notes at SGriffin's blog.
If you just want to run the MFCMAPI or MrMAPI, get the executables. If you want to debug them, get the symbol files and the source.
The 64 bit builds will only work on a machine with Outlook 2010/2013 64 bit installed. All other machines should use the 32 bit builds, regardless of the operating system.
↧
Updated Release: September 2015 Release (Sep 02, 2015)
Build: 15.0.0.1043
Full release notes at SGriffin's blog.
If you just want to run the MFCMAPI or MrMAPI, get the executables. If you want to debug them, get the symbol files and the source.
The 64 bit builds will only work on a machine with Outlook 2010/2013 64 bit installed. All other machines should use the 32 bit builds, regardless of the operating system.
![Facebook Badge]( "Facebook Badge")
Full release notes at SGriffin's blog.
If you just want to run the MFCMAPI or MrMAPI, get the executables. If you want to debug them, get the symbol files and the source.
The 64 bit builds will only work on a machine with Outlook 2010/2013 64 bit installed. All other machines should use the 32 bit builds, regardless of the operating system.
↧
New Post: Mapi tool verse powershell
When I count my archive folder via the following powershell command
" Get-Mailboxfolderstatistics -Identity "mymail" -Archive -FolderScope RecoverableItems -IncludeAnalysis
I am getting about 20K in messages. This includes the /deletetions folder under it.
Any idea why when I go into the same archive folder with the mapi tool and browse to /deletions I get a higher count than the powershell count. I'd expect it to be lower. Is the Mapi tool counting more than just the # of messages?
" Get-Mailboxfolderstatistics -Identity "mymail" -Archive -FolderScope RecoverableItems -IncludeAnalysis
I am getting about 20K in messages. This includes the /deletetions folder under it.
Any idea why when I go into the same archive folder with the mapi tool and browse to /deletions I get a higher count than the powershell count. I'd expect it to be lower. Is the Mapi tool counting more than just the # of messages?
↧
Source code checked in, #111729
Problem: Store EID V3 not getting parsed
Fix: Add parser logic
↧
↧
New Post: Should MFCMapi work with Outlook 2016?
Hi, just tried MFCMapi on a clean newly setup Windows 10/Outlook 2016 system (both x64). Should that run? Im getting MAPI_E_CALL_FAILED on MAPIInitialize when trying to logon via MFCMapi.
↧
New Post: Should MFCMapi work with Outlook 2016?
You can ignore the question i was sure the incredible "no questions asked"-Installer for Office 2016 would install the x64 version on a x64 system but it didn't. Remember never assume that an installer that doesn't ask anything would do the obvious thing :(
↧
Commented Unassigned: Crashing at logon [17449]
Windows 7 SP2, Outlook 2010 SP2, Exchange Online mailbox. After opening MFCMAPI, I select Session>logon. The prompt to select a profile appears. I select the profile, and the application crashes with a popup stating MFXMAPI x86 has stopped working.
Application Event Log contains:
Log Name: Application
Source: Application Error
Date: 6/5/2015 3:37:48 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: MMCNALLY-W7.domain1.company.com
Description:
Faulting application name: mfcmapi.exe, version: 15.0.0.1042, time stamp: 0x53daa53b
Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9
Exception code: 0xc0000005
Fault offset: 0x0003b4a8
Faulting process id: 0x1bec
Faulting application start time: 0x01d09fc714142da6
Faulting application path: C:\Users\mmcnally\Downloads\MFCMapi.exe.15.0.0.1042\mfcmapi.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
Report Id: 5832b6f6-0bba-11e5-9987-d067e51f39f8
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="2015-06-05T19:37:48.000000000Z" />
<EventRecordID>40755</EventRecordID>
<Channel>Application</Channel>
<Computer>MMCNALLY-W7.domain1.company.com</Computer>
<Security />
</System>
<EventData>
<Data>mfcmapi.exe</Data>
<Data>15.0.0.1042</Data>
<Data>53daa53b</Data>
<Data>MSVCR90.dll</Data>
<Data>9.0.30729.6161</Data>
<Data>4dace5b9</Data>
<Data>c0000005</Data>
<Data>0003b4a8</Data>
<Data>1bec</Data>
<Data>01d09fc714142da6</Data>
<Data>C:\Users\mmcnally\Downloads\MFCMapi.exe.15.0.0.1042\mfcmapi.exe</Data>
<Data>C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll</Data>
<Data>5832b6f6-0bba-11e5-9987-d067e51f39f8</Data>
</EventData>
</Event>
Comments: ** Comment from web user: kirkgrabowski **
Application Event Log contains:
Log Name: Application
Source: Application Error
Date: 6/5/2015 3:37:48 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: MMCNALLY-W7.domain1.company.com
Description:
Faulting application name: mfcmapi.exe, version: 15.0.0.1042, time stamp: 0x53daa53b
Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9
Exception code: 0xc0000005
Fault offset: 0x0003b4a8
Faulting process id: 0x1bec
Faulting application start time: 0x01d09fc714142da6
Faulting application path: C:\Users\mmcnally\Downloads\MFCMapi.exe.15.0.0.1042\mfcmapi.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
Report Id: 5832b6f6-0bba-11e5-9987-d067e51f39f8
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="2015-06-05T19:37:48.000000000Z" />
<EventRecordID>40755</EventRecordID>
<Channel>Application</Channel>
<Computer>MMCNALLY-W7.domain1.company.com</Computer>
<Security />
</System>
<EventData>
<Data>mfcmapi.exe</Data>
<Data>15.0.0.1042</Data>
<Data>53daa53b</Data>
<Data>MSVCR90.dll</Data>
<Data>9.0.30729.6161</Data>
<Data>4dace5b9</Data>
<Data>c0000005</Data>
<Data>0003b4a8</Data>
<Data>1bec</Data>
<Data>01d09fc714142da6</Data>
<Data>C:\Users\mmcnally\Downloads\MFCMapi.exe.15.0.0.1042\mfcmapi.exe</Data>
<Data>C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll</Data>
<Data>5832b6f6-0bba-11e5-9987-d067e51f39f8</Data>
</EventData>
</Event>
Comments: ** Comment from web user: kirkgrabowski **
I ran into this too once Microsoft rolled out MAPI over HTTP to our Exchange Online tenant. Adding the registry key HKCU\Software\Microsoft\Exchange\MapiHttpDisabled = 1 (DWORD) resolved the issue by reverting to the older RPC over HTTPS protocol. (You may need to clear the Autodiscover.xml files from %localappdata%\Microsoft\Outlook and restart Outlook a couple of times for the setting to take effect. There's some general information about the newer protocol at the following links. Also, once I upgraded to Outlook 2013, the problem went away without needing to disable MAPI/HTTP.
http://blogs.technet.com/b/exchange/archive/2014/05/09/outlook-connectivity-with-mapi-over-http.aspx
https://technet.microsoft.com/en-us/library/dn635177%28v=exchg.150%29.aspx
↧
More Pages to Explore .....
