|
POST
|
Our organization performs database maintenance using a python script against our enterprise geodatabase on a daily basis (well at least during workdays). While the script we use has been in place for a couple of years, a colleague and I decided to re-look at the script to see if we could improve any performance or make any adjustments to make it better. In a nutshell our script works like this: Block connection to database > disconnect users > reconcile versions > analyze datasets > compress database > rebuild indexes > accept connections to database The issue we are having at the moment is the proper usage of analyze datasets tool; admittedly the correct usage of this tool has always baffled me. But in any event, right now the we way have it set up is that runs against the following: tables, feature classes that reside at the root level of the database, feature datasets, and all feature classes that reside within each feature dataset. My main question is this: running the analyze datasets against the feature datasets and the feature classes that reside in the feature datasets separately, is that overkill? For instance, say we simply run the tool against the feature datasets ... does that also analyze all the feature classes that live within it? Or is the way we have it set up the correct way? The way we have it set up is definitely the slower way. So if in fact what we are doing is overkill, we would like to modify appropriately in the interest of time and cut down on any superfluous tasks.
... View more
12-09-2020
12:37 PM
|
1
|
8
|
4483
|
|
POST
|
Glad I found this thread. Our organization seems to have encountered the same issue as the OP and others have posted; we've discovered that the Join Field tool in arcpy corrupts the input feature class. Just as some background, we had a script on a server that would run nightly via task scheduler. It would take a polygon feature class and join it to records from a standalone table to populate a feature class on our SDE and a map service (note we are running 10.4.1 and have SQL as RDBMS). The script had been in place for at least a couple of years running smoothly, however, sometime in early November of this year it was failing during the join step. After reviewing the error log we set up, a colleague and I attempted to troubleshoot. We spent a good amount of time trying to figure out why it was failing but were coming up dry. It was driving us crazy because nothing had changed on the code end; it just stopped working. After looking at the intermediate output data (we had a scratch GDB set up to see what was going on), we encountered an error on the staging join feature class. We couldn't open it up in ArcMap/Pro, view properties, nor could arcpy delete it ... it became corrupt. Personally, I had a suspicion that it may have been due to security updates that were installed on the server where the script resides. But I honestly don't really have a way to prove that besides timestamps when this script started failing and when updates were installed. We needed to find a workaround. Basically we modified the code to use Add Join and the in_memory workspace in place of Join Field. While it did indeed at some lines of code to our script, overall, it's been good in the sense that we went from a task that took an hour and 15 minutes to run, to a task that only takes roughly 10 minutes to complete. So at least something positive came out of the issues we were having. Overall, it was just highly annoying when you expect a tool to work, and it does for an extended period of time, but fails suddenly without any rhyme or reason.
... View more
12-07-2020
08:51 AM
|
0
|
0
|
2289
|
|
POST
|
Mark Johnson wrote: I'm a little confused on the SetLogHistory option, I like to be able to refer back to my history in Desktop/Pro, I just don't want it attached to my data. I agree, I am also confused about the SetLogHistory option; is there just a way to turn it off completely against an enterprise GDB? I've cleared Geoprocessing history using the GUI tools referenced in this link ... it was successful in assisting with some performance issues we were experiencing. But turning it off completely; how is that performed exactly?
... View more
05-18-2020
11:54 AM
|
0
|
1
|
1563
|
|
POST
|
You provided some pretty simple, yet extremely valuable information. I was wondering why my buildings were extruding artificially high, all the while not realizing CE defaults to meters. Obviously I needed to convert my data to feet, but I must have missed that in the tutorials I was following ... in any event, I am appreciative of your post.
... View more
03-05-2020
10:29 AM
|
0
|
0
|
2339
|
|
POST
|
Thank you for the reply Andrew. I'll most likely log a support ticket, however, you response makes me feel a bit more comfortable with the upgrade. We'll probably just upgrade to 10.6 for the moment and then per your advice, come up with and follow an update cycle on a regular basis.
... View more
02-03-2020
10:53 AM
|
0
|
0
|
1859
|
|
POST
|
Hey Andrew, Your response was helpful, but still a bit leery on some things. I understand that running ArcGIS License Manager at a lower level than the Desktop installations could be problematic; I'm actually surprised our client machines at 10.5 run hitting the 10.4.1 License Manager. Perhaps we found a glitch? In any even, you are basically recommending that we upgrade to the latest version of ArcGIS License Manager, which at the moment is version 2019.1? And then keeping up to date with the most current release? One of the items that makes me a bit hesitant to jump on this upgrade is the authorization number differences for versions greater than 10.5 ... honestly, the process confuses me and I'm unclear on the workflow needed to upgrade. As a result it makes me a bit hesitant to perform upgrades on the server side, especially since we have to perform these upgrades during the evening or on weekends when support is not directly available. Note this link was another one I consulted, for those following this thread.
... View more
01-30-2020
11:00 AM
|
0
|
2
|
1859
|
|
POST
|
My organization has a server that hosts ArcGIS Server and License Manager at both version 10.4.1. Most of the client machines at our organization run Desktop at version 10.5 with no problem, even connecting with the 10.4.1 License Manager. To throw a monkey-wrench in our current setup, we recently learned from one of our vendors that we need to have at least one Desktop machine running 10.6 for a specific set of tools to work with an enterprise system. Would it be possible to upgrade the License Manager to version 10.6 on this box while keeping the ArcGIS Server version at 10.4.1.? Some of you may ask: why not upgrade everything? Ahh the problem lies with legacy systems; we eventually plan to upgrade the entire fleet, but limited funding, dealing with old systems, and being a relatively small operation prevent this from happening overnight.
... View more
01-28-2020
04:45 PM
|
0
|
4
|
1982
|
|
POST
|
... and why has this post been marked as 'Assumed Answered'?
... View more
12-04-2019
10:53 AM
|
0
|
0
|
489
|
|
POST
|
Our organization is currently testing the use of workforce with one of our departments. Most of the pilot project has gone smoothly except for the 'Search for an address' component. For instance, if a dispatcher searches for an address and clicks the '+Create Assignment' button, two entries appear, separated by comma. A dispatcher has to manually clean up the address. Also, to clarify, Workforce is only dropping one point on the map, but still the address shows up twice in text format. Another item to note is that dropping a point manually in the map will only result in one entry (but most of the dispatchers at our organization are not comfortable with zooming to an area and dropping a point; they prefer the search functionality). Has anyone else seen/experienced this behavior? Can it be modified?
... View more
12-03-2019
10:55 AM
|
0
|
1
|
554
|
|
IDEA
|
I'm glad I'm not the only one who like to have a list of questions/fields that a worker and/or dispatcher would fill out at the beginning of an assignment and then get automatically transferred to Survery123. We currently have a small pilot project going on for a particular department and this limitation is a hold up; without this functionality I am not sure we can proceed going the 'paperless' route.
... View more
10-22-2019
08:11 AM
|
0
|
0
|
2084
|
|
BLOG
|
As a user that is part of organization that is really pushing for the usage of Pro over ArcMap, I found the hard way that there are indeed many different between the datetime modules/submodels. Suppose I need to get to studying the link you provided ...
... View more
07-02-2019
12:25 PM
|
1
|
0
|
1063
|
|
POST
|
...I changed the name of the 32 bit python to python32... What exactly did you change the name of? python.exe? pythonw.exe? Right now I am struggling with this issue on a server, both 32 and 64-bit versions of python are installed. Even if I manually try to run a script using the 32-bit version, it always runs in 64 ...
... View more
06-19-2019
11:54 AM
|
0
|
0
|
21915
|
|
POST
|
Glad to hear that this is a known issue and it will be addressed in the next release! As far as the second issue is concerned, I have not seen the behavior repeat itself. I'm thinking it may have just been a hiccup; but I am not sure on which end ... the ESRI end or the Microsoft side? In any event, I am glad it has 'self-resolved' ...
... View more
04-25-2019
05:34 AM
|
0
|
0
|
1660
|
|
POST
|
Small update with regard to Issue 2. To see if we could replicate the time issue I experienced yesterday, I had a survey submitted @ 1:28pm. Lo and behold it triggered the email blast and spreadsheet population in SharePoint. That appears to have debunked my 1pm time issue theory. Plus I have not seen the non-triggering flow issue occur again. One thing I've read online is that a flow will not be triggered if a survey is edited after it's been submitted, however, there doesn't seem to be any way for that type of activity to occur due to the way we have this particular form set up ...
... View more
04-12-2019
11:33 AM
|
0
|
0
|
1660
|
|
POST
|
I've been experiencing some weird behavior with regard to Survey123 and time. This is kind of multi-part issue really, I'm hoping they are somewhat related, but my guess is they are two separate issues. I'll do my best to describe below. Issue 1: Our organization set up a survey where you have two sections where you can manually enter time (although it will auto populate based on the current time): 'Time of Notification' and 'Time of Arrival'. However, if you select anytime between 12:00 PM and 12:45 PM it presents an error message, stating 'This is a required question.' Note that for this section, you can only pick 15 minute intervals, so 12:00, 12:15, 12:30, and 12:45 will error out. Issue 2: We've set up another survey where it's populating an Excel spreadsheet in SharePoint and sending out email notifications using Microsoft Flow. Note this one has no manual time entry ... however, it's still recording time on the back end of ArcGIS Online. This process has been working fine except today I noticed that a survey that was submitted at 1:25 PM did not trigger in Microsoft Flow. However, Microsoft Flow does not show it as a 'fail', it just flat out did not trigger. Thus the spreadsheet was not populated nor was an email notification sent out. I discovered this particular one after poking around the 'stakeholder' point file on ArcGIS Online. Anyone experienced the behavior described in the scenarios above? Really it appears the first one is just a back-end Survey123 bug … however, I cannot explain the fault behind the second scenario. Plus it's just that much more difficult to troubleshoot; I suppose I can keep monitoring the data and making sure both the point file in AGOL match what populates in the spreadsheet.
... View more
04-12-2019
05:33 AM
|
0
|
4
|
1748
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 09-23-2025 06:39 AM | |
| 1 | 12-13-2021 09:19 AM | |
| 1 | 12-09-2022 06:41 AM | |
| 1 | 04-11-2022 08:19 AM | |
| 3 | 07-17-2023 07:44 AM |
| Online Status |
Offline
|
| Date Last Visited |
10-01-2025
09:07 AM
|