Q My Windows Secondary Print Provider fails to connect to the Application Server and I get the following error message in the Print Provider log:
Sep 02 12:24:41 DEBUG: Error initiating connection - The requested address is not valid in its context. (Error: 10049) [3116] Sep 02 12:24:41 DEBUG: unable to establish TCP connection [3116] What can I do?
This can mean that the Application Server hostname is having trouble being resolved to an ip address (i.e. a DNS issue). It would be worth trying an ip address for the Application Server instead of hostname by updating the configuration file of
[app-path]/providers/print/win/print-provider.conf:
ApplicationServer=[the server's IP address] -–
Articles in this section
- Print Deploy for VDI Best Practices
- Biometric Hardware Support
- System Maintenance August 2024
- End User Support and Resources
- Branch Office Direct Printing
- Using SSL Packet Inspection (Man-in-the-Middle) with PaperCut NG/MF
- Xerox Embedded Troubleshooting
- Important points to know about PaperCut MF version 24
- Setting up application consent in Microsoft Azure for Scan to Microsoft OneDrive and SharePoint Online
- PaperCut NG/MF Security Bulletin (May 2024)
Comments
0 comments
Please sign in to leave a comment.