topic Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2 in Product Forum

Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

YiniZhang — Wed, 21 Dec 2022 13:14:12 GMT

Hi Eric @ewilson and all

we are not able to get the received emails from the subfolder of one of our shared mailboxes since the beginning of this month. We tried MS Outlook VBO 6.10.7 and the newest one 10.2.2 both and removed all the filter expressions. Getting emails from the inbox directly works, from the subfolder under the inbox however doesn't.
We already enabled the Use Cached Exchange Mode and Download shared folders.

Blue Prism Version: v7.1.1
Outlook VBO versions: v6.10.7 & 10.2.2

Does anyone have a solution please? Many thanks.

Best Regards,
Yini

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

ewilson — Wed, 21 Dec 2022 14:00:48 GMT

@Yini Zhang,

If you have v10.2.2 of the Outlook VBO then you also have access to the new Get Items in Folder action. Have you tried using it? If not, I would recommend that you do. It's much more flexible at retrieving mail from different folders. Just make sure to pay attention to the format of folder path input. From the screenshot, it looks like yours may be \\Posteingang\test2, but that depends on whether there's another level above Posteingang which isn't clear from the screenshot.

Cheers,
Eric

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

YiniZhang — Wed, 21 Dec 2022 18:15:01 GMT

@ewilson Thank you for your reply, Eric. "Posteingang" is exactly "inbox" in German.:) So I tried the Get Items in Folder just now and got this error instead:

I also tried "\\[email-adress of the shared mailbox]\Posteingang\test2" and "\\[name of the shared mailbox](eg. 'DE-FM Dev', with and without single quote)\Posteingang\test2", unfortunately it didn't work either.

Secondly, were there any updates at the beginning of this month? "Move Item" from V6.10.7 seems to be not working as well.

Our purpose is to
1. move the emails from the inbox of a shared mailbox to one of its subfolders and
2. check afterwards by using Get Items in Folder of this subfolder and Collection Contains Value of Utility - Collection Manipulation, whether the target email is correctly moved.

Which action would you suggest for moving emails in our case? Move Item or Move Email to Inbox Sub Folder of v10.2.2 pls?

BR,
Yini

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

ewilson — Wed, 21 Dec 2022 19:32:04 GMT

@Yini Zhang,

Have you tried restarting Outlook and Blue Prism and testing again? I've run several tests against shared mailbox folders (i.e. Inbox, Sent Items, and custom top-level folders), folders of the main mailbox (i.e. Inbox, Sent Items, and custom top-level folders), and subfolders of both. I haven't run into any issues with the Get Items in Folder action throwing exceptions about not being able to follow the path unless I gave it an invalid path. That could include misspellings or even the inclusion of extra whitespace in the name of a folder (ex. TestFolderX where X is actually a space).

Here's a view of one of my test machines and the folder structure:

I'm able to pull data from these folders through paths such as \\ewilson@xyz.com\Inbox, \\ewilson@xyz.com\Inbox\Test Folder, \\ewilson@xyz.com\Inbox\Test123\Test222, \\Mailbox01\Inbox, \\Mailbox01\Inbox\TestFolder01, etc.

When you test, do you have Outlook up-and-running? If not, does your Outlook instance have multiple profiles or one single profile?

Regarding the Move Item action, it hasn't changed since v6.10.7 release of the VBO back in August.

Cheers,
Eric

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

YiniZhang — Thu, 22 Dec 2022 17:34:31 GMT

@ewilson
Yes, we noticed that Outlook must be running during the process, otherwise the object could not be found.
We only have one profile in Outlook on this server which has the full permissions of the mentioned shared mailbox as owner. Still the object with the following paths (subfolder directly under inbox or sub- subfolder, eg. inbox\test2 and inbox\testVBO\testVBO1) could not be found, except once after I restarted the server and BP. Which means the space in the name of the shared mailbox is not the problem, the action with the same path as in the screenshot could run to the end sucessfully. But in most cases, we got the following error.
We got the same error by Move Item and Move Email to Inbox Sub Folder.

BR,
Yini

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

ewilson — Thu, 22 Dec 2022 18:14:25 GMT

@Yini Zhang,

A little clarification here. The format of the folder path with the actions Get Received Items (Basic) and Move Email to Inbox Subfolder is different from the format of the folder path for the actions Get Items in Folder and Move Item. For Get Received Items (Basic) and Move Email to Inbox Subfolder you just need to set the Subfolder input value to the name of the specific subfolder under Inbox. If you have nested subfolders, then you would enter Subfolder1\Subfolder2\..... So, based on your screenshots, you would set the value of Subfolder to test2 or testVBO\testVBO1, as examples, for either Get Received Items (Basic) or Move Email to Inbox Subfolder. Of course, you would also need to supply a value for the Account Display Name.

The path format is different between the older actions and the newer Get Items in Folder and Move Item actions because those actions aren't hardcoded to work only with the Inbox or Sent Items folders.

For the newer functions, there is a change we could make as a debugging technique to try and figure out where the search is failing. It will require a few changes in the Global Code section and adding an additional namespace reference. If you're interested, let me know and I'll type up the steps.

Cheers,
Eric

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

YiniZhang — Fri, 23 Dec 2022 05:51:01 GMT

@ewilson
noticed, thank you for the clarification.
Yes please , it would be very helpful, since in our business scenarios we work with Outlook very often. We had a big problem with moving emails to one of the inbox sub folders with Move Email to another Mailbox (And Subfolders) in v6.10.5 by one running bot of us. The emails in the inbox could not be found and moved because the operation failed, even though one retry logic and a code stage for the Outlook (re-)connection were built on this page. The same emails however would be found and moved in the next bot running.

BR,
Yini

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

ewilson — Tue, 27 Dec 2022 17:01:40 GMT

@Yini Zhang,

One of the easiest ways to debug Code stages is to use the .NET MesageBox object. That gives you the ability to pop-up a dialog where you can add information to give you an idea how things are progressing in your code, what paths the code takes, etc. To do this, you need to add a DLL reference and a namespace reference in the Code Options of the VBO Properties.

Open the Outlook VBO and then on the Initialize tab double click on the Note stage. This will bring up the VBO Properties dialog.

Click on the Code Options tab. Under the External References section, add the following DLL: System.Windows.Forms.dll. Under the Namespace Imports section, add the following namespace entry: System.Windows.Forms. It should look something like this when you're done:

Once you've done that, you now have access to the .NET MessageBox object. On the Global Code tab you can now add calls to MessageBox.Show() to help us understand where things are going awry. Here's an example:

Here's what it will look like as you step through the process:

WARNING: Make sure you go back and remove all of the MessageBox entries before trying to run the process in production. Otherwise, your process will stop at each MessageBox.Show call and wait for someone to dismiss the messagebox by clicking the OK button.

Cheers,
Eric

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

YiniZhang — Wed, 28 Dec 2022 12:45:58 GMT

@ewilson Thank you for the debugging steps in details. Here is the result:
The folder "\\DE-*** RPA Dev\inbox\testVBO\testVBO1" was located successfully at first and the bot kept running in the loop. After that, "\\DE-*** RPA Dev\inbox\testVBO\testVBO5" however could not be located. I changed the current value of Destination Folder to "****\testVBO1", which was indeed found successfuly. This time the same error again.
BR,
Yini

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

ewilson — Wed, 28 Dec 2022 17:17:53 GMT

@Yini Zhang,

Very strange. It's almost as if the Namespace reference is being lost or corrupted somehow. 🤔 When trying to work with testVBO5 the first time, or testVBO1 the second time, are you seeing message boxes displayed telling you at what point the processing made it to before the exception was thrown?

-- EDIT --
One other thing you could try doing is adding these two lines to the start of the GetFolderFromPath function in the Global Code section.

olNamespace = Nothing
olNamespace = olApp.GetNameSpace("MAPI")

Basically this refreshes the Namespace/MAPI reference.

Cheers,
Eric

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

YiniZhang — Thu, 29 Dec 2022 17:47:52 GMT

@ewilson Thanks. I added the two lines to the start of the GetFolderFromPath function in the Global Code section and restarted the server.
I usually log on to the server for the BP testing in two ways:
1. I sign in to Windows with my Active Directory account and the Outlook profile is setup with my business email address
2. I sign in to Windows with the bot account and the Outlook profile is setup with the bot account email address
The only difference between the two email addresses is - as far as I know - that my own mailbox, as well as our testing Functional Mailbox ("DE- *** RPA DEV") were migrated to Exchange Online while the testing bot account was not, since we found that the actions of MS Outlook VBO v.6.10.7 for sending, moving and getting emails suddenly failed after the migration.
After the two lines were added in the Global Code section, I can move the emails from the inbox of the shared box mentioned above to one of its subfolders by the action Move Item with the bot account now. But I still get the "operation failed" error with my AD account for Windows and my business mailbox for Outlook.

On the other hand, I tested further the action Get Items in Folder. All the paths (\\DE- ***DEV\Inbox\testVBO\testVBO1, 2, 3, 4, 5) are correct which were proved by the action Move Item.
I can get the emails from testVBO1 eg. with my AD account for Windows and my business mailbox for Outlook. But I got one of the following errors with the bot account instead while testing:
The RPC server should be the current running server. I saw no errors on it with my AD account or the bot account. Other Outlook VBO actions such as Send Mail worked.

I'm not sure whether all the strange behaviors come from one single problem or whether my brief description made it a little bit clearer..

BR,
Yini

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

ewilson — Fri, 30 Dec 2022 14:17:57 GMT

@Yini Zhang,

Given that this started after the migration of your accounts to Exchange Online, I'd suggest checking the status of the Use Cached Exchange Mode and Download shared folders options for each account again. I know you said they're enabled, but just verify that they are enabled for your business account and not just the bot account. That's the only thing I can think of that would cause issues with getting access to folders.

If they are enabled try disabling and restart Outlook. Then re-enable them and try again. If that doesn't solve the issue, you may need to consider looking at the Microsoft 365 connector for Outlook. It uses the Microsoft Graph API to work with Exchange online instead of trying to work through the local Outlook instance.

Cheers,
Eric

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

YiniZhang — Wed, 11 Jan 2023 14:07:16 GMT

@ewilson Thank you Eric for your suggestion. You mean the one under Blue Prism Digital Exchange right?
Best Regards,
Yini

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

ewilson — Wed, 11 Jan 2023 16:46:49 GMT

Hi @Yini Zhang,

Yes, that is correct.

Cheers,
Eric

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

YiniZhang — Thu, 12 Jan 2023 10:06:36 GMT

@ewilson thank you, we will give it a try. If you have any other ideas about the issue, please write me at any time. Much appreciated.:)
BR,
Yini

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

abhi.sachdev_hcl — Fri, 07 Mar 2025 07:56:46 GMT

I tried this approach and downloaded the system.windows.forms.dll from internet and added it into the blueprism automate folder and referenced it in the above manner, but it is giving me error like messagebox not declared in code stage and system.windows.forms namesapce is not publically declared.

@ewilson,@YiniZhang - Can you help me on this one, can i share my errors in detail here.

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

ewilson — Fri, 07 Mar 2025 14:38:40 GMT

@abhi.sachdev_hcl if you have the .NET Framework installed on your machine you already have the System.Windows.Forms.dll installed on your machine. It's likely in you GAC (Global Assembly Cache).

The error you're getting means you've missed something in the declaration of the DLL and Namespace in the Global Options settings. Can you post a screenshot of your definition?

Cheers,
Eric

Re: Still "operation failed: An object could not be found" issue with Outlook VBO 10.2.2

abhi.sachdev_hcl — Fri, 07 Mar 2025 15:34:41 GMT

@ewilson - Thank you for your response. I tried again with carefully checking my inputs and it worked. I was able to debug code with MessageBox.Show(). thanks!