|ID||Activity or Function||Issue||Workaround||Module||10.3.1||10.4.1||10.5||10.5.1||10.6.1||Plan||Submit by||Priority|
|Bug-000101699||Export Network Service||The Export Network tool does not get the latest geodatabase version state when executed as a service.||Change the recycle frequency of the GP Service to minimize the impact of the issue in the current environment.||Server|
|BUG-000110742||Realign||Realigning a route to create a gap calibrates the To Measure on event incorrectly||Desktop||@fixed||NCDOT||Medium|
|BUG-000106791||ArcMap Symbology||Creating a layer from the Create Layer From Selected Features option does not honor the selection and displays all the features.||Desktop||fixed||resolved||NCDOT||high|
|Export Network Service||Tool fails to run if there is a complex route concurrency (one loop, one lollipop, plus a typical route shape that is partially concurrent with the loop and lollipop routes) across different time slices . Previous thought bug was due to Production Mapping being installed in ArcGIS Desktop 10.5, but that is not the case||Remove route concurrency by reassigning to bogus route id or retiring||Server||found patch 1||fixed||NCDOT||high|
|Network Edit - Reverse Route||Reverse Route causes calibration point measures to change beyond 6 decimal places.||Manually edit calibration point and recalibrate downstream||Desktop||found||fix||NCDOT||high|
|NCDOT case 01889567||Relocate Events Service||Relocate events service stretches events beyond end of route. The issue relates to a defect that is fixed in 10.5.1. However, cartographic realignments done in Roads and Highways pre-10.5.1 with the condition that there is more than one calibration point downstream of the edit will exhibit the symptom in this support incident. Edits on 10.5.1 of Roads and Highways will not have this symptom. Hotfix estimated August 4, 2017 that will mask the symptom of pre-10.5.1 cartographic realignment edits from external systems, such as AgileAsset’s system(s)||Server||found||hotfix*||NCDOT|
|Route Edit - extend, realign||Extending a route to create a concurrency then realigning the other route to remove the concurrency on the same date results in incorrect event behaviors for the non-concurrent events on the realigned route||Use reassign instead of extend if possible||Desktop||found patch 4||exists||exists||fix||NCDOT||high|
|Route Edit - Reverse, Reassign||Reverse and Reassign to Create Gap Causes Measures Downstream From Gap to be Incorrect. Issue also occurs doing a reverse and retire to create a gap||Reassign, then reverse if possible||Desktop|
|Realign, Cartographic Realignment||Realign then cartographic realignment results in retired routes becoming NaN. Cartographic realignment of route at new alignment (retired route becomes NaN); Cartographic realignment of route at old alignment (active route becomes NaN); Possibly fixed in 10.4.1 (based on testing at 3rd party vendor site)||Use Generate Route GP Tool on NAN routes (need to refresh version and verify measures correctly added to route - NCDOT has seen this tool not work correctly)||Desktop|
|Retire, Cartographic Realignment||Retire to create gaps then cartographic realignment results in routes becoming NaN.||Use Generate Route GP Tool on NAN routes (need to refresh version and verify measures correctly added to route - NCDOT has seen this tool not work correctly)||Desktop|
found patch 4
|Reassign, Cartographic Realignment||Reassign then cartographic realignment results in retired routes becoming NaN. Retired and active routes become NaN.||Use Generate Route GP Tool on NAN routes (need to refresh version and verify measures correctly added to route - NCDOT has seen this tool not work correctly)||Desktop|
|Extend, Cartographic Realignment||Extending a route, and performing a cartographic realignment on the extended portion results in a Not a Number (NaN) calibration||Desktop|
|Launch a URL (i.e. instance of RCE) from Workflow Manager Online||ArcGIS Workflow Manager for Server opens browser (IE) in server when executing Launch URL step in a client environment. Causes server instability. ArcGIS services become unresponsive. Database validation fails for datastores||Dynamically examine the memory usage and periodically eliminate the ‘zombie’ server processes; alternatively, reboot server.||server|
|Realign, Retire||Realigning a route to create a concurrency followed by retiring the other route to eliminate the concurrency on the same date results in the snapped events getting incorrect measures.||Use reassign instead of realign if possible||Desktop|
NCDOT case 01888502
|Calibration||Vertex measures flip when recalibrating||none||Desktop|
NCDOT case 01904018
|Add Machine to an ArcGIS Server site||After upgrading an ArcGIS 10.3.1 site to 10.5, the Add Machine operation fails with error: "\relational-datastore-types" folder cannot be located||Using Windows commands on the config-store file share, create an empty file folder in the config-store named "relational-datastore-types". Proceed normally with adding the new machine.||Server||found||?||?||not in plan||NCDOT||High|
|Reassign or Retire||Retire or Reassign route to create gap causes the ends at the gap to have same measures even though Euclidean Distance has been set. This issue is not in 10.3.1 Patch 4.||Desktop||found||not in plan||NCDOT||Medium|
NCDOT case #01906828
|Realign, Cartographic Realignment||Events shift downstream of realignment if a cartographic realignment is subsequently performed||Desktop||found||not in plan||NCDOT|
|Display Route Events||Display Route Event tool maps 2 event items with identical log values to 2 different LRS measured vertices (2 events log = 1.335 but 1 gets mapped to 1.335 other is 1.334||In LRS processes leading up to Display Route Event tool needs, increase the M-value scale by 1 (chang from 0.001 to 0.0001)||Desktop|
|exists||exists||exists||exists||not in plan||Ohio DOT|
|Undefined Editing Error||Upon running a linear overlap validation tool in desktop (built by Transcend Spatial) we are discovering where records are being duplicated behind the scenes. This tool is designed to check specified tables for gaps and overlaps. By design R&H extension should not cause gaps and overlaps to occur and thus there is an underlying flaw yet to be identified.||Weekly run of this tool followed by manual editing to correct the issues||Desktop|
|exists||exists||exists||exists||not in plan||Ohio DOT|
|Bug||Add Calibration Point||Identified a situation where a new calibration point was added along an existing route (around the 1 mile mark) in desktop. As a result of the desktop edit we found in RCE a record (0.00-0.633) in an event table was retired incorrectly. Upon noticing this we removed the retired date to bring back the incorrectly retired record. The next day we discovered there were 2 records in the event table for the same segment (0.00-0.633)||Manual delete of the newly duplicated record to retain a single record that correctly exists and isn't retired||RCE/Event Editor||found||exists||exists||exists||exists||not in plan||Ohio DOT|
|Bug||Same Location Calibration Points Identical Measure Value||Multiple Calibration Points at the same location with the same measure deleting 1 of the CP's causes issues|
1. Turn off the Roads and Highways extension in ArcMap by going to Customize > Extensions > Roads and Highways. Make sure ArcCatalog is closed on that machine as well.
2. Add your CPs to a MXD 3. Verify in the edit log that no timestamped activity was logged for adding the feature to the map.
4. Delete the CPs via the attribute table. You can do this in a geodatabase version and rec/post the deletions if you prefer.
5. Verify again that there is no deletion activity logged in the RH edit log.
6. Save your edits and rec/post as needed.
7. Turn on the Roads and Highways extension.
|Desktop||found||exists||exists||exists||exists||not in plan||Ohio DOT|
|Bug||Same Location Calibration Points Different Measure Value||Multiple Calibration Points at the same location with different measures deleting 1 of the CP's causes issues||Desktop||found||exists||exists||exists||exists||not in plan||Ohio DOT|
|Bug||Modify Measure with leave/re-enter issue||When modifying a measure on an existing leave/re-enter situation in desktop the system will not allow user to adjust the measure on the re-enter point as it wants to create a non-monotonic route.||Desktop||found||exists||exists||exists||exists||not in plan||Ohio DOT|
|Bug||Recalibrate Downstream||When using the realign tool and selecting the recalibrate downstream option the updated measure values are not calculated correctly if there is a leave/reenter or overlap situation on the route. Even when the calibration point is specified to use 3 decimal precision, when users open the attribute table it initially shows 3 decimal precision in the from/to fields, however, if users select the from/to fields on records associated with the recalibration downstream process the full 16 decimal precision is shown||Desktop||found||exists||exists||exists||exists||not in plan||Ohio DOT|