Skip to main content

In my startup script I use an "import ArcPy" in order to create a new version of my ArcSDE database. I changed the Python interpreter to C:\Windows\SysWOW64\python27.dll.

My code (some "private parts" disguised with <XXXXXX>

import sys
import datetime
import arcpy
import fme
inWorkspace = r'<XXXXXX>BUDATA/ArcSDE Connecties/GABUAPP_AREAALDATA.sde'parentVersion = 'sde.DEFAULT'
versionName =  'GISIBsync_' + datetime.datetime.now().strftime('%Y%m%d_%H%M%S')
arcpy.CreateVersion_management(inWorkspace,parentVersion,versionName,"PUBLIC")

To my surprise during runtime it seems as if the startup script is trying to create an Autodesk 3Ds reader (in bold in the output beneath), which is strange since my FME-workspace only contains Oracle Spatial and ArcSDE readers. It also seems that this reader is trying to read the ArcGIS toolboxes (!).

Even stranger: after this unsuccesful creation of a reader, the startup script continues, and finally creates the ArcSDE database version. 

Starting translation...

2016-12-14 09:05:02|   0.8|  0.8|INFORM|FME 2015.0 (20150217 - Build 15253 - WIN32)

2016-12-14 09:05:02|   0.8|  0.0|INFORM|FME_HOME is 'C:\Program Files (x86)\FME\'

2016-12-14 09:05:02|   0.8|  0.0|INFORM|FME Desktop Oracle Edition (floating)

2016-12-14 09:05:02|   0.8|  0.0|INFORM|Permanent License.

2016-12-14 09:05:02|   0.8|  0.0|INFORM|Machine host name is: <XXXXXXX>

2016-12-14 09:05:02|   0.8|  0.0|INFORM|START - ProcessID: 1136, peak process memory usage: 53012 kB, current process memory usage: 53012 kB

2016-12-14 09:05:02|   0.8|  0.0|INFORM|FME Configuration: Command line arguments are `C:\Program Files (x86)\FME\fme.exe' `D:/git_repo/Etl/Geodatabase_writer\wb-xlate-1481702696704_1512' `LOG_STANDARDOUT' `YES' `LogCountServerName' `{c70fed7a-9180-42a0-a51c-7f03e505c4b8}'

2016-12-14 09:05:03|   1.0|  0.2|INFORM|Using user-specified Python interpreter from C:\Windows\SysWOW64\python27.dll

2016-12-14 09:05:03|   1.0|  0.0|INFORM|Python version 2.7 successfully loaded

2016-12-14 09:05:03|   1.0|  0.0|INFORM|FME_BEGIN_PYTHON: evaluating python script from string...

2016-12-14 09:05:12|   8.8|  7.8|INFORM|FME Extension for ArcGIS (9) (20140217 - Build 14241 - WIN32)

2016-12-14 09:05:12|   8.8|  0.0|INFORM|FME 2015.0 (Build 15253)

2016-12-14 09:05:25|  20.2| 11.4|INFORM|Creating reader for format: Autodesk 3ds

2016-12-14 09:05:25|  20.2|  0.0|INFORM|Trying to find a DYNAMIC plugin for reader named `3DS'

2016-12-14 09:05:25|  20.3|  0.0|INFORM|Loaded module '3DS' from file 'C:\Program Files (x86)\FME\plugins/3ds/3ds.dll'

2016-12-14 09:05:25|  20.3|  0.0|INFORM|FME API version of module '3DS' matches current internal version (3.7 20141021)

2016-12-14 09:05:25|  20.3|  0.0|INFORM|Creating reader for format: Autodesk 3ds

2016-12-14 09:05:25|  20.3|  0.0|INFORM|Trying to find a DYNAMIC plugin for reader named `3DS'

2016-12-14 09:05:25|  20.3|  0.0|INFORM|FME API version of module '3DS' matches current internal version (3.7 20141021)

2016-12-14 09:05:25|  20.3|  0.0|INFORM|3DS Reader: Reading in Variable FeatureType mode

2016-12-14 09:05:25|  20.3|  0.0|INFORM|3DS Reader: Opening dataset: 'C:/Program Files (x86)/ArcGIS/ArcGISDataReviewer/Desktop10.2/ArcToolbox/Toolboxes/Data Reviewer Tools.tbx'

2016-12-14 09:05:25|  20.3|  0.0|ERROR |3DS Reader: Failed to load file: 'C:/Program Files (x86)/ArcGIS/ArcGISDataReviewer/Desktop10.2/ArcToolbox/Toolboxes/Data Reviewer Tools.tbx'

2016-12-14 09:05:25|  20.3|  0.0|ERROR |3DS Reader: Error opening the dataset: 'C:/Program Files (x86)/ArcGIS/ArcGISDataReviewer/Desktop10.2/ArcToolbox/Toolboxes/Data Reviewer Tools.tbx'

2016-12-14 09:05:25|  20.3|  0.0|INFORM|3DS Reader: Closing reader

2016-12-14 09:05:25|  20.3|  0.0|WARN  |UniversalReader -- readSchema resulted in 0 schema features being returned

2016-12-14 09:05:25|  20.3|  0.0|WARN  |Reader Parameter(0) = >C:\Program Files (x86)\ArcGIS\ArcGISDataReviewer\Desktop10.2\ArcToolbox\Toolboxes\Data Reviewer Tools.tbx<

2016-12-14 09:05:25|  20.3|  0.0|WARN  |Reader Directive(0) = >UNIQUE_ID_ATTRIBUTE<

2016-12-14 09:05:25|  20.3|  0.0|WARN  |Reader Directive(1) = >FME_FEATURE_ID<

2016-12-14 09:05:25|  20.3|  0.0|WARN  |Reader Directive(2) = >PERSISTENT_CACHE<

First of all, you can drop the "import fme" statement and see if that makes a difference.

Also, try temporarily removing the startup script and compare the logs, does FME still try to create the Autodesk reader?


Dropping the "import fme" doesn't make a difference.

When removing the startup script completely FME doesn't create the Autdesk 3Ds Reader. Also, when having a startup script without import ArcPy the Autodesk Reader isn't created.

One thing to note is that our ArcGIS (10.2.2) setup includes the Data Interoperability extension.

 

Perhaps this lead to a sort of "circular reference"?

(unfortunately I can't remove the Data Interop extension myself to check it out, the entire setup of both FME and ArcGIS have been scripted)


The Data Interop might possibly explain it, but that sounds like a question for Safe support.

Is it a show-stopper for your workspace?


Not a show-stopper, as the script continues and creates the new version in ArcSDE.

 

But a bit inconvenient, since I'd rather have my scripts & workspace error-free

I can symphatize. Consider opening a support ticket with Safe: https://support.safe.com/knowledgeSubmitCase?


Reply