iControl fails to take the node down as "forced offline"

Hello,

 

 

a little background....

 

 

I used PS Server Control as a guide to develop my own version of node utility. I have a sandbox version of BIGIP Configuration Utility which contains a few pool members and nodes. When I run my script through PowerShell, it successfully "forces offline" all the specified nodes. While forcing offline one of the nodes (lets call it nodeX), PS displays number of active connections and within seconds they are all disconnected and the node is forced offline. After that I normally go to BIGIP Configuration Utility to manually check if the node was forced offline and I have never been disappointed!

 

 

the actual problem....

 

 

After my successful development and testing, I moved my project to the dev environment and I tried to do the same testing there. The dev environment has the similar pool members and nodes as my sandbox. So, whenever it reaches to nodeX and tries to disable it, the active connections don't seem to disconnect any time soon and the script just waits on them for ever saying "Waiting for current connections to drop to zero...". However, if I load up the BIGIP Configuration Utility and manually click the node (nodeX) and click on "force offline" it can easily take the node down to "forced offline" without waiting a second!

 

 

So, my concern here is how do I make sure my script does not wait on the active connections for ever and just forces them offline like it did on my sandbox? I don't want to login into the BIGIP Configuration Utility and manually do the process for just that specific node.

 

 

I tried copy-pasting my code here but the forum didn't let me saying I entered too many words.