Pega Automation unable to Open Outlook and Automation getting stopped
Hi All,
We have an Automation running in a VDI 24/7 and we uses outlook in our automation.
As part of Automation, we have used outlook connector and other outlook components like Outlook.open(), outlook.close() complonents in pega studio while coding.
So as part of automatio, There will be a restart of outlook happens once it reaches a specific Threshold but out automation is successfully closing the outlook but unable to open the outlook and a error message is getting triggered and restart is not getting success and Automation is getting stopped.
I have attached the Error Screenshot.
Kindly check and suggest any workaround to be performed in VDI or the root cause of this Scenario.
Pegasystems Inc.
US
Ford Motor Company Ltd
IN
@ThomasSasnett Yes You are correct, we are restarting outlook based on the amount of emails automation is reading. Since our automation is 24x7 when left outlook running continuosly, we are getting a memory exception, to avoid that we made the changes in code in such a way that outlook gets restarted automation once it reaches a specific threshold. But after multiple successfull restarts, Recently we are facing this, Outlook is getting closed and Not opening and getting the above Error.
Pegasystems Inc.
US
@rahulk99 The Outlook connector will connect to a running instance of Outlook. You can use a Process component on the Toolbox to start Outlook directly.
Ford Motor Company Ltd
IN
@jeffbadger Yes , we are currenlty the using the same, Outook start and stop components from toolbox. but still facing some times Automation is not able to open and throwing the Errors
Pegasystems Inc.
US
@rahulk99 Jeff was suggesting that instead of starting and stopping Outlook itself, you use the static method Process.Start to launch Outlook.exe and then use the connector from the Toolbox to connect to that. This way, you're not constantly starting and stopping the Outlook process.
To add the Process.Start method to your Toolbox;
- Right-click on your Toolbox
- Select "Choose items..."
- Select the "Pega Robot Static Members" tab
- Select the "From Global Assembly Cache" radio button
- Select the "System" assembly
- Locate the Process node and expand it
- Find the "Start" method and select the checkbox
- Click OK
- You can now drag the Start method to an automation to launch a process
@rahulk99Please correct me if I am wrong, but it sounds like this error appears after several restarts of Outlook as opposed to not working at all on a given machine. Is this correct?
If that is correct, how often are you restarting your Outlook application in your automation? I have seen issues with Office applications when you restart them too many times with restarting the machine itself. Is it possible to leave Outlook running rather than restart it?