June 2024, on Pro 3.2.1, and the symptoms and results are the same for me as described by everyone else here. To say this is an anomaly is ridiculous. Doesn't matter which workstation, which update, what data set, how many layers, how many records, it hangs forever. This is a bug, clearly, and if it was fixed before, its broken again.
If it doesn't effect every user, then we need to isolate what commonality is causing it, could be as simple as the feature layer label starts with the character "2", or the input map you select has a different coordinate system than the selected feature later and its taking longer to translate. (These are random stabs in the dark, because I don't know.) Some combination of variables causes this to happen, very commonly.
I have noticed the tool does NOT hang for me prior to running if you set all the parameters BEFORE selecting the Input Map.
For example I fill out the fields from the bottom up, starting with Output Layer, then I select Convert unplaced labels, then I select my extents, the output geo database, then select single layer and select the feature layer, then I select the conversion scale, and FINALLY when I select the input map, it spins and spins for 2 to 10 minutes before I can even run the tool. I find it funny that it allows me to select a feature layer prior to selecting an input map.
Once its done hanging, I am able to run the tool, which can vary from 2 to 20 minutes, sits on 2% completed, jumps to 100%....several times....and then sits updating.
Then eventually finishes and unlocks the rest of the remaining layers. Even in situations where is spits out a warning about no applicable records in the scale (002847: No labels to convert. There are no feature layers that are labeled at the conversion scale.). It will present the warning, and spin updating for like 10 minutes prior to finalizing.(What is it doing if it clearly indicated there are no records...what's to finalize?)
If I do not leave the geoprocessing pane, the convert labels to annotation tool will try to refresh itself with the current settings after anything I click in ArcGIS. For example if I deselect a layers visibility, the tool refreshes, if I change to the edit ribbon.....the tool refreshes. This could be expected behavior, however...bugs are all in the details.
In the last 4 weeks I have used this tool with many data sets of varying sizes, created/produced by many different sources, using many different coordinate systems, in many different project files (created independent of each other) also I have these same results on multiple workstations.
It is only this geo processing tool, all others work with all data sets in an expedited manner, regardless of their size, coordinate system, workstation. This is the only geoprocessing tool that this happens to, constantly.
I hope any of this description helps someone narrow this down because this thread was opened in 2017, its 2024.....thats 7 years. It only took the US 8 years and 2 months to send mankind to the surface of the moon, and that was 55 years ago. I understand you can't fix something if you can't replicate it yourself, but just because you can't replicate it yourself, doesn't mean it isn't a genuine issue for users. Be annoyed at my post because you think you know better than me, but if this wasn't a bug, you wouldn't have a 7-year-old post with people still suffering from such a simple request, experiencing the same results.
P.S. I shouldn't have to open another bug when there is one. Even if someone believes its fixed.
BUG-000121190 for ArcGIS Pro (esri.com)
