nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

WardMitchell1

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

Encuentra más publicaciones etiquetadas con

Desktop

Accepted answers

TimothyRudzik

Updating the Microsoft Access Database Engine per instructions at https://pro.arcgis.com/en/pro-app/latest/help/data/excel/prepare-to-work-with-excel-in-arcgis-pro.htm has corrected my issue.

All comments

KoryKramer

Sorry to hear that you're running into issues @WardMitchell2 Since you mention Excel, please be sure to note that there are driver requirements related to the .NET 6 update https://pro.arcgis.com/en/pro-app/latest/help/data/excel/prepare-to-work-with-excel-in-arcgis-pro.htm This will not affect all users as they may already have the correct drivers in place, but is something that you should look into.

For specific troubleshooting issues, hopefully you are already working with Technical Support. If not, please contact them here.

jcarlson

For what it's worth, some of the new Parcel Fabric enhancements have been an absolute dream to work with, and I wouldn't go back to 2.9.x for anything. Our 2.9.x projects have all opened up in 3.0 without issue, and so far, none of our typical workflows or editing tools have failed to perform as expected.

That said, it's a perfectly reasonable approach to wait for the first patch, after the early adopters have found the bigger bugs.

TimothyRudzik

After my update to 3.0 yesterday the Map Series function no longer works. It just spins. Here is what I have tried so far.

I let it run over night, no luck.
I created a brand new project, map, and layout, no luck.
I use a different feature class, no luck.
i reduced my map and layout to be as simple as possible (to eliminate any other possible reasons), no luck.
I rebooted my computer, no luck.

The app is unresponsive from the point I click on the Map Series button. If I don't click Map Series everything seems to run fine.

Can anyone confirm same issue?

Thanks,

Tim "Ryan" Rudzik

WardMitchell1

Thanks Cory, I will look into that.

WardMitchell1

Sorry *Kory

TimothyRudzik

Updating the Microsoft Access Database Engine per instructions at https://pro.arcgis.com/en/pro-app/latest/help/data/excel/prepare-to-work-with-excel-in-arcgis-pro.htm has corrected my issue.

Kara_Shindle

I haven't actually upgraded yet because I got the attached error when I tried to. Going to have to get in touch with IT.

arcpro download error.png

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.htm 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.htm#LI_6C0EF8ACE83C4599AFC35141822488C4

TonyHowze

My analyst has just told me it crashes when trying to export out a series.

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.

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_CAF5C09ED07F42AB94619FC9B19D19EB

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.

RichardPearson_org

On upgrading to 3.0 I had a stuck on loading screen issue which I managed to fix by applying the AccessDB update mentioned above. The latest Windows update seems to have broken things again though! Trying to open an aprx file which includes a link to an Exel spreadsheet causes Pro to get stuck on the loading screen once more. I've tried applying the fix again, but it's not worked this time :-(. Wondering if anyone else is seeing this?

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.

WardMitchell1

As of around 8:30-9 am Monday morning I am no longer able to connect to my D-Drive and H-Drive only when creating a new project. I can open existing projects on both drives. The D drive is my local computer, and the H Drive is our network drive. The error that comes up states “ Cannot Connect to Network”. I am running the ArcPro 3.0version. I rebooted twice yesterday and once this morning and it didn’t change anything. I have updated both the .Net and excel driver, as suggested by ESRI when updating to 3.0 version. Everything was basically working until Monday morning. Do you guys have any suggestions as to how to fix this?

KoryKramer

When you say you're trying to connect to the D and H drive when creating a new project, do you mean you have created a new project first and then are trying to add folder connections? Are you trying to create connections in your new project directly to those root drives or to folders on those drives?

Do you have the connections stored as Favorites that can be added to the project? We do have an issue logged with Technical Support (not specific to ArcGIS Pro 3.0, and to-date not reproducible in house) that sounds similar. The listed workaround is:

Drag and drop the item in question from Windows File Explorer to Catalog (folder connection).
Use a geoprocessing tool, and copy and paste the output location into the input text box, without using the file browser (Create File Geodatabase, Create Folder).

Are you able to drag/drop from Windows file explorer to create connections? It may be that you're running into this issue, but again, we have had that reported by others before 3.0. We are trying to get a solid repro case in order to understand if there is a fix that we are able to make in ArcGIS Pro or whether this is environment-specific.

WardMitchell1

Heres a quick video of what is happening

Connect to network error.mp4

KoryKramer

The video is helpful. Thanks.

A couple of things:

1. It looks like you're creating and storing projects in a OneDrive location. Please be sure to read the support policy for Pro on OneDrive: https://support.esri.com/en/technical-article/000025605

2. It looks like you are typing in a location that doesn't exist. Once you are in your ThomhillNightFlight071522 folder and you want to create a new folder in there to house your project, go to New Item > Folder and create it. Then you should be able to set that folder as the location for the new project.

I got the same network location error you did when I followed the steps in your video. But when I created the folder first and set it as the location there was no problem. Hope that helps.

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!

ArtK

I also had to update microsoft access driver to get it to work. It doesn't look like Arc Hydro has a 3.0 installer release yet. Might get away with simply dropping the python files into the correct directory and still import them for arcpy processes, I haven't tested this yet. I will probably end up testing in the next week if it works.

Edit: the Arc Hydro package remained installed through the upgrade, so fortunately procedures involving it still run as expected. I am noticing extremely slow project load times and geoprocessing speeds however. It may be isolated to certain projects since sometimes it processes at normal speed, other times quiet slowly. Not something I experienced in 2.8 or 2.9. Running standalone procedures with Ipython console is much faster at least. Another consideration is if you have an Anaconda conda environment set up for 2.9 it won't automatically work with 3.0 as far as I can see..

ArtK

I decided to uninstall 3.0 and re-install 2.9 . I think Esri should have a warning message for this update since it is not backwards compatible and may cause unforeseen issues for larger projects when converting them. Additionally would be nice to have a snooze update option so it doesn't notify every time you open it.

AdrienneJohnson

I am and I hate it here. I've updated all the drivers. I've restarted. I even tried to go back to 2.9x and because my project had been opened in 3.0, that didn't work. Updating to 3.0.1 didn't help. I am tired of 15 minute tasks turning into 2 hour support searches for developer level items. It's not right.

HemnAlSalihi

I fixed it by installing the "Microsoft Access database engine 2016".

GrantDickins_OX2

Yes, we have a nightmare since upgrading to 3.0. We admit to not following the 'migrate to 3.0 documents' but only because we thought it would have minimal impact and would just be a simple process to fix existing minor bugs we already had with 2.9.3. However, now we regret the upgrade to the point of my superiors wanting to can Arc altogether. On upgrading to 3.0 and now to3.0.1 we have several projects that would open in3.0 but are now useless, becoming stuck on loading screens. At least three projects opened after moving to 3.0 but now those same projects will not open at all. We have already re-built two entire projects from scratch because they were not openable at 3.0.1.We have done all of the Excel and .NET fixes/recommendations, etc. mentioned above. Are we just a bad exception or are these issues affecting more than then 1 or 2? Of greatest concern is that some projects opened AFTER moving to 3.0 but now they will not. In one case we left a project running, trying to open, for three days - and it finally did. But others still will not. I have become the whipping person in the company for the delays and hold ups with the GIS outputs - after 20 years I feel like an amateur and am about to quit! No one seems to know how to fix this. The only solution I got from support was to 'Perhaps uninstall 3.0 and go back to 2.9'. That's no good now when most of the projects are in 3.0.1. Sorry, but I'm frustrated.

TimothyRudzik

Hi Grant,

Did you follow the Excel Decision Tree Guide strictly? It is especially important to do a silent install of the MS Access Database Engine IF your other MS products were installed using the method Click-To-Install. The decision tree below is from https://pro.arcgis.com/en/pro-app/latest/help/data/excel/prepare-to-work-with-excel-in-arcgis-pro.htm#ESRI_SECTION2_26C59527A7D8462D86A17F74B6ADBFFC

You can check the method by which your MS products were installed (Click-to-Run vs MSI) by opening up any of the MS apps, click the File pull down menu, then click Account and look for something like this....

click to run.JPG

If your MS products were installed using Click-to-Run then you must do a silent install of the Access DB driver. If your MS products are 32 bit then you must also do a silent install of the .NET Runtime.

I hope this helps.

Tim "Ryan"

KoryKramer

Hi @GrantDickins_OX2 I'm really sorry to hear about your attempt at updating to 3.0. While you can see that a few others have experienced some issues, we have seen many thousands of users successfully make the move. Your post led me to look for the support case with Esri Australia and I didn't see any information about troubleshooting that was done.

Given @TimothyRudzik's response about checking the Access database drivers, and I know you said you worked through the Excel recommendations, but we have seen some cases where that needs to be looked at very specifically. Did Support go into the detail that Tim shared below?

Do the projects you've had problems with contain Excel tables? If they do, and the correct drivers aren't in place, that could potentially lead to a project not opening. If they do, and your drivers are installed and working correctly, or if the problem projects do not contain Excel tables, then something else is going on and it needs to be figured out.

I'm not sure if you are in a position to share project packages that don't work for you in 3.0 (i.e. have you rolled back to 2.9, and could you package a project there and share it with me?), but if you can, shoot me an email at kkramer@esri.com. We want to help figure this out and without having any specifics about the problem projects, that isn't possible. Looking forward to hearing from you soon.

KeithAddison1

Anyone else having Python problems in label expressions? Basic expressions seem to not work anymore.

GrantDickins_OX2

Hi Kory and Tim. First, my apologies for my frustrated rant. Below I have outlined what has occurred as best that I can determine.

1. I did not know of the 'decision tree' that was shown to me by Tim. So, I could not get the required Microsoft Access Database Engine 2016 files to install as described when upgrading, so I then had our IT support company install the Access DB 2016.exe for me. They got it installed and the ArcGIS Pro projects would open (those with and those without Excel files in them). I do not know if that means the files were installed silently or not. The Excel application on my machine indicates it was installed Click to Run.

2. Microsoft Access Database Engine 2016 is currently installed on the PC.

3. My Aus support case was Esri Case #03129769 - ArcGIS Pro 3.0 Corrupt Upgraded Project Files?

The responses (and support assistance) were always generally helpful but I/we have never been able to resolve the issues that still prevent opening some projects.

4. Should I uninstall Arc and reinstall it? Going back to 2.9 is not an option now that I have already upgraded most projects to 3.0.1. But I think that is all I can do from this point? I haven't done this already because I am paranoid I will not be able to open any of the projects at all, i.e. break something else. However, I think your meaning is to rollback to 2.9 and open the older projects that don't currently open in 3.0 and then somehow save them so they open in 3.0?

5. I have never used project packages. I will see if I can do that and send one to you.

Thanks.

shagggypanda

I can also confirm major issues with ArcGIS Pro 3.0 update. It seams like everyday I run into another problem which wasn't an issue before. Making my job a nightmare!

- Created Project

- From the start the project Geodatabase is "Either invalid or out of date. [Invalid Geodatabase release}"

Completely broken GDB with every new project. Also had many of the same issues mentioned in the thread. Software patch please!

just_a_university_student

Hello! Sorry or reopening this discussion, but you mentioned "going back to 2.9.3" and I was wondering if that is still possible, and how to go about it?

but I wanted to ask if it is possible to go back to the previous patch of 2.9 (I think I had 2.9.5 ) after having updated to 3.0 -

I had only updated ArcGIS Pro from 2.9.5 to 3.0 because I needed the Hexagon Gridding tool, but it turns out I no longer have the Business Analyst extension (I'm a university student, so I don't know the logistics of my university's license) and I get a warning about the incompatibility of my file with 2.X updates if I proceed, so I haven't used it. I was able to get ArcGIS Pro 2.8 by following my university's instructions, but now ESRI doesn't show the upgrades available for 2.9 at all (only 3.0) and I get a similar warning regarding working on a version below 2.9.

Thank you for your time!

- Just_A_University_Student

RussellLundstrumUSACE

yup I found that out too. In my case I upgraded the project from 2.(something) when to export the map series and like you, Pro just becomes unresponsive. I can't even close it the right way and have to kill the process.

ArmstKP

After upgrading to 3.0 from 2.8, all of our schedule geoprocessing models will not run successfully. I can run them manually, but not if they are scheduled...

ArmstKP

I upgraded Pro to 3.1 today and it still does not fix my scheduled geoprocessing model issue as I mentioned above.

LeviCecil

Good to know, thanks. I rely on Python scripts running in task scheduler, so I'll keep that machine at 2.9 until this is sorted out.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.