BuildForge Help

Known Issues

This section describes issues that remain open in this release at production time.

RATLC01039370: Cannot connect to Microsoft SQL Server database if a case-sensitive collation is used

If a Build Forge database on Microsoft SQL Server is created using a case-sensitive collation, Build Forge fails during startup with the following error:
C:\Program Files\BuildForge>BuildForge -d
DBD::ODBC::st execute failed: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'information_schema.tables'. (SQL-42S02)
[Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be prepared. (SQL-42000)(DBD: st_execute/SQLExecute err=-1) at /PerlApp/BuildForge/DB/Handle.pm line 211.
 
8808 /PerlApp/BuildForge/DB/sqlserver.pm(BuildForge::DB::sqlserver):42
 
8808 /PerlApp/BuildForge/DB/Handle.pm(BuildForge::DB::Handle):413
 
8808 /PerlApp/BuildForge/DB/ConnectionHandler.pm(BuildForge::DB::ConnectionHandler):34

Workaround: use a case-insensitive collation, such as the default: SQL_Latin1_General_CP1_CI_AS.

RATLC01038469: Build Forge on Solaris hangs if file descriptor limit is set higher than 1024

Build Forge on Solaris can hang while trying to acquire a license due to a known issue in the Rational License Server.

To determine the file descriptor limit, use the following command:
ulimit -n

Workaround: set the file descriptor limit to 1024 or lower. If you do this while Build Forge is hanging, the license server corrects itself and Build Forge acquires a license immediately.

RATLC01036678: Environments: backslash before ending quote in a variable assignment does not yield expected result

In a variable assignment (.bset env) there are unexpected results if the last character before the ending quote is a backslash. This true even if preparsing is turned off (_NO_PREPARSE_COMMAND is true). Example from step execution log:
195	01/28/08 03:45PM	STEP	.bset env "VAR07=C:\"
196	01/28/08 03:46PM	EXEC	.bset env 'VAR07' = ''
Workaround: put a space before the ending quote. Example from step execution log:
187	01/28/08 03:45PM	STEP	.bset env "VAR032=C:\ "
188	01/28/08 03:45PM	EXEC	.bset env 'VAR032' = 'C:\'

RATLC01035275: URL for version 7.0 notification templates might not work in later versions

The notification template URL provides a link in the notification e-mail to the build report in Build Forge.

In version 7.0.1, the URL in the notification templates changed. Consequently, when you upgrade from 7.0 to any later version, the notification template URL links might not work.

If you experience a link error, make the following changes to the notification templates:
  1. Select Project > Templates.
  2. Click on the notification template to display its properties on the Details tab.
  3. In the Body field, locate the URL for the template. The URL should be similar to the one in the following example:
    http://${CONSOLEHOST}:${CONSOLEPORT}/fullcontrol/index.php?mod=projectruns&action=
    edit&bfid=${PID}&bfid=${BID}&bfid=${UID}
  4. Replace the following 7.0 URL elements with the appropriate 7.0.1 (and later) URL elements:
    7.0 URL elements 7.0.1 (and later) URL elements
    projectruns jobs
    & &

RATLC01029756: IE6 generates Visual C++ runtime error on save of data

Internet Explorer 6 users may see a Visual C++ runtime error if the Google toolbar is installed.

As a workaround, in IE go to Tools > Internet Options > Advanced and the uncheck the "Enable third party browser extensions" option.

RATLC01031764: Build Forge System i agents need to change standard agent port (5555)

The standard Build Forge agent port (5555) may be preassigned on a System i server. In this case, change the Build Forge agent port to an unassigned port before starting the agent. You can edit the BFagent.conf file directly or use another method to change the port. For details, see the installation guide.

This problem will be fixed in a future release of the product.

RATLC01021966: Duplicate column values not displayed in Quick Report wizard-generated reports

In wizard-generated reports, column values are not displayed if they duplicate or match the column value of the previous record. This display convention makes it look like report data is missing when it is not.

This problem is due to a limitation in the Eclipse reporting tool, BIRT. In a future product release, the ability to hide or display duplicate column data will be provided.

RATLC01021475: Some tool tip messages in system configuration settings are truncated

This display problem is due to a limitation in Mozilla Firefox. Presently, there is no workaround. The problem will be addressed in a future product release.

RATLC01022565: Quick Report titles in performance report may be truncated

Because of a dynamic chart sizing issue in the current version of the Eclipse reporting tool BIRT, performance report titles may be truncated. Presently, there is no workaround. The problem will be addressed in a future product release.

RATLC01038257: Quick Report titles cannot contain periods

When you create a report, you must specify a title. If your report title contains a period, an error is generated and the report is not created.

Do not include periods in your report titles.

RATLC01020695: Not all installed components run if the Management Console is installed to NLV path

Do not use national language characters in the installation directory path name that you specify for the Management Console. Problems with the installer prevent Build Forge from installing correctly. Use US-ASCII characters only for the installation directory path. This problem will be addressed in a future product release.

RATLC01020895: Output for Build Forge agent install script (install.sh) is English-only

If you install the Build Forge agent on a host with an operating system language other than English, for example French on AIX, the output from the install script is in English. This issue will be addressed in a future product release.

RATLC01036414: Install panels for MS Visual Studio .NET for Build Forge are English-only

The installation panels for installing and setting up MS Visual Studio .NET 2005 for Build Forge are not internationalized. The panel text is English only.

RATLC01037445: DB2 error when upgrading from version 3.8 on MySQL to 7.0.2 on DB2 Express

If you migrate from version 3.8 with MySQL database to version 7.0.2 with DB2 Express, you run the bfdbmigrate script to migrate the database.

When you restart the Build Forge engine, the migrated database is started up. You might see a DB2 ALTER TABLE error.

Ignore the DB2 ALTER TABLE error; it is caused by an error in the Build Forge upgrade procedure. The upgrade procedure will be deprecated in a future release of the product.

Workaround: migrate to version 7.0 or 7.0.1, then migrate version 7.0.2.

Oracle 9.x database fails with ORA-01400 error

The following error occurs only if the Management Console is using an Oracle 9.x database, the DBD::Oracle driver, and the ora_ph_type parameter is set to a value that strips trailing blanks.

DBD::Oracle::st execute failed: ORA-01400: cannot insert NULL into("BLDFORGE"."BF_RESULT"."BF_ENV")

To fix the error, do the following:

Set the ora_ph_type parameter. The value for ora_ph_type in <bf-install>/db.ini must be set to a value that does not cause the driver to strip trailing blanks. The setting ora_ph_type=96 is recommended. If set to a value that strips trailing blanks (for example, SQL_VARCHAR), you will receive an error. The problem does not occur with Oracle 10.

Quick Report fails to start (Microsoft SQL Server and Oracle databases)

Limitations in JDBC drivers cause the following requirements:

  • Oracle: the database name and SID must use the same value (tnsnames.ora)
  • Microsoft SQLServer: in an ODBC driver, the Database Name and Data Source Name must use the same value.

If these requirements are not met, the Quick Report reporting feature does not work. The requirements are documented in Build Forge Installation Guide.

RATLC01021966: Duplicate column values not displayed in Quick Report wizard-generated reports

In wizard-generated reports, column values are not displayed if they duplicate or match the column value of the previous record. This display convention makes it look like report data is missing when it is not.

In a future product release, the ability to hide or display duplicate column data will be provided.

RATLC01023309: Management Console cannot connect to MySQL 5.0.41 database on console start (Windows only)

If Management Console fails to start and connect to the database, it might be caused by an error in the libmysql.dll file. To determine this, open the php_error.log file located in C:\<BF_installationdir>\Apache\logs. If the following error message is present, the error is in libmysql.dll.

PHP Warning: PHP Startup: Unable to load dynamic
library 'C:\Program Files\BuildForge\Apache\php\ext\php_mysqli.dll' - Invalid access to memory location.
To fix the problem in libmysql.dll , download and copy a new version, as follows:
  1. Download mysql-noinstall-5.0.41-win32.zip from the MySql Web site, for example: http://www.mysql.org/get/Downloads/MySQL-5.0/mysql-noinstall-5.0.41-win32.zip/from/http://mirror.x10.com/mirror/mysql/
  2. In the zip file, locate \mysql-5.0.41-win32\lib\debug\libmysql.dll.
  3. Stop MySql.
  4. Copy libmysql.dll to the <mysql_installdir>\bin directory.
  5. Start MySql.
  6. Restart the Management Console.

RATLC01022347: New license server ignored on upgrade

If you enter a different host name for the license server on an upgrade install than you entered when the Management Console was first installed, the installation program ignores the new value.

To enter the host name of the license server after you install the Management Console, use the License Server system setting. In the Management Console, select Administration > System to access License Server in the list of system settings.

RATLC01020674: Inconsistencies in BOM display for large BOMs

If the BOM for your project is large, you may notice that the category names for a section might not be displayed correctly.

RATLC00501623: Assign hidden option not hiding variable value in logs

If you select the Assign Hidden property when you create a variable, the variable value is displayed in the step log instead of being masked with asterisk (*) characters.
Note: If you export a project, variables with the Assign Hidden property are shown in cleartext in the exported XML file.

This problem will be fixed in a future release of the product.

RATLC01025502: Environment variable names that contain periods

If an environment variable name contains a period, attempts to reference that variable name in another variable fail. Shell-command parsing works differently on different platforms, which makes finding a uniform fix difficult.

Workaround on Windows platforms only:
  1. Set an environment variable to the value of the variable name you want.
    Name: tmp_var      Value: Version_1.1
    
  2. Within a step, use the variable as the variable-name portion of an assignment.
    set $tmp_var = 7

When the job runs, a variable Version_1.1 is created with the value 7.