Information
We are currently investigating an issue with the editor of some pages. Please save your work and avoid to create new pages until this banner is gone.
Why does the container emit a "Failed to create Python object" message when I try activating my component?
The simple answer is because for some reason or another the Python container is unable to create the component based on the information found in $ACS_CDB/MACI/Components/Components.xml (or from a dynamic component client).
Some of these reasons include but are not limited to:
Traceback (most recent call last): File "../lib/python/site-packages/Acspy/Container.py", line 238, in activate_component File "../lib/python/site-packages/IERSImpl/IERS.py", line 60, in initialize addProperty(self, "dUT") File "/alma/ACS-4.1/ACSSW/lib/python/site-packages/Acspy/Util/BaciHelper.py", line 128, in addProperty interf = interf._narrow(CORBA.InterfaceDef)
this is most definitely the case. Typical causes of this are failure to install your module into an $INTROOT before issuing the acsStart command. Additionally, it's possible that some bad IDL (i.e., interfaces declared twice, enum values declared twice in the same namespace, etc) has corrupted the Inferface Repository. Please pay very close attention to the output coming from acsStart if you think this may be the case. To verify that this type of error is occuring, simply start ACS and run the irbrowser command to see if your IDL interface is really loaded into the CORBA interface repository.
Also, if you're running the Python container from the acscommandcenter you're not seeing the entire output of the container (temporarily at least) and more importantly the underlying error message from the Python interpreter. Try starting the container from the command-line instead. See FAQ on Delayed Output for more details.
-- DavidFugate - 06 Aug 2004