JMX script loads in local JMeter but generates "Invalid chararacter was found" error or validation fails when uploaded

Products

• BlazeMeter

Issue/Introduction

Sometimes it may happen that an upload of a JMeter script to a Blazemeter test results in an error "Invalid Character was found in script" even though the script opens well in JMeter itself:

 

Or the script may just fail to be validated:

 

Environment

Blazemeter SaaS

Cause

Blazemeter is not (yet) capable of handling non ASCII characters as listed in http://www.asciitable.com/

Resolution

Open the script in your local JMeter and do a search for characters that don't match the ASCII table. Since ASCII characters are in the range of hexadecimal 00 - 7F, look for any characters outside that range and make sure to check the Regular Exp. checkbox:



Once found, get rid of all non ASCII characters, save the file and upload it to the Blazemeter test again. The error message will no longer show up.

Additional Information

The entire script is parsed, so all components, even the disabled ones, need to contain ASCII characters only.

This is documented in the File Content Restrictions section of the Uploading Files article