E1: PKG: BSFNs Do NOT Build On Windows Server - Error: 'cl' is not recognized as an internal or external command, operable program or batch file
(Doc ID 643457.1)
Last updated on APRIL 03, 2024
Applies to:
JD Edwards EnterpriseOne Tools - Version SP23 and Prior and later Information in this document applies to any platform.
Symptoms
Scenario 1
Full package will NOT build for Windows Enterprise Server. All BSFN .err logs have this error:
'cl' is not recognized as an internal or external command, operable program or batch file.
Server Package UBE R9622 PDF shows that every BSFN and NER had errors.
.STS files show that no objects built for the DLLs (Business Libraries).
Scenario 2
Server Package compiler errors on an EnterpriseOne Xe SP23_J1 Windows 2000 enterprise server. Error:
'cl' is not recognized as an internal or external command, operable program or batch file.
Scenario 3
Windows platform. Customer trying to build an update or full package which contains any business function. The client package completes okay, but the server package generates a spec Build Status error for BSFN object and no BSFNs or NERs are built.
Errors in ALL BSFNs .err logs:
'cl' is not recognized as an internal or external command, operable program or batch file.
Changes
Cause
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
