Hi All,
I am migrating to 2024.1 from 2022.2, we have a bpm that uses auto print function and generates a bartender file in epicordata folder.
When I use the bpm in 2024.1 and try to generate the file, I am getting the below error? Is this an access issue?
Failed to launch task to submit report. Error: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
---> System.UnauthorizedAccessException: You can only log on via single sign-on.
at Epicor.ServiceModel.Channels.ImplBase.CallWithCommunicationFailureRetry(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, RestRpcValueSerializer serializer) in C:\_releases\ICE\ICE4.3.100.0\Source\Shared\Framework\Epicor.ServiceModel\Channels\ImplBase.cs:line 1028
at Epicor.ServiceModel.Channels.ImplBase.CallWithMultistepBpmHandling(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy) in C:\_releases\ICE\ICE4.3.100.0\Source\Shared\Framework\Epicor.ServiceModel\Channels\ImplBase.cs:line 962
at Epicor.ServiceModel.Channels.ImplBase.Call(String methodName, ProxyValuesIn valuesIn, ProxyValuesOut valuesOut, Boolean useSparseCopy) in C:\_releases\ICE\ICE4.3.100.0\Source\Shared\Framework\Epicor.ServiceModel\Channels\ImplBase.cs:line 941
at Ice.Proxy.Lib.RunTaskImpl.RunSubTask(String subTaskAssemblyName, List`1 taskParameters) in C:\_releases\ICE\ICE4.3.100.0\Source\Shared\Contracts\Lib\RunTask\RunTaskProxy.cs:line 43
at InvokeStub_RunTaskImpl.RunSubTask(Object, Span`1)
at System.Reflection.MethodBaseInvoker.InvokeWithFewArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
--- End of inner exception stack trace ---
at System.Reflection.MethodBaseInvoker.InvokeWithFewArgs(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)
at Ice.Hosting.RunTaskHelper.RunSubTask(ImplBase runTaskImpl, String subTaskAssemblyName, List`1 taskParameters) in C:\_releases\ICE\ICE4.3.100.6\Source\Server\Framework\Epicor.Ice\Hosting\TaskCaller\RunTaskHelper.cs:line 42
at Ice.Hosting.SubTaskLauncher.CallTaskInternal(String sysUserId, String sysUserPassword, String subTaskAssemblyName, List`1 parameters, TimeSpan operationTimeout) in C:\_releases\ICE\ICE4.3.100.6\Source\Server\Framework\Epicor.Ice\Hosting\TaskCaller\SubTaskLauncher.cs:line 82
at Ice.Hosting.SubTaskLauncher.CallTask(String sysUserId, String sysUserPassword, String subTaskAssemblyName, List`1 parameters) in C:\_releases\ICE\ICE4.3.100.6\Source\Server\Framework\Epicor.Ice\Hosting\TaskCaller\SubTaskLauncher.cs:line 55
at Ice.Lib.AutoPrint.SubmitImmediateAutoPrintReport.RunSubTask(SubTaskLauncher subTaskLauncher, String sysUserName, String password, List`1 parameters) in C:\_releases\ICE\ICE4.3.100.0\Source\Server\Internal\Lib\BAM\AutoPrint\SubmitImmediateAutoPrintReport.cs:line 154
at Ice.Lib.AutoPrint.SubmitImmediateAutoPrintReport.<>c__DisplayClass3_0.<RunImmediateSysTaskAsync>b__0() in C:\_releases\ICE\ICE4.3.100.0\Source\Server\Internal\Lib\BAM\AutoPrint\SubmitImmediateAutoPrintReport.cs:line 113
This seems odd.
I would say there is s problem with your task agent/system agent account. Do other print jobs work?
Pretty sure there is a KB article for this error on Epicare … Not in front of a proper computer to dig it up, sorry.
Yes, if I want to generate a print preview for packslip using customer shipment entry I can.
Also, we have the same bpm method on closing the packing slip to generate the preview, that doesn’t work either and has the same error.
Are you making rest calls in your BPMs?
humour me and check your system agent account in Epicor, and also check if the auto print is set to immediate or queued.
I would ensure that whatever accounts are being used to drive the process do not have this checked off on their User Account.
the system agent has the below has same credential used to deploy the app server and the auto print is to immediate, the same used in 2022.1 where it generates the file.
It is unchecked on the account used for the process.
Sorry, incorrect information.
I had tried unchecking it before. In 2022.1, the service account is set to checked.
Now, in this one if I uncheck in on the account and initiate the label generation, it goes in active task and stay at “Rendering report” status.
That is unsual… Can you set the autoprint to Queued?
I’ll try, do you want me enable SSO on the User account maintenance?
If that does not work then.
I’d be inclined on the app server to login as the account that uses system agent. Delete your Task agent and reinstall it… This way you ensure it is running as SSO as well.
Getting late here so I’ll have to leave you in the hands of other Printing Devotees to assist. Don’t forget you also have Epicor support.
reinstalling the task agent now.
any other details other than rendering report?
Is there a Company level setting for SSO?
I don’t think so. Do you know where to check?