Last night we had 11 Jobs Stopped in the Orchestrator.
- They were not stopped manually
- They had the same End Time and Start Time so they stopped immediately after starting
- There is no Info and no Logs generated
We checked Event Viewer on the Virtual Machine and at the same time when Job was stopped there was a Warning level event from the Orchestrator with the below message:
*UiPath.Executor 126.96.36.199 *
/Widths array is missed in font dictionary
We have an upgrade (to 2023.x) version planned for later this year but currently any support would be appreciated.
This situation typically points to a problem with the job execution itself or Orchestrator settings.
This is related to font dictionary issues in the context of UiPath. It’s often seen in the logs or Event Viewer when running UiPath processes.
This error typically indicates a problem with a font dictionary for a PDF document or another type of document being processed by a UiPath workflow.
When multiple jobs stop unexpectedly with the same start and end times, it indicates an issue that affected those jobs simultaneously
To investigate and resolve this issue, it’s important to look into Orchestrator logs, workflow logs, resource utilization, and any error messages to identify the root cause. If you’re unable to determine the cause of the abrupt job stops, I would recommend reaching out to UiPath Support for assistance on this as it should not disturb your other functionalities
Hope this clarifies
The problem is that this happened on various processes on the same VM - all of which worked before and are working after those “stopped” Jobs.
There are no logs to investigate as no logs were generated and the only Events on the machine during that time are the ones I posted “/Widths array is missed in font dictionary”. On the Orchestrator machine, on the other hand, the only Warning (there are no Errors) level log is:
Abp.Authorization.AbpAuthorizationException: Current user did not login to the application!
at UiPath.Orchestrator.Web.Authorization.UiAuthorizationHelper.AuthorizeAsync(IEnumerable`1 authorizeAttributes)
at Abp.Authorization.AuthorizationHelper.CheckPermissionsAsync(MethodInfo methodInfo, Type type)
at UiPath.Orchestrator.Web.Authorization.UiAuthorizationHelper.AuthorizeAsync(MethodInfo methodInfo, Type type)
at UiPath.Orchestrator.Web.Authorization.UiAuthorizationFilter.OnAuthorizationAsync(AuthorizationFilterContext context)Abp.Authorization.AbpAuthorizationException: Current user did not login to the application!
at async Task UiPath.Orchestrator.Web.Authorization.UiAuthorizationHelper.AuthorizeAsync(IEnumerable<IAbpAuthorizeAttribute> authorizeAttributes)
at async Task Abp.Authorization.AuthorizationHelper.CheckPermissionsAsync(MethodInfo methodInfo, Type type)
at async Task UiPath.Orchestrator.Web.Authorization.UiAuthorizationHelper.AuthorizeAsync(MethodInfo methodInfo, Type type)
at async Task UiPath.Orchestrator.Web.Authorization.UiAuthorizationFilter.OnAuthorizationAsync(AuthorizationFilterContext context)
As far as resource utilization goes - there were Unattended Robot licenses and runtimes available on the VM so Jobs should have been executed.
It looks like issue with user authentication or authorization at the time the jobs stopped.
I hope user accounts used to execute the jobs have the necessary permissions and roles assigned.
Yes, they do. As I mentioned the same Jobs on the same users successfully executed Jobs before and after this “accident”. The authorizations were also not changed.
Yeah the issue is with different users only na
Then we need to see whether those users have similar permissions isnt it