This is a known issue for ArcGIS 10: NIM058011. The metadata geoprocessing tools are written in C#. If you add GpMetadataFunctions.dll and MetadataTranslator.dll to the Global Assembly Cache (GAC) the script will run successfully outside of ArcGIS. This issue affects all of the metadata geoprocessing tools, not just Export Metadata.
NOTE: this issue has nothing to do with Map Automation, and probably belongs in a general geoprocessing forum.
This is a known issue for ArcGIS 10: NIM058011. The metadata geoprocessing tools are written in C#. If you add GpMetadataFunctions.dll and MetadataTranslator.dll to the Global Assembly Cache (GAC) the script will run successfully outside of ArcGIS. This issue affects all of the metadata geoprocessing tools, not just Export Metadata.
NOTE: this issue has nothing to do with Map Automation, and probably belongs in a general geoprocessing forum.
I was able to fix the problem by installing .NET Framework 2.0 SDK and adding the .dlls to the GAC using gacutil.exe /i
"C:\Program Files\Microsoft.NET\SDK\v2.0\Bin\gacutil.exe" /i "C:\Program Files\ArcGIS\Desktop10.0\Bin\GpMetadataFunctions.dll"
"C:\Program Files\Microsoft.NET\SDK\v2.0\Bin\gacutil.exe" /i "C:\Program Files\ArcGIS\Desktop10.0\Bin\MetadataTranslator.dll"
thanks for the info!
I have an 'export metadata' python script written using 9.3 module and when running it on a ArcGIS 10.0 box it would always cause python to crash.
Installed .NET SDK then added the above 2 .dll's to the GAC and the script works perfectly now...just had to change all the ref's from 9.3 tools/meta translators to the v10 paths and all is well. Sure wish the install dir's were the same with v9.3 and v10; sure makes using old scripts on v10 a hassle.
thanks again
thanks for the info!
I have an 'export metadata' python script written using 9.3 module and ....