Apply Asset Package Fails - ERROR 999999: Something unexpected caused the tool to fail

[rohanrajan_hms]

Good Day,

I am trying to do Apply Asset Package. My Asset Package has new fields that I added to the UN feature classes (before exporting Asset Package). I got Warnings that some field names were Reserved like shown below

I removed all such fields. Then I got this error 

ERROR 999999: Something unexpected caused the tool to fail. Contact Esri Technical Support (http://esriurl.com/support) to Report a Bug, and refer to the error help for potential solutions or workarounds.
General function failure
General function failure
General function failure
General function failure
General function failure
General function failure
WARNING 000952: Failed to execute (AssignDomainToField).

This persisted even after I removed the reserved fields.

Q1. Is there any list of the reserved fields available for reference

Q2. What could be causing this error. 
Any advice would be much appreciated.

Thank You,

[gis_KIWI4]

@rohanrajan_hms - I think the first problem is the Field Names used - Number, Size, Length

The second issue suggests its failing at the ApplyDomain tool is failing. It could be the values in the domain list. We had issues when loading values with "/" character in the string. The GP tool failed where as adding the domain description manually worked.

I would suggest trying to add one simple value as a test to see if that works. 

[rohanrajan_hms]

Yes, figured out the fields, but the asset package is same as UtilityNetwork Asset Package from ESRI. It used to work well even with domains having "/" in the description. And it would be very useful if there was a list of reserved field names.

[JoaquinMadrid1]

Perhaps a silly question, @rohanrajan_hms, but... Does your machine have enough free disk space? In my experience, when my free disk space starts dropping below 30 GB, applying an AP with (a substantial amount of) data throws the 99999... 

Good luck.

Regarding the warnings about the field names. Do not worry... it's truly just a worning. (Nevertheless, make sure those field names would not cause some issues in your enterprise E-GDB instance.)

[rohanrajan_hms]

I tested this with two different machines with ArcGIS Pro versions, 3.2 and 3.4, both failed. and about the disk space, one machine had less than 30GB but the other had ample disk space, yet both threw the same error.