"Invalid EBX-Version from client: not sent" error is probably a proxy server problem.

Issue
Server-Code 400
400 Bad Request
Invalid EBX-Version from client: not sent

Solution
The ebx version is sent in a custom header, so the last line above provides a clue to the problem:

The fact that the server says that it's a Bad Request means that something is wrong between the client and the server. Most likely, the Adobe custom HTTP headers are being stripped off somewhere between the end user's machine and the fulfillment server--most likely by a Proxy Server.

The network administrator will have to look at the settings in their proxy server and/or the proxy server logs (or maybe a firewall) and see what setting is blocking Reader's custom headers.

This will involve detective work on the part of the network administrator. The only instruction to the network admin would be that it appears that something on your network--probably a proxy server (firewall maybe) is blocking/caching Reader's custom HTTP headers.

Here's the list of all the HTTP headers we use--open them for both directions. The ports are the standard http ports. (We don't use SSL.)

x-EBX-Version
x-ABX-Client
x-EBX-Authenticate
x-EBX-Authorization
x-EBX-Authenticationinfo
x-EBX-Authinfo2
---------
SOAPAction
Accept-Language
accept
Connection
Pragma
Cache-Control

Was this Knowledgebase document helpful? Yes  No