PI43373: WINDOWS BUILD FORGE 8.0.0.2 WITHOUT TOMCAT FOR WAS INTEGRATION CAUSES ERROR 1813

Rational Build Forge Fix Pack 4 (8.0.0.4) for 8.0
Rational Build Forge Fix Pack 5 (8.0.0.5) for 8.0
Rational Build Forge Fix Pack 6 (8.0.0.6) for 8.0
Rational Build Forge Fix Pack 7 (8.0.0.7) for 8.0
Rational Build Forge Fix Pack 8 (8.0.0.8) for 8.0
Rational Build Forge Fix Pack 9 (8.0.0.9) for 8.0
Rational Build Forge Fix Pack 10 (8.0.0.10) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.10
Rational Build Forge Fix Pack 11 (8.0.0.11) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.11
Rational Build Forge Fix Pack 12 (8.0.0.12) for 8.0
Rational Build Forge Fix Pack 13 (8.0.0.13) for 8.0
Rational Build Forge Fix Pack 14 (8.0.0.14) for 8.0
Rational Build Forge Fix Pack 15 (8.0.0.15) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.15
Rational Build Forge Fix Pack 16 (8.0.0.16) for 8.0
Rational Build Forge Fix Pack 17 (8.0.0.17) for 8.0
Rational Build Forge Fix Pack 19 (8.0.0.19) for 8.0
Rational Build Forge Fix Pack 18 (8.0.0.18) for 8.0
Rational Build Forge Fix Pack 20 (8.0.0.20) for 8.0
Rational Build Forge Fix Pack 21 (8.0.0.21) for 8.0
Rational Build Forge Fix Pack 22 (8.0.0.22) for 8.0

APAR status

• Closed as program error.

Error description

• When installing Build Forge 8.0.0.2 under Windows and
  configuring your own Application server, the Windows Error 1813
  is generated.
  
  Services
  
  	Windows could not start the IBM Rational Build Forge Management
  Console 8.0.0.2-1-0035 service on VAAISHAPPR38.
  
  	Error 1813: The specified resource type cannot be found in the
  image file.
  
  Steps to reproduce:
  
  - Install Build Forge 7.1.3.x with the option to supply separate
  application server.
  - Attempt to upgrade to Build Forge 8.0.0.x.
  
  Expected result:
  
  - Upgrade completes without issue.
  
  Actual result:
  
  - Provided Apache server is started, but Build Forge services is
  not labelled as running.
  Requires Apache processes to manually be killed if restarting
  Build Forge.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Provided Apache server is started, but Build Forge services  *
  * is                                                           *
  * not labelled as running.                                     *
  * Requires Apache processes to manually be killed if           *
  * restarting                                                   *
  * Build Forge                                                  *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * WINDOWS BUILD FORGE 8.0.0.2 WITHOUT TOMCAT FOR WAS           *
  * INTEGRATIONCAUSES ERROR 1813                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• fixed in  BuildForge 8.0.0.4 release
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RATIONAL BUILDF

• Fixed component ID

  5724S2700

Applicable component levels

• R800 PSN

     UP