com.glide.processors.soap.SOAPProcessingException: Web service update called for a missing record: 1883aa810f3df5001fb4715be1050e38

[ravikumar]

Hello Experts,

We are testing the incident - wsdl in SOAP UI tool. Using the insert we are able to insert a new record in Service now. Now from the soap response, copied the sys_id and we are updating record using the sys_id, it is giving us the following response

-------------------

com.glide.processors.soap.SOAPProcessingException: Web service update called for a missing record: 1883aa810f3df5001fb4715be1050e38

-----------------

We are stuck with this issue. Please guide us in the regard.

Regards,

Ravi Kumar. M

[will_leingang]

Hi Ravi, looks like you're having several issues using the soap interface

If you go to incident.do?sys_id=1883aa810f3df5001fb4715be1050e38

do you see the record you created?

Can you please attach or include your soap request body for the update?

Thanks.

Will

[ravikumar]

Hello Leingang,

My Applogies, above output I am getting is when I am trying to do a Update via SOAP UI Tool

sys_id is exists in incidents table

Here is the SOAP Request:

--------------

    <soapenv:Body>

          <inc:update>

                <sys_id>1883aa810f3df5001fb4715be1050e38</sys_id>

                <short_description>this is updated</short_description>

          </inc:update>

    </soapenv:Body>

------------------------------------
SOAP Resonse:

-----------------------

<SOAP-ENV:Body>

          <SOAP-ENV:Fault>

                <faultcode>SOAP-ENV:Server</faultcode>

                <faultstring>com.glide.processors.soap.SOAPProcessingException: Web service update called for a missing record: 1883aa810f3df5001fb4715be1050e38</faultstring>

                <detail>com.glide.processors.soap.SOAPProcessingException: Web service update called for a missing record: 1883aa810f3df5001fb4715be1050e38</detail>

          </SOAP-ENV:Fault>

    </SOAP-ENV:Body>

----------------------

[will_leingang]

Hi Ravi, might be permissions. Have you verified that the user your soap client is using can access that record?

If you're using the soap.guest account to update the record then you will get a record not found if that user doesn't have access to that record.

You can always verify what you have access to by impersonating that user. Just make sure the web_service_access_only=false on the user you're trying to impersonate.

Impersonating a User - ServiceNow Wiki

Will

[ravikumar]

Hello Leinganag,

I am using direct wsdl that solved all the issues. Thank you.

Regards,

Ravi Kumar. M