Hi all,
Wanted to see if anyone could help shed some wisdom to what may hopefully be a simple solution.
We noticed that when we do a copy from our Live environment to our Test environment, our PDFs cease to generate/send from the Test environment. I do see these errors in our processing service logs, but not sure where to proceed to resolve. TessituraProcessingService|RunReportsScheduler||Error|There was an error getting queued requests. Error Message : <ErrorMessages xmlns:i="">www.w3.org/.../XMLSchema-instance"><ErrorMessage><Code i:nil="true" /><Description>There was an error validating credentials. Please check error logs for details.</Description><Details i:nil="true" /><ErrorPath i:nil="true" /></ErrorMessage></ErrorMessages>
TessituraProcessingService|ProcessingService|||Error|There was an error flushing incomplete requests.
I suppose my question is, what are the configuration points to check to ensure working PDF generation when copying from one environment to another? Safe to say our Live environment is working fine.. so I would assume it would do the same in the test environment?
Thanks,Allan
What version of Tessitura are you running? Self-hosted or RAMP? Are you on O365, Google, etc?
Either way, check your font settings.
Thanks, I will check. We are on 15.1.1 - Self Hosted using Google.
Gotcha.
We’re on O365 and had a bunch of problems with Tessitura recognizing it as a secure connection. We ended up having to set up our SMTP relay using a connector. I don’t know if there would be a difference between your test and live environments, but that would be something to compare as well.
Think I have seen a similar issue on my Live environment when I have been patching servers.It was caused by the Processing Service starting up before the REST API was fully up and running.Stopping and restarting the Processing service once the API was up fixed it.
If it isn't that the other thing to check is that the Tessitura account used by the processing service can log in to the Test Tessitura.
Mark
Hm thanks. I tried both, but no luck. I wonder if the errors from the report scheduler is somehow blocking PDFs from sending. Something must not be matching up from since in the test environment, I've removed all scheduled reports from the queue and it's still looking for them. *thinking face*
I figured out my issue. The machine location for the print server was reset after copy down. Needed to reassign it.