crash on publish with chinese characters

Aug 03, 2014

hi,

im getting a crash when I try to publish a slide that contains chinese characters. below is the bug report.

thanks

<?xml version="1.0" encoding="utf-16"?>
<ErrorReport xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<ReportType>Error</ReportType>
<ApplicationName>Articulate.Presenter</ApplicationName>
<Version>7.2.1402.2817</Version>
<SerialNumber />
<Enterprise>false</Enterprise>
<Email />
<Date>2014-08-04T11:18:22.2878184+10:00</Date>
<Message>Exception has been thrown by the target of an invocation.</Message>
<Source>mscorlib</Source>
<StackTrace>System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.NotImplementedException: Not implemented (Exception from HRESULT: 0x80004001 (E_NOTIMPL))
--- End of inner exception stack trace ---
at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)
at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args)
at Articulate.Presenter.Common.Reflection.ReflectedComCall.InvokeMember(Object comWrapper, String memberName, BindingFlags bindingFlags, Object[] args)
at Articulate.Presenter.Common.Reflection.ReflectedComCall.GetProperty[T](Object comWrapper, String propertyName, Object[] args)
at Articulate.Presenter.Common.Reflection.ComObjectModelBase.get_Tags()
at Articulate.Presenter.Common.Reflection.ComObjectModelBase.SetTag(String tagName, String tagValue)
at Articulate.Presenter.Model.PowerPoint.ObjectModel.Shape.fk()
at Articulate.Presenter.Model.PowerPoint.ObjectModel.Shape.Duplicate()
at a.aa.e.b.h.r.d()
at a.aa.e.b.h.e.a(IPublishContext A_0, Shape A_1)
at a.aa.e.b.h.e.c(IPublishContext A_0, Shape A_1)
at a.aa.e.b.h.h..ctor(IPublishContext A_0, ba A_1, i A_2, Shape A_3, Shape A_4, bwVectorData A_5, RectangleF A_6, Int32 A_7, Int32 A_8)
at a.aa.e.b.d.a9.o(IPublishContext A_0, bwVectorData A_1, RectangleF A_2, Int32 A_3, Int32 A_4, s A_5)
at a.aa.e.b.d.a9.o(IPlayerService A_0, IPublishContext A_1, s A_2, bwVectorData A_3, String A_4, bwTextData A_5, RectangleF A_6, Int32 A_7, Int32 A_8, Boolean A_9)
at a.aa.e.b.d.a9.p(IPlayerService A_0, IPublishContext A_1, bwVectorShape A_2, bwVectorData A_3, RectangleF A_4, Int32 A_5, Int32 A_6)
at a.aa.e.b.d.a9.p(IPlayerService A_0, IPublishContext A_1, s A_2, bwVectorShape A_3, bwVectorData A_4, RectangleF A_5, Int32 A_6, Int32 A_7)
at a.aa.e.b.d.i.b7(IPlayerService A_0, bwVectorShape A_1, IList`1 A_2, s A_3)
at a.aa.e.b.d.i.b7(IPlayerService A_0, bwSlideBase A_1)
at a.aa.e.b.d.i.cn(IPlayerService A_0, bwSlideBase A_1)
at Player.PlayerWriter.m(IEnumerable`1 A_0, bwSlideBase A_1)
at Player.PlayerWriter.m(IPlayerSlide A_0, bwISlideContainer A_1)
at Player.PlayerWriter.WriteContent(IPlayerContentProvider contentProvider, Boolean merged)
at Player.PlayerWriter.Write(IPlayerContentProvider contentProvider)
at Articulate.Design.Publish.TargetContext.PublishBackgroundWorker.OnDoWork(DoWorkEventArgs e)
at Articulate.ComponentModel.STABackgroundWorker.a(Object A_0)</StackTrace>
<FlashVersion>WIN 11,7,700,202</FlashVersion>
<PrivateMemory>148,816 K</PrivateMemory>
<VirtualMemory>650,248 K</VirtualMemory>
<OSVersion>Windows 7 6.1.7601 Service Pack 1</OSVersion>
<CLRVersion>2.0.50727.5477</CLRVersion>
<ProcessorCount>4</ProcessorCount>
</ErrorReport>

2 Replies
Steven Strell

Are the characters in a table and you're using update 2? This is a known bug. You have to right-click the table and turn it into an image, then delete the table and insert the image. Supposedly this is fixed in update 3, but since update 3 crashes every time I click any button on the Articulate ribbon, I can't confirm that it's fixed.

Steve

This discussion is closed. You can start a new discussion or contact Articulate Support.