Well, I came across this the other day and I just couldn’t get the EnterpriseOne package build to rebuild successfully. There were no usual suspects, like coding errors or running out of disk space. The only error I had was:
Attempting to Link. Command: 'chdir=E:\JDEdwards\E900\DDP\packages\PDF6000\obj\CLOC' Entering DoTheLink. Executing: 'dir /b *.obj >> link_cmd'. Executing: 'link @link_cmd >> CLOC.log'. Entering RunMtExe. Executing: 'mt.exe -manifest E:\JDEdwards\E900\DDP\packages\PDF6000\bin32\CLOC.dll.manifest -outputresource:E:\JDEdwards\E900\DDP\packages\PDF6000\bin32\CLOC.dll;#2'. builddll.c:4719 BUILDDLL0191 ERROR: Failed to run mt.exe successfully Exiting RunMtExe. builddll.c:2394 BUILDDLL0082 ERROR: Exiting DoTheLink with failure. Finished Linking. Copying .c, .h, .hxx, and bin32 to Package Location.
So, I started messing around with the mt.exe command that it was trying to run and came up with this:
C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin>mt.exe -manifest E:\JDEdwards\ E900\DDP\packages\PDF6000\bin32\CLOC.dll.manifest -outputresource:E:\JDEdwards\E 900\DDP\packages\PDF6000\bin32\CLOC.dll
Then, I resubmitted the build using Package Build History and it completed successfully.
Do you have any tricks for getting by odd package build issues?