Bug List from RHUG

1065
3
12-12-2018 02:30 PM
Labels (1)

Bug List from RHUG

IDActivity or FunctionIssueWorkaroundModule10.3.110.4.110.510.5.110.6.1Plan Submit byPriority
Bug-000101699Export Network ServiceThe 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

found

patch 4

existsexistsfixedNYSDOTHigh
BUG-000110742RealignRealigning a route to create a gap calibrates the To Measure on event incorrectlyDesktop@fixedNCDOTMedium
BUG-000106791ArcMap SymbologyCreating a layer from the Create Layer From Selected Features option does not honor the selection and displays all the features.DesktopfixedresolvedNCDOThigh

BUG-000108601

TFS-53113

Export Network ServiceTool 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 caseRemove route concurrency by reassigning to bogus route id or retiringServerfound patch 1fixedNCDOThigh

BUG-000106993

TFS #54450

Network Edit - Reverse RouteReverse Route causes calibration point measures to change beyond 6 decimal places.  Manually edit calibration point and recalibrate downstreamDesktopfoundfixNCDOThigh
NCDOT case 01889567Relocate Events ServiceRelocate 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)Serverfoundhotfix*NCDOT

BUG-000101392

TFS51810

Route Edit -  extend, realignExtending 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 routeUse reassign instead of extend if possibleDesktopfound patch 4existsexistsfixNCDOThigh

TFS51854

Route Edit - Reverse, ReassignReverse and Reassign to Create Gap Causes Measures Downstream From Gap to be Incorrect.  Issue also occurs doing a reverse and retire to create a gapReassign, then reverse if possibleDesktop

found

patch 4

existsexistsfixNCDOThigh

TFS51855

Realign, Cartographic RealignmentRealign 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

found

patch 4

fixNCDOThigh

TFS52078

Retire, Cartographic RealignmentRetire 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

fixNCDOTHigh

TFS52077

Reassign, Cartographic RealignmentReassign 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

found

fixedNCDOTHigh

BUG-000101941

Extend, Cartographic RealignmentExtending a route, and performing a cartographic realignment on the extended portion results in a Not a Number (NaN) calibrationUse 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

Patch 4

fixedNCDOTHigh

BUG-000102184

Launch a URL (i.e. instance of RCE) from Workflow Manager OnlineArcGIS 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 datastoresDynamically examine the memory usage and periodically eliminate the ‘zombie’ server processes; alternatively, reboot server.server

found

existsexistsfixedNCDOTHigh

BUG-000101393

TFS51811

Realign, RetireRealigning 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 possibleDesktop

found

existsexistsexistsexistsin planNCDOTHigh

TFS45251

NCDOT case 01888502

CalibrationVertex measures flip when recalibratingnoneDesktop

found

fixedNCDOTHigh

NCDOT case 01904018

Add Machine to an ArcGIS Server siteAfter upgrading an ArcGIS 10.3.1 site to 10.5, the Add Machine operation fails with error: "\relational-datastore-types" folder cannot be locatedUsing 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 planNCDOTHigh

Reassign or RetireRetire 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

foundnot in planNCDOTMedium

NCDOT case #01906828

Realign, Cartographic RealignmentEvents shift downstream of realignment if a cartographic realignment is subsequently performedDesktop

foundnot in planNCDOT

BUG-000102964

Display Route EventsDisplay 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.334In 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

found

existsexistsexistsexistsnot in planOhio DOT

Bug

Undefined Editing ErrorUpon 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 issuesDesktop

found

existsexistsexistsexistsnot in planOhio DOT
BugAdd Calibration PointIdentified 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 retiredRCE/Event Editorfoundexistsexistsexistsexistsnot in planOhio DOT
BugSame Location Calibration Points Identical Measure ValueMultiple 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.

Desktopfoundexistsexistsexistsexistsnot in planOhio DOT
BugSame Location Calibration Points Different Measure ValueMultiple Calibration Points at the same location with different measures deleting 1 of the CP's causes issuesDesktopfoundexistsexistsexistsexistsnot in planOhio DOT
BugModify Measure with leave/re-enter issueWhen 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.Desktopfoundexistsexistsexistsexistsnot in planOhio DOT
BugRecalibrate DownstreamWhen 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 shownDesktopfoundexistsexistsexistsexistsnot in planOhio DOT
Labels (1)
Comments

This is the list of bugs and issues we complied from the previous RHUG site.  I would like to break up this list and report each bug or issue as an individual discussion item with tags for version numbers affected and status.

Kyle, that was my intent also. I believe Erin deleted it but I had a how to post for the R&H Bug category and posted our bug as a working example. From what I recall of the post it was something like this: Esri Bug Number and description, R&H version, any other detail information, workaround if known and any other comments. This way folks can talk an each issue and not have it in one giant post or like the post and importance/impact across the user group can discovered. I was going to post more of ours but didn't have any write ups for the workarounds and other comments yet. 

Ive added some of the release announcements  and was going to start doing these listed bugs one by one.  I think it would make sense (to me) use a matrix tracking system for bugs at reported version vs fixed version, many of the bugs reported in our lists have potentially been fixed.   I was going to work on a more trackable format, like this:

IDTFSReported byActivityIssueWorkaroundVersion 10.3.1Version 10.4Version 10.4.1Version 10.5Version 10.5.1Version 10.6.1Version 10.7
BUG-000101699 New York State DOTExport Network ServiceThe 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.reported patch 4verifiedverifiedverifiedresolved  
BUG-000110742 North Carolina DOTRealignRealigning a route to create a gap calibrates the To Measure on event incorrectly     reported  
BUG-000106791 North Carolina DOTArcMap SymbologyCreating a layer from the Create Layer From Selected Features option does not honor the selection and displays all the features.     reportedresolved 
BUG-00010860153113 North Carolina DOTExport Network ServiceTool 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    reportedresolved  
BUG-000106993TFS #54450North Carolina DOTReverse Reverse Route causes calibration point measures to change beyond 6 decimal places.Manually edit calibration point and recalibrate downstream    reportedresolved 
NCDOT case 01889567 North Carolina DOTRelocate Events ServiceRelocate 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.   reportedreportedhotfix  
BUG-000101392TFS51810North Carolina DOTExtend, RealignExtending 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 routeUse reassign instead of extend if possiblereported patch 4verifiedverifiedverifiedresolved  
Version history
Last update:
‎12-12-2018 02:30 PM
Updated by:
Contributors