Resolve "Invalid Request" when submitting End of Day manifest for carriers POS and POM via PDX in SendSuite Xpress or Ascent

Products affected: SendSuite® Xpress, Ascent™

Issue

When performing End of Day for carriers  POS or POM after changing from FTP to Postal Data Exchange (PDX) transmission in SendSuite® Xpress or Ascent™, one of the following errors is displayed:

Error #1:
Invalid Request '

<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1.0"
                http-equiv="Content-Type" content="text/html
charset=UTF-8">
<!--Bootstrap-->
<link href="/resources/css/bootstrap.min.css"
                rel="stylesheet" media="screen">
<link href="/resources/css/dataTables.bootstrap.css"
               rel="stylesheet" media="screen">
<link href="/resources/css/jquery.fileupload.css"
               rel="stylesheet" media="screen">
<link href="/resources/css/jquery.fileupload-ui.css"
               rel="stylesheet" media="screen">
<link href="/resources/css/datepicker3.css"
               rel="stylesheet" media="screen">
<link href="/resources/css/application.css"
               rel="stylesheet" media="screen">
<meta http-equiv="X-UA-Compatible" content="IE=Edge" />
<!-- HTML5 shim and Respond.js IE8 support of HTML5 elements and media
queries -->
<!--[if lt IE 9]>
   <script src="/resources/js/html5shiv.js"></script>
   <script src="/resou.
Error #2:
Invalid Request: '<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN"     "https://www.w3.org/TR/html4/loose.dtd"><html><!--
Large comment due to IE8 bug not accepting content in 500 return code under a 
certain content length
--><!--........................................................................
...............................................................................
...............................................................................
......................................................-->
<head>                  <meta http-equiv="content-type" content="text/html
charset=UTF-8">                     <title>Authentication failed</title>
<style type="text/css">                            #kerberos_page {
                           font-family: sans-serif
                                           width:    600.

Error #3:
Invalid Request: 'Error 400: Error 400: There are no files matching the specified
criteria. Please modify selected criteria and try again.
'..
Error #4:
Invalid Request: '<HTML><HEAD>
<TITLE>Access Denied</TITLE>
</HEAD>
<BODY>
<FONT face="Helvetica">
<big><strong></strong></big><BR>
</FONT>
<blockquote>
<TABLE border=0 cellPadding=1 width="80%">
<TR><TD>
<FONT face="Helvetica">
<big>Access Denied (authentication_failed)</big>
<BR>
<BR>
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
Your credentials could not be authenticated: "Credentials are missing.". You will not be permitted access until your credentials can be verified.
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica">
This is typically caused by an incorrect username and/or password, but could also be caused by network problems.
</FONT>
</TD></TR>
<TR><TD>
<FONT face="Helvetica" SIZE=2>
<BR>
For assistance, contact your network support team.
</FONT>
</TD></TR>
</TABLE>
</blockquote>
</FONT>
</BODY></HTML>
'   at PBI.PBDS.USPS.FileTransfer.UploadProcess(XDocument xRequest)
   at PBI.PBDS.USPS.USPSAPI.Process(String request, String& response)

 

Cause

  • Error #1: The sign in information that was used for PDX submission does not have the PDX service granted on the account at the USPS Business Customer Gateway site.
  • Error #2: Access to pdx.usps.com is being blocked by a network device, firewall, anti-virus program, proxy server, or content filter.
  • Error #3: The program has become corrupted.
  • Error #4: Proxy settings are blocking communication.

Resolution

UPDATED: August 30, 2017
Error #1:
  1. Sign in to the USPS Business Customer Gateway with the username that was used for PDX submission.
  2. On the left side, select Shipping Services.
  3. Scroll down until you see Postal Data Exchange (PDX). To the right will be displayed either Go to Service or Get Access. Because this error usually occurs when you do not have access, you will most likely see the Get Access option.
  4. Select Get Access:
    • If you are a Business System Administrator, you will be given access right away. Once access is given, attempt to resubmit the manifest to USPS.
    • If you are a Basic User, you will be advised that you are emailing the Business System Administrator so that they can provide you with access. Once the access is provided, attempt to resubmit the manifest to USPS.

Error #2:

Contact your IT department for assistance in determining what may be blocking access to pdx.usps.com.  As soon as that site is unblocked, the error will go away and you files should transmit.


Error #3:
  1. Close any open SendSuite Xpress or Ascent programs.
  2. Go to Start > Control Panel > Programs and Features (Uninstall a Program).
  3. Right-click on PBI - PBDS USPS Component and select Uninstall. Follow the prompts to uninstall the program.
  4. Close the Control Panel.
  5. Go to Start > Computer.
  6. Browse to the USPS folder:
    • SendSuite Xpress: C:\Xpress\NetSetup\USPS (default path)
    • Ascent: C:\Ascent\NetSetup\USPS (default path)
  7. Right-click on pbi.pbds.usps and select to Run as administrator. Follow the prompts to install the program.
  8. Once program is installed, open Xpress or Ascent processing.
  9. Go to Reports > Archived Reports.
  10. Select the Source button in the lower right.
  11. Select the POS/POM carrier line, then select OK.
  12. Once the screen loads, select any file in the window and the select the Get button at the bottom.
  • If no errors are received, issues is resolved and you can close the Archive Reports window.
  • If an error appears, contact client support for assistance.

Error #4:

Contact your IT department for assistance in configuring or removing the proxy settings that may be blocking access to pdx.usps.com. As soon as that is resolved, the error will no longer occur and your files should be transmitted.