Ref: 201011231014
Last Edited: August 18th, 2011
Development Ref: 80 Fixed in PN 11.1
Symptoms:
When a map is opened in Visio, the following error is reported:
23/11/2010 10:08:21
Object reference not set to an instance of an object. An error occurred in the VisEventProc event === 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. An error occurred in the VisEventProc event System.NullReferenceException: Object reference not set to an instance of an object.
at Triaster.ProcessNavigator.Common.ProcessObjects.Relationship.InitSecondaryProperties() at Triaster.ProcessNavigator.Common.ProcessObjects.Map.AddMapPage(Page pagObj, Boolean blnEnableUpgrade) at Triaster.ProcessNavigator.Common.ProcessObjects.Map..ctor(Document& docObj, Boolean blnEnableUpgrade) at Triaster.ProcessNavigator.Common.ProcessObjects.Maps.Add(Document docArg, Boolean blnEnableUpgrades, String strFullPathAndFileName) at Triaster.ProcessNavigator.Common.ProcessObjects.Maps.Add(Document docArg, Boolean blnEnableUpgrades) at Triaster.ProcessNavigator.Common.ProcessObjects.DocumentsBase.Add(Document docArg) at Triaster.ProcessNavigator.MappingEdition.Wrapper.clsAppEventSink.HookDocument(Document docObj) at Triaster.ProcessNavigator.MappingEdition.Wrapper.clsAppEventSink.VisEventProc(Int32& eventCode, Object& sourceObj, Int32& eventID, Int32& seqNum, Object& subjectObj, Object& moreInfo) === Finish For Triaster Support === An error dialog may also be displayed.
Cause:
One or more shapes have connection points (small blue crosses) in positions not expected by Process Navigator.
Extra connection points can be added to Activities and Deliverables through their Properties dialogs. Through this mechanism, connection points are distributed evenly along the sides. However, connection points can also be added through Visio's own connection point tool, and in positions that Process Navigator doesn't handle properly, which can result in this error.
Solution:
Connection points in such positions need to be removed, and perhaps replaced with others through Process Navigator shapes' Properties dialogs.
The whole shape could be deleted and replaced, but consider attributes such as drill-down behaviour and properties that would need to be reset.
Managing connection points through the ShapeSheet, as described here, can be difficult, depending on the complexity of the formulae used. The following example is a relatively simple one, but if yours is more complex, or if you are not confident about this procedure, contact support@triaster.co.uk for help.
Tips for identifying a problem shape
If may not be obvious which shape causes the error, particularly if the map contains multiple pages and/or many shapes.
Applies to:
Related articles:
|
KB >