Forum Discussion

rvisaTEST's avatar
rvisaTEST
Occasional Contributor
14 years ago

Cancelled request due to invalid content

Hello all,

I am having a weird behaviour running teststeps in soapUI.

I can run testsuites and testcases correctly but if I have one teststep opened and try to run the testcase where it is contained, it jumps to the next step when reach the opened one.
Going further, if I open one teststep and try to run I get the message: "Cancelled request due to invalid content". It happens with all teststeps.

I have tried to run the same project in another machine and it works. I am able to run testcases or teststeps one by one with no problem.

Do you have any idea about this issue?

Thanks in advance.

Regards,
RV
  • Surekha's avatar
    Surekha
    Occasional Contributor
    12 years ago
    I experience the same problem.
    Did you find a way to work around it? [Considering you had posted this question in May 2011)
  • JayBofNS's avatar
    JayBofNS
    Occasional Contributor
    12 years ago
    I am seeing this issue in a simple REST request to an echo service with a JSON payload (no prams or templates). I am (trying to) using 4.6.4 64bit.
  • JayBofNS's avatar
    JayBofNS
    Occasional Contributor
    11 years ago
    >:( I still have this issue after uninstalling SoapUI 4.6.4/64, the 64-bit JRE and reinstalling the 32-bit versions. I have not found any work-around. It seems also that there is no benefit for me to continue with my evaluation. I cannot promote a purchase for software that is not supported.
  • GiscardN's avatar
    GiscardN
    Frequent Contributor
    11 years ago
    Hi,

    I was not able to reproduce this issue you have described. Make sure to try the version with the bundled JRE.
    If you have a SoapUI Pro license, you can open a support case so we can investigate further. If you are evaluating, I suggest that you request a SoapUI Pro Trial.

    Regards,

    Giscard
    SmartBear Support
  • JayBofNS's avatar
    JayBofNS
    Occasional Contributor
    11 years ago
    >:( I have no problem repeating this, with 64-bit or 32-bit, embeded JRE (Windows Installer) or external JRE (Zip):

  • JayBofNS's avatar
    JayBofNS
    Occasional Contributor
    11 years ago
    Thank you for your earlier reply, suggesting that I download SoapUI Pro. I have no problem hitting the same SoapUI project using Pro. So it is a mixed message here. Although I am glad that I have a means to test my REST services with SoapUI Pro, the unsupported version apparently has a bug which causes this issue I have experienced. Since I used the ZIP of the Pro Trial, I have both the 32-bit SoapUI installed, with JRE, and the Pro Version, without JRE, extracted to a separate location. I can use the same project in either Pro or SoapUI and I can repeat the issue in SoapUI. This does not instill confidence.

    SoapUI-4..6.4 Unsupported

    java.version=1.7.0_40
    java.vm.info=mixed mode
    java.vm.name=Java HotSpot(TM) Client VM
    sun.boot.library.path=c:\program files (x86)\smartbear\soapui-4.6.4\jre\bin
    soapui.home=C:\Program Files (x86)\SmartBear\SoapUI-4.6.4/bin

    SoapUI-Pro-4.6.4 Trial

    java.version=1.7.0_51
    java.vm.info=mixed mode
    java.vm.name=Java HotSpot(TM) 64-Bit Server VM
    sun.boot.library.path=C:\Users\<me>\Tools\Java\JDK\jre\bin
    soapui.home=C:\Users\<me>\Tools\SoapUI-Pro-4.6.4\bin\

    My reported issues were with 64-bit (with and without JRE) and now 32-bit (with JRE). And add SoapUI-5.0.0-beta (Zip) to the list, as well.
  • JayBofNS's avatar
    JayBofNS
    Occasional Contributor
    11 years ago
    ....and I would speculate that the high view count for this post suggests the issue is not limited to the few commenters in this thread.
  • JayBofNS's avatar
    JayBofNS
    Occasional Contributor
    11 years ago
    I am not sure if this comment will have any bearing to the issue, but I noticed that Pro has additional sub-tabs in both the Request and Response. And I noted that even for my simplest of Hello World, type REST tests, Pro has the following noted in the Form tab of the request:

    Missing parameter/body definitions for Request: Missing parameter/body definitions for Request:

    I would repeat, that the request is successful for this project using Pro. And in this case the test is a GET, so Body is irrelevant. But the Form comment does appear. And it appears in a test on a similar templated POST (no body content) request to the same Hello-World style test service.