Skip to main content

FATAL ERROR EVL2203: Found excluded US-ASCII character '20' in URI

Article # 3036708 - Page views: 29


From Designer for Windows an interactive document, that uses an XMLFile DID, is created using ComposerUI for J2EE. In the file upload dialog, after clicking on Ok to submit the data file, the following error is given:

ITPLOG: FATAL ERROR EVL2203: Found excluded US-ASCII character '20' in URI C:\Program Files\Apache Software Foundation\Tomcat 9.0\instance-CCMRuntime-5.3\work\Catalina\localhost\onl_core_01\C33AD4ADAF9C799636A7AD1DE85972B1\upl7438050452307287075.dat. These characters should be escaped by %.
Fatal error.
Throwing error message "<itp:code>itp.Fatal</itp:code><itp:reason><![CDATA[Dec  3 10:48:17.998[0] [C33AD4ADAF9C799636A7AD1DE85972B1]: Fatal error.


This error occurs if the Composer for J2EE session is not fully initialised. This happens when the session not started with modelbegin.jsp, but with runmodel.

Another possibility is that the session cookie is blocked by the Internet Browser. The used Internet Browser must accept session cookies. Without session cookies ComposerUI for J2EE cannot function correctly.


Verify the URL

When testing from Designer for Windows, the correct URL is:


An example of an incorrect URL using runmodel is (do not use this URL):



Session cookie is blocked

To check if the session cookie (JSESSIONID) is blocked, the developer tools of the used Internet Browser can be consulted. 

  1. Test the document from Designer for Windows.
  2. The ComposerUI for J2EE session is opened in the used internet browser. 
  3. Copy the URL to notepad.
  4. Change runmodel in the copied URL to modelbegin.jsp. E.g.


  1. Open Google Chrome.
  2. Open the developer tools (shortcut is F12) and change to the tab Network (in the developer tools).
  3. Paste the URL from step 4 (with modelbegin.jsp) and visit the URL.
  4. In the developer tools, click on the "modelbegin.jsp?....", this will result in an additional pane being displayed. Check in the Response Headers if the Set-Cookie works. If the cookie is blocked, Chrome will display an exclamation mark.
  5. If the cookie is blocked, contact your system administrator. Chrome is possibly configured by IT not to accept session cookies. 

This is an example of a working situation. If the cookie was blocked, the exclamation mark would be shown behind the "Set-Cookie:....;HttpOnly" line.

Set-Cookie in developer tools
A workaround for Google Chrome is to use the IP address instead of the hostname. E.g. if the IP address of the KCM server is


Level of Complexity 



Applies to  

Product Version Build Environment Hardware
Kofax Communications Manager 5.3 (should apply to all versions) n/a A different Internet Browser than Internet Explorer is used. n/a


  • Was this article helpful?