nep
2009-01-22 15:46:01 UTC
I wish to generate a PDF file on disk - I am using the standard Axapta PDF
engine which in this case is good enough.
For testpurpose I have changed the standard report 'CustBaseData' to include
the companylogo in the header. When prompted I select the print-medium
"File", an UNC path as file-name and the file-formata 'PDF'.
When I run this report from the client it works fine!
However when I submit it to batch the batchengine fails with this error:
The server-side impersonated (RunAs) session tried to invoke a method that
is available for client-side processing only.
(S)\Classes\PDFViewer\writeBitmap - line 47
(S)\Classes\ReportOutputUser\writeField
(S)\Classes\ReportOutputUser\printViaClass
If I remove the companylogo it works fine again.
The "funny thing" is that if I print e.g. a sales order confirmation with
the same setup it works fine printing the logo.
Is seems to me that the class PDFViewer has some issues handling things on
the AOS - maybe due to use of the WinAPI class. I have considering changing
this to use the WinAPIServer class - but that does not explain how (and why)
the sales form letter class works?!
I am puzzled - anyone got an idea?
engine which in this case is good enough.
For testpurpose I have changed the standard report 'CustBaseData' to include
the companylogo in the header. When prompted I select the print-medium
"File", an UNC path as file-name and the file-formata 'PDF'.
When I run this report from the client it works fine!
However when I submit it to batch the batchengine fails with this error:
The server-side impersonated (RunAs) session tried to invoke a method that
is available for client-side processing only.
(S)\Classes\PDFViewer\writeBitmap - line 47
(S)\Classes\ReportOutputUser\writeField
(S)\Classes\ReportOutputUser\printViaClass
If I remove the companylogo it works fine again.
The "funny thing" is that if I print e.g. a sales order confirmation with
the same setup it works fine printing the logo.
Is seems to me that the class PDFViewer has some issues handling things on
the AOS - maybe due to use of the WinAPI class. I have considering changing
this to use the WinAPIServer class - but that does not explain how (and why)
the sales form letter class works?!
I am puzzled - anyone got an idea?
--
Regards
nep
Regards
nep