Latest Contributions by JakeSkinner

Hi @Kato, Can you post a screenshot of how you have the tool setup?   Do you receive the same error when converting to a feature class? ... View more

@IqbalRidwan yes, the Portal service will restart:   ... View more

@imansbburg if the replicas are not in use, you can unregister them. Also, test to make sure there are no orphaned locks.  Stop ArcGIS Server and disconnect all users from the geodatabase.  You can then query the following tables: sde.sde_layer_locks sde.sde_object_locks sde.sde_state_locks sde.sde_table_locks These should be empty at this point.  If there are any rows, you can delete these.  Before deleting be sure you have a database backup. ... View more

@Hal-AhmedShehata the Update Enterprise Geodatabase Data Stores.py will only update the metadata of the services.  Ex:   The script will not repoint the service to the new data source.  This is done by updating the Data Store connection itself.  There is no downside of not running the scripts other than seeing the incorrect database information reported in ArcGIS Server Manager (screen shots above). ... View more

@KevinMorrow I'm not an expert with Web Scenes, but the issue may be going from AGOL to Portal.  What version of Portal are you running?  Also, if you want to share the Web Scene to a Group and invite my AGOL account, my username is 'jskinner_rats'. ... View more

@RafaelFSouza referenced services are now supported. ... View more

@imansbburg there is most likely locks that are causing the delta table not to be compressed.  Are there any replicas in your geodatabase?  If so, make sure you synchronize these before executing the tool. ... View more

@RafaelFSouza I may have this completed in the next week. ... View more

@DougBrowning I highly recommend heavily used services to be set to Dedicated.  For the number of instances, there is no default answer.  I would recommend starting at a min of 1 and a max of 4.  Let the service receive requests for a some time (i.e. half day/full day) and take a look in ArcGIS Server Manager > Logs > Statistics.  You can view the number of requests that particular service is receiving.    Check the Average Response Time statistic for the service.    I typically recommend keeping the response to 2 seconds or less.  If you see excessive times, check the Service Maximum Running  Instances for the service: If the Max Running Instances are maxed out (i.e. 4 instances) this is indicating clients are waiting for a instance to handle their requests, which means you should increase the max instances for this service. ... View more

@Philip_Sarnecki you may get better performance using an Update Cursor rather than the field calculator.  Ex: import arcpy pointFC = r"C:\temp\test.gdb\points" polygonFC = r"C:\temp\test.gdb\polygons" # Perform Spatial Join spatialJoinFC = arcpy.SpatialJoin_analysis(.....) # Create lookup dictionary nameDict = {} with arcpy.da.SearchCursor(spatialJoinFC, ["uniqueId", "area_name"]) as cursor: for row in cursor: nameDict[row[0]] = row[1] del cursor # Update point feature class with arcpy.da.UpdateCursor(pointFC, ["uniqueId", "name"]) as cursor: for row in cursor: row[1] = nameDict[row[0]] cursor.updateRow(row) del cursor ... View more

Hi @Jay_Gregory, I don't know the specifics of how the distributed collaboration works, but I know GlobalIDs are required to create copies of the data and keep them in-sync, so I agree with you that the recreation of this field is the culprit.   Are there several feature classes/tables that are updated via SQL that participate in your collaboration?  It may be worth exploring other options outside of a distributed collaboration to keep these datasets in-sync.  Here is one solution I've implemented with several customers: https://community.esri.com/t5/arcgis-online-documents/overwrite-arcgis-online-feature-service-using/ta-p/904457 ... View more

Yes, opening a support ticket would be a good idea. ... View more

Just "CSV Files". ... View more