Hi all,
I'm testing our PAHT set-up in Test right now, and when I try to Print Order in the client, I'm getting an error pop-up as well as a PAH Exception email.
The error pop-up in the client is a doozy and says:
Select Error: An error occurred in the Microsoft .NET Framework while trying to load assembly id 65564. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error:System.IO.FileLoadException: Could not load file or assembly 'tessiturasqlservices, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A)System.IO.FileLoadException: at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark
This is followed by a PAH Exception email that says:
Server was unable to process request. ---> System.Data.SqlClient.SqlException: Order is already locked by batch [batch no.]. Order [order no.] could not be locked.
After I close the error in the client and press Done on the order, I do receive the PAH tickets.
Has anyone seen this before?
thanks,
frannie
Hey Frances, I wonder how you went with this? I am trying to setup order confirmation emails to be sent when a purchase is made via box office. I'm also getting the same error message and not sure where to turn. Did you have any success? :(
Hello again, Aaron, et al,
I am now again receiving these PAH Exception error emails reading "Server was unable to process request. ---> System.Data.SqlClient.SqlException: Order is already locked by batch 78857".
I got this error on 8 orders over the last 3 days, 6 of which were Print at Home delivery method processed within our Call Center. It seems to happen the most often with these, but it also appeared on one order processed on the Web with a PAH method, and one processed in the Call Center with HABO as delivery.
For the 7 PAH orders, there are successfully generated tickets on the eTicket server in the templates drive. We haven't received any complaints from these customers about their not receiving tickets.
Has anyone determined cause of this?
In case anyone runs into this - the helpful Network folks confirmed for me that this shouldn't be of concern - it happens if the PAH service cycles through the orders with PAH delivery before they are closed. It will catch them on the next cycle and "print"/deliver them without issue.