Welcome to the Panopto Community

Please note: All new registrants to the Panopto Community Forum must be approved by a forum moderator or admin. As such, if you navigate to a feature that is members-only, you may receive an error page if your registration has not yet been approved. We apologize for any inconvenience and are approving new members as quickly as possible.

SOAP API generating faults in PHP

Trevor HughesTrevor Hughes Tyro
in API

We are experiencing inconsistent behaviors from two SOAP API endpoints starting December 6, 2024. 
We are using PHP on a Linux server to connect to the API and we suddenly started getting the following errors:

  • Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing Schema: element 'http://schemas.microsoft.com/2003/10/Serialization/:anyType' already defined in RemoteRecorderManagement.php:39
  • Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing Schema: element 'http://schemas.datacontract.org/2004/07/Panopto.Server.Services.PublicAPI.V40:AuthenticationInfo' already defined in RemoteRecorderManagement.php:39
  • Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing Schema: element 'http://schemas.microsoft.com/2003/10/Serialization/:anyType' already defined in SessionManagement.php:39

We have been running this script unchanged since around September of this year. Each time you run the script, it's a roll of the dice as to which of these errors you receive. This indicates to me, that the API endpoint isn't consistently returning the same response to our script.

Impacted EndPoints

  • RemoteRecorderManagement
  • SessionManagement

Script Objective

We have been running a script against the RemoteRecorderManagement endpoint that gets information about our Remote Recorders. Once it has the basic information about each Remote Recorder, it then uses the SessionManagement endpoint to get a list of upcoming sessions for each remote recorder. 

Issue Timeline

We first started noticing the issue on the morning of 12/6/2024, which may point to something in the 12/5/2024 service update as a possible cause. The issue appeared to be resolved on 12/12/2024. The issue returned on 1/6/2025. 

Tagged:

Best Answer

  • Adis HrnjicaAdis Hrnjica Crackerjack
    Answer ✓

    Hi Trevor,

    Can you try to switch from using the "wsdl" format to using the "singlewsdl" format?

    So if you used
    https://{yoururl}/Panopto/PublicAPI/4.6/SessionManagement.svc?wsdl

    Now try to use
    https://{yoururl}/Panopto/PublicAPI/4.6/SessionManagement.svc?singlewsdl

    That should help, and if it doesn't please open a support ticket so we can investigate further.

    I hope that helps.

    Thanks.

    Adis

Answers

  • Charles BarbourCharles Barbour Superstar

    Did you ever get any update on this? Is it still happening?

  • Trevor HughesTrevor Hughes Tyro

    The change from ?wsdl to ?singlewsdl appears to have resolved the issue. With the nature of this issue being inconsistent I'm reluctant to say it's fully resolved until we have time to monitor the code change for a while. But we implemented the code change and our next 3 scheduled runs were error-free. So that's a step in the right direction.

  • Trevor HughesTrevor Hughes Tyro

    I've reviewed our logs related to this script and it has been running error-free since the code change Adis suggested.

Sign In or Register to comment.