For me - they are the same.
That's one issue.
The second issue is that the settings file only references the keystore in the SSL settings of the soapUI preferences panel. Unless there's something in that settings file that shows loadUI how to reach the soapUI project-level keystores (I have four per tier - one set for QA and one set for PROD) I'm essentially dead in the water.
Such as it is - I went back to my soapUI Preferences and changed my SSL Keystore settings to match the keystore that I'm using right now on the project level. Then I saved settings, saved the project, closed soapUI, close loadUI - then opened loadUI and created a fresh loadUI project with the soapUI Runner using the test case from the targeted project.
Still fails.
