AnsweredAssumed Answered

Issue with search/was/finding since recent upgrade

Question asked by wkolatac on May 3, 2019
Latest reply on May 6, 2019 by wkolatac

Since the recent upgrade (end of March), some of my search/was/findings calls are failing.

For example:

<ServiceRequest>
   <preferences>
      <verbose>false</verbose>
      <limitResults>1000</limitResults>
   </preferences>
   <filters>

      <Criteria field="qid" operator="EQUALS">150054</Criteria>

      <Criteria field="id" operator="GREATER">0</Criteria>
   </filters>
</ServiceRequest>

 

This fails with this message: 

2019-05-03 15:47:11 api call: search/was/finding failed: Qualys api call failed search/was/finding : OTHER_ERROR Details: An error occurred during request processing. Please contact your account manager.

If I change the value of the limitResults to 900, it works .....

 

But a call using this XML works fine ....

<ServiceRequest>
   <preferences>
      <verbose>false</verbose>
      <limitResults>1000</limitResults>
   </preferences>
   <filters>
   <Criteria field="severity" operator="GREATER">3</Criteria>
   <Criteria field="type" operator="EQUALS">VULNERABILITY</Criteria>
   <Criteria field="status" operator="NOT EQUALS">FIXED</Criteria>
   <Criteria field="id" operator="GREATER">0</Criteria>
   <Criteria field="ignoredReason" operator="NOT EQUALS">FALSE_POSITIVE</Criteria>
   < Criteria field="ignoredReason" operator="NOT EQUALS">RISK_ACCEPTED</Criteria>
   <Criteria field="ignoredReason" operator="NOT EQUALS">NOT_APPLICABLE</Criteria>
   </filters>
</ServiceRequest>

 

Anyone have any idea what happened?  Did the XML parameters/values change?

 

thanks in advance!

Outcomes