Skip to main content

OpenPrinter_1: rc:0 lastError:1801(0x709) The printer name is invalid In Axapta 2009

By
When I open  the report getting the below in Dynamics AX 2009
Error message as below:
"OpenPrinter_1: rc:0 lastError:1801(0x709) The printer name is invalid."

Actually 2 places we need to Change


First Place:

      Classes->RunBaseReportDialog->main() 

static void main(Args args)
{
    RunBaseReportDialog     reportDialog    = new RunBaseReportDialog(args.caller());
    RunBaseReport           runBaseReport   = args.caller().runbase();
    ReportRun               reportRun       = runBaseReport.reportRun();
    Report                  report          = reportRun.report();
    boolean                 oldInteractive;
    boolean                 res;
    Dialog                  dialog;
;

    oldInteractive = report.interactive();
    report.interactive(true);

    //res = reportRun.prompt();   //removed
    res = reportDialog.prompt();  //Added 

    report.interactive(oldInteractive);
    if (!res)
        return;

    dialog = Dialog::getDialogFromCaller(args.caller());
    if (dialog)
    {
        dialog.updateServer();
    }
    runBaseReport.dialogUpdatePrinterSettings(dialog);
    reportDialog.run();
}
Second One:

Change the report design Property  orientation:Auto


Happy Daxing....:)


Comments

  1. Rudi HansenNovember 26, 2013 at 7:31 AM

    I am still getting the same error after making your correction.
    Any further ideas?

    ReplyDelete
  2. AnonymousDecember 13, 2013 at 4:24 PM

    We tried this as well and no luck.
    We have few citrix servers and error appears in two of them, but there might be differences depending on the user.
    We are using AX2009.

    Any ideas?

    ReplyDelete

Post a Comment

Popular posts from this blog

Using File path on a form getting Error in Axapta

By
Hi Folks, After a long time am coming  back to posting few new things here for AX Developer... When we want to select the file path in form level. Normally what we will do create one EDT and extends with filepath (EDT), but that time when you are trying to select the path we will get error like stack-trace/Error message .Don’t worry there is no problem with your ax application. Simple we need to provide the method to the form like filepathLookUpTitle (). Below method we need to add it into form level methods, i.e. str filePathLookupTitle() {     return "Select document folder"; } Thanks Happy Daxing....
20 comments
Read more

Convert word Documents into PDF report [using X++ in Dynamics AX 2009]

By
Hi Friends, This is the way we can convert word format report into PDF in ax2009 static void dsiple_PDS(Args _args) {     Args args;     ReportRun rr;     str reportName = "ReportName";     PurchRFQLine rfqLineTable;     str myPath;     str pdfFileName;     int i;     COM wordApplication;     COM wordDocuments;     COM wordDocument;     COM wordRange;     str a[];     str path;     str pdfPath;     str finalPath;     int length;     int minus;     ;     i = 1;     myPath = winApi::getTempPath();     info(myPath);     args = new Args(reportName);     args.caller(rr);     //rr =...
1 comment
Read more

AIF (Endpoint) Error : The user is not authorized to perform this action.

By
"The user is not authorized to perform this action."  We started getting this error message in our AX 2009 System, when ever we try to consume an XML file using an  Endpoint   thru a  File System  Channel to create a  Sales Order. We did not made any code changes / setup changes, but all of the sudden started getting this error. Solutions : 1. Validate the "SourceEndpointUser". in inbound XML  The User ID should be a valid user Id in DAX, in GNS Active Directory and the "\" should be back slash in the XML file or where you use this combination in entire process or setup. ex : Domain \ User Id. In our case when we had the above error, the SourceEndPointUser user id was deleted from the Active Directory in GNS, so we added it back to Active Directory then it solved the problem. NOTE : If nothing wrong with the User ID, try to add the user id in "Users" tab in Endpoints form for that End Point used by the process. 2. Verify th...
1 comment
Read more