]]>By: gkahlerhttp://itknowledgeexchange.techtarget.com/itanswers/rep-0066-error-executing-ca-utility/#comment-64002
Wed, 27 May 2009 21:52:30 +0000#comment-64002I found the issue. The parm form had a LOV that was too large. I guess this error is related to memory.

Thanks for your help Carlos.

]]>By: gkahlerhttp://itknowledgeexchange.techtarget.com/itanswers/rep-0066-error-executing-ca-utility/#comment-63902
Sat, 23 May 2009 23:49:48 +0000#comment-63902OK thanks. The change was done last Feb. I will try my other PC in the office and the patch.
]]>By: carlosdlhttp://itknowledgeexchange.techtarget.com/itanswers/rep-0066-error-executing-ca-utility/#comment-63893
Fri, 22 May 2009 21:36:34 +0000#comment-63893I have not encountered this error, but the first thing I would do is to apply the latest patchset available, which I think is patch 18.

Second, what is the difference between the old version and the new one ? I would try starting from the previous version and applying one change at a time, to see what is the change that generates the error.

Also, have you tried compiling the report in other machine, and run it in the machine where it is giving the error ?

]]>By: gkahlerhttp://itknowledgeexchange.techtarget.com/itanswers/rep-0066-error-executing-ca-utility/#comment-63891
Fri, 22 May 2009 20:47:04 +0000#comment-63891oops forgot Report Builder 6.0.8.11.3
]]>By: gkahlerhttp://itknowledgeexchange.techtarget.com/itanswers/rep-0066-error-executing-ca-utility/#comment-63890
Fri, 22 May 2009 20:40:30 +0000#comment-63890Yes I am using reports builder 6i. I open the report then try to run it. It waits for a while then gives an error. I can open a older version of the report and run it OK. I am able to compile it and create a run time OK. The reports runtime gives me the same error but I can run it on my server OK.

Greg

]]>By: carlosdlhttp://itknowledgeexchange.techtarget.com/itanswers/rep-0066-error-executing-ca-utility/#comment-63889
Fri, 22 May 2009 20:18:28 +0000#comment-63889Per the error code, we must assume you are using Oracle Reports. If that is correct, what version and patch level ?

Are you calling the report from a forms application ?
Did this report work before ?
Does this error occur with this report only ?

The more information you provide, the better chances to get useful responses.