Hello Everyone. I trust you all had a nice Thanksgiving holiday. If not, head over to my place – we have plenty of turkey leftover!
Over the last several weeks, we have been working on setting up APR (Advanced Print Routing) so our SO Acknowledgement PDFs are emailed out. We think everything is setup properly, but we’re now getting an error message in the System Monitor indicating that the app pool is not setup for single sign-on. This is in fact true since the user “print” is not in our Active Directory. So I guess we need to know where to specify the login & password for the print engine to use.
I have tons of documentation detailing the project, but didn’t want to overwhelm you with unnecessary details. For now, I can tell you that we use a UD field to signal that the SO Acknowledgement should be sent out. There is an In-Process and a Standard Data Directive from OrderHed that checks the UD field (and other things), and enables the Std. DD which kicks off the Auto-Print. I’ve combed through the various settings and options within Report Style Maintenance and can’t find anything that would allow me to specify the login and password for user “print”.
Any thoughts and insights on this would be greatly appreciated. Thanks!
Hmm, I can’t think of a setup “error” that would only present problems when trying to email via APR… Do you get the error when using the email routing manually, or only when it triggers from your BPMs?
Anyways, here are the relevant setup screens that could provide some clues into what’s gone wrong in your system:
Thanks so much for the comprehensive response, Tom. I went through all the screenshots, and didn’t see anything that was seriously wrong. I will say that the error only shows up in the System Monitor when the email is being triggered from my BPM, so it has to be something I overlooked there.
Thanks for jumping in, Shizar. The SSRS Report Setup parameters appear to be correct (using Tom’s previous post as a reference). This is our very first report that will be processed via APR.
Failed to launch task to submit report. Error: System.ServiceModel.FaultException: MICROAIRE\erpdevapppool is not setup for single sign-on.
Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Ice.Contracts.RunTaskSvcContract.RunSubTask(String subTaskAssemblyName, List`1 taskParameters)
at Ice.Proxy.Lib.RunTaskImpl.RunSubTask(String subTaskAssemblyName, List`1 taskParameters) in C:\_Releases\ICE\ICE3.2.700.0\Source\Shared\Contracts\Lib\RunTask\RunTaskImpl.cs:line 66
at System.Dynamic.UpdateDelegates.UpdateAndExecuteVoid3[T0,T1,T2](CallSite site, T0 arg0, T1 arg1, T2 arg2)
at Ice.Hosting.SubTaskLauncher.CallTaskInternal(String sysUserId, String sysUserPassword, String subTaskAssemblyName, List`1 parameters, TimeSpan operationTime) in C:\_releases\ICE\ICE3.2.700.6\Source\Framework\Epicor.Ice\Hosting\TaskCaller\SubTaskLauncher.cs:line 72
at Ice.Lib.AutoPrint.SubmitImmediateAutoPrintReport.RunSubTask(SubTaskLauncher subTaskLauncher, String sysUserName, String password, List`1 parameters) in C:\_Releases\ICE\ICE3.2.700.0\Source\Server\Internal\Lib\BAM\AutoPrint\SubmitImmediateAutoPrintReport.cs:line 155
at Ice.Lib.AutoPrint.SubmitImmediateAutoPrintReport.<>c__DisplayClass3_0.<RunImmediateSysTaskAsync>b__0() in C:\_Releases\ICE\ICE3.2.700.0\Source\Server\Internal\Lib\BAM\AutoPrint\SubmitImmediateAutoPrintReport.cs:line 113
Thanks everyone for all your help. We were missing the erpdevapppool user (which is in the Active Directory), and needed to populate that into User Account Maintenance. Once that was done, I was able to see the null reference error which I saw two weeks ago, and to fix that, we needed to set the Auto-Print Report Parameter OrderNum to ttOrderHed.OrderNum.