Hi Bharat,

The context in which this message usually occurs is when code in an object's method references its hierarchical parent where the parent no longer exists.

This commonly occurs when there is a dangling reference to the object somewhere so the object is not destroyed when its parent is destroyed. Then, when code in the object makes reference to the parent, this error occurs.

I do not know how this may apply to your situation, but I suspect there is a dangling object reference being left in one of your modules which is making reference to a parent that no longer exists.

Regards,