Home › Discussions › Questions & Answers › Corrupted FND Binary Prevents Output Generation

Corrupted FND Binary Prevents Output Generation

Avatar photoCustomer Questions & Answers 5 replies

Our reports, which run as host concurrent programs, complete ‘Normal’, but the output button is greyed out. The log file says: ‘Output is not being printed because: The print option has been disabled for this report.’ We get no output file, even though the report is successful.

5 replies

  • Support Enginatics

    This is a classic sign that the FND binary responsible for output generation, `$FND_TOP/bin/fndcpesr`, is corrupted or zero bytes, likely following system maintenance. This corruption prevents the output file from being created.

  • How do we repair the corrupted `fndcpesr` file?

  • Support Enginatics

    You must relink the FND binary. Log in as the application owner and execute the command: `adrelink.sh force=y ranlib=n “FND fndcpesr”`.

  • After relinking, is a full application tier bounce necessary?

  • Support Enginatics

    You only need to bounce the concurrent managers for them to pick up the corrected binary and resume generating output files.

  • You must be logged in to reply to this post.