English

Bug: Cannot copy a network dataset when fields get auto-renamed

Description

After copying a network dataset from one geodatabase to another, the copied network dataset is unable to be opened.

The two geodatabases have different DBMSs.

Cause

DBMSs have field names that are reserved and cannot be used. When copying feature classes between different DBMSs, some fields may be renamed so that they are compliant with the reserved field names. The evaluators on the network dataset are not accounting for the renamed fields.

Workaround

Before copying the network dataset, make sure that the feature classes do not have fields with names that conflict with the reserved names of the target DBMS:

  1. For fields on the feature class that have names that conflict with the reserved names in the target DBMS, create new fields on the feature class with names that do not conflict.
  2. Copy the contents of the old fields to the new fields. You can use the Calculate Values command in ArcMap to accomplish this.
  3. In ArcCatalog, open the Network Dataset Properties dialog and change the evaluators to point to these new fields.
  4. If desired, delete the old fields.