Latest Contributions by JustinMuise

@Bud - What version of ArcGIS Pro are you using? The -494 error in the log file maps to "SE_UNSUPPORTED_DATABASE_VERSION" which makes me believe you are in a configuration that does not support Oracle 18: (https://help.arcgis.com/en/geodatabase/10.0/sdk/arcsde/api/capi/returncodes_incl.htm). For example, Oracle 18 is not supported with ArcGIS Pro 3.0 or above:  https://enterprise.arcgis.com/en/system-requirements/11.0/windows/database-requirements-oracle.htm ... View more

Hello! If the DEFAULT version somehow reverted back to public, that could be a bug. However, when altering the DEFAULT version for branch versioning, as previously stated, you need to do this through the database connection. More specifically however, you need to make sure the database connection is using a branch versioning connection (Geodatabase Connection Properties > Branch). You should not be required to re-publish or restart your service. Hope this helps! Justin ... View more

Hi Jonathan, The access level of default needs to be altered through a database connection connected as the geodatabase administrator (typically either sde or dbo). Hope this helps! Justin ... View more

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 ... View more

@DasheEbra , Branch versioning does not support having the dbo user or the sde user as the data owner since it causes the behavior as you described. In ArcGIS Pro 3.0, we will be blocking the ability to register datasets as branch for these users, and the documentation will also be updated. Apologies for the inconvenience. Thanks! Justin ... View more

Hi @DasheEbra , Can you comment on who own the underlying feature class that was used to publish the feature service? Are they the sde or dbo user by any chance? Justin   ... View more

Moelsaket, Can you comment on whether the user has any permissions from the Administrator Privileges list? Also, which user owns the underlying data? Thanks! Justin ... View more

Hi Brian, You are correct - the notion of having to delete your version after you have posted your edits to Default is not applicable to Branch Versioning. With Traditional Versioning, this workflow was recommended as your version could hold state locks which could prevent a good compress. Since Branch Versioning was built in a manner that eliminates the requirement to compress, so does the requirement to delete your version. However, deleting versions which are no longer used by users is always a good practice! Hope this helps! Justin ... View more

Michael, Sorry to hear that the original suggestion did not work for you, but I am happy to heard that installing the UN Patch 5 Version B allowed you to have a successful reconcile. Regards, Justin ... View more

Hi Michael, I believe Tim is referring to completing the entire Reconcile process directly using the REST Endpoint. In this case, you would be responsible to call startReading, startEditing, Reconcile, stopEditing and stopReading through the REST Endpoint using the appropriate URLs.  This avoids the time-out issue because what is timing-out in this scenario is the client, ArcGIS Pro - which waits for a response from the server for 10 minutes. The GP tool is not being ran off the server. Hope this clarifies things. Justin ... View more

Hi Tim, I suspect the 10 minute timeout you are seeing is actually a client-side (Pro) timeout. The application also has internal timeouts in regards to how long ArcGIS Pro will wait for a request back from the server. Unfortunately, there is no way to configure the client timeout; therefore, the workaround you've identified is the right approach. I would like to add a couple of things though: 1) If you are ever concerned about the performance of a reconcile operation, it's best to get in contact with Support to see if there are any improvements we might be able to make to optimize the operation; and, 2) In an upcoming release, the Reconcile Versions geoprocessing tool will actually be executed asynchronously, so there will be a manner in Pro to complete long running reconcile processes. Thanks! Justin ... View more

Hi Aaron, You are correct - Branch Versioning does not support "grand-child" versions; therefore, the QA/QC workflow you are describing is not possible. With Branch Versioning, the recommended workflow to achieve a similar experience would be the change the ownership of the Editor version to a Version Administrator (user with elevated privileges) to complete the QA/QC process, who can then post to the Default version when the process is complete. Hope this helps! Justin ... View more

Hi Josh, How long is the reconcile operation running for? Can you also provide some information on the settings you are using with the Reconcile GP tool? More specifically, do you have the option to "Abort if Conflicted Detected" checked? Thanks! Justin ... View more