I have found the issue – it is something that can be solved with the user application – it doesn’t require a hot fix.The issue is with the M tolerance of the Route FC that is created in the clients applicationDefinition: M tolerance and Z tolerance are extremely small values that define the minimum distance between M values and Z values before they are considered equal ('clustered') by spatial processing operations. Coordinates containing M or Z values whose distance from each other are within the M or Z tolerance of each other will be will be given the same M or Z value. The Route FC being created by their application has an M Tolerance of 2. With this Route FC, as you said over 3000 events did not display because of Zero_length line errors. This is because the events are 2 measure units or less… and therefore, based on the M tolerance of 2, were being collapsed.To confirm this I created a new FC with a Tolerance of 0.0001 and displayed the events… only 18 events displayed with Zero_length line errorsSo – this means that when your client is defining the spatial reference in the code – they can also set the Mtolerance to an appropriate value for their data… and then get the results they are looking for.The methods they can user are --> IspatialReferenceTolerance::Mtolerance <a href="http://edndoc.esri.com/arcobjects/9.2/ComponentHelp/esriGeometry/ISpatialReferenceTolerance_MTolerance.htm" target="_blank">http://edndoc.esri.com/arcobjects/9.2/ComponentHelp/esriGeometry/ISpatialReferenceTolerance_MTolerance.htm</a>--> IspatialReferenceTolerance::SetMinimumMTolerance <a href="http://edndoc.esri.com/arcobjects/9.2/ComponentHelp/esriGeometry/ISpatialReferenceTolerance_SetMinimumMTolerance.htm" target="_blank">http://edndoc.esri.com/arcobjects/9.2/ComponentHelp/esriGeometry/ISpatialReferenceTolerance_SetMinimumMTolerance.htm</a>