Forum Discussion
jbp123
16 years agoNew Contributor
*SOLVED*
OK, corrupt soapui cache/settings caused this problem, most likely from upgrading from soap 3.5.1 to 3.5.1 Pro version without uninstalling the first instance first.
The solution was to uninstall all instances, then I cleared out my soapui settings xml file and also the cache folders.
Back in action!
OK, corrupt soapui cache/settings caused this problem, most likely from upgrading from soap 3.5.1 to 3.5.1 Pro version without uninstalling the first instance first.
The solution was to uninstall all instances, then I cleared out my soapui settings xml file and also the cache folders.
Back in action!