Skip to main content
Question

ESRI ArcGIS Data Interoperability, Running spatial ETL tool - "Debug..." mode runs, "Open..." mode fails

  • September 11, 2019
  • 4 replies
  • 122 views

bwasserstein
Participant
Forum|alt.badge.img

This is somewhat of a bigger picture type question and perhaps better if directed at ESRI, but figured I'd ask here too. I've had this problem with FME 2015 and my current 2018 version (FME(R) 2018.0.0.2 (20180414 - Build 18301 - WIN32)). I use ESRI ArcGIS Data Interoperability extension to access the FME workbench.

I generally will run my tools directly in workbench, but occasionally I'll run them from the toolbox containing the Spatial ETL tool in ArcCatalog. I can only get this to work if I run my tools in "Debug..." mode. Opening a spatial ETL tool ("Open..." or simply double-clicking it) pulls up the dialog box where I can enter published parameters, but clicking "OK" to run the tool this way always results in the spatial ETL tool failing and/or ArcCatalog kicking out a background processing warning ("Backing processing has encountered a serious error and is unable to continue"). The Results pane in ArcCatalog gives an "ERROR 000819: The tool is not available or is unassigned."

Again, might be a question better suited for ESRI, but figured I'd give it a shot here. How do I correct this so I can run my spatial ETL tools by simply double-clicking them? I suspect that there's a specific setting somewhere that I don't have set correctly or something. I'd like to be able to just double-click the spatial ETL tool, apply the published parameters, then run the tool without ever opening workbench or running in 'Debug...' mode. This makes it much easier to pass a toolbox off to someone else who might be less familiar with FME.

I'm happy to provide any more info if need be & thanks for any help you can provide.

FME Information:

Edition: Data Interoperability (node locked-crc)

 

Version: FME(R) 2018.0.0.2 (20180414 - Build 18301 - WIN32)

 

Locale: en_US

 

Codepage: 1252 (ANSI - Latin I)

 

Home Folder: C:\\Program Files (x86)\\Esri\\Data Interoperability (x86)\\

 

Operating System: Microsoft Windows 10 64-bit (Build 17763)

4 replies

rahulsharma
Safer
Forum|alt.badge.img+10
  • Safer
  • September 11, 2019

Hi @bwasserstein

Can you confirm if you have the extension turned on i.e. Go To Customize > Extension > FME Extension for ArcGIS?

If not, close the workbench, Enable the extension and run the tool again.

 


bwasserstein
Participant
Forum|alt.badge.img
  • Author
  • Participant
  • September 11, 2019
rahulsharma wrote:

Hi @bwasserstein

Can you confirm if you have the extension turned on i.e. Go To Customize > Extension > FME Extension for ArcGIS?

If not, close the workbench, Enable the extension and run the tool again.

 

Oh yes, that is on. I'm able to run FME just fine from workbench and in "Debug..." mode, but not from "Open..." mode (i.e., just double-clicking the tool in the toolbox from ArcCatalog or right-clicking it and choosing "Open...").

I haven't been able to find anything on GeoNet about this issue.


bruceharold
Contributor
Forum|alt.badge.img+17
  • Contributor
  • September 11, 2019
bwasserstein wrote:

Oh yes, that is on. I'm able to run FME just fine from workbench and in "Debug..." mode, but not from "Open..." mode (i.e., just double-clicking the tool in the toolbox from ArcCatalog or right-clicking it and choosing "Open...").

I haven't been able to find anything on GeoNet about this issue.

If you have 64bit background processing installed it will not work, Data Interop 10.x only uses the 32bit install. Turn off background GP to run the ETL tool in immediate mode.

 


bwasserstein
Participant
Forum|alt.badge.img
  • Author
  • Participant
  • September 11, 2019
bruceharold wrote:

If you have 64bit background processing installed it will not work, Data Interop 10.x only uses the 32bit install. Turn off background GP to run the ETL tool in immediate mode.

 

@bruceharold VOILA! Thank you for solving the issue that has eluded me for a couple years now. Ha! I knew it was something easy. I guess I should have caught on to this with the background processing error message.

 

Thank you, thank you, thank you :)


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings