Print Management Error when running in Batch

(0) Share

Report

Posted on by FAC.Ansel

1,632

I can successfully use Print Management to print/e-mail Sales Order Invoices when I do NOT run as a batch.

But if I enable batch, then SOME of the records will send successfully (both print and/or e-mail) but will fail part way through with the following error message:

6886.Invoice-Error.jpg

ANY suggestions or thoughts, no matter how crazy they may sound are welcomed at this point. Here is some general information about the setup:

-AX 2012 R3 CU 8

-3 AOS's using RD web access for client connection

Things I have tried:

- Running the batch on different AOS's

- Running the batch with only 1 thread (eliminating multithreading)

- Running the batch at different times

- Running the batch without also posting the invoices (using Print Management after invoice posting)

- Running in a Dev and Test environment restored from Production (These run successfully)

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

Mea_ 60,284 on at

Like (0)

Report

Hi Ansel Slagle,

You have custom report, so probably error is caused by code inside of it. Easiest way to find it is to debug. Did you try ?

Was this reply helpful? Yes No
Rizwan Ahmed 200 on at

Like (1)

Report

Hi,

Have you checked logs for the SSRS? There might be more information there in the time when you are getting these errors. I assume that these are not constantly coming on the same document (invoice etc ...)

You can find log locations and details at following link:

https://technet.microsoft.com/en-us/library/cc512029.aspx

See what you find there...

Thanks,

Rizwan

Was this reply helpful? Yes No
FAC.Ansel 1,632 on at

Like (0)

Report

ievgen - Thanks for the suggestion. The issue is only happening in Production, which does not have debugger turned on. The invoice report has been customized, but the odd thing is that it works just fine when not run in Batch and will print roughly 40 out of 100 invoices in the batch before it fails.

Was this reply helpful? Yes No
FAC.Ansel 1,632 on at

Like (0)

Report

Rizwan, I have checked the logs and the message there is just as vague and unhelpful as the one I get in AX. I will go back and take a look again, maybe I missed something the first time I looked through the log. The issue is actually only with the Invoice, as far as I can tell. We are using print management for the packing slip (print and e-mail) as well and that appears to be working just fine.

Was this reply helpful? Yes No
Mea_ 60,284 on at

Like (0)

Report

HI Ansel Slagle,

If you say that it does not work in batch that could be connected to CIL. Do you have CIL fully build on all AOSes (if you have more than one) without errors ?

Are you printing this report to file ? Maybe you have file path not accessible from AOS or you use not valid email to email it out ?

Was this reply helpful? Yes No
Martin Dráb 237,970 Most Valuable Professional on at

Like (0)

Report
If you look into code (because the call stack tells you exactly which line is throwing the error, you'll see two things:

The error intentionally isn't thrown in client sessions, which may explain why you see different behavior in client and batch.

It doesn't provide any error message, because it claims that "the infolog will already contain the actual error message from the source of the error". Review the infolog once more; maybe you missed some other message. Or maybe the assumption is incorrect.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

,I just had what I think is the same issue.

Using print management while running statements in batch, the job failed. The info log error was similar to yours. I tracked it down to a specific customer that was problematic using a production debugging backdoor (I know "don't debug in production"). Anyhow, I tried running this customer statement in UAT, but not in batch and with print management turned on. No issues. When I submitted it to batch, it erred. I debugged in UAT down to the email being sent and the print management settings that drive the emails for that customer. It turns out the CC email address had a ";" appended to it. Removing the ";" on the email address produced positive results.

Ultimately the invalid character message did not get propagated up the call chain to the user and wasn't handled gracefully to allow the process to continue printing statements for other customers. Now I'm off to find a hotfix???

Was this reply helpful? Yes No