I have developed a Python Script that performs a variety of geoprocessing and data-loading tasks, including kicking off SQL statements through the command-line. We have tested the script extensively in our development environment, and it successfully runs in production. However when run through the windows task scheduler the target SDE feature class ends up getting stuck in "Load-Only Mode", even though the script ran successfully.
All SQL statements run as a sub-process and report errors back to the Python environment, but messages that do not halt execution are not transferred.
I'm at a loss as to why this would happen exclusively through automation and not when run manually. Any help, ideas, or comments would be appreciated.
All SQL statements run as a sub-process and report errors back to the Python environment, but messages that do not halt execution are not transferred.
I'm at a loss as to why this would happen exclusively through automation and not when run manually. Any help, ideas, or comments would be appreciated.