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
- How to remove a print job from the queue
- Upgrading the PaperCut Hive Ricoh Full Embedded App
- Share ARM64 Drivers from Windows Print Servers
- Printing from Microsoft Edge Browser and other Windows 10 and 11 Store Apps
- Top 10 best practices for implementing Print Quotas in education
- PaperCut Hive and SentinelOne
- Troubleshooting Mobility Print and Lightspeed
- Troubleshooting PaperCut Pocket & Hive Login
- Smooth MFD Upgrades: A Step-by-Step Guide
- PaperCut NG/MF Security Bulletin (December 2024)
Comments
0 comments
Please sign in to leave a comment.