Skip to main content
Solved

WorkspaceRunner does not work on Data InterOperability extension of ArcGIS Pro 3.2

C

Hi there,

I recently installed ArcPro 3.2 on my machine with the data interoperability extension. Looking under the hood, the data interoperability extension uses this FME version, FME(R) 2022.2.1.0 (20221202 - Build 22776 - WIN64).

 

When I use the WorkspaceRunner transformer to run a simple workspace (read a text file and view in inspector), the transformer fails to read the published parameter, is says "Specified workspace has no parameters or could not be read". If you run the workspace using the workspacerunner, it gives you an error, "2023-08-03 14:20:14|  2.3| 0.0|ERROR |WorkspaceRunner_ExecutorAndRouter (TestFactory): An error was encountered evaluating a TestFactory test: An error occurred while evaluating a test parameter: @Tcl2 -- failed to evaluate expression `WorkspaceRunner_df4bad67_c886_4b16_8145_a18050c02ff01_runner {} {F:\\ETL\\TEST\\Workbench\\TESTING/workspace1.fmw}' -- unexpected token "END" at position 0; expecting VALUE".

 

Is this an issue with the version of DI ESRI deploys for the ArcPro 3.2? If I use ArcPro 2.9, the workspacerunner does not fail.

 

Hope to hear from the FME engineers.

Cheers,

Chris

Best answer by wrijs

Hi @AliAtSafe , it turns out that if I create and run the fme workspaces directly from ArcGIS Datainterop. Workbench (instead of opening Datainterop from a toolbox in ArcGIS PRO) everything works fine! Being able to open the workspace seperatly from ArcGIS software is new to our version of ArcGIS.

I will view this as my workaround for now.

 

Thanks!

View original
wrijs
1 person upvoted this
  • wrijs
    wrijs
Did this help you find an answer to your question?

7 replies

thejando
Contributor
Forum|alt.badge.img+4
  • thejandoContributor
  • Contributor
  • October 12, 2023

Hi @cpedrezuela​, ArcGIS Pro 3.2 has not been released yet. Do you mean ArcGIS Pro 3.1.2?

 

I can't give you a definitive answer, however the following links could be useful if you haven't seen them yet:

 

The following page describes compatibility between FME and ArcGIS Pro Interoperability extension, however unfortunately it does not appear to have been updated with information regarding ArcGIS Pro 3.1.x

https://community.safe.com/s/article/version-of-fme-equivalent-to-the-esri-data-interop

 

The following page talks about FME and ArcGIS Pro version compatibility. The page recommends that FME version 2022.2.5 and higher is used with ArcGIS Pro 3.1.x. This could be relevant to your scenario.

https://community.safe.com/s/article/notes-on-fme-and-esri-versions-and-compatibility

 

wrijs
Contributor
Forum|alt.badge.img+3
  • wrijsContributor
  • Contributor
  • July 17, 2024

I have the same issue but with ArcGIS PRO 3.3.0 and FME version 2024.0.1.0

AliAtSafe
Safer
Forum|alt.badge.img+22
  • AliAtSafeSafer
  • Safer
  • July 22, 2024

Hi, @wrijs.

Sorry for the trouble. As @thejando had mentioned with the last paragraph (the link as well), ArcGIS Pro 3.3.x is supported with FME Form 2024.0.2.2 and newer. An upgrade would be needed to use Pro 3.3.x. Hope this helps!

Thanks,

Curiosity conquers fear
wrijs
Contributor
Forum|alt.badge.img+3
  • wrijsContributor
  • Contributor
  • July 23, 2024

@AliAtSafe sorry I wasn't clear. But I actually use the Data Interoperability extention that comes with ArcGIS PRO.The latest fme data interop version is 2024.0.1.0. That still might be why the workspacerunner doesnt work sometimes? I have noticed it sometimes does work, I haven't figured out why yet.  

AliAtSafe
Safer
Forum|alt.badge.img+22
  • AliAtSafeSafer
  • Safer
  • July 24, 2024

Hi, @wrijs.

No worries! Apologies, just checked on https://support.esri.com/en-us/knowledge-base/faq-what-are-the-build-numbers-of-the-data-interoperabi-000028999; so you should be fine there. If you’re comfortable, could you share your log file and an example workspace? It will help troubleshoot the issue better.

Thanks!

Curiosity conquers fear
wrijs
Contributor
Forum|alt.badge.img+3
  • wrijsContributor
  • Contributor
  • Best Answer
  • July 26, 2024

Hi @AliAtSafe , it turns out that if I create and run the fme workspaces directly from ArcGIS Datainterop. Workbench (instead of opening Datainterop from a toolbox in ArcGIS PRO) everything works fine! Being able to open the workspace seperatly from ArcGIS software is new to our version of ArcGIS.

I will view this as my workaround for now.

 

Thanks!

AliAtSafe
1 person upvoted this
  • AliAtSafe
    AliAtSafe
chrisp
Contributor
Forum|alt.badge.img+3
  • chrispContributor
  • Contributor
  • February 1, 2025

Hi guys,

I have solved this issue, pretty much the problem is created when you create your workbench within ArcPro (i.e. right-clicking a toolbox to create a spatial ETL or tool). What this does to the output workbench file is that is gives the tool XML tags of [ETL TOOL]….[/ETL TOOL] instead of [WORKSPACE]….[/WORKSPACE]. The WorkspaceRunner transformer prefers the latter tags and would fail if the former is used.

So quick solution:

  • Create your workbenches using DI but outside ArcPro
  • If workbench was created in ArcPro, simply open the FMW file in NotePad++ and update the tags [ETLTOOL]..[/ETLTOOL] to [WORKSPACE]...[/WORKSPACE].

 

Reply


Helpful Members This Week

Community Stats

31,139
Posts
118,062
Replies
38,770
Members

Latest FME

Terms & ConditionsCookie settings

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
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.