Forum Discussion

rmullaart's avatar
rmullaart
Occasional Visitor
3 months ago

Error when trying to check WSI compliance

I am trying to check the comliance of an WSDL file. But when I try to run WSI compliance I get the follwing error:

Running WSI Analyzer for [MMCHubBinding]

directory: C:\Program Files\SmartBear\SoapUI-5.7.2\wsi-test-tools
command: [cmd.exe, /C, C:\Program Files\SmartBear\SoapUI-5.7.2\wsi-test-tools\analyzerV10.bat, -config, C:\Users\rmt\AppData\Local\Temp\wsi-analyzer-config3201042973247304002.xml]
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

I cant't seem to find a way to fix this

  • Humashankar's avatar
    Humashankar
    23 days ago

    Hi rmullaart 

    The error you're experiencing with WS-I compliance checking in SoapUI is due to the space in the directory path "C:\Program Files".

    To resolve this, you'll need to adjust the command execution by quoting the directory path. Here are the steps to follow:

    First, ensure the directory path is properly quoted in the SoapUI settings. Go to File > Preferences > WS-I Settings, and in the Tool Location field, quote the path, for example: "C:\Program Files\SmartBear\SoapUI-5.7.2\wsi-test-tools". 

    Furthermore, verify that the WSI_HOME environment variable is set correctly and quoted if necessary.

    To configure and run the WS-I compliance check in SoapUI, follow these steps:

    • Download and configure the WS-I Interoperability Testing Tools 1.1, and extract them to a directory.
    • In SoapUI, set the Tool Location to the extracted directory, ensuring it is quoted if there are spaces in the path.
    • Set the WSI_HOME environment variable to the same directory.

    Finally, create a new SoapUI project, import your WSDL file, and run the compliance check to generate a report detailing any compliance issues.

    Hope this helps - Happy to help further!!
    Thank you very much and have a great one!
    Warm regards

  • Humashankar's avatar
    Humashankar
    Champion Level 3
    23 days ago

    Hi rmullaart 

    The error you're experiencing with WS-I compliance checking in SoapUI is due to the space in the directory path "C:\Program Files".

    To resolve this, you'll need to adjust the command execution by quoting the directory path. Here are the steps to follow:

    First, ensure the directory path is properly quoted in the SoapUI settings. Go to File > Preferences > WS-I Settings, and in the Tool Location field, quote the path, for example: "C:\Program Files\SmartBear\SoapUI-5.7.2\wsi-test-tools". 

    Furthermore, verify that the WSI_HOME environment variable is set correctly and quoted if necessary.

    To configure and run the WS-I compliance check in SoapUI, follow these steps:

    • Download and configure the WS-I Interoperability Testing Tools 1.1, and extract them to a directory.
    • In SoapUI, set the Tool Location to the extracted directory, ensuring it is quoted if there are spaces in the path.
    • Set the WSI_HOME environment variable to the same directory.

    Finally, create a new SoapUI project, import your WSDL file, and run the compliance check to generate a report detailing any compliance issues.

    Hope this helps - Happy to help further!!
    Thank you very much and have a great one!
    Warm regards