KB‎ > ‎

Visio has reported an unanticipated exception when exporting to HTML

 This article is suitable for a Library Administrator

Ref: 201004301658 
Last Edited: April 4th, 2013
Development Ref: 70
 
Symptoms:
When exporting to HTML, Visio crashes, and an error is usually reported in the publication logs (if running an automated publication) or in the progress windows (if running Process Navigator interactively).
30/04/2010 17:05:11
Visio has reported an unanticipated exception when exporting to C:\Documents and Settings\Administrator\My Documents\Process Navigator\HTML\html export test\55-50xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.50yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy
.html
=== Begin For Triaster Support ===
The following content may be useful to the Triaster support team.
Please copy and paste it into an e-mail to
support@triaster.co.uk
and attach any referenced files if you would like help understanding
how to avoid this issue reoccurring.
The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT))
Visio has reported an unanticipated exception when exporting to C:\Documents and Settings\Administrator\My Documents\Process Navigator\HTML\html export test\55-50xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.50yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy
.html
System.Runtime.InteropServices.COMException (0x80010105): The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT))
   at Microsoft.Office.Interop.Visio.PageClass.Export(String FileName)
   at Triaster.ProcessNavigator.Common.ProcessObjects.PageBase.CreateHTMLFile(String strMultiMapRoot, String strTargetRoot, enumVisioVersion lngVisioVersion, Boolean blnUseSubFolders, Boolean blnUseVisio2002MouseOver, Boolean blnUseDescriptionMouseOver, Boolean blnConvertHyperlinkCircleLinks, String strHTMLMapName)
=== Finish For Triaster Support ===
 
Further errors may be reported, as Visio is unable to run properly. Consequently, no further maps will be published.
 
Note:
Although an error report is expected, we have seen a progress log where there was no such message. In that case, the Export to HTML task listed only the problem file, and then appeared to end, suggesting no further files were exported.
 
Cause:
The combination of a file name (excluding its '.vdx' extension) and the name of one or other of its pages exceeds 99 characters.
When exporting to HTML using a frameset, Visio crashes when trying to export such a page. A Triaster publication will use a custom frameset when exporting.
 
Solution:
Shorten the file and/or page names so that their combined length is a maximum of 99 characters.
Ensure there isn't a dead Visio.exe process remaining on the publishing computer, as described here.
In Process Navigator 10.1.11, the Export to HTML routine has been altered so that only those process map files that create HTML equivalent files of length 99 characters or less are exported. No attempt is made to export other files, but an entry is made in the User Actions Required log of which files are affected.
The Report Exchange contains a new version of the Publish Checklist report. This new Publish Checklist lists those files that are affected by the limitation on file name length.
 
Applies to:
  • Visio 2003, Visio 2007
  • Process Navigator - all versions                 Fixed in PN 11.2
 
Related Articles:

Need further help? Contact the Triaster Support team by e-mailing support@triaster.co.uk or by calling us on 0870 402 1234.
 
Do you have any feedback or suggestions that you would like to share with Triaster? We would love to hear from you! Please e-mail feedback@triaster.co.uk