06-24-2018 09:23 AM
Hi,
After recovering some recordings from the recycling bin, and calling the "downloadNBRStorageFile" method from NBR Web Services API with the recovered recording-id, the server respond whit a status 500 and a fault string "Can not create ARF.".
Any ideas?
Many thanks!
XML request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns1:downloadNBRStorageFile xmlns:ns1="NBRStorageService" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<siteId xsi:type="xsd:long">******</siteId>
<recordId xsi:type="xsd:long">******</recordId>
<ticket xsi:type="xsd:string">******</ticket>
</ns1:downloadNBRStorageFile>
</soapenv:Body>
</soapenv:Envelope>
XML Response:
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>Can not create ARF.</faultstring>
<faultactor>NBRStorageService</faultactor>
<detail>
<ns1:exceptionName xmlns:ns1="http://xml.apache.org/axis/">com.webex.webservice.nbr.xmlhelper.NBRException</ns1:exceptionName>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Solved! Go to Solution.
06-25-2018 05:26 PM
Thanks,
I think this will show that the NBR API isn't necessarily the faulty part of the equation, it serves to reason that the ARF cannot be packaged because the recording has become corrupted in some way. I can really only guess at the explanation of any corruption, NBR is a collection of multiple pieces of data when stored in the WebEx cloud and moving that data to the recycle bin may not be as simple as moving a file in a directory tree or setting an inactive flag in a database table. It would be best to contact the technical support team via the contact methods provided when signing in to http://support.webex.com, they may have previous experience with this exact issue, or have an established escalation procedure to correct corrupted recordings or create a bug report for recovered recordings. Feel free to refer to this forum thread, it is publicly accessible.
06-25-2018 11:14 AM
Hello,
I have seen this error in the past when the recording owner account has been deactivated. There could also be an issue with the record ID, depending on how you are retrieving it. You may try calling the NBR API request getRecordIdList to see if your record ID is present in the list. You may also try calling XML API request lstRecording with one or more serviceType values specified, and again with no serviceType element to try the differing record IDs that it provides. Unfortunately, the error doesn't provide much information to go on, other than some data is missing from the record entry to properly package the ARF file for download.
06-25-2018 03:53 PM
Hi Nathan,
Thanks for your reply. The account has never been deactivated.
I actually get the Recording ID from the XML API LstRecording without the serviceTypes keys (we have separated sites for meeting and event). The getNBRRecordIdList response list the same Recording IDs.
I tried adding the serviceTypes key, the recording Names are the same, but the Recording IDs are different.
Calling downloadNBRStorageFile with the RecordingID from LstRecording whit serviceTypes key specified, gave me a "The recording you are looking for does not exist or is no longer available":
XML Response:
<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://ww
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server.userException</faultcode>
<faultstring>The recording you are looking for does not exist or is no longer available.</faultstring>
<faultactor>NBRStorageService</faultactor>
<detail>
<ns1:exceptionName xmlns:ns1="http://xml.apache.org/axis/">com.webex.webservice.nbr.xmlhelper.NBRException</ns1:exceptionName>
<ns2:hostname xmlns:ns2="http://xml.apache.org/axis/">nsj1wss226.webex.com</ns2:hostname>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
06-25-2018 04:26 PM
Hello,
Thanks for the additional information. There is one more thing I will need to know before I can recommend the best course of action. Are you able to manually download the same recording from the WebEx user interface? If so, do the lstRecording fileURL and streamURL both work and play back properly? If all yes, I will need to report to engineering on a possible NBR API bug. If all no, technical support may be a better resource to properly escalate as a corrupted recording that might be recoverable.
06-25-2018 05:08 PM
All no... "Archivo deshabilitado No se puede reproducir ni descargar esta grabación porque fue desactivada por el organizador."
Rough translation: "File disabled This recording can't be played or downloaded because it was deactivated by the organizer."
The weird part is "File disabled" only happens after recovering the recording from recycling bin, and WebEx user interface shows download and play enabled. Also the WebEx user interface shows 0.0 KB.
There is no direct interaction with the user interface, all recording management is done by the API client, and this issue happened in 2 different sites. All affected recordings are more than 40 days old.
06-25-2018 05:26 PM
Thanks,
I think this will show that the NBR API isn't necessarily the faulty part of the equation, it serves to reason that the ARF cannot be packaged because the recording has become corrupted in some way. I can really only guess at the explanation of any corruption, NBR is a collection of multiple pieces of data when stored in the WebEx cloud and moving that data to the recycle bin may not be as simple as moving a file in a directory tree or setting an inactive flag in a database table. It would be best to contact the technical support team via the contact methods provided when signing in to http://support.webex.com, they may have previous experience with this exact issue, or have an established escalation procedure to correct corrupted recordings or create a bug report for recovered recordings. Feel free to refer to this forum thread, it is publicly accessible.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide