This video file cannot be played.(Error Code: 224003) when clicking preview on a MP4 video
Problem reported by Hasegawa Hironori - 11/28/2019 at 4:26 PM
Not A Problem
Hi,

We got reports from one of our users when previewing video on File Ultimate the user was prompted with a error message "This video file cannot be played.(Error Code: 224003)". This only happens on Microsoft Edge and IE 11.

Please advise if any workaround to fix this problem?

Thank you

8 Replies

Reply to Thread
0
Cem Alacayir Replied
Employee Post
The video player depends on browser's HTML5 video codec support. For example, MP4 videos using the H.264 video codec and the AAC audio codec should be played in all browsers and devices. So what's the codecs used in your MP4 file? It may be played on Chrome but not on Edge or IE11.
0
Hasegawa Hironori Replied
Below is the Media information. Is this format not supported?
0
Cem Alacayir Replied
Employee Post
Your MP4 info looks ok, however Microsoft's decoder may be picky, see here:

It may be related to this:

It was due to IE Document-mode version too low. Press 'F12' and using higher version( My case, above version 9 is OK)
Though FileUltimate automatically adds

<meta http-equiv="X-UA-Compatible" content="IE=edge">
to the host page, maybe your page overrides it with a header?

Did you test your file with the live demo?
The MP4 files I testes works on IE11 and Edge.

0
Hasegawa Hironori Replied
I have tested the live demo on IE11 and they are working fine for the MP4 video.
As you have mentioned I have removed some meta in header and managed to solve for the test site. 
But once I published to the official site I'm still not able play video.
I have captured the console  in IE11 developer tools. but I don't quite understand this errors. These errors do not appear on the test site.

Just for your info the two site are a sub site of the main domain. Which means they are using the same codes.

Thank you
0
Hasegawa Hironori Replied
Looking in the to developer tools --> network there was a internal server error. 

If I copied this link  and paste it to the browser I got the following error.

I'm using File Ultimate why is it asking for the Document Ultimate assembly?
I have already registered file ultimate on the html also
0
Cem Alacayir Replied
Employee Post
In the error message I see "GleamTech.DocumentUltimate, Version=4.5.5.0", this is an old version which means you are also using old version of GleamTech.FileUltimate which binds to this DLL.

Update FileUltimate to the latest version 7.3.2, you already have a license key for 7.x:

Renamed nuget package to "GleamTech.FileUltimate".From now on, same package names will be used for both get.gleamtech.com feed and nuget.org feed (no .NuGetOrg suffix).Please uninstall all GleamTech packages with old names and install the ones with the new names.In Visual Studio: Go to Tools -> NuGet Package Manager -> Package Manager Console and run these commands one by one in order:

Uninstall-Package FileUltimate -RemoveDependencies
Uninstall-Package FileUltimate.NuGetOrg -RemoveDependencies
Install-Package GleamTech.FileUltimate
If you are using direct DLL references, note that the dependency assembly "GleamTech.Core" is renamed to "GleamTech.Common".So in this case, first clean your project, remove references to old assembly, add references to new assembly and build your project.


Regarding DLLs:

The other DLLs in the same folder, i.e. GleamTech.ImageUltimate.dll, GleamTech.VideoUltimate.dll and GleamTech.DocumentUltimate.dll are assemblies that FileUltimate depends on for some of the features. They are separate assemblies as they are also standalone products with the same names. MSbuild or Visual Studio will automatically copy these 3 DLLs along with the main referenced assembly GleamTech.FileUltimate.dll to your bin folder during build so they don't need to be referenced directly (unless you are using these products separately in the same project and you have a license for them). Note that even without these 3 DLLs, FileUltimate will work but it will just turn off the corresponding features such as generating image or video thumbnails or the document viewer. So with this modular approach, you can opt-out of the features you do not need by excluding the corresponding DLL, i.e. MSBuild or Visual Studio would automatically copy a dependency only if that DLL is found in the same folder as the main referenced DLL so you can simply delete a DLL in the extracted folder to opt-out.
0
Hasegawa Hironori Replied
I have followed your insttruction to uninstall the file ultimate. Followed by installation of the newer file Ultimate.

After installation i checked the reference of the Visual Studio

but when run the application i'm getting a new error.


0
Hasegawa Hironori Replied
After some checking noticed there is the GleamTech.Core still in the Bin folder after removing it the above error disappeared but getting parse error which seem to be still referencing to the GleamTech.Core still. In the below page i have this mark up:
<%@ Page Title="" Language="vb" AutoEventWireup="false" MasterPageFile="~/Site.Master"
    CodeBehind="DownloadOfficialAnnouncement.aspx.vb" Inherits="CBDesign.DownloadOfficialAnnouncement" %>

<%@ Register TagPrefix="GleamTech" Namespace="GleamTech.FileUltimate" Assembly="GleamTech.FileUltimate" %>
<%@ Register TagPrefix="GleamTech" Assembly="GleamTech.FileUltimate" Namespace="GleamTech.FileUltimate.AspNet.WebForms" %>
<asp:Content ID="Content2" ContentPlaceHolderID="MainContent" runat="server">
   
    <br />
    <GleamTech:FileManagerControl ID="fileManager" runat="server" SortRootFolders="True"
        Width="1307px" />
</asp:Content>







Reply to Thread