Forum Discussion

Arin's avatar
Arin
New Contributor
11 years ago

SoapUI NG can't detect automatic Proxy!

 Hello,     We are using TOX client to connect to Client Network -  A Webservice hosted in Client network could not be accessed from SoapUI NG - getting the following error   "Thu Jul 09 20:32:2...
Arin's avatar
Arin
New Contributor
11 years ago

Hello Smart Bear team,

 

Can you please help with this issue? We are not able to import any WSDL for our projects for the same error. Though everthing works fine in 3.6.1 version.

 

WE have already bought  NG Pro licenses and those licenses do not work for 3.6.1. So, we are in a dead lock situation.

 

Request your help with this,

 

Thanks

Arindam

TanyaYatskovska's avatar
TanyaYatskovska
Icon for Alumni rankAlumni
11 years ago

Hi Arin,

 

Are you using Ready! API and SoapUI on one computer? Perhaps, some security settings block accessing to the computer where are running the SoapUI NG test. Can you check this?

  • Arin's avatar
    Arin
    New Contributor
    11 years ago

    Hi Tanya,

     

    We installed Ready API 1.3 and could see SoapUI NG Pro on the same screen. We tried in both but could not connect to the WSDL

     

    We have a corporate Soap UI Pro License for this.

     

    http://osb.int.esb.apmoller.net:9200/RateManagementV2/RateManagement

     

    We also installed SoapUI 4.5.2 with the same licnese but this wsdl does not work. It's the same issue for all our project WSDL.  Only those WSDL work in these versions which can be accessed through internet.  All these WSDL s can be accessed through TOX Client from Vendor network to  our client network.

     

    These WSDL s works fine with SoapUI 3.6.1  with the same TOX client setup. Probably this is the only version which supports our WSDL s.

     

    Please help us underatand what has changed in the new version and is there a way we can fix this - else we need to work with our Prcurement deparatment on how to swap the licenses but I am hopefull that you will have a solution.

     

    Kindly help.

     

    Thanks

    Arindam

     

     

     

     

    • Arin's avatar
      Arin
      New Contributor
      11 years ago

      Hello Smartbear team,

       

      This is what I could find out from your site

       

      5.1. Which ports need to be opened in a firewall to access the floating license server
      The floating license server uses RMI to communicate with the client (SoapUI Pro or loadUI Pro) and requires ports 1099 and 10991 to be opened accordingly.

      http://www.soapui.org/about-soapui/soapui-faq.html#5-1-Which-ports-need-to-be-opened-in-a-firewall-to-access-the-floating-license-server

       

      Can you please confirm if this was not needed in 3.6.1 and something which was introduced in higher version so that I can follow up with  our Network team on this?

       

      Not sure - why Only 3.6.1 version is working in our current set up and no higher version.

       

      Please share some inshight.

       

      Thanks

      Arindam

       

       

       

       

       

      • TanyaYatskovska's avatar
        TanyaYatskovska
        Icon for Alumni rankAlumni
        11 years ago

        Hi,

        I don’t think that this behavior is related to the license consumption. So, there is no need to analyze the port settings.

         

        I would suggest that you compare project settings set in your SoapUI 3.61 and other SoapUI versions (including Ready! API). I guess that the difference in settings causes this. Check Proxy settings and others.