Forum Discussion
14 years ago
I found this issue in the soapUI Pro forum. It was confirmed by SmartBear tech support as a known bug (in 4.5.1 I believe) involving the soapUI internal browser. The workaround listed there (using a command-line switch to disable the browser) didn't work for me on Windows 7, but I found that I could launch soapUI, go to File > Preferences > UI Settings tab and uncheck the 2nd-to-last option, “Disable Browser,” to prevent this issue with the IE network settings from occuring. I don't know what other impact disabling the internal browser may have, but my stuff works fine for me so far.