Home Discussions Questions & Answers Corrupted FND Binary Prevents Output Generation

Corrupted FND Binary Prevents Output Generation

Avatar photoCustomer December 9, 2022 at 4:11 pm

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.

Viewing 4 reply threads
  • Author
    Replies
    • Support December 11, 2022 at 12:43 pm  

      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.

    • Avatar photoCustomer December 12, 2022 at 10:12 pm  

      How do we repair the corrupted `fndcpesr` file?

    • Support December 14, 2022 at 7:25 pm  

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

    • Avatar photoCustomer December 16, 2022 at 4:49 am  

      After relinking, is a full application tier bounce necessary?

    • Support December 16, 2022 at 11:01 am  

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

Viewing 4 reply threads
  • You must be logged in to reply to this post.

Login with: