Forum Discussion

Michael_Brown_1's avatar
Michael_Brown_1
Icon for Nimbostratus rankNimbostratus
Sep 18, 2004

'Could not connect to iControl CORBA Portal' msg

Hello,

 

I figured this was more of a general question than a .NET question....

 

I have code (C) that successfully accesses iControl in one environment, but when I move it to the next environment (completely separated network), the same code generates the message 'SoapException: Could not access requested iControl CORBA Portal'.

 

I am passing the IP address of the BigIP box into the code and building the ITCMLocalLBNode.URL from the passed in parm, so the access to the portal should be getting the correct URL in each environment. I can access the portal WSDL definitions via the portal URL from Internet Explorer - but apparently not from my code (same client machine).

 

Is there something besides the node.URL property that might be pointing to the old environment's BigIP server ? Or am I missing something else ?

 

Thanks for any help ! Mike.
dev
devops
iControl
v4
  • Joe_Pruitt's avatar
    Joe_Pruitt
    Sep 18, 2004
    On the 4.x platforms, the SOAP server is a client proxy to the CORBA server on the BIG-IP. The "Could not connect to iControl CORBA Portal" error indicates that either the CORBA portal isn't running on the BIG-IP, or it is not configured to listen on the loopback address.

     

     

    Your situation is a server configuration problem, not with your client code. The WSDL request does not connect to the CORBA portal so that is why you aren't getting an error when trying to request the WSDL documents.

     

     

    You can try to reset the CORBA portal with the following command

     

     

    "$ bigstart shutdown portal

     

    $ bigstart startup"

     

     

    This will make sure that the CORBA portal is running. Then re-run your client app and see if this corrects the problem. If not, then something is amiss with your configuration (which isn't supposed to be changed).

     

     

    If this doesn't correct your problem, then I'd suggest you contact F5 Technical Support to get the issue resolved. As this is a BIG-IP configuration issue, you will have better results going through our normal support channel.

     

     

    F5 Technical Support

     

    Email:

     

    Phone: 206-272-6888

     

    Web: http://www.f5.com/support/

     

    AskF5: http://tech.f5.com/

     

     

    -Joe