Relink from adadmin giving error

Question

While trying to relink FNDLIBR.exe and FNDSM.exe through adadmin is giving below error. I have also sourced the env file correctly.
I am getting same error if I try from command prompt aswell.
adrelink.sh force=y link_debug=y “fnd FNDLIBR”
adrelink.sh force=y link_debug=y “fnd FNDSM”
Please advise how to resolve the below error.
+Enter executables to relink, or enter 'all' [all] : FNDLIBR.exe+
D:/oracle/apps/apps_st/appl/ad/12.0.0/bin/adrelinknew.sh 33: save: fork_level=1SetHandleInformation() failed: fd 0 handle 0x3 type 2: The parameter is incorrect.
D:/oracle/apps/apps_st/appl/ad/12.0.0/bin/adrelinknew.sh 35: save: fork_level=1
SetHandleInformation() failed: fd 0 handle 0x3 type 2: The parameter is incorrect.
An error occurred while relinking application programs.

Answer 1

It's a typing mistake, my environment is 2008 not 2003. Yes it is on win 2008 64bit R2. while this is working fine in production but only after cloning to new test environment is giving this error of OPP not coming up and service manager not coming up. While all the other services are running fine and autoconfig on db and apps tier is also executed successfully. So due to this problem only our XML publisher based reports that will be using OPP are failing. Other than this OPP and Service Manager rest all is fine. Please suggest if you can give any idea to resolve it so I can bring OPP and service manager up and running. I almost tried all the below,
0. check the OPP log file. You follow below navigation
System Administrator -> Concurrent : Manager -> Administrator
On this screen click on Output Post Processor and then click on Processes button -> Manager Log button
A new web page will open showing the manager log. Come to the bottom, you might see the error.
1. bounce the OPP (or all the CMs using adcmctl.sh script) and try again.
2. Increase 'concurrent: OPP Response Timeout' profile value from 60 to about 180. Then restart the concurrent manager program.
3. the path /appslog/fin_top/utl/fintest/out/ might not be correct. So as per the note ID 428855.1 changed the path to valid location, Navigate the following as the responsibility “XML Publisher Administrator”
Select Administration on the Personal Home Page
Under the Configuration tab select Properties and then General.
From there the Temporary directory will be displayed.
Changed the path to some thing that is existing physically.
After that bounce the output post processor. This should resolve the issue
====================================
+*<Moderator edit - deleted MOS Doc content - pl do not post contents of MOS Docs - this is a violation of your Support agreement>*+
====================
I think, Do the below if Service Manager is not running or not available.
+*<Moderator edit - deleted MOS Doc content - pl do not post contents of MOS Docs - this is a violation of your Support agreement>*+
=====================