TMS API booking fault hidden by invalid SOAP message

[cdnadmin]

This document was generated from CDN thread

Created by: David Stimson on 01-04-2011 11:25:47 AM
Hi,

We have successfully linked our booking system into a loan TMS and can make, view and delete bookings using the TMS API.

When we tried the pre-production TMS we get an error when we try to book or view. We don't get an error when we delete an existing booking - the booking is successfully deleted on the TMS.

The errors we get back are:

Message: System.ServiceModel.CommunicationException: Server returned an invalid SOAP Fault.  Please see InnerException for more details. ---> System.Xml.XmlException: End element 'Fault' from namespace 'http://www.w3.org/2003/05/soap-envelope' expected. Found element 'detail' from namespace ''. Line 1, position 571.

The same user account can book, view and delete on the TMS Portal website.

1) Why do we always get invalid SOAP Fault messages?

2) What could stop an API user booking and viewing, but can still delete?

Thanks

David

There is a difference in the versions between the Loan TMS and Pre-production TMS Portal

Loan TMS S/N: 80A00012     Version: 13.0

Pre-production TMS S/N: 80A03823     Version: 12.6

The main difference is that the more up to date loan TMS API has an additional function GetConferenceForUser() – we do not use this function. Tandberg do state that the API is backward compatible.

Just in case the version is causing the problem I have rebuilt using the WSDLs supplied by the Pre-production TMS.

I still get the booking and view errors on the pre-production TMS. I can still make, view and delete bookings on the loan TMS.

I also tried changing the ClientVersionIn from 5 back to 4.

It is not clear which version of the API is implemented on each of the TMS systems.

Still can’t book on pre-production TMS.

Running out of things to try from my end…..

Using WFC - expects fault in sequence order as per http://www.w3.org/2003/05/soap-envelope/

<xs:sequence>
  <xs:element name="Code" type="tns:faultcode" />
  <xs:element name="Reason" type="tns:faultreason" />
  <xs:element name="Node" type="xs:anyURI" minOccurs="0" />
  <xs:element name="Role" type="xs:anyURI" minOccurs="0" />
  <xs:element name="Detail" type="tns:detail" minOccurs="0" />
</xs:sequence>

Subject: RE: TMS API booking fault hidden by invalid SOAP message
Replied by: Torgeir Johansen on 22-11-2011 09:56:41 AM
David,

it seems like you do not have the Application Integration License Key installed on your pre-production TMS server. As far as I know, the user can delete a conference without a proper licences, but will receive an error if trying to enumerate or saving conferences without a proper license.

Anyway, it seems like the SOAP exception returned is not properly formatted, but that's a different issue.

Will adding a API license correct your issue ?

Regards,
Torgeir