When the locale of the Web Browser is set to French and a parameterized
Stored Process is opened in the BI Portal or Stored Process Web
application, a Javascript error occurs. The error message will be
similar to the following:

  Problems with the Web page might prevent it from being displayed
  properly or functioning properly.

    Line: 83
    Char: 26
    Error: Expected ';'
    Code: 0
    URL: http://aa.bb.com:8080/SASStoredProcess/do?_program=xxxx

The cause of this behavior can be found in the "Resources_fr.properties"
file that is in the "sas.svc.storedprocess.webapp.jar" file (that is in
the "SASStoredProcess.war" file).  The translated text is "Options
d'exécution". The apostrophe is coded as unicode u0027. The text is an
input parameter of a function which is quoted with single quotes. A
single quote cannot be enclosed in a text string that is itself enclosed
within single quotes. That is, the following statement is invalid:

   window.status='Options d'exécution';

Because of this, the rest of the line does not get rendered properly
and the statement is not valid.

There are several ways to avoid this problem. You can modify the
"Resource_fr.properties" file and changing "Options d'execution" to
another value that does not contain an apostrophe.

If you are running the Tomcat server, you can create a directory at a
location that is similar to the following:

   C:\Tomcat4.1\webapps\SASStoredProcess\WEB-INF\classes\com\sas\
   services\storedprocess\webapp

Then, include the modified copy of the "Resources_fr.properties" file in
this folder.  The servlet will look here first before it uses the
"Resources_fr.properties" in the jar file.

Another option is to create a new "SASStoredProcess.war" file that
contains the modified "Resources_fr.properties" file.

Select the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Information Delivery Portal 9.1.3 is available at:

A fix for this issue for SAS Web Olap Viewer 3.1 is available at:

A fix for this issue for SAS Information Delivery Portal 9.1.3 is available at: