1
Exception error on view ppt or pptx file via documentViewer
Problem reported by Liang Liu - 9/6/2017 at 8:40 PM
Resolved
Hi,
I purchased DocumentUltimate and use it in my website. When view a ppt or pptx file via documentViewer, it is crashed.
 
The exception message as below:
Error
“_pEc”的类型初始值设定项引发异常。
---> “_XyE”的类型初始值设定项引发异常。
---> “_XyE”的类型初始值设定项引发异常。
---> “_b1E”的类型初始值设定项引发异常。
---> “_b1E”的类型初始值设定项引发异常。
---> “_ADF”的类型初始值设定项引发异常。
---> “_ADF”的类型初始值设定项引发异常。
---> 未将对象引用设置到对象的实例。
 
I'm sorry the message is Chinese, so I transfer to English via translation software as below
 
The type initializer of _pEc causes an exception.
The initial value of "_XyE" type I set a exception.
The initial value of "_XyE" type I set a exception.
The initial value of "_b1E" type I set a exception.
The initial value of "_b1E" type I set a exception.
The initial value of "_ADF" type I set a exception.
The initial value of "_ADF" type I set a exception.
The object reference is not set to an instance of the object.
 
 
There are some information need to let you know:
1, I try it on few servers, just crashed on only one server, other servers are successed.
2, All of server's OS is Windows Server 2008 R2 Enterprise.
3, On the problem server, it will be crashed when view all of ppt or pptx file, not specific file.
4, On the problem server, view all of file except ppt(x) is success. 
5, Already update to version 3.5, the problem still exist.
6, Fonts are the same on all of server.

6 Replies

Reply to Thread
0
Cem Alacayir Replied
Employee Post
Hi,
I suspect this error may happen due to different culture of the server (Windows Culture). Please add the below setting in your web application's Web.config file:
 
<system.web>
    <globalization culture="en-US" />
</system.web>
Basically we are forcing English culture and overriding the server's default culture (e.g. Chinese). If it works with this setting on the problem server, then it proves the error is related to culture.
 
Note that I can not replicate the error when I override culture with Chinese on an English server . It seems it only happens on a Chinese server. It may be related to .NET Framework version (e.g. unpatched .NET 4.0, the last patch was .NET 4.0.3) or the localization packages included in non-english Windows installations.
 
Let me know your findings and we will fix it.
0
Liang Liu Replied
I set the culture to en-US, the problem still exist.
by the way, my web site need .Net 4.0, so I'm sure install .Net 4 on the problem server.
0
Cem Alacayir Replied
Employee Post
Of course you have .NET 4.0, I was talking about PATCHES for .NET 4.0 specifically this one:

Run this command on your problem server to see which exact .NET 4.0 minor version is installed:
reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\full" /v version
Then you can run it also on other servers and compare the version.
0
Liang Liu Replied
Already run the command on two servers. The problem server is 4.6.00081, another(this server can view ppt) is 4.5.51209.
Is there some bug in 4.6.00081?
0
Cem Alacayir Replied
Employee Post
Please test the latest version and let me know:
Version 3.14.0 - March 24, 2018
  • Fixed: Word-Processing and Presentation file format support:

    • Some DOCX files were causing infinite loop and failing to convert or display.

    • PPT/PPTX files with asian fonts were causing an error on some machines and failing to convert or display.

  • Fixed: "Any word" search still did not find results when keywords had more than 1 hyphen in-between (e.g. "24-3-2018").

0
Cem Alacayir Replied
Employee Post
For future reference;
This error can also be caused by .NET Framework January 2018 Security and Quality Rollup (KB 4055002)

Windows Presentation Foundation (WPF) applications that request a fallback font or a character that is not included in the currently selected font return the following error messages:

System.TypeInitializationException
 
“FileFormatException: No FontFamily element found in FontFamilyCollection
that matches current OS or greater: Win7SP1”.

Inner exception originates from: CompositeFontParser
To fix it please install Fixit tool for KB4074906

Reference:



Reply to Thread