nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Import Meta Data fail

JoeBorgione

I have a script that runs a a scheduled task: it first deletes features in a target feature class and then appends features to that target from a source. That part of the script works fine. However, the last part of the script attempts to import meta data from the source to the target and fails with a generic error of "Object: Error in executing tool". I can run import metadata from an arc catalog python without a problem. Not sure what I should be looking for....

&nbsp;&nbsp;&nbsp; <SPAN class="keyword token">try</SPAN><SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; arcpy<SPAN class="punctuation token">.</SPAN>MetadataImporter_conversion<SPAN class="punctuation token">(</SPAN>SourceFeatureClass<SPAN class="punctuation token">,</SPAN>TargetFeatureClass<SPAN class="punctuation token">)</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="keyword token">print</SPAN> <SPAN class="string token">'Successfully Imported Metadata From {} To {}'</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN>SourceFeatureClass<SPAN class="punctuation token">,</SPAN>TargetFeatureClass<SPAN class="punctuation token">)</SPAN>
&nbsp;&nbsp;&nbsp; <SPAN class="keyword token">except</SPAN> Exception <SPAN class="keyword token">as</SPAN> err<SPAN class="punctuation token">:</SPAN>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <SPAN class="keyword token">print</SPAN> err
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sendEmail<SPAN class="punctuation token">(</SPAN>err<SPAN class="punctuation token">)</SPAN><SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

Find more posts tagged with

Accepted answers

JoeBorgione

ESRI tech support has suggested that the issue is due to a 64 bit install of python.exe and a 32 bit import metadata conversion tool. The computer that runs the scheduled task has two python installs:

C:\Python27\ArcGIS10.5

and

C:\Python27\ArcGISx6410.5

He would like me to 'point' the scheduled task script to the 32 bit exe, but doesn't offer a suggestion as to how to do it. Any suggestions?

eta: I went to the script in question, and with a right click chose 'Open With' and selected the 32bit python.exe.

All comments

JoeBorgione

This particular machine does not have pro on it: it's a server. I think I have it figured out though, as some of the other guys have had the same problem. In the task scheduler, you mojo around with the settings and point the trigger to the 32 bit python.exe and add the script name as an argument....

DanPatterson_Retired

remove 64-bit python 2.7 would be my suggestion... you can use ArcGIS Pro your 64-bit needs.

JoeBorgione

C:\Python27\ArcGIS10.5

and

C:\Python27\ArcGISx6410.5

He would like me to 'point' the scheduled task script to the 32 bit exe, but doesn't offer a suggestion as to how to do it. Any suggestions?

eta: I went to the script in question, and with a right click chose 'Open With' and selected the 32bit python.exe.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.