There was a feature class table already joined to one of the feature classes that was part of this spatial join. I unjoined that feature class and then this ran without an error.
This is happening to me with version 10.2.2 on Windows 10.
The interesting thing is if I change all numeric inputs in both the target and join feature classes to short integer (as my feature classes only hold 0 or 1 for the fields of interest) instead of their original float type - the spatial join bombs out with a generic windows 9999 error ....
Before considering your issue as a defect I need to repro it locally.
Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.