Skip to main content
  • EN

I upgraded a workspace in version

FME(R) 2019.2.1.0 (20191202 - Build 19813 - WIN64)

 

Reason was to solve a sudden problem concerning fan out on a autocad writer.

When scheduled and called trough a windows scheduled batch file it fails to complete the fan out.

 

If i run it direct, the fan out works.

 

So i decided to upgrade transformers,.

 

 

 

Now i get this error related tot the feature ordering across or over all ports.

 

This error is given for all the testers in my workspace!

 

Wh..wh..why?

 

THis does not happen if i run the workspace directly (not trough a windows batfile)

 

Here is the error:

 

 

               FME 2019.1.1.0 (20190801 - Build 19617 - WIN64)

                    FME Desktop Oracle Edition (floating)

                              Permanent License.

                      Machine host name is: LDNPVWAPP074

Operating System: Microsoft Windows Server 2012 R2 Server 4.0 64-bit (Build 960

0)

                Copyright (c) 1994 - 2019, Safe Software Inc.

                              Safe Software Inc.

 

 

The clause 'FEATURE_TABLE_SHIM_SUPPORT Yes PRESERVE_FEATURE_ORDER ACROSS_OUTPUT_

PORTS' within 'FACTORY_DEF * TestFactory FACTORY_NAME Tester_2 INPUT FEATURE_TYP

E StatisticsCalculator_COMPLETE TEST @EvaluateExpression(FDIV,STRING_ENCODED,<at

>Value<openparen>_count<closeparen>,Tester_2) = 1 ENCODED BOOLEAN_OPERATOR OR CO

MPOSITE_TEST_EXPR 1 FEATURE_TABLE_SHIM_SUPPORT Yes PRESERVE_FEATURE_ORDER ACROSS

_OUTPUT_PORTS OUTPUT PASSED FEATURE_TYPE Tester_2_PASSED OUTPUT FAILED FEATURE_T

YPE Tester_2_FAILED' is incorrect. The clause must look like: FEATURE_TABLE_SHI

M_SUPPORT E(yes|no)]

Program Terminating

 

Translation FAILED.

Press any key to continue . . .

 

Anyone seen this?

 

Hi @gio​,

Just posting here after my response to your support case as well. The change in the Tester was introduced in FME 2019.2. Based on the info you have here you updated the workspace in FME 2019.2.1.0, but from your log excerpt, your .bat file initiated FME 2019.1.1.0. If you have multiple version of FME installed, consider listing your latest version first in your Path system environment variable as mentioned in this thread as well. Hope this works!

Hi @gio​,

Just posting here after my response to your support case as well. The change in the Tester was introduced in FME 2019.2. Based on the info you have here you updated the workspace in FME 2019.2.1.0, but from your log excerpt, your .bat file initiated FME 2019.1.1.0. If you have multiple version of FME installed, consider listing your latest version first in your Path system environment variable as mentioned in this thread as well. Hope this works!

Hi.

I got around to addressing the issue. I was forced to as it popped up increasingly.

It was indeed the problem.

The path variable form the FME server is, which is FME 2019.1.1.0, was set before the pathvariable from workbench which is FME 2019.2.1.0. (on that particular server).


We reversed that and the problem was solved.

Thanks for your help.


Greets and stay safe Safe,

Gio

Reply


Community Stats

30,017
Posts
113,998
Replies
37,636
Members
Terms & ConditionsCookie settings