This section describes issues that remain open in this release at production time.
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.
Build Forge on Solaris can hang while trying to acquire a license due to a known issue in the Rational License Server.
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.
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:\'
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.
http://${CONSOLEHOST}:${CONSOLEPORT}/fullcontrol/index.php?mod=projectruns&action= edit&bfid=${PID}&bfid=${BID}&bfid=${UID}
7.0 URL elements | 7.0.1 (and later) URL elements |
---|---|
projectruns | jobs |
& | & |
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Limitations in JDBC drivers cause the following requirements:
If these requirements are not met, the Quick Report reporting feature does not work. The requirements are documented in Build Forge Installation Guide.
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.
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.
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
to access License Server in the list of system settings.If the BOM for your project is large, you may notice that the category names for a section might not be displayed correctly.
This problem will be fixed in a future release of the product.
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.
Name: tmp_var Value: Version_1.1
set $tmp_var = 7
When the job runs, a variable Version_1.1 is created with the value 7.