Hello, we set up collaborations between our portals (10.5.1). Although some times i have to manually run the sync to get the contents synced, most times we are pretty happy with it. In the past couple of days, one of our users tried to share an map image layer (map service as the source) and it didn't get through. When I tried manually running the sync, unsharing/resharing it like what i used to do, it still didn't go through. I noticed whenever I ran the sync, the following warning message appeared in the portal log.
Failed to export item '57116782cc064eca9078cc87c02b9a55' into a replication package
Based on my understanding, data for only hosted feature layers gets replicated during collaboration while for map services, just, just a reference is shared. But why it's trying to replicate the data for this case? Since I couldn't make it work, our user tried republishing the service and re-shared it and it was able to get through. But republishing the service is not a solution for us since it will change the portal item IDs and mess up any existing map/apps using the item.
Can anyone please help why the sync didn't work? Any workarounds or solutions?
Hello,
Did you figure this out? I'm having the same issue. I've noticed that it happens when I add hosted features with multiple layers and tables.
Thanks!
Having the same issue with only 2 features in my UAT env. One un-versioned (works) and one versioned (which has this error)
no solution here, yet, but I am working on this with tech support.
Same error, in a collaboration between ArcGIS Online (AGOL) and our Enterprise Portal. Ours started failing without warning on 6/10/2022, after months of syncing fine. The package fails on all services not just one. (The only thing that changed around the same time that syncs started failing was generating a portal token - using the Portal REST directory, https://<portal>/<webadaptor>/sharing/rest/GenerateToken - for a specific user, *using our own portal as the referrer*.)
If we delete the destination content (the *copy* created on the host from the portal), the first sync works, but any subsequent ones fail. Also, it seems to only push a copy of the map services, not the feature services.
Configuration
Fails on push of portal services-to-AGOL
Task Name: | Export replication package |
Task Status: | failed |
Fails on push of hosted service in AGOL-to-Portal
Export and download peer replication package | |
Task Status: failed |
What we Tried So Far
TIP: Esri recommended that anytime I force a sync, to do it from the REST API for the Portal (ex. https://<portal>/<portalwebadaptor>/sharing/rest/portals/<portalOrgID>/collaborations/<collaboration... "sync" and then "sync status"