Latest Contributions by collindegueurce

‎02-01-2021

If your scheduled task completes successfully (code 0x0), but nothing seems to happen as the result of your code, the cause may be how you are using relative paths in your script. Yes, you may have enter fully qualified paths to python.exe and your script (and maybe filled the "start in" item too) when configuring the scheduled task BUT the scheduled task itself starts from C:\win32 and certain relative path syntax that work in an IDE (e.g., IDLE, pyCharm, etc.) will not work as a scheduled task. For example, a script containing a relative path of /pathToItem works just fine in IDLE. However, if you print out the path (to a txt file) that is created from when executed from Task Scheduler you can see that the script is actually looking for the resource in C:\win32\pathToItem. Obviously, this isn't going to work. Changing the relative path to ./pathToItem is a simple fix that may allow your script to truly execute successfully from Task Scheduler.

‎09-08-2015

Asrujit is right. You can upgrade your sde geoDB if you are upgrading sqlserver from the 2008 to the 2012 or 2014 without rename it. Then use arccatalog and upgrade the DB, if you have changed arcgis version.

‎09-02-2015

There is much discussion about compression and I am hoping someone can clear up an issue I am having. We are using versioned editing. Each user has a version that they have created under their own connections. We were having an issue with compression ending states being high - around 40. Many of the versions were old and some were stale. So I rec/posted and deleted the versions. end state was 1. Then I asked everyone to create a new version for themselves. The problem with this is that not everyone used the same name in creating their new version so many of the datasources in their maps became broken. It was a hassle, but the performance gains of the near-full compression were notable and worth the trouble. However, now that users have recreated their versions my state count is going up again after compression. Even if I reconcile the versions first, I can't get below 10 ending states - we have 10 versions. I would like to script the deletion and recreation of the versions as part of an automated workflow, but since the users own their versions, I would have to have a connection as each user to be able to do that. Is that correct? I have the same issue with rebuilding indexes and analyzing datasets...I need to do it under the data owner connection - is that correct? Should I just force all versions to be owned by DBO? Am I missing something that will allow me to achieve what I want without users having to constantly recreate their own versions? Is it normal that each version will account for at least 1 end state after compression even if it is first reconciled?

Re: Keeping track of user licenses · ‎08-12-2015

Thank you Sent from my iPhone

‎07-14-2015

I stand corrected. The update cursor did in fact work. Thank you guys!

‎11-24-2014

Looks like the answer was actually very simple. I had upgraded my Desktop version to the 10.3 pre-release while the server version is 10.2...When I published from 10.2.2 Desktop everything worked just fine.

‎08-25-2014

Thanks!

Online Status	Offline
Date Last Visited	‎11-11-2020 02:24 AM

My Ideas

Latest Contributions by collindegueurce

Re: Python Script not running through Task Scheduler on Windows Server 2008

Re: Migrating to a new geodatabase

SDE Compression and named versions

Re: Keeping track of user licenses

Re: Field calculator python script and OBJECTID ordering issue

Re: Collector only working when connected to company network

Re: arcpy.AddFieldDelimiters