I was working on Uipath Upgrade for our existing projects. Suddenly from today morning, when im opening the projects its getting opened as below,
Error persists even after reinstalling Uipath Studio.
Additional Error Details:
19.10.4+Branch.support-v2019.10.Sha.fe819a658cad0585a64d2f8af94fad5c30b8d122
Cannot find resource named ‘ResourceToImageConverter’. Resource names are case sensitive.
Open Document Error: UiPath.Studio.Contracts.RecoverableException —> UiPath.Studio.Contracts.RecoverableException: The project ‘D:\Zurich_RPA_Processes\Claims Registration\Src\Claims Registration Loader\project.json’ could not be opened: Provide value on ‘System.Windows.StaticResourceExtension’ threw an exception… —> System.Windows.Markup.XamlParseException: Provide value on ‘System.Windows.StaticResourceExtension’ threw an exception. —> System.Exception: Cannot find resource named ‘ResourceToImageConverter’. Resource names are case sensitive.
at System.Windows.StaticResourceExtension.ProvideValueInternal(IServiceProvider serviceProvider, Boolean allowDeferredReference)
at System.Windows.StaticResourceExtension.ProvideValue(IServiceProvider serviceProvider)
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.CallProvideValue(MarkupExtension me, IServiceProvider serviceProvider)
— End of inner exception stack trace —
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator)
at UiPath.Studio.Plugin.Workflow.Toolbox.ToolboxControl.InitializeComponent()
at UiPath.Studio.Plugin.Workflow.Services.ToolboxWindowService.GetToolboxWindow()
at UiPath.Studio.Plugin.Workflow.Services.Interfaces.IToolboxWindowService.GetToolboxWindow()
at UiPath.Studio.Plugin.Workflow.Services.ToolboxWindowServiceProxy.GetToolboxWindow()
at UiPath.Studio.Plugin.Workflow.Toolbox.ActivitiesToolWindow.CreateControl()
at UiPath.Studio.Plugin.Workflow.Toolbox.ActivitiesToolWindow._toolboxWindowService_WindowCreated(Object sender, EventArgs e)
at UiPath.Studio.Plugin.Workflow.Services.ToolboxWindowServiceProxy.OnAfterConnectToInnerService()
at UiPath.Studio.Plugin.Workflow.Services.MarshalByRefServiceProxyBase1._appDomainController_ChildAppDomainCreated(Object sender, EventArgs e) at System.EventHandler.Invoke(Object sender, EventArgs e) at UiPath.Studio.Plugin.Workflow.Services.AppDomainController.OnChildAppDomainCreated() at UiPath.Studio.Plugin.Workflow.Services.AppDomainController.<SetupAppDomain>d__20.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at UiPath.Studio.Plugin.Workflow.Services.AppDomainController.<CreateAppDomain>d__18.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at UiPath.Studio.Plugin.Workflow.Project.Services.ProjectLoaderService.<CreateProjectAppDomain>d__27.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at UiPath.Studio.Plugin.Workflow.Shared.Project.BaseWorkflowProjectFactory.<OpenAsyncInternal>d__46.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at UiPath.Studio.Plugin.Workflow.Shared.Project.BaseWorkflowProjectFactory.<OpenAsync>d__45.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at UiPath.Studio.Core.Services.PersistableServiceBase3.d__19.MoveNext()
— End of inner exception stack trace —
at UiPath.Studio.Core.Services.PersistableServiceBase3.<OnOpenAsync>d__19.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at UiPath.Studio.Core.CommonServices.ProjectServiceBase.<OnOpenAsync>d__43.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at UiPath.Studio.Core.Services.PersistableServiceBase3.d__10.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UiPath.Studio.Core.CommonServices.OpenCloseCommandsService.d__26.MoveNext()
— End of inner exception stack trace —
at UiPath.Studio.Core.CommonServices.OpenCloseCommandsService.d__26.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UiPath.Studio.Core.CommonServices.OpenCloseCommandsService.d__19.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UiPath.Studio.Shell.ShellApplication.StudioShellApplication.d__17.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at UiPath.Studio.Shell.ShellApplication.StudioShellApplication.<>c__DisplayClass16_0.<b__0>d.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.b__6_0(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler), HResult -2146233088
This seems like an issue with an Enterprise version. Would you mind contacting our technical support at this link?
1 Like
Hi! This was as an identified issue, that is currently fixed in Studio 19.10.5. The issue was caused by unpinning the Properties and Outline panels, but leaving the Orchestrator Resources panel pinned, with multiple assets, queues and processes, then opening a project - the idea was to have the Resources panel upfront whenever the user opened a project. As a workaround - you can minimize and maximize Studio (using the not-so-visible) button, or upgrade to 19.10.5, where the issue is no longer present. Hope this helps! 
3 Likes
Thanks for your immediate response @coramia @loginerror
@coramia Yes, the workaround works. But will it have any impact when we run our process through Orchestrator?
1 Like
No, it has no functional impact on running the processes through Orchestrator. It’s a Studio UI issue.
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
Anil_G
supermanPunch
Jithesh_R
Suraj_B_Shetty
ushu
Manish540
ppr
vishal.kp
arjunshenoy
ptrobot