KB‎ > ‎

Error 'Object reference not set to an instance of an object' when publishing

Ref: 201102111117
Defect ID: 2633371 
Last Edited: August 18th, 2011
 
 
Description:
When a map is being exported to HTML, an error is reported.

11/02/2011 10:03:20
Failure exporting C:\Triaster\Map Store\ProcessLibrary\2 Maps for Review\MyMap.vdx to 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.
Object reference not set to an instance of an object.
Failure exporting C:\Triaster\Map Store\ProcessLibrary\2 Maps for Review\MyMap.vdx to html.
System.NullReferenceException: Object reference not set to an instance of an object.
   at Triaster.ProcessNavigator.Common.ProcessObjects.DocumentBase.get_EngineVersion()
   at Triaster.ProcessNavigator.Common.ProcessObjects.Map.ExportToHTML
(String strTargetRoot, Boolean blnAddHeaderAndFooter, String strHeaderFileName, String strFooterFileName, enumHTMLMetaTagOptions lngMetaTagOptions, Boolean blnUseVisio2002MouseOver, Boolean blnUseDescriptionMouseOver, Boolean blnConvertHyperlinkCircleLinks)
   at Triaster.ProcessNavigator.AnalystEdition.clsExportToHTML.PerformExport(String strTargetRoot, Boolean blnIncludeHeaderAndFooter, String strHeaderFileName, String strFooterFileName, Boolean blnAddMetadata, Boolean blnIncludeProperties, Boolean blnUseVisio2002MouseOver, Boolean blnUseDescriptionMouseOver, Boolean blnConvertHyperlinkCircleLinks, Boolean blnExportModifiedFilesOnly)
=== Finish For Triaster Support ===

Note the information emphasised. It's this information that's pertinent to the scenarios described.
 
Possible Cause 1:
Visio doesn't have a key applied, or may not be activated. It's prompting for user action, and is unresponsive to automation commands. If it's running non-interactively, such as in an automated publication, this prompt won't be visible.

Workaround:
Ensure Visio has a valid key and is activated.
 

Possible Cause 2:
Visio has been configured to run as a specific user, but that user account is different from that which is running Process Navigator, from which Visio is launched.
Scenarios could be:
  • An automated publication, where the Visio user and the Publication user (i.e. the user that runs the 'PN Publication Wrapper' service) aren't the same.
     
  • Exporting to HTML from an interactive session of Process Navigator, being run under a different user account from the Visio user.

Workaround:
Ensure that Visio is being run under the same account as Process Navigator. See this article for details:

 Applies to:
  • All versions of Process Navigator, Visio and Windows.
Comments