Strange InterfaceSupportsErrorInfo error - checkErrorInfo -2147352567 Error: Exception occurred

Question

I'm currently building a bit of code to search my emails for a particular subject and then search the body of the emails for some particular terms, then take comma separated data out of it. However I have now encountered an issue which I've never seen before, and that has only started appearing recently.

Whenever the code reaches:

inbox <- outlookNameSpace$Folders(6)$Folders("Inbox")

I get the following error:

<checkErrorInfo> 80020009 
No support for InterfaceSupportsErrorInfo
checkErrorInfo -2147352567
Error: Exception occurred.

Now I've seen people encounter similar errors around the place, but they seem to be dealing with sending emails rather than searching for particular emails.

I was wondering if anyone had any advice on how to fix this?

Full code:

library(RDCOMClient)

Fruit_1 <- "Apples"
Fruit_2 <- "Pears"
##Create vector to store searchables
searchf <- c(Fruit_1, Fruit_2)
## create object for outlook
OutApp <- COMCreate("Outlook.Application")
outlookNameSpace = OutApp$GetNameSpace("MAPI")

search <- OutApp$AdvancedSearch("Inbox", "urn:schemas:httpmail:subject = 'FRUIT QUANTITIES'")
inbox <- outlookNameSpace$Folders(6)$Folders("Inbox")

vec <- c()

get_vals <- function(report,searches) {
  data <- read.table(text=report,sep=",")
  colnames(data) <- c('key','value')
  
  date <- data[grepl("date",data$key,ignore.case=T),"value"]
  
  lst <- split(data$value,data$key)
  
  c(list(date=date),lst[searches])
}

for (x in emails)
{
  subject <- emails(i)$Subject(1)
  if (grepl(search, subject)[1])
  {
    text <- emails(i)$Body()
    print(text)
    break
  }
}

alec22 · Answer 1 · 2022-02-02T09:55:06.973

2

Turns out the reason for the failure was R was running too many lines of code. Therefore the addition of a Sys.sleep(5) after the 'search' variable solved the problem.

So my code looks like:

search <- OutApp$AdvancedSearch("Inbox", "urn:schemas:httpmail:subject = 'FRUIT QUANTITIES'")
Sys.sleep(5)

edited Feb 02 '22 at 09:55

answered Feb 01 '22 at 16:51

alec22

735
2
12

Again, do not hardcode indices. There is absolutely no reason to use asynchronous `Application.AdvancedSearch` if you are only searching in one folder - retrieve Inbox using `Namespace.GetDefaultFolder(olFolderItnbox)` and call `Items.Find/FindNext` or `Items.Restrict`. – Dmitry Streblechenko Feb 01 '22 at 18:54

Dmitry Streblechenko · Answer 2 · 2022-02-01T18:51:51.157

1

Why are hardcoding the mailbox index (6)? If you need the default Inbox, use Namespace.GetDefaultFolder(olFolderInbox). If you need a particular mailbox, use its name rather than index.

edited Feb 01 '22 at 18:51

answered Feb 01 '22 at 13:40

Dmitry Streblechenko

62,942
4
53
78

score 0 · Answer 3 · answered Feb 01 '22 at 20:52

Try to replace the order of the following lines of code:

inbox <- outlookNameSpace$Folders(6)$Folders("Inbox")

search <- OutApp$AdvancedSearch("Inbox", "urn:schemas:httpmail:subject = 'FRUIT QUANTITIES'")

The AdvancedSearch method of the Application class performs a search based on a specified DAV Searching and Locating (DASL) search string on a secondary thread. So, you should be aware that programmatically creating a large number of search folders can result in significant simultaneous search activity that would affect the performance of Outlook, especially if Outlook conducts the search in online Exchange mode.

In the code I didn't find how you handle the search results, but you may be interested in handling the Application.AdvancedSearchComplete event which is fired when the AdvancedSearch method has completed.

But if you need to search for items in a single folder (like in your code) you could used synchronous methods like the Find/FindNext or Restrict methods. You can read more about them in the following articles:

Strange InterfaceSupportsErrorInfo error - checkErrorInfo -2147352567 Error: Exception occurred

3 Answers3