Latest Contributions by Natalie_Runyan

In SQL Server Management Studio (SSMS), you can find the list of sequences by connecting to the database instance > Database > Programmability > Sequences > and the sequences are listed there.   ... View more

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 We have server federated with enterprise portal at 10.9.1 Windows Source data in SQL geodatabase registered with the GIS Server services with Global IDs, and archiving enabled (no versioning), and (both with or without replica tracking enabled) feature services published with Pro 2.9, with sync enabled Collaboration set to send and receive, but workspace set to copy only (not reference, and *unchecked create reference if unable to copy*) all items shared with "public" and the collaboration groups Fails on push of hosted service in AGOL-to-Portal Export and download peer replication package Task Status: failed   created a hosted service for testing initial copy is made to the portal, but subsequent updates fail What we Tried So Far Deleted the entire collaboration and built a fresh one, using a different geodatabase source; ; sync still fails at the Export Replica step, both ways. -- this seems to point to an issue with the portals instead of the data or the collaboration per se. Full ReIndex of Portal; still fails; sync still fails at the Export Replica step, both ways.  Even though the index numbers matched, tried this just in case. In each, Portal and AGOL:  Organization > Settings > Security > Trusted Servers > Added corresponding servers from both sides; sync still fails at the Export Replica step, both ways. Confirmed could add the feature service to AGOL from portal as a "new item from URL"; works with no issues.  So, AGOL can reach the services in our portal directly. 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/<collaborationID>/workspaces/<workspaceID> "sync" and then "sync status" ... View more

I'm getting same errors on a new 10.9 build (Datastore, Server, Portal on separate machines; federated, hosting; OS Windows 2019). Identity store is SAML Azure AD. Domain service account on all servers have full control to relevant program and content directories. ... View more

Hi Naresh, did you ultimately discover a way to edit via a query layer?  for years we have published read-only services of our non-SDE/RDBMS data, even as feature services for taking into offline workflows. However, we've never actually attempted to edit the records from the GIS side.  We'd like to do that now, just for attributes not the geometry field.  I can understand that the geometry would not be editable because that is what is used to create the query layer in the first place (it would be a circular logic problem I think).  I'm thinking maybe we could use an "update" statement instead of a "select" to actually create the query layer? ... View more

Thank you Jonathan. I was able to get webgisdr to work. I suspect the online instructions have been updated since I last used them, which clarified the use of the FQDN. Thank you for the great explanations and offer of help. ... View more

In my case, I cannot get command line webgisdr.bat to run, however I can "Export Site" using Portal Administrator UI.  The output is a *.portalsite file, which is correctly owned by the domain service account of the Portal.  Is this portalsite file contain the same content as the webgisdr.properties?  Can I recover (using import site:  Import Site—ArcGIS REST API: Administer your portal | ArcGIS for Developers) without having run the webgisdr? The disaster recovery guidelines (such as here: Configure disaster recovery for ArcGIS Enterprise—Portal for ArcGIS (10.6) | ArcGIS Enterprise) refer to the webgisdr utility, and I can't find a reference that references "Export Site" in as much detail.  Can you provide documentation that distinguishes or provides pros/cons of these methods?   ... View more

In our case, the problem was a network firewall. I resolved it by going off-network and using WiFi. ... View more

in our case, we use locks because if the schema changes while folks have data offline in field-editing workflows, they can't sync... the replica would become corrupt. ... View more

I now push updates directly to the user JSON files which at least circumvents the need to login under each profile. ... View more

This happens to us on all of our story maps now. The story map is built and hosted in ArcGIS Online, and the data layers in the maps are hosted on our Enterprise GIS Server (10.6). The map content is all visible to public users of the story maps, so we don't believe anything is actually broken, but of course we wonder because the layer in the application editor is marked "INACCESSIBLE" ... View more

I am assuming you've resolved this, but for the sake of the thread: my understanding is that your services won't re-create a lock unless they are actively being used (such as a map pan action right after you disconnect user/release the lock). The only way to avoid that is to stop the service. I learned recently though that feature classes in the same dataset all get locked even if the lock is actually only on one layer. For this reason, you will want to avoid using feature datasets unless you have a specific need (like managing a geospatial network dataset). If your feature layers are stand-alone (not in a dataset), then you could disconnect all the users in Admin so that new locks are only created on the layers that are being actively queried. You'll have to stop the service to prevent those new locks on active services. If someone knows better, I'm glad to hear also. ... View more

I'm getting it at 10.6; my SQL Server is 2016 ... View more

As the sys and geodatabases admin, it is important that I be able to silently load the geodatabase connections for users based on their role in the multi-user editing processes and in business units. As it is, I'm going to need to run Pro on each user's machine and add every single geodatabase connection manually?! That's 60 users with at least 6 geodatabase and arcgis server data sources. Yes, ridiculous. I guess the expectation is that users of desktop GIS should know how to add these themselves, and that other users should be using web maps? However, in our case, it's not a user expertise issue, it's that we're using SQL Logins for our user roles, instead of domain logins, so every database connection is pre-configured with passwords that the users cannot know themselves. ... View more

This happened to me also today when I tried to reindex after renaming the existing & unpacking "empty_index". I have an incident logged with Esri.  For what it's worth, our GIS Server is federated with Portal, and the Portal identity store is Active Directory via LDAP. I created a new admin account (in the local identity store, independent of Active Directory) using tool "accountmanagement\createadminaccount" but could not log in with that account either. Ultimately reverted to the old index, but then of course, all my indexing problems still remain. ... View more

FYI, Mike, it sounds like your issue is different from the one in this thread, because you are getting a login prompt. That means your issue is not about a cached login as much as maybe something is not shared correctly. In our case, once, it was the settings in the enterprise geodatabase, not on the services per se. ... View more