Select to view content in your preferred language

Is Error 000372 an Error or Warning?

3715
4
Jump to solution
05-26-2017 12:51 PM
PatrickMcKinney1
Frequent Contributor

Has anyone else ever received the following error message when running the Append tool, but found that the records were copied into your dataset?

Error: ERROR 000372: Spatial Reference for output is invalid, Please update to allow output to become valid
Failed to execute (Append).

I understand how this may be a technical error, but because the records were copied over, it almost seems like a false positive.  Does anyone know why this is an error message instead of a warning?  Typically when  you get an error message, the tool failed.  But in this case, the records were appended.

1 Solution

Accepted Solutions
DanPatterson_Retired
MVP Emeritus

hmmmm the link I posted seems to error so I will try again here....

http://support.esri.com/bugs/nimbus/QlVHLTAwMDA4MTY3OA==

which indicates it was fixed in 10.5 but identifies much earlier

View solution in original post

0 Kudos
4 Replies
DanPatterson_Retired
MVP Emeritus

hmmm a bug on an error...

http://support.esri.com/bugs/nimbus/QlVHLTAwMDA4MTY3OA==

and

https://community.esri.com/thread/64067

seems no one was too worried, but check arcmap 10.5 to see if it goes away or persists

0 Kudos
JayantaPoddar
MVP Esteemed Contributor

What version is your ArcGIS?

I guess this issue was there till ver. 10.2.2 which were resolved using Spatial Reference Consistency Patch.

ArcGIS 10.2.1 for (Desktop, Engine, Server) Spatial Reference Consistency Patch 

ArcGIS 10.2.2 for (Desktop, Engine, Server) Spatial Reference Consistency Patch 

ArcGIS 10.3 and later shouldn't have such issues.



Think Location
0 Kudos
DanPatterson_Retired
MVP Emeritus

hmmmm the link I posted seems to error so I will try again here....

http://support.esri.com/bugs/nimbus/QlVHLTAwMDA4MTY3OA==

which indicates it was fixed in 10.5 but identifies much earlier

0 Kudos
PatrickMcKinney1
Frequent Contributor

We're using version 10.3.  Good to know it was fixed at 10.5.

0 Kudos