Latest Contributions by MattMoore

Did you ever find a solution to this? Have a customer that came across the same issue.  ... View more

@SSWoodward how does this apply to ArcGIS Enterprise, specifically ArcGIS Server 10.9.1 versus 11.1? I'd imagine 11.1 supports this but what about 10.9.1? ... View more

yes turn on verbose or debug logging on your federated ArcGIS Server machine and you should be able to see what the issue is when initiating a sync. ... View more

Assuming your GIS servers are joined to your domain, a simple DNS alias (ex: \\gisfiles.domainname) could shorten your path to "\\xxxxxxxxxxxxxxxxxx.file.core.windows.net". You shouldn't have to rename the base URL to your Azure file storage.  Hopefully you have lower test environments you can test against as you will have to update the ArcGIS Server configuration directories to hit the DNS alias.  ... View more

Good deal, happy to help! ... View more

Should be able to use ArcGIS Server manager to change all the configuration and input directory locations. It will move all the content for you. I'd recommend "C:\arcgisserver" since ESRI decided that adding 190+ characters to the path where it uploads the replica GDBs was a good idea.  192 characters directories\arcgissystem\arcgisuploads\services\Hosted\workforce_dc0b60ddbb49451dba857d5e10df9659.FeatureServer\if8f03b3f-7185-4f4c-93a4-2001748e7d09\du_zgogxolq7mrst52w7ecjvsjw2d.geodatabase Should be able to sync all existing replicas created in workforce afterwards. ... View more

This looks to be your issue as well. The path in your log to the sql lite geodatabase ESRI uses for the replica sync is 273 characters. Shorten that path and you should be good to go. ... View more

Thanks for replying. We are actively engaging the Workforce product development team. Ill post back here if we get resolution to this problem. ... View more

We are having the same issue. Were you able to ever find a fix for this? ... View more

In our case I tested with Portal users that do not own the item (the Feature Service) and yes they can still edit default. These other portal users are publishers only and not portal administrators.  ... View more

I am having the exact same issue against a test environment we setup to test branch versioning. Our environment is 10.6.1 for what its worth. I started a support ticket with ESRI and the support analyst said he is working our issue along with another one someone else submitted to him running 10.7.1. I am hoping to hear back from them in the next few days after they do some internal testing. For what it is worth when I published my feature service to portal I initially attempted to do so as a user ("giseditor") in the GDB that does not have writes to edit DEFAULT(as it is protected and only the schema owner, "SDE" in our case, should be able to edit DEFAULT). However, Pro through an error when I went to publish the service saying that "Version Management is enabled, but the connected geodatabase user, 'giseditor', is not the branch versioned dataset's owner, 'SDE'. Consequently I had to change that connection to the SDE user and publish my service. The outcome is a Feature Service that lets any user with access to the service edit DEFAULT. Not exactly what we were looking for. Portal users with access to that service can technically create branch versions, so that works, but there is nothing protecting DEFAULT.  ... View more

Thanks for the update. Looking forward to the patch. Have a number of customers eager to use Enterprise Sites and this missing functionality is a real challenge. ... View more

Graham, When is ESRI planning on releasing download support for anonymous users in Enterprise Sites? This is a pretty critical function for organizations that have IT policies that wont let them use AGOL/Hub. ... View more