web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Invalid printer settings
Microsoft Dynamics AX (Archived)

Invalid printer settings

(1) ShareShare
ReportReport
Posted on by bankk 6,603

Hello.

I've had a reoccurring issue reported from a user who at the beginning of a work day while attempting to print a picking list would encounter this error.

"Settings to access printer '[printer]' are not valid."

I would clear their cache file and things would start printing again. The printer is on a valid print server and has been added to the terminal servers as well as on the AOS servers. The issue just surfaced over the last few days for one user. I don't want to get into a daily routine of having to clear his cache so i'm wondering if anyone knows of a potential cause / fix I can look into?

Thanks very much.

*This post is locked for comments

I have the same question (0)
  • Alexander.Dobinson Profile Picture
    Alexander.Dobinson 140 on at
    RE: Invalid printer settings

    Did you ever find a resolution to this issue, as we are having exactly the same issue and cant seem to get to the bottom of it?

    Thanks

    Alex

  • bankk Profile Picture
    bankk 6,603 on at
    RE: Invalid printer settings

    Unfortunately, not yet. Printing continues to be a issue for us in general. If you stumble across anything I'd appreciate an update. Thanks.

  • Community Member Profile Picture
    Community Member on at
    RE: Invalid printer settings

    We also continue to be plagued with printing issue is AX in regards to "Settings to access printers are invalid" but most of our issues appear to be focused on print management. We are currently running AX 2012 R2 CU6 and have applied several hotfixes to resolve things such as random client crashes and one in particular that was supposed to address the printing issue but appears to have made it worse. I would be happy to share our experience with the printing issues, but I'm also looking for a solution as well.

  • Suggested answer
    Umesh Pandit Profile Picture
    Umesh Pandit 9,315 User Group Leader on at
    RE: Invalid printer settings

    Hi, Check if this works for you.

    stackoverflow.com/.../error-settings-to-access-printer-printername-are-not-valid-when-printing-fro

  • Community Member Profile Picture
    Community Member on at
    RE: Invalid printer settings

    Although these may be good steps to try for the others, unfortunately we have been through both of these scenarios and are still getting the printing error. I have isolated our issue to either SSRS or the AOS during our testing due to the fact that either running our client from our terminal server or running it locally exhibits the exact same behavior. There seems to be an issue in the process of the initial creation of our sales orders and picking lists when running print management. It seems to hang at the instant where the print management engine passes the job to SSRS for processing.  We get a sales journal and can print using print management just fine from the journal, but the initial process that creates the journal and sends it to the printer always seems to fall down at the printing process and throws the "Settings to access printer error". Every other aspect of printing after that process runs works fine. and every other application other than AX prints fine as well.  

  • Community Member Profile Picture
    Community Member on at
    RE: Invalid printer settings

    The really odd thing is that our purchase orders have always printed fine through print management, which makes me wonder if it's a form problem?

  • bankk Profile Picture
    bankk 6,603 on at
    RE: Invalid printer settings

    Has anyone out there SUCCESSFULLY (and consistently) gotten printing to work with AX via Terminal Services? Please share how you've approached the printer setup.

    BTW, adding the printers on the AOS server(s) and configuration to use server printers on the client and server are optional, correct? We had terminal server setup with the printers and was it working (as well as can be expected) whether the AOS servers had them installed or not. I understand the benefit to setting up the client to use server printers was it saved the hop back to the client to print. In any case, we've set up server printing with no improvement (just more questions).

  • Community Member Profile Picture
    Community Member on at
    RE: Invalid printer settings

    KBanh to answer your question, yes adding printers to the AOS server is optional. Our setup is to assign the printers to the terminal server through group policy. Originally I had the printers setup to use printer redirection from the client and that worked for a while, then I set them up locally on the terminal server and that worked for a while and then I finally ended up assigning them to the terminal server through group policy and running a script that clears all the printer connections when the client logs on and group policy reassigns them automatically. In each case I still would eventually get the "Settings to access printer are invalid" when printing using print management and processing sales orders or picking and packing lists. This leads me to believe that it's not a client side issue, but either an AOS or SSRS problem.

    I'm curious, what version of Dynamics AX are you running?  

  • bankk Profile Picture
    bankk 6,603 on at
    RE: Invalid printer settings

    Hi...We're running DAX R2 CU7.

    Funny to read your response as it closely mirrors our own experiences with AX and printing.

  • Community Member Profile Picture
    Community Member on at
    RE: Invalid printer settings

    I could be wrong, but it's my understanding from our system integrators that print management passes the print job from AX to SSRS for processing. The SSRS server is the one that actually generates the print language (spools the job) and passes it on to the printer. In our environment there seems to be a disconnect between when the AX client releases the job to SSRS during the initial creation process. The job never prints and the AX client displays the "Settings to access printer are invalid" message in the info log. It's almost like AX releases the job to SSRS and waits for a response back from SSRS that it printed successfully. The SSRS server acts as though it never received the job and simply goes on its merry way. All subsequent jobs generated from the journal using print management work fine, which leads me to believe that the handshake (code) between AX and SSRS in the initial generation process is somehow broken.      

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Join experts in person to explore low code and AI agents at the Power Platform Community Conference sponsored by Microsoft

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Congratulations to the September Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Community Member Profile Picture

Community Member 4

#2
Guy Terry Profile Picture

Guy Terry 2 Moderator

#2
Nayyar Siddiqi Profile Picture

Nayyar Siddiqi 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans