MFCMAPI

PR_ATTACH_LONG_PATHNAME is used as part of the process of attaching the file. After that, whether it's there or not is pretty much undefined. If you're trying to get the long file name of an attachment, you should be using PR_ATTACH_LONG_FILENAME.

It's still not a message store property. It is, however, present as a row in the message store table, hence the restriction can work.

It's not always the case that a property present in the row of a table is also present in the object that the row in the table describes. This is one of those cases. You'll see several more cases like that in the attachment and recipient tables. The table rows can and do contain additional metadata about the object they reference.

I don't repro. At this point, a screen shot would be appropriate. BTW - you can insert your screenshot directly into your reply where everyone can see it - you don't need to upload it to another repository that requires me to jump through hoops to view.

You don't mention the version of Outlook, but I believe this is a known issue with emsmdb32.

However - your report is contradictory - how can MFCMAPI crash and then somehow also display a window?

I don't repro - what version of Outlook and Exchange? Cached or uncached?

What's the error dialog say?

I use PR_DISPLAY_NAME as this value also gives same as PR_ATTACH_LONG_FILENAME and PR_ATTACH_LONG_FILENAME is absent when MSG is an attachment.

If that works for you, great. For more general code, you should detect the attachment style and pick the property you use accordingly.

How to insert image in this reply as you told me?

Attachment is of type MSG.

Guess I should have tried it first. :) Looks like the image does need to be hosted somewhere. Sorry about that.

Outlook 2007 32 bit.

Ok - try applying the last updates for Outlook 2007. If you still repro, let me know if you can repro with 2013.

Exchange 2007, Outlook 2007 32 bit, cached.

Error:
Code: MAPI_E_FAILONEPROVIDER == 0x8004011D
Function CallOpenEntry( lpMDB, NULL, NULL, NULL, NULL, NULL, MAPI_BEST_ACCESS, NULL, (LPUNKNOWN*)&m_lpContainer)
File MsgStoreDlg.cpp
Line 68

Hehe - Image problem - Microsoft

Ok - lemme know if you repro with something still under support.

You got this too?

The blank window is a side effect of me not implementing a way to cancel the request to open the window. I don't ever plan on fixing it. The failure to open the store means either you got your flags wrong, your permissions are inadequate, or the mailbox is otherwise inaccessible.

I got 2 different results, both of which were unexpected:

1) Using Outlook 2007 32 bit

2) Using Outlook 2013 32 bit

This error mainly occurs when server and client are unable to connect because of a network failure or of Offline folder file corruption. I am sharing a link that shared steps to resolve this issue by connecting with Exchange server and sync OST file or if OST file is corrupted converts OST to PST.

New Post: PR_ATTACH_LONG_PATHNAME giving value when email is saved

New Post: PR_RESOURCE_FLAGS not visible in message store

New Post: Double clicking on attachment row gives a new window

New Post: MFCMAPI crash

New Post: Unexpected behaviour

New Post: Unexpected behaviour

New Post: PR_ATTACH_LONG_PATHNAME giving value when email is saved

New Post: PR_ATTACH_LONG_PATHNAME giving value when email is saved

New Post: Double clicking on attachment row gives a new window

New Post: Double clicking on attachment row gives a new window

New Post: MFCMAPI crash

New Post: MFCMAPI crash

New Post: Unexpected behaviour

New Post: Unexpected behaviour

New Post: Double clicking on attachment row gives a new window

New Post: Unexpected behaviour

New Post: Unexpected behaviour

New Post: Unexpected behaviour

New Post: MFCMAPI crash

New Post: Error : Cannot open your default e-mail folders. the file ..outlook.pst is in use and cannot be accessed.