Hi Sunil,
I resolved this issue by arranging the sequence of the fields in webservice but
now we have Error 8962:Unexpected element encountered in the XML Document for
fields (Manufacturer, Product Name, Product Categorization Tier 1, Product
Categorization Tier 2, Product Categorization Tier 3,Product Model/Version,
Corporate ID, Internet Email etc(ie. Non Mandatory fields))
Any thoughts?
Regards,
Praveen Kumar Saraswat
Solution Consultant
Column Technologies Australia Pty Ltd
Phone: +61 (0) 280 656 598 | Web: www.columnit.comhttp://www.columnit.com/
Mobile: +61 (0) 450 639 470 | Email:
psaras...@columnit.commailto:sskerr...@columnit.com
[cid:image001.jpg@01CDD7CA.1FBBA810]
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of itsm.support
Sent: Tuesday, 11 December 2012 5:33 PM
To: arslist@ARSLIST.ORG
Subject: Re: 8961 error with Impact and Reported Source
**
Hi,
This is what I found while navigating for below issue:
The real problem seems to be the order of the elements in the input XML call.
It seems that Remedy, or perhaps whatever mechanism they used to implement the
web services, isn't happy if the input elements aren't in the same order as
defined in the web service. It's ok if there are optional or defaulted elements
left out of the call, but those that are present must be in the order as
defined in the web service.
I recently had an integration team with this exact scenario. The field reported
as missing was passed, but still the error was thrown. I built a SoauUI call,
and the operation worked fine. Turns out this is because I used the SoauUI
function that automatically builds the input call from the web service
definition, so all of the elements are in the same order.
I then took the input xml reported by the integration team, and inserted it in
place of the automatically generated xml in the SoauUI, and I got the same
error reported by the integration team.
I manually rearranged the elements to match the operation definition, and
trying again, it was successful.
Integration teams will not be happy that they have to make sure the elements
are in the right order, and you'll need to avoid rearranging the element unless
everyone is on board with the change. However, if you do make use the elements
in the right order, this error will not occur.
HTH
--
Regards,
Sunil
Vyom Labs Pvt. Ltd.
BSM Solutions Services || ITIL Consulting Training
Email: [hidden
email]http://ars-action-request-system.1093659.n2.nabble.com/user/SendEmail.jtp?type=nodenode=7583733i=0
|| Web Site: www.vyomlabs.comhttp://www.vyomlabs.com Follow Vyom Labs
http://twitter.com/#!/vyomlabshttp://twitter.com/#%21/vyomlabs ||
http://www.linkedin.com/company/vyom-labs
From: Action Request System discussion list(ARSList)
[mailto:arslist@ARSLIST.ORG] On Behalf Of Saraswat, Praveen
Sent: Tuesday, December 11, 2012 8:06 AM
To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG
Subject: 8961 error with Impact and Reported Source
Importance: High
**
Hi Guys,
I have created a custom webservice on HPD:IncidentInterface_Create form which
is being consumed by other application.
When I am running the wsdl file in SOAP UI I am getting a proper response and
Incident is getting created.
But when the other party is trying from their application it throws 8961 error.
Earlier it was throwing error for Impact now its coming for reported source.
I have checked the sequence, I have made the fields nillable for which other
application is not passing any value. But with no success
We are stuck very badly here.
Any suggestions?
Regards,
Praveen Kumar Saraswat
_ARSlist: Where the Answers Are and have been for 20 years_
No virus found in this message.
Checked by AVG - www.avg.comhttp://www.avg.com
Version: 2012.0.2221 / Virus Database: 2634/5449 - Release Date: 12/10/12
_ARSlist: Where the Answers Are and have been for 20 years_
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Where the Answers Are, and have been for 20 years
inline: image001.jpg
