Free Download Software Arcgis 9.3 Full Version
Errolan Price
I use the newest version of ArcGIS Pro for my environment, of course it's 11.1 so slightly different, but I haven't experienced any issues so far with the interaction. As long as a license manager is setup and proper communication can be made from your network to the manager, you'll be set.
We are trying to get to 10.9.1 Enterprise so we can transition from ArcGIS Desktop to ArcGIS Pro. After that and a lot of test we will go to Enterprise 11.1. Right now, we are having problems with ESRI getting the migration from Enterprise 10.8.1 to 10.9.1 right - long story and ESRI has an update bug.
This is the history of every upgrade for me. Always some weird problem that "no one has ever seen before". I had a conversation with someone who consults for Esri and says he's done 100's of upgrades with no problems. I am sure it's better when you know the answers to the ambiguous upgrader script questions in advance? I always do the upgrades off hours and that means there is never a support tech available to me.
At 10.8 every web app builder app stopped working and Esri was unable to help. While waiting for an answer ("we've never seen this before") we migrated all apps to the WAB Developer Edition to avoid any repeats of that in future upgrades.
At 10.9, one of the components (Data Store) never installed correctly and now I have to fix it before I can go to 11. (It functions but runs under the wrong ownership.) Spent hours with techs and they were not able to fix it so I gave up.
ArcGIS Pro version is 2.4.3 and SDE for .NET version 2.4.0.19948. A couple of months ago I asked about using ArcGIS Pro sdk to Get all edits in a version. I'm testing this code against and Oracle 12.1 database and I'm seeing invalid results. In the image below the OOTB version changes tool is showing 13 edits in the current version. I ran my code with and selected by objectid each layer on the map and I get 8 changes in the version (updates only). Is there something different that needs to be done to get the objectids of Deletes/Updates?
I tried a second example version this time it OOTB tool shows 1 edit and I get 106,067 changes in the version. My assumption that a reconcile might help this and it does, after reconcile it correctly shows the one edit. Question two is it expected that I would add code to reconcile before checking for changes? The SDK WIKI doesn't mention that it might be necessary to reconcile.
I got a workaround to do this by creating a complex DB view for each Branch version then publish this DB views on Enterprise to use in MapView or Dashboard. BUT the problem is we integrate with Third-Party apps so there are another complex SQL Views so it's too complicated to use views with branch versions. whoever now I search for a way that lead me to be able to access a specific version into MapViewer without DB view.
I haven't had the opportunity to test this for your exact scenarios, but with the latest version of Map Viewer in ArcGIS Enterprise 10.9.1 (i.e. formerly Map Viewer Beta) you can specify Custom Parameters when adding a layer from a URL (see Add layers from a URL).
When you do this, the parameter is appended to all requests to the specified resource. So theoretically, you could add gdbVersion as the parameter and the named version as the value and it should target that version for ArcGIS Server requests.
This works to view versions in the web map, but when trying to edit the version added to the web map using this method, it will not allow adding or editing features. For testing purposes, I made this version public. I am able to edit the default version with no issues. How can I make data edits in the version? Thank you
We've been looking for the ability to share different Branch Versions of a service outside of Pro without the need to take data offline and then sync later. Distributed Databases was nice to be able to synchronize data between different databases. For example, we could have a production database and a development database.
We've been thinking we could do this with Branch Versioning but it seems like the only way to switch between versions with a direct link to the geodatabase is within Pro. We would like to publish services to our Portal with different versions.
Hi Michael,
The method discussed in the solution of this thread should be possible with previous versions of ArcGIS Enterprise.
Unfortunately for now, you are correct however - Distributed Geodatabase functionality is not currently supported with Branch Versioning and you cannot publish a specific version to ArcGIS Enterprise. However, you should be able to use the solution of this thread to add a service to a web map to access a version (e.g. adding the gdbVersion parameter in the URL).
Hope this helps!
Justin
If ESRI is forcing me to save as 3.0, why does it deceptively suggest I have any choice in the matter? I clicked 'No,' but was not provided a backsave option, like Microsoft Office products provide you with (Word, Excel, etc.). Or ArcGIS Desktop, for that matter.
This dialog box strikes me as deceptive - making the user think he has a free choice when he has none. I don't have an issue per se with the forced choice, but with the fake illusion that it's not forced...
so the other departments that are still using 2.8 will have no way of opening up my project now that I'm at 3.0? You always had the option of saving to an earlier version in desktop. C'mon ESRI, be better than this!
It is so frustrating, I think ArcMap started that way as well and added the option to save older versions later. I would think that it is obvious that working together with different versions is needed.
The ArcGIS documentation on migrating from 2.x to 3.x claims that Project Packages should be openable in 2.x. If that doesn't do the trick, you could try using arcpy to export the package with a version argument.
I am excited to find this group. I am hoping to get your advice on an ArcGIS Pro upgrade strategy for my organization of about 100 ArcGIS Pro users. I upgrade our organization a couple times every year. We unfortunately experienced a lot of issues after we upgraded to 3.0.3 recently so I would like to aim for the most stable versions going forward. Does anyone have a rule of thumb or a process for picking which upgrades to apply when you can only upgrade a couple of times each year?
Hi Jim,
This documentation is really helpful. It sounds like there are different degrees of software recertification depending on whether it's a major upgrade, minor upgrade, or a patch. Because 3.0.3 was a patch, it wouldn't have gone through the extensive recertification process that 3.0 and 3.1 did so I'll probably aim for the minor upgrades like 3.1 going forward.
Thanks so much for the quick reply!
We'll often wait for the first patch before updating all of our workstations, or else we'll update one of them to test workflows in the newest version. We keep an eye on the Esri Community as well, to see if others are reporting issues after a new version is released.
Stability of the desktop software can depend on other factors, too. We had been holding off updating to 3.0 for a while because our Parcel Fabric performed terribly in the latest version of Pro. But when we republished the service itself from a 3.0 instance, those issues disappeared. So our stability issues related to the publishing runtime of the service being used.
Hi Josh,
Thanks so much for this insight. That might be a good strategy to wait for the first patch and I have started inviting some of our power users to test out upgrades before I deploy. They are usually excited to get to upgrade earlier so they don't mind as much if they run into issues.
Veronica
We've been working with tech support regarding the Parcel Fabric performance issues - a couple official bugs. Fix for at least one of the bugs was originally supposed to be implemented in 3.2 but was rolled into 3.1.1. 3.2 (Q4 2023) is still supposed to be the one that achieves stability according to what info comes my way.
A lot of this is, imho, on the prolonged ArcMap retirement. So much has changed in the OS since last development upgrade of ArcMap that the job of maintaining backwards compatibility in structure and tooling development across the Pro and ArcMap platform must be super challenging.
Maybe I'm being generous in postulating but methinks that once the ArcMap API (32 bit) support is removed from everything we'll see a lot fewer performance issues. I personally can't wait till ESRI embarks on multi-processor and GPU enabling its tooling for its basic user tools like Manifold has done. Being able to leverage CUDA Cores and multiple NUMA nodes in geoprocessing is a game changer.
Hey all, hope things are well. I was hoping a knowledgeable person could help me understand the table in the link below. Does each version of the Experience Builder (Developer Edition) version require a specific version of Enterprise to work properly, or is it agnostic? IE, Can I stand up a 1.13 version of the Experience Builder, and following the steps on this page, wire it up to a v 10.9.1 version of Enterprise? Or is 1.7 the highest version of Experience Builder that a 10.9.1 Enterprise can support? Any information you can provide would be appreciated, many thanks.
About release versions ArcGIS Experience Builder ArcGIS Developers
I suppose it is technically possible to find some sort of compatibility issue. In practice, I have not found or heard of any. I have used Experience Builder 1.11 and 1.12 with Enterprise 10.9.1 without encountering any compatibility problems.
Thats encouraging to hear, thanks Jeffrey; Maybe I'm just going through the installation steps incorrectly. Did you go through the ClientID steps to register the Experience Builder in your Enterprise, according to the steps here?
ArcGIS Experience Builder install ArcGIS Experience Builder ArcGIS Developers