IBM Support

IT46453: INSTALL OF 6.2 ON WINDOWS SERVER 2022 WILL NOT COMPLETE START UP.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • After what appears to be a successful install or upgrade of 6.2
    (per the install log), when the system is started, it doesnt
    complete the start up process. When running the
    startWindowsService.cmd script, it appears to go through the
    standard start up process, where Ops service starts and enters
    the running state, and then the service stops after 15-20
    seconds. Then the main service and NoApp service also enter the
    Starting and Running state, and then also stop after about the
    same time. There is very little logged, though the
    Noapp_exe.log, ops_exe.log, and si_exe.log all logs have just
    standard messages nothing pointing our like any error.
    

Local fix

  • STRRTC - B2BISFG-69599
    DS / DS
    Circumvention: None
    

Problem summary

  • Users Affected:
    All
    
    Problem Description:
    The installation of 6.2 on Windows Server 2022 does not complete
    
    the start-up. After what appears to be a successful install or
    upgrade of 6.2 (per the install log), when the system is
    started, it does not complete the start-up process. When running
    
    the startWindowsService.cmd script, it appears to go through the
    
    standard start-up process, where the Ops service starts and
    enters the running state, and then the service stops after 15-20
    
    seconds. Then the main service and NoApp service also enter the
    Starting and Running state, and then also stop after about the
    same time. There is very little logged, though the
    Noapp_exe.log, ops_exe.log, and si_exe.log all logs have just
    standard messages, nothing pointing out any errors.
    
    DS / DS
    Circumvention: None
    
    Platforms Affected:
    Windows
    

Problem conclusion

  • Conclusion:
    The startup of Sterling B2B Integrator is not getting completed
    on Windows 2022.
    
    Resolution Summary:
    The issue appears due to the presence of IBMJCEPlusFIPS, which
    was not required.
    
    Delivered in:
    6010206
    6020003
    All future Fix Packs can be found in the Release Timeline Matrix
    
    - https://www.ibm.com/support/pages/node/6194265
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT46453

  • Reported component name

    STR B2B INTEGRA

  • Reported component ID

    5725D0600

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-07-01

  • Closed date

    2024-09-03

  • Last modified date

    2024-11-13

  • 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

    STR B2B INTEGRA

  • Fixed component ID

    5725D0600

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS3JSW","label":"Sterling B2B Integrator"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"610","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
14 November 2024