alexanac
Member
Hello,
I am running OneWorld Xe SP16.1 in a Windows 2000 environment (1 DEP/ 1 ENT) and am running into the following issue when trying to build a full package:
I am building the package for both client and server. The client side on the deployment server finishes fine and w/o error. The enterprise server side, however, gives me a multitude of errors in the generated pdf file. Starting w/ CAEC, most of the "C*" objects below that end in error. Further down in the pdf file, it lists each individual object that caused the "C*" objects in general to fail (there are over 100 pages of them). After checking the compile logs on the enterprise server, I see that every failed object gives the same error. It is as follows:
'cl' is not recognized as an internal or external command,
operable program or batch file.
It looks like it is trying to build these objects by calling 'cl', but fails when it does so. I have never seen this error before. Does anyone have any ideas? Thanks in advance for any help!
- Tony
I am running OneWorld Xe SP16.1 in a Windows 2000 environment (1 DEP/ 1 ENT) and am running into the following issue when trying to build a full package:
I am building the package for both client and server. The client side on the deployment server finishes fine and w/o error. The enterprise server side, however, gives me a multitude of errors in the generated pdf file. Starting w/ CAEC, most of the "C*" objects below that end in error. Further down in the pdf file, it lists each individual object that caused the "C*" objects in general to fail (there are over 100 pages of them). After checking the compile logs on the enterprise server, I see that every failed object gives the same error. It is as follows:
'cl' is not recognized as an internal or external command,
operable program or batch file.
It looks like it is trying to build these objects by calling 'cl', but fails when it does so. I have never seen this error before. Does anyone have any ideas? Thanks in advance for any help!
- Tony