Transaction issue w/ iControl v11

Posted By Joe on 03/28/2012 08:35 AM

 

Yes, this is a known issue with transactions. In fact, we talked about it on the recent iControl Guru webcast we did.

 

 

Yes it was me who asked for this issue :)

 

 

 

The issue is due to the fact that some of the methods (such as the monitor methods) rely on the underlying objects to be created for internal validation to occur. In a transaction, when the calls are made, validation happens but the objects are not actually created until the commit happens. But, for the methods that have validation that looks for certain objects to physically exist, they will fail.

 

 

Again, this is a known issue and it is only present on a few methods, which you've found some of them.

 

 

First of all, I'd submit a support request to get it fixed.

 

 

Second, as a workaround for now, the best solution is to break your code up into 2 transactions where the monitors are created in a second transaction after the first completes.

 

 

-Joe

 

 

 

that's what I did until there is a proper solution.