Hi fellows,

I came across the following strange situation:

We have two instances of the Siebel 8.1 here, one is not customized (default) and the other, in the same server, is a completely customized version.

The QTP 11 with Siebel addin installed can perfectly identify the Siebel objects, everything is fine at that environment, it means that the automation properties are on and I'm using the "SWECmd=AutoOn" (I'm really using)

The other instance, the customized one, cannot recognize any object but header.

- Possible causes:
Wrong customization?
Different instances?
The customized instance can be linked to another instance (we have 5) that is not enabled.

I'll check those possible causes with Siebel admin, any other idea?