O365 Mail Reader Cannot Select Mailbox

AETLE v6.3.12.14 x64

Hello, we have a significant issue where the O365 Mailbox Reader Package Action Object seemingly on random occasions stops due to and "unable to select Mailbox" error. 

We have numerous packages with similar readers and most work without issue but then all of a sudden one or two of them will have this. I initially thought it was the regex filters, but the error infers that it doesn't even get to that point. 

Then I thought it may have been the fact that I used a variable in the inbox folder name but then I used a hardcoded folder name and out of the blue this error appeared.

Unfortunately, I can't provide a mailbox for this to be tested against and I wish I could provide more detail but as I have said it is random and works more cases than not. But when it fails it causes us grief as many of these messages are time critical. I can usually get it through by even going to the extreme of editing the package or the connection and just generally forcing a change. But then again it may occur again. If there was some more detail in the error, then this may help troubleshoot. 

I was also wondering if it had anything to do with the number of folders in the inbox. But as I say, I can then get it to work by forcing a change to the package action.

Another though I just had is I am wondering if has anything to do with the package running via the agent (which is how it normally runs via schedule) and running via the designer UI (which is how I ultimately try and troubleshoot and force execution). One of the packages that seems to be a repeat offender does only come in every few weeks which would correlate with the apparent randomness of the issue. I'm wondering if when running via the agent if there is a timeout that results in this error.

regards


 
 

The log should show the actual mailbox name but it is empty
We can assume that it is being replaced with a variable value
So the variable name will have the exact name as a folder name and the variable value is blank.
You should be able to see it in the Variables tab if running from the interface

You can also try enabling the Write Variables option on the execution tab

www.etl-tools.com/wiki/advanced-etl-proc...tions/#execution-tab

This will help you understand what is happening with variables.

At some stage, we would need to review how we work with variables/parameters
I think it is too complicated at the moment.

 

Hi Mike

That was what I thought as well... That a variable name in the mailbox connections settings may be "empty". Which it was as this is how I manage DEV and PROD mailboxes. However, I did switch it out to use a connection that was a hardcoded mailbox folder name and even selected it from a refreshed folder list. This worked on another package that was using a similar connection.

I'd like to use "write variables" but this is for the entire AETL instance and not just for a specific package execution. We have close to 18,000 package executions in a month so that would generate a lot of text in log files and no doubt have some impact on performance and even resources.

If I could turn on write variables just for a specific package, then that could help troubleshoot.

Another question. When adding the O365 Reader Action into a package. Does store any of the details of the Action Object in the Package? I'm wondering if there is some stale info that is fixed inside the package itself and is overriding the package Reader config itself.

Cheers

Another question. When adding the O365 Reader Action into a package. Does store any of the details of the Action Object in the Package? I'm wondering if there is some stale info that is fixed inside the package itself and is overriding the package Reader config itself.

It does store ConnectionID but not actual connection details.

They are taken from connection objects and details are replaced with variables before the action execution

Hi

I believe that the root cause of this MAY BE related to the REGEX on the filters. IF the regex is malformed or perhaps too long. There is no immediate feedback in the designer - well at least none that I get.

Then at runtime there is no feedback that this is the cause that the 'mailbox is not selected' but rather this misleading message. 

Also, it seems that if the package is executed by the Agent, then this type of scenario MAY BE more likely to trigger this specific error.

Kind Regards
 

Can you post a screenshot so we can see the regex?

If it is related to regex the message must be different, so we have to correct it.