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
- PaperCut MF - New SSL certificate (macOS)
- New KB article template
- Xerox embedded devices - Incorrect login screen issues
- Handling hidden characters in card numbers
- Scan to multiple email destinations
- PaperCut NG/MF Security Bulletin (March 2026)
- PaperCut Hive and Pocket Compatibility Tool
- Enabling ARM64 support in PaperCut NG/MF Print Deploy
- Incorrect stapling when printing multiple copies via a Find-Me queue using HP PCL drivers
- Resetting the PaperCut Hive or Pocket app (Android & iOS)
Comments
0 comments
Please sign in to leave a comment.