I am getting this error when i am trying to add Ad Breaks a VMAP Ad URL.
I tested with the doubleclick ad server.
When the VAST INLINE reponse from the ad server provides a MediaFile withe the mime-type "application/x-mpegURL", the Cast SDK throws and error 104.
Find below some logs :
app.js:1433 MediaCast.onPlayerLoadComplete
app.js:1433 sendStreamInformation: {"version":1,"action":"stream_information","duration":2108}
cast_receiver_framework.js:116 [ 6.103s] [cast.framework.media.util] cannot guess mime type from given contenId/Type. Assume that this is video/mp4
th # cast_receiver_framework.js:116
2app.js:1433 Media Manager MEDIA STATUS
app.js:1433 MediaCast.onLoadStart
app.js:1433 MediaCast.setState LOAD
app.js:454 ---> STATE :: LOAD
app.js:1433 MediaCast.isMediaState
app.js:1433 MediaCast.clearTimerState
cast_receiver_framework.js:116 [ 6.219s] [StitchingPlayer] player event: break clip error
cast_receiver_framework.js:116 [ 6.224s] [cast.receiver.MediaManager] Sending error message to :
app.js:1433 Media Manager ERROR: {"type":"ERROR","detailedErrorCode":104}
app.js:1433 MediaCast.onError
It seems to be case sensitive issue. When i try with an other static URL where i can change the type to "application/x-mpegurl", it works.
In SDK Cast, i do not find an api to set the list of accepted mime-types.
Have someone already experienced this error ?
Best regards,
kaderdib
Related
I'm running an SAP PI/PO scenario and having a problem with finding the response message (the error one).
Scenario:
PROXY (class) -> SAP PI/PO 7.5 -> SOAP (wsdl)
The error when executing the scenario is:
Transmitting the message using connection
SOAP_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
Error encountered while executing mapping:
com.sap.aii.af.service.mapping.MappingException:
com.sap.aii.utilxi.misc.api.ResourceException: Could not determine
mapping steps for message 3b14b3f8-0860-11ed-a034-000001795062
The problem is that I cannot find the message (3b14b3f8-0860-11ed-a034-000001795062) in SAP PI monitor. It's the response message (who is causing the error), as the request message I did find in the monitor and it's correct.
Where I can find it? Why is not showing?
From what I read, this problem happens with several reasons, I just want to find this message.
The webservice works correctly, I test it in SOAP UI.
To find the response message (which contains the error), we have to first activate the Integrated Configuration log (it's not active by default).
To activate the log, we have to follow these steps (more info: https://blogs.sap.com/2012/11/06/message-staging-and-logging-options-in-advanced-adapter-engine-of-pi-73x/)
Go to "Advanced Settings" in the target Integrated Configuration.
Change the "Use global configuration" radio button to "Use scenario-specific configuration" in both, "Staging" and "Loging".
Change all "Staging" lists to "Store".
Change all "Logging" lists to "Log".
Save and activate.
Now, in the SAP PO monitor (Message monitor), by clicking the "Related Messages" option, we can see the response message error.
In this case, the error was:
<sap:Error xmlns:sap='http://sap.com/xi/XI/Message/30'
SOAP:mustUnderstand='1'>sap:CategoryXIAdapter</sap:Category><sap:Code
area='SOAP'>FAULT</sap:Code>sap:P1http://schemas.microsoft.com/ws/2005/05/addressing/none</sap:P1>sap:P2ActionNotSupported</sap:P2>sap:AdditionalTextThe
message with Action '' cannot be processed at the receiver, due to a
ContractFilter mismatch at the EndpointDispatcher. This may be because
of either a contract mismatch (mismatched Actions between sender and
receiver) or a binding/security mismatch between the sender and the
receiver. Check that sender and receiver have the same contract and
the same binding (including security requirements, e.g. Message,
Transport, None).</sap:AdditionalText><sap:ApplicationFaultMessage
namespace='http://schemas.microsoft.com/ws/2005/05/addressing/none'>ActionNotSupported</sap:ApplicationFaultMessage></sap:Error>
In which the Action was empty.
I'm using AWS Media Tailor to test an ad inserting demo. The demo page is this one: https://github.com/aws-samples/aws-media-services-simple-vod-workflow/tree/master/12-AdMarkerInsertion.
When I place my manifest into a TheoPlayer I always get an 504 error. My manifes page is: https://ebf348c58b834d189af82777f4f742a6.mediatailor.us-west-2.amazonaws.com/v1/master/3c879a81c14534e13d0b39aac4479d6d57e7c462/MyTestCampaign/llama.m3u8.
I have also tried with: https://ebf348c58b834d189af82777f4f742a6.mediatailor.us-west-2.amazonaws.com/v1/master/3c879a81c14534e13d0b39aac4479d6d57e7c462/MyTestCampaign/llama_with_slates.m3u8.
The specific error is:
{"message":"failed to generate manifest: Unable to obtain template playlist. sessionId:[c915d529-3527-4e37-89e0-087e393e75de]"}
I have read about this error: https://docs.aws.amazon.com/mediatailor/latest/ug/playback-errors-examples.html
But don't know how to fix it.
Maybe I did something wrong or do I need a quote in AWS?
Any idea?
Thanks for the inquiry!
The following example shows the result when a timeout occurs between AWS Elemental MediaTailor and either the ad decision server (ADS) or the origin server.
An HTTP 504 error is known as a Gateway Timeout meaning that a resource was unresponsive and prevented the request from completing successfully. In this case since MediaTailor is returning an HTTP 504 this means that either the ADS or Origin failed to respond within the timeout period.
To troubleshoot this you will need to determine which dependency is failing to respond to MediaTailor and correct it. Typically the issue is the ADS failing to respond to a VAST request performed by MediaTailor which you can confirm by reviewing your CloudWatch logs.
https://docs.aws.amazon.com/mediatailor/latest/ug/monitor-cloudwatch-ads-logs.html
Make sure that your ADS follows the guidelines listed below for integrating with MediaTailor.
https://docs.aws.amazon.com/mediatailor/latest/ug/vast-integration.html
I have created a Talend job and deployed it as a Axis Web Service.
I am calling this Web Service from my Web Application.
My application and web service are deployed over Tomcat server.
For Valid Inputs:
Runs Perfectly.
For Invalid Inputs:
It throws Error/exceptions in Tomcat Server.
I want this Errors into my application. I didn't get any error related information in the Response sent by web service.
Error message on Tomcat Server
XML response of Web service
If I understand your question you are not so much asking how to fix this error, but how to get feedback about your error. There are several ways but here is a simple method.
Add a tLogCatcher to your job, and point its output to a tSendMail component. You can run the output thru a tMap do things like adding HTML formatting. You can also create a joblet with these two components and use the joblet in every job so you do not have to recreate it every time.
The diagram below shows a real simple case where I add tLogCatcher and tSendMail directly to the job. When there is an error it will send me an email with the details. You can use any of the columns in row11, I am only using job and message in my example.
This error : For input string "fabrik"
is generated by the tFileInputExcel component when encountering a non valid field (expected : integer ; given : string). You can't directly catch this error with the tFileInputExcel component (it's just printed out on the console).
However, you can use a tSchemaComplianceCheck component after your tFileInputExcelComponent : it will throw an error if a data is not valid for your schema. This component has a reject link to catch the error.
tFileInputExcel->tSchemaComplianceCheck->tMap->tMSOutput
If you use tLogCatcher component to catch the error then, at the end of the flow, you can add a tBufferOutput component. Keep the fields with the information you want for.
component configuration
The result will be like this (note that they are shown in the same order):
result
My situation:
I create via OTRS Admin Backend a custom webservice:REST
added an custom invoker on GenericInterface::Invoker::ModuleRegistration
added new invoker:REST Event-Trigger: TicketSlaveLinkAdd
configured otrs as requester HTTP::REST Host as: http://myhost.com
controller mapping: /LinkAdd/:TicketID
standard command: PATCH
My Problem:
System Log returns:
DebugLog error: Summary: HTTP::REST Error while determine Operation for request URI '/LinkAdd'. Data : No data provided.
DebugLog error: Summary: Request could not be processed Data : HTTP::REST Error while determine Operation for request URI '/LinkAdd'..
DebugLog error: Summary: Returning provider data to remote system (HTTP Code: 500) Data : HTTP::REST Error while determine Operation for request URI '/LinkAdd'..
Maybe somebody know about my problem and can help :)
The Error while determine Operation text points out that OTRS is the incoming call is not able to determine the Operation for the incoming URI; please check your data mapping.
I'm using MPGW service which will hit the CICS service and return back the response.
This is my flow. UI --> DP MPGW gateway --> MPGW Service --> CICS service.
In case of "No data Found" response from CICS, I just want to set the error code as 100 and message as "No data found" and pass on to UI. But everytime datapower is return 500 Internal server error to UI.
I'm using errorHandler.xslt to check the fault code from CICS and setting the error code and error message.
Is there something I need to change the dp:response-header('x-dp-response-code')? If so how to do this?
Note: Process Backend error : 'On' in both the MPGW(gateway and service).
Try this:
If a response contains 500 not found error. Do a dp:reject at the response rule.This will take control to error rule. At error rule, configure an xslt and set below values:
<dp:set-variable name="'var://service/error-protocol-response'" value="'100'" />
<dp:set-variable name="'var://service/error-protocol-reason-phrase'" value="'No Data Found'" />
As per https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014432297 you want:
Within an Error Rule:
Within a Response Rule:
That should do the trick for an MPGW I believe.