Error - Process Start Failure for unattendend Robot

General
, , ,
1

Hi,

For Unattended robots, when adapter fails to start within given timeframe, Process Start Failure message shows which require manual intervention.

I had decompile the OpenSpan.Adapters.Windows dll, i found below method as culprit:

protected bool ShowStartTimeoutDialog(string name)

{

DialogResult dialogResult;

try

{

dialogResult = ((Target)this).get_NotificationService().ShowMessage($“The process {name} failed to start within the given timeframe. Continue waiting?”, “Process Start Failure”, MessageBoxButtons.YesNo, DialogResult.No);

}

catch (NullReferenceException)

{

Diagnostic.TraceWarning(TraceCategory.ADAPTERS, “WindowsProcess.ShowStartTimeoutDialog: NotificationService is null - Designer may have been closed while waiting for a process to start.”);

throw new ProcessStartTimeoutException($“The process {name} failed to start within the given timeframe.”);

}

if (dialogResult == DialogResult.No)

{

throw new ProcessStartTimeoutException($“The process {name} failed to start within the given timeframe.”);

}

return true;

}

I have tried to turned off all Diagnostic for runtime as well as studio, but no luck.

Either I have to modify dll code (Which is not possible at this time) OR I have to set notification service turned OFF (which either I’m not able to)

Can someone help me to get rid of this?

2

Hi @PushkarS

Did you try to set SuppressNotifications and SuppressAdapterExceptions paramteres in RuntimeConfig.xml to True?

SuppressNotifications — Determines whether Runtime suppresses messages to the notification service. If set to True, adapter exceptions are logged but not shown to the user. The default is False.

SuppressAdapterExceptions — The default is False. When set to False, the exceptions raised by adapters will be shown to the user. The user may then choose whether to stop Runtime or continue running. When True, adapter exceptions are logged but not shown to the user.

3

@Konstantin Serditov Yes I did. I have tried with both runtime config option but still no luck.

Problem is whenever this message shown, execution frozen until someone manually click on Yes/No option. In our case, Unattended robot are running on VM and cases are getting timed out due to this.

4

@PushkarS @KONSTANTIN In the CommonConfig file there is a setting available on the RobotManager key. It is named suppressNotificationsForRPA. This will suppress all popup dialogs when set to True and the RPA key is True as well.

If the timeout happens occasionally due to the machine being busy or network bandwidth issues, I would increase the StartTimeout as well. The default value is 10 seconds and that may not be enough in all situations.

5

@jeffbadger Thanks a lot. This setting solve the issue.

For reference, I have modified as below (In CommonConfig.xml):

<Server name=“RobotManager” baseURL=“xxxxxxxx” enabled=“True” proxyAddress=“” RPA=“True” authenticationType=“Basic” RPAServiceOperator=“xxxx” workgroup=“xxxx” robotName=“xxxx” suppressNotificationsForRPA=“true” />