Resolution:
Cause
1. This could be due to the mismatch in the NLS_LANG properties set in the database server for the Workflow Server and the value on the machine where workflow server is installed. By default workflow server uses the character set AMERICAN_AMERICA.US7ASCII. If the database is installed with any other character set, the NLS_LANG environment variable should accordingly be set on the workflow server machine. Oracle 9.2 database server by default uses AMERICAN_AMERICA.AL32UTF8 character set. Hence if you have the workflow database installed on Oracle 9.2, make sure to set the right environment variable.


Resolution
Execute the following statement against the Workflow Server Database:
select * from nls_database_parameters;

Make a note of the following parameters:
nls_language
nls_territory
nls_characterset

Add the following two lines:
NLS_LANG=&ltnls_language>_&ltnls_territory>.&ltnls_characterset>
export NLS_LANG
to the file &ltbwwf_home>/server/&ltservername>/bin/IcTSMstartServer_env.sh

On Windows do one of the following:
- Search in windows registry for NLS_LANG and replace it with the right value as seen from the database e.g. AMERICAN_AMERICA.AL32UTF8.
- Add a new environment variable NLS_LANG and set the correct value as seen in the database.

Restart the Workflow Server.

After successful installation of BW-Workflow (GA version), connection to the workflow server from designer fails. Even connection through Batch Registry and PC GUI fails.