PAS00108 error during web upload - c06350182
The error is related to the communication between CPS/PTS and the Status Server. This error is a very misleading one as it states in the browser "Account information is incorrect or you are not permitted to use this service" and generally people will start troubleshooting authentication when they see this.
The error details in our Server Message Reference document are different, but it is also more accurate:
PAS00108 Error received by license server, or unable to contact license server. Possible Causes: If reported independently, the Status Server is unable to contact the PrinterOn License Server, in these cases, the Status Server fails to launch. this is returned as the userMessageID in combination with a returnCodeReason for integrators. Users will receive a message that contains the returnCodeReason from PTS itself. If encountered by an integrator, the integration should review the returnCodeReason to determine the root cause of the issue. MessageID: PAS00108 MessageText: PAS00108: The service is temporarily unavailable.
What's actually happening is that the Status Server can't get to the PTS service to confirm the printer details in order to continue processing the job. This communication for PTS uses the Internal Service URL as defined in the license, and adds "/rest/ELMValidate" to the end. If you visit [internalServiceURL]/rest/ELMValidate (eg. https://printeron.printanywhere.com/cps/rest/ELMValidate) in a browser, it should return an XML response like ?return_code=ELM10000?svr_trans_ver=2.3.2?svr_sw_ver=4.0.0.6?user_msg=ELM10000: An error has occurred.?error_txt=ELM10000: A required value was not supplied or was invalid. (if you see a blank page, or an error, you'll need to view source on the page to confirm the XML response is shown).
Symptoms:
- No Job Reference number displayed in browser
-
Errors in Status Server logs can include:
-
"PTS transaction returned invalid format"
- This line will appear when logs are on default "Information setting"
-
"Did not receive a Job Reference ID from PTS on Validate"
- This line will appear when logs are on default "Information setting"
-
"Did not receive valid Job Reference ID after x tries, aborting"
- This will be shown 3 times and will appear when logs are on default "Information setting"
-
Could not contact PTS after 1 retries, retrying connection. HTTP status code: 200
- This will be shown up to 3 times and will appear when logs are on default "Information setting
-
<!DOCTYPE html><html><head><title>Apache Tomcat - Error report</title><style type="text/css">h1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} h2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} h3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} body {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} b {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} p {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;} a {color:black;} a.name {color:black;} .line {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP Status 404-/rest/ELMValidate<//u></p><p><b>type</b>Status report</p><p><b>message</b><u>/rest/ELMValidate</u></p><p><b>descrtion</b><u>The requested resource is not available</b></p><hr class="line"><h3>Apac30-11-2017 09:34:57:615 0x1924T10 Validate response failed to parse.
- This will be shown when logs are increased to "Trace" level
-
"PTS transaction returned invalid format"
Resolution:
- Adjust the license file to reflect the Service URL as https://[IP or DNS]/cps and the Internal Service URL as https://[IP or DNS]/cps (if all components are on the same server you can leave this as the loopback address)
- Validate your Service URL and Internal Serivce URL are correct as this communication
- Upload new license file to local server from the Licensing tab of the PrinterOn Configuration Manager
- Restart all services from the Services tab and then test again
- Change the LDAP profile to somewhere lower in the LDAP tree; closer to the user or where the user would be (possible that the LDAP server is just too big to search so the PrinterOn Enterprise solution times out)
- Confirm the LDAP profile has been configured with LDAP Referrals enabled (required in some environments)
NOTE:
Applies to PrinterOn Enterprise 3.x and later