DO NOT update to 3.0, Update to ArcPro 3.0 is a disaster so far.

[WardMitchell2]

So I updated to 3.0 yesterday and I highly recommend waiting as long as you can before doing so. I am having very odd behaviors and some things simply not working like clipping a raster. Prior to updating to 3.0 yesterday afternoon,  I was working on a new project, and when I updated that project no longer opened up. It has taken 3 attempts to recreate the basic portion of the project. It would just sit and spin on the FGDB and did the same thing when selecting an excel doc. I can sometimes shut down ArcPro as you normally do but at least 50% of the time I'm having to use task manager to close ArcPro. Just an FYI as this is a major release going back to 2.9.3 might cause even more problems according to ESRI documentation. Migration from ArcGIS Pro 2.x to 3.0—ArcGIS Pro | Documentation . Just a friendly PSA

[KoryKramer]

Hi Kara  - yes, you'll need .NET 6 first. More on that along with other information to consider before upgrading can be found here: https://www.esri.com/arcgis-blog/products/arcgis-pro/announcements/get-ready-for-arcgis-pro-3-0/ 

Please read through that first. It references other good information in this help topic: https://pro.arcgis.com/en/pro-app/latest/get-started/migrate-2x-to-3.htm

Finally, an issue that we've seen tripping up some users, is if the appropriate Excel driver (compatible with .NET 6) is missing. So if you have any Excel files in your maps, make sure to read https://pro.arcgis.com/en/pro-app/latest/help/data/excel/prepare-to-work-with-excel-in-arcgis-pro.ht... specifically the section about 3.0: https://pro.arcgis.com/en/pro-app/latest/help/data/excel/prepare-to-work-with-excel-in-arcgis-pro.ht... 

[AdrianWelsh]

@KoryKramer , I did these updates (particularly the Excel driver) and things worked. However, my Dell laptop did some huge BIOS update and then my Pro projects with an excel file started hanging again. I had to reinstall the Access Database Engine Driver and things started working again. I have no idea what my Dell BIOS update did, but it apparently removed that driver update. Anyways, just a little note for people who go through a Dell BIOS settings update, you may have to reinstall that driver!

[TonyHowze]

So far 3.0 feels like a Beta version. I keep getting hung on random tasks or things just fail.  I've already caught a bug that has been documented with Tech Support.  All images copied from the clipboard and pasted into a layout in 2.9 are now corrupt.  Now when you copy from a clipboard and paste directly in 3.0, and open properties of the image, click into the simple path (don't have to change anything) then you click back in the layout the image pasted disappears.  It's wild.  

[KoryKramer]

I apologize that you encountered a bug, Tony - thank you for submitting the issue to technical support. If other community members happen to run across the same issue, you can subscribe to it here https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDE1MDgxMg== Subscribing will set you up for notifications as well as increment the count of affected users. We'll work on getting this fixed.

[LeviCecil]

I'm advising our team to not update from 2.9. None of our production Python scripts will run on the machines we have upgraded to 3.0. Now we have to figure out how to roll these machines back. This is annoying, but really not surprising. I think we'll wait until it hits 3.1 or 3.2. 

[gprince]

Hi Levi, sorry you're having trouble. Can you provide more details about what type of problem you're having with python scripts/What errors you're getting?

thanks

[LeviCecil]

On error turned out to be that the script wouldn't recognize a path with spaces in the name. This wasn't an issue before. Today we got this error running a geocoding script: ERROR 000010: Geocode addresses failed. The Fields collection did not contain an expected geometry field. Failed to execute (GeocodeAddresses).

I had the user delete Pro 3 and reinstall 2.9 and it's working again.  

[KoryKramer]

I wonder if your scripts contained the deprecated geocoding tools noted in https://pro.arcgis.com/en/pro-app/latest/get-started/migrate-2x-to-3.htm#ESRI_SECTION1_CAF5C09ED07F4... 

The Get Ready for ArcGIS Pro 3.0 blog points to that migration from Pro 2.x to 3.x blog. We'd be interested if you can confirm if your scripts were using the deprecated tools.

[LeviCecil]

Yes, our locators were created with the old tools. We're not ready to recreate them yet. 

[KoryKramer]

Thanks for confirming. The scripts will need to updated to the supported tools when you're ready.