Question

a3kumarz on Wed, 05 Dec 2012 08:13:25


In Outlook 2013, I do a search using Outlook UI and select a search result email and run the following code in VBA:

Sub test12()
    Dim oMail As Outlook.MailItem
   
    Set oMail = Application.ActiveExplorer.Selection(1)
    Debug.Print oMail.EntryID
    Set oMail = Nothing
End Sub

On the line Debug.Print oMail.EntryID, I get the following error:

Run-time error '-1144782585 (bbc40107)':
Could not open the item. Try again.

I am using a pop3 account linked into the Outlook 2012 32bit on Windows 8 32bit.
It I open the email and run the code on the open Inspector, I can access all the properties.

Am I doing something wrong or is this a bug in Outlook 2013?

Thank you.
Anand

Replies

Ken Slovak MVP on Wed, 05 Dec 2012 14:25:55


Is the item actually selected? What happens if you select an item independent of any search, does the code work then?

--
Ken Slovak
[MVP-Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007
"a3kumarz" <=?utf-8?B?YTNrdW1hcno=?=> wrote in message news:0297e404-6116-45f7-b1fc-9d45551b5ed5...

In Outlook 2013, I do a search using Outlook UI and select a search result email and run the following code in VBA:

Sub test12()
    Dim oMail As Outlook.MailItem
   
    Set oMail = Application.ActiveExplorer.Selection(1)
    Debug.Print oMail.EntryID
    Set oMail = Nothing
End Sub

On the line Debug.Print oMail.EntryID, I get the following error:

Run-time error '-1144782585 (bbc40107)':
Could not open the item. Try again.

I am using a pop3 account linked into the Outlook 2012 32bit on Windows 8 32bit.
It I open the email and run the code on the open Inspector, I can access all the properties.

Am I doing something wrong or is this a bug in Outlook 2013?

Thank you.
Anand

a3kumarz on Wed, 05 Dec 2012 20:01:39


Yes, I do click on the item to select it, it gets highlighted.

If i donot do a search and go to the folder in which that email resides, select it and run the code, it works fine without any errors.

Ken Slovak MVP on Thu, 06 Dec 2012 15:35:11


I don't have a Windows 8 VM set up yet, I tested this on Outlook 2013 x86 release version running on Windows 7 x86 with a POP3 account. I can't repro the problem there.
 
I took your sample code and put it in the VBA project, I ran a search in Sent Items and repeated a different search in Inbox. In both cases I selected an item from the search return in the UI and then ran the code. The EntryID was printed to the Immediate window with no errors.
 
Can you repro on a different OS than Windows 8? Can you repro this on another machine? You're testing with the release version and not a beta version?

--
Ken Slovak
[MVP-Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007
"a3kumarz" <=?utf-8?B?YTNrdW1hcno=?=> wrote in message news:749a2862-c374-4a09-84ff-f7894866d596...

Yes, I do click on the item to select it, it gets highlighted.

If i donot do a search and go to the folder in which that email resides, select it and run the code, it works fine without any errors.

a3kumarz on Fri, 07 Dec 2012 02:21:26


Hi Ken,

I didn't get a chance to test on any other OS other than on Win 8.

Yes, its the latest release Office 2013 version that was released on 28/10/2012,
Microsoft Outlook 2013 (15.0.4420.1017) MSO (15.0.4420.1017) 32-bit.

I did some further testing and here's what I found:

Outlook Search provides the following search scope:

If the scope is set to Current Folder, Subfolders or Current Mailbox, then the code works without any errors. But if the scope is set for All Mailboxes or All Outlook items, then I get the error.

For my situation, there are multiple psts linked into my Outlook so have to search for All Mailboxes scope.

In previous versions of Outlook, this is working fine but not in Outlook 2013.

Ken Slovak MVP on Fri, 07 Dec 2012 18:30:23


I'll try to verify that, but I won't be able to get to that until next week.

--
Ken Slovak
[MVP-Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007
"a3kumarz" <=?utf-8?B?YTNrdW1hcno=?=> wrote in message news:d421e857-fe0b-4ab1-af32-7d3c7944a16b...

Hi Ken,

I didn't get a chance to test on any other OS other than on Win 8.

Yes, its the latest release Office 2013 version that was released on 28/10/2012,
Microsoft Outlook 2013 (15.0.4420.1017) MSO (15.0.4420.1017) 32-bit.

I did some further testing and here's what I found:

Outlook Search provides the following search scope:

If the scope is set to Current Folder, Subfolders or Current Mailbox, then the code works without any errors. But if the scope is set for All Mailboxes or All Outlook items, then I get the error.

For my situation, there are multiple psts linked into my Outlook so have to search for All Mailboxes scope.

In previous versions of Outlook, this is working fine but not in Outlook 2013.

a3kumarz on Tue, 11 Dec 2012 00:06:51


Hi Ken, Any update on this issue?

许阳(无锡) on Tue, 11 Dec 2012 07:47:01


Hi a3kumarz,

Thanks for posting in the MSDN Forum.

I have similar environment like Ken mentioned. I still can't reproduce your issue. Please find out where is the different between us from the following screen shooting.

Have a good day,

Tom

Ken Slovak MVP on Tue, 11 Dec 2012 15:20:09


Hi Tom,
 
Did you have more than 1 PST file opened, and were you set up with your profile to use a POP3 account? I was able to repro the bug running on Win7x86 with Outlook 2013 x86 with scope set to All Outlook Items or All Mailboxes with 4 PST files opened.

--
Ken Slovak
[MVP-Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007
"Tom_Xu MSFT" <=?utf-8?B?VG9tX1h1IE1TRlQ=?=> wrote in message news:6f783f38-1c4c-4655-8b30-5a769a7b277b...

Hi a3kumarz,

Thanks for posting in the MSDN Forum.

I have similar environment like Ken mentioned. I still can't reproduce your issue. Please find out where is the different between us from the following screen shooting.

Have a good day,

Tom

Ken Slovak MVP on Tue, 11 Dec 2012 15:20:10


I was able to repro the bug running on Win7x86 with Outlook 2013 x86 with scope set to All Outlook Items or All Mailboxes with 4 PST files opened.
 
I reported the bug to the Outlook product group, and to the PM who is now in charge of the Outlook object model.

--
Ken Slovak
[MVP-Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007
"a3kumarz" <=?utf-8?B?YTNrdW1hcno=?=> wrote in message news:68f02158-a5e3-426d-9f3a-78fe181afe97...
Hi Ken, Any update on this issue?

a3kumarz on Wed, 12 Dec 2012 02:01:23


Hi Ken, thanks for the reply. Yes I was able to get hold of a Windows 7 with Office 2013 Virtual Machine and was able to recreate the error as well.

In Win 7 & Office 2013, you have to select one of the search results that actually resides in another PST and then run the code to get the error.

In Win 8 & Office 2013, the search result items may reside within the same or different PST's and you run the code to get the error.

I however, donot see as to why the outcome is different when tested in different OS. Both OS and Office that I used for testing was 32bit.

Thanks.

Ken Slovak MVP on Wed, 12 Dec 2012 15:02:50


I was able to repro the bug no matter what PST the selected item is in, but the bug has been reported so that's about all we can do until the product group decides whether to fix it or not. About the only other thing that can be done is if you were to open a support incident, as it's a bug any charges would ultimately be refunded, and see if a hot fix can be arranged.

--
Ken Slovak
[MVP-Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007
"a3kumarz" <=?utf-8?B?YTNrdW1hcno=?=> wrote in message news:46ef2857-cc3f-41cb-aa65-b2b9467a30ff...

Hi Ken, thanks for the reply. Yes I was able to get hold of a Windows 7 with Office 2013 Virtual Machine and was able to recreate the error as well.

In Win 7 & Office 2013, you have to select one of the search results that actually resides in another PST and then run the code to get the error.

In Win 8 & Office 2013, the search result items may reside within the same or different PST's and you run the code to get the error.

I however, donot see as to why the outcome is different when tested in different OS. Both OS and Office that I used for testing was 32bit.

Thanks.

Jimmy Bergmark on Mon, 04 Feb 2013 08:49:31


I also run into this problem. I hope for a hotfix soon. I have Office Processional 2013 32-bit (version 15.0.4454.1004) on Windows 7 32-bit.

Brain2000 on Mon, 20 Jan 2014 23:49:10


We currently have a customer with this error.  Is there a fix yet?

Ken Slovak MVP on Tue, 21 Jan 2014 18:45:09


There is no fix yet as far as I can tell, based on the latest available code.

If this is important you should open a support case with MS support and try to get a fix. The bug has been reported to the product group, but from there it's up to them to triage bugs and decide which to fix and when.

Ken Slovak MVP on Tue, 21 Jan 2014 18:52:13


I reported this again to the product group, but I do encourage you to open a support incident if you can.

Alex Koder on Thu, 23 Jan 2014 18:05:22


I am seeing the same issue. This post has exact step-by-step to reproduce, in case somebody finds it useful.

http://social.msdn.microsoft.com/Forums/en-US/5df28604-44ab-4a5e-b12e-3c45055e5892/outlook-2013-errors-on-messages-in-search-results?forum=outlookdev

yahya omar on Tue, 27 Feb 2018 13:05:51


Any new, I have this problem (Windows 10 64 bit and office 2013 32 bit).

I got this problem when I upgrade office from 2010 to 2013

Please help me and urgent this matter

Please expedite to fix this error