When I run Data Interoperability via Windows Task Scheduler, I receive an "ERROR : Python Exception <ExecuteError>: ERROR 160236: The operation is not supported by this implementation. Failed to execute (DeleteRows)." from my shutdown script.
When I run it manually in ArcPro, I do not receive any errors and everything works as expected.
Any suggestions?
Also, @BruceHarold -- is there a way to subscribe to your "What's New in ArcGIS Data Interoperability" blog posts?
Thank you!!
Hello Ashley
It seems you have struck an issue we haven't found a cause for:
If you open a support call the analyst can look at your workflow.
Re. subscribing, if you subscribe to the whole Data Interoperability board you'll get everything, and thank you for asking.
Hi Ashley,
Were you able to resolve this issue? I have been intermittently encountering the same error while running scripts through Task Scheduler and have been unable to determine the cause or a fix.
Thank you!
Any luck?
This is still a problem. I had a bat script running for a little over a month with no issues. Now it consistently fails when run from scheduler, no issues at all from manually running the bat. The only thing that coincided with the crash was logging back into my AGOL portal. the script seems to still be able to read and recognize it is in the correct portal.
I get the same error using deleteFeatures() and/or DeleteRows()
I think you should open a support call, it will be hard to troubleshoot here.
Just chiming in that we have had the same experience as Jonathan. Python script randomly fails at .DeleteRows with error 160236 (which is why I subscribed to this discussion).
The 'schedule' is monthly, so running the script manually is acceptable (for this case, for now). We've tried different user accounts, administrative user accounts, 'run with highest privileges', and more.
OK, sorry to hear that but the good news is the team at Esri will act on reproducible issues so sharing your code will help with that.
Like Jonathan, my account is not an "authorized caller", so I won't be able to escalate this beyond the Community.