Select to view content in your preferred language

Distributed Collaboration ArcGIS Enterprise Version Number Out of Sync

600
2
05-12-2025 12:04 PM
Joshua-Young
MVP Regular Contributor

A few months ago, we upgrade from ArcGIS Enterprise 11.3 to 11.4. Now in ArcGIS Enterprise our distributed collaboration with ArcGIS Online has the version number as 11.4.0, but in ArcGIS Online the ArcGIS Enterprise Version is still 11.3.0.

How do I get ArcGIS Online to recognize the new version number without breaking our collaboration? Is ArcGIS Online limiting collaboration because it thinks ArcGIS Enterprise is running at 11.3?

"Not all those who wander are lost" ~ Tolkien
0 Kudos
2 Replies
GlenterpriseUK
Esri Contributor
0 Kudos
Joshua-Young
MVP Regular Contributor

Hello @GlenterpriseUK ,

I had not seen that post. I ended up deleting and recreating the entire collaboration to get the version numbers in sync. To be honest, we are starting to consider moving away from distributed collaborations and going back to Python scripts that truncate/append from ArcGIS Enterprise to ArcGIS Online. Our distributed collaborations keep having consistent, yet random, issues.

  • Collaboration items on ArcGIS Online will randomly have their permissions changed from Everyone (or specific groups) back to Private.
  • Collaboration workspaces will eventually start failing to sync. How long they run successfully varies. Sometimes they will be fine for months, other times weeks, and sometimes only days. The logs on ArcGIS Enterprise usually have something about failure to create replication package and it tends to happen with enterprise geodatabase feature layers more than hosted feature layers. Creating separate workspaces for hosted feature layers and enterprise feature layers has helped some.
  • I have stopped marking feature layers as Authoritative in ArcGIS Enterprise for collaboration items because that flag seems to make the workspace sync fail more often.

I have been going over the issues addressed lists and I see things that are supposed to be fixed that we still have issues with, or the same BUG number is referenced in more than one release. I am planning on going from 11.5 to 12.1 once it is released and completely rebuilding our distributed collaboration one more time. If we are still having issues after that then I will have to move us back to our old Python scripts.

"Not all those who wander are lost" ~ Tolkien