Latest Contributions by NeilEtheridge

Hi Jonas, I'm having the same issue at server v10.8.1.  Did you ever get past this issue? Thanks, Neil ... View more

In my case I was getting this error when 2 of my arcgis server machines federated with the portal were shutdown.   Cheers, Neil ... View more

Thanks Gintautas.  This was the approach went with ... just checking the token hadn't expired before I needed it again. Cheers, Neil ... View more

Thanks Jake for the reply - I should have thought to try it this way as I already do similar in other scripts when making direct calls to the REST interface.  I wasn't sure if subsequent Utility Network commands would recognise this token so went with the down the same track as Gintautas has suggested below. ... View more

Hi Jessy, sorry no I never did resolve the issue.  I usually access the tools through code which still works fine. -N ... View more

This might just be particular to my environment. After installing, untools is listed as version 2.5.1 in the installed packages list as you have shown here Will, but the "Utility Network Package Tools" toolbox is not available on the Geprocessing pane.  I think I will try uninstalling Pro completely next. ... View more

Yes tried this Manoj - no joy unfortunately ... View more

Thanks Michael for the very prompt reply!  I thought the same thing so have already been through that process, but didn't fix it.  ... View more

I tested using untools v2.5.1 but the result was the same.  While doing this test though with a different asset package, which has the same UN definition but different data - this one had no data in one of the problem Asset Groups - the domain successfully applied to that Asset Group.  Based on this I tried loading with the SCHEMA_ONLY option and all domains successfully loaded. ... View more

I have been trying to narrow down at what stage the domains get assigned so I was monitoring the StructureJunction XML definition in the database throughout the AssetPackageToUtilityNetwork execution and found something I wasn't expecting to ... the domain does get assigned and then later on it is removed.  In reference to the attached log ... at 18:45 the definition of the ElectricWaterCrossing subtype looked like this (note at line 7 the domain is assigned): <Subtype xsi:type="typens:Subtype"> <SubtypeName>Electric Water Crossing</SubtypeName> <SubtypeCode>271</SubtypeCode> <FieldInfos xsi:type="typens:ArrayOfSubtypeFieldInfo"> <SubtypeFieldInfo xsi:type="typens:SubtypeFieldInfo"> <FieldName>ASSETTYPE</FieldName> <DomainName>6_AssetType_StructureJunction_ElectricWaterCrossing</DomainName> <DefaultValue xsi:nil="true" /> </SubtypeFieldInfo> <SubtypeFieldInfo xsi:type="typens:SubtypeFieldInfo"> <FieldName>ASSOCIATIONSTATUS</FieldName> <DomainName>EQL_6_AssociationStatus</DomainName> <DefaultValue xsi:type="xs:short">0</DefaultValue> </SubtypeFieldInfo> <SubtypeFieldInfo xsi:type="typens:SubtypeFieldInfo"> <FieldName>SUBNETWORKNAME</FieldName> <DomainName /> <DefaultValue xsi:type="xs:string">Unknown</DefaultValue> </SubtypeFieldInfo> </FieldInfos> </Subtype> </Subtypes>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ At 18:56 it is still assigned.  However by 18:58 the domain has been removed: <Subtype xsi:type="typens:Subtype"> <SubtypeName>Electric Water Crossing</SubtypeName> <SubtypeCode>271</SubtypeCode> <FieldInfos xsi:type="typens:ArrayOfSubtypeFieldInfo"> <SubtypeFieldInfo xsi:type="typens:SubtypeFieldInfo"> <FieldName>ASSETTYPE</FieldName> <DomainName /> <DefaultValue xsi:nil="true" /> </SubtypeFieldInfo> <SubtypeFieldInfo xsi:type="typens:SubtypeFieldInfo"> <FieldName>ASSOCIATIONSTATUS</FieldName> <DomainName>EQL_6_AssociationStatus</DomainName> <DefaultValue xsi:type="xs:short">0</DefaultValue> </SubtypeFieldInfo> <SubtypeFieldInfo xsi:type="typens:SubtypeFieldInfo"> <FieldName>SUBNETWORKNAME</FieldName> <DomainName /> <DefaultValue xsi:type="xs:string">Unknown</DefaultValue> </SubtypeFieldInfo> </FieldInfos> </Subtype>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Here is an excerpt from the log: 2020-05-06 18:57:17     ...SetSubnetworkDefinition (48/121) 2020-05-06 18:57:28     Start Time: Wednesday, 6 May 2020 6:57:19 PM Succeeded at Wednesday, 6 May 2020 6:57:24 PM (Elapsed Time: 4.52 seconds) 2020-05-06 18:57:28     ...SetSubnetworkDefinition (49/121) 2020-05-06 18:57:40     Start Time: Wednesday, 6 May 2020 6:57:31 PM Succeeded at Wednesday, 6 May 2020 6:57:36 PM (Elapsed Time: 4.49 seconds) 2020-05-06 18:57:40     ...SetSubnetworkDefinition (50/121) 2020-05-06 18:57:51     Start Time: Wednesday, 6 May 2020 6:57:43 PM Succeeded at Wednesday, 6 May 2020 6:57:47 PM (Elapsed Time: 4.62 seconds) 2020-05-06 18:57:51     ImportRules (14/24) 2020-05-06 18:57:51     ...ImportRules (51/121) 2020-05-06 18:58:07     Start Time: Wednesday, 6 May 2020 6:57:53 PM Succeeded at Wednesday, 6 May 2020 6:58:03 PM (Elapsed Time: 9.65 seconds) 2020-05-06 18:58:07     DisableEditorTracking (15/24) 2020-05-06 18:58:07     ...DisableEditorTracking (52/121)‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Could ImportRules be causing this?  Seems like an unlikely candidate. ... View more

Thanks for the response Paul.  Our last project sprint this was the only domain not assigned, this sprint the same domain is still not assigned and there is now a second domain not assigned - this one on StructureBoundary which was ok last time but this time round it has data in it (which it did not in the previous sprint).  I've looked for any issues with the field type and default values but everything seems to check out - I would expect it should though given the asset package has the domains assigned correctly.  I've also taken a look at the data in these tables in case there is a conflict but again I couldn't see anything that misaligned with the domains.   ... View more

This is thread has been inactive for a while but though I'd share my recent experience in case it is useful.  I have created a number of "Float" type domains via python and successfully applied them to Float type fields (ArcGIS Desktop 10.2.1 - SQL Server hosted geodatabase).  However when viewing the values in these fields in ArcMap the code would display rather than the description.  And in the ArcFM Attribute Editor the values would display with square brackets and hightlight red as an invalid value.  Viewing the domain in ArcCatalog the domain type was showing as Double. Digging in the bowels of the geodatabase in the sde.gdb_items table you can find the XML definition of the domain. SELECT [Definition] FROM [Electricity].[sde].[GDB_ITEMS] where name like 'Distribution Transformer Bottom Tap'‍‍ Here you can observe the coded values have been created as a type of double rather than float. <FieldType>esriFieldTypeDouble</FieldType> ... ... <CodedValue xsi:type="typens:CodedValue"> <Name>2</Name> <Code xsi:type="xs:double">2</Code> </CodedValue> If you cut and paste the definition to a text editor, replacing esriFieldTypeDouble with esriFieldTypeSingle and xs:double with xs:float you can reapply it to the database to update the definition. UPDATE sde.gdb_items SET definition = '<GPCodedValueDomain2 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:typens="http://www.esri.com/schemas/ArcGIS/10.1" xsi:type="typens:GPCodedValueDomain2"><DomainName>Distribution Transformer Bottom Tap</DomainName><FieldType>esriFieldTypeSingle</FieldType><MergePolicy>esriMPTDefaultValue</MergePolicy><SplitPolicy>esriSPTDuplicate</SplitPolicy><Description>Distribution Transformer Bottom Tap</Description><Owner>ARCFM</Owner><CodedValues xsi:type="typens:ArrayOfCodedValue"><CodedValue xsi:type="typens:CodedValue"><Name>Unknown</Name><Code xsi:type="xs:float">-9999</Code></CodedValue><CodedValue xsi:type="typens:CodedValue"><Name>Other</Name><Code xsi:type="xs:float">-9997</Code></CodedValue><CodedValue xsi:type="typens:CodedValue"><Name>1</Name><Code xsi:type="xs:float">1</Code></CodedValue><CodedValue xsi:type="typens:CodedValue"><Name>2</Name><Code xsi:type="xs:float">2</Code></CodedValue><CodedValue xsi:type="typens:CodedValue"><Name>3</Name><Code xsi:type="xs:float">3</Code></CodedValue><CodedValue xsi:type="typens:CodedValue"><Name>4</Name><Code xsi:type="xs:float">4</Code></CodedValue><CodedValue xsi:type="typens:CodedValue"><Name>5</Name><Code xsi:type="xs:float">5</Code></CodedValue><CodedValue xsi:type="typens:CodedValue"><Name>6</Name><Code xsi:type="xs:float">6</Code></CodedValue><CodedValue xsi:type="typens:CodedValue"><Name>7</Name><Code xsi:type="xs:float">7</Code></CodedValue><CodedValue xsi:type="typens:CodedValue"><Name>8</Name><Code xsi:type="xs:float">8</Code></CodedValue><CodedValue xsi:type="typens:CodedValue"><Name>9</Name><Code xsi:type="xs:float">9</Code></CodedValue><CodedValue xsi:type="typens:CodedValue"><Name>10</Name><Code xsi:type="xs:float">10</Code></CodedValue></CodedValues></GPCodedValueDomain2>' WHERE type = '8C368B12-A12E-4C7E-9638-C9C64E69E98F' AND name = 'Distribution Transformer Bottom Tap'‍‍‍‍‍‍‍‍‍‍‍‍‍‍ After this update the field and domain performs correctly inside ArcMap and you can add additional values to the domain via ArcCatalog. I'm sure this falls in the category of a hack and totally unsupported ... but works. Testing creation of a domain in ArcCatalog under 10.7.1 suggests this has been fixed in a post 10.2.1 release.  I was able to specify a Float domain and have it stay a Float domain. ... View more