Latest Contributions by ShelbyZelonisRoberson

I set the max records as 2000 but there are only 100 features. Still slow to load even when I clear cache and zoom in. With only 100 records I would expect an extremely fast draw time (like with the hosted version)! ... View more

So, interestingly when I add the /0 map server endpoint - now it doesn't draw! Takes forever and I get the same error about too many features.  ... View more

Yep both https  ... View more

1. I'm assuming you mean why am I using a feature service as opposed to a map service? For one, some of the layers I want to publish eventually are larger (~2000 points) and I want to be able to symbolize them using the heat map styling. Can't do that on a map service. Plus - there's obviously something wrong that I'd like to figure out just for sanity's sake! 2. The simple query returned the results in about 3 seconds, so yes quickly. 3. Logging level is set to verbose. After setting it to Info and adding one of the problem layers to the web map, the most prevalent error is listed as SEVERE and says "Error performing query operation Wait time of the request to the service 'Shortname_Thefts.MapServer' has expired". The full log from the last 15 mins is attached. 4. Portal admin logs don't have anything to do with the service or slowness. One INFO about me updating the log settings to info level but that's it. Thanks very much! ... View more

Hi Patrick -- I'm having a related problem and I was hoping you could provide insight. I am able to get query layers to work in my dashboard items (the query layers are coming from SQL server, similar to what your setup seems to be). However, I don't have any options to create Actions in any of the items (charts, lists, etc) with the layers that are built on query layers. There are no Actions tabs to configure when I choose these data sources. Patrick, are you able to use Actions with your query layer feature services or is this not possible in Ops Dashboard?  ... View more

I feel your pain. Some things that seemed to get the script to at least run partially were: 1. full UNC paths to EVERYTHING, even local paths; 2. Using concurrent licensing; 3. Adding a path to the python folder location in the "Start in" box in the Actions tab of the Windows task.  Like I said, my script still failed at the export to PNG step, but it did partially run when not logged in (it ran at the specified time, imported arcpy, created a folder, and called an ArcGIS Pro project...but then it would stop before creating the exports of the layouts in the Pro project).  ... View more

Thomas - have you found any resolution? I've been working with Esri the last couple weeks but they can't reproduce. I've tried everything I can possibly think of (permissions, paths, file names, etc etc). I actually got to a point where I could get the script to run when not logged in, but it would not finish (it would stop at the last step which was exporting a layout to a PNG).  Have you done any testing? If we find anything similar in our system environments it could help pinpoint the issue.   I ended up uninstalling the production version of 2.1 and re-installing the Beta 2.1. Everything works fine again, so something definitely changed between the two releases. I can manage with the Beta version for now, but I'd really like to be able to upgrade at some point.   ... View more

I didn't change a single thing. I've had a Windows task running a python script every week for the past few months. When I updated to the production version of 2.1 two weeks ago, the task no longer runs when I'm not logged in. I think there might be two issues, possibly related, and I do have a ticket into Esri Tech Support. Here's what happened and my testing steps: The task did not run as scheduled two weeks ago after updating to 2.1 (I had no issues prior to production version of  2.1, it worked in the Beta 2.1 also). I first checked to see if I could run the python script as a standalone. It failed when calling a custom model in the code. *NOTE* no changes were made to this script so the model failing was very strange since it had always worked before. Also, the model runs fine when I run it through Pro 2.1 directly, so it's not like anything changed with paths, data, etc. that would otherwise cause it to fail. To test if it was just an issue with the model, I commented out those lines of code in the python script and tried to run the script again. With these lines commented out, it runs fine as a standalone. I scheduled a Windows task for the script with the model lines commented out. Despite this, it still will not run when I am logged out. However, it does run when I am logged in.  So, I'm back to my original problem (script not running as scheduled task when not logged in) but with an additional complication that my custom model also has stopped working in the script. Again, I have a ticket into Esri tech support and I got an email from them this morning that they elevated my issue due to the complexity. Hopefully that means they might have an understanding of what is going on? ... View more

All -- this stopped working for me when I upgraded my Pro two weeks ago to the production version of 2.1 (and subsequent 2.1.1). My script no longer runs when I am not logged in. Oddly, it worked fine in the Beta of 2.1. Are any of you having similar issues? Thanks. ... View more

I use concurrent use Pro with my script no problem. The one difference between mine and yours is I do not have my Pro set to work offline. If you have taken your Pro offline I can certainly see how that could be an issue. Ever since 2.0.1 this process has worked seamlessly for me. I would definitely suggest contacting Esri tech support if putting your Pro back online doesn't fix the problem.  ... View more

For anyone interested... a patch was released this week for Pro (2.0.1) and it includes the fix for this bug. I tested it and it works! Thanks to all who tried to help solve the issue. Release notes for ArcGIS Pro 2.0—ArcGIS Pro | ArcGIS Desktop  ... View more

Thank you! I feel much less crazy now because I thought that bug was fixed in 2.0 but apparently not. Please keep us posted.  ... View more