E1: PKG: Client Package Build UBE R9621 Error - LNK1104 "cannot open file" in Deployment Server Shared Folder (Doc ID 1193545.1)

Last updated on DECEMBER 02, 2024

Applies to:

JD Edwards EnterpriseOne Tools - Version SP24 and later
Information in this document applies to any platform.

Symptoms

Scenario 1 - Existing Installation that Built Packages Without Errors Now Seeing LNK1104 BSFN Errors

Client package build UBE (R9621) show failed with many BSFN errors. The package build log buildlog.txt has errors looking like below:

LINK : fatal error LNK1104: cannot open file '\\deployment_server_name\E812\DV812\package\package_name\bin32\CALLOBA.dll'

mt.exe : general error c10100b1: Failed to load file "\\deployment_server_name\E812\DV812\package\package_name\bin32\CALLOBA.dll". The system cannot find the file specified.

Scenario 2 - New Installation DLL Reports "Not Built" and "Build Failed"

Customer has new 9.1 installation. The client package is showing an error for one DLL. The R9621 reports that the DLL (in this instance, CTRAN) is "Not Built". The ClientPkgBuild.log reports:

Mon Jul 15 18:57:54 - PkgStatus.cpp:196 PKGSTS0004 ERROR: At least one parent DLL was not built correctly. Check buildlog.txt in the work directory for details.

The BuildLog.txt file shows no errors for the BSFN builds or the DLL within the log, but the summary at the end of the log states:

CTRANS.dll - 0 error(s), 0 warning(s): Build failed. Restored previous dll.

Changes

No noticeable changes, but anti-virus software was running on the Deployment Server.

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!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.