Skip to main content

I have a workspace that I am running locally on my computer. This workspace is connected to an sde database on Amazon EC2 instance. This workpace is very simple translation just a reader and a writer, the purpose of the workspace is to completely delete all features from the sde database. However when I publish this workspace to FME Server the translations fail due to this error.

 

2020-10-18 05:39:39 | An error occurred while attempting to open the table,,...]. The error number from ArcObjects is: '-2147216057'. The error message from ArcObjects is: {Invalid parameter value passed to function}

2020-10-18 05:39:39 | It could have failed to open because it contains ArcGIS Pro-only features, for example Arcade expressions. If this is the case, please install ArcGIS Pro or Pro-compatible ArcGIS Server and 64-bit FME

 

Has anyone had an error like this before? I just don't know why desktop workspace works fine but once it is published to FME Server the workspace no longer functions, is weird.

Do you have the ArcGIS libraries installed on your FME Server?


Also, what type of ArcGIS product is installed on your FME Server? ArcGIS for Enterprise, Desktop, Pro, other?


The problem had to do with the FeatureTypes being read, the workspace I am using reads all features at once, so I simply cleared the list of feature types being read and the problem went away.


Is there a different workaround than "clear the list of features"? My workflow requires all schemas to be read and processed. Thanks!


Is there a different workaround than "clear the list of features"? My workflow requires all schemas to be read and processed. Thanks!

Try creating a private parameter and set type to existing file set the value as your sde connection file. Then link that parameter to the sde reader. When you publish the workspace make sure the .sde connection file is copied to the server.


Hi there! Sorry for writing here, but, for some reasons, I have no rights for creation of topics

I have a project within workbench, which uses some feature readers transformers to get features from database with several constraints which are based on previous steps. Everything works perfectly in Workbench, but when I'm trying to use server instead some problems are identified. The project stops during the execution of FeatureReader with error:

FeatureReader (QueryFactory): The clause 'IGNORE_NULLS <Unused>' within 'FACTORY_DEF {*} QueryFactory FACTORY_NAME FeatureReader INPUT FEATURE_TYPE Creator_CREATED FCTQUERY_INTERACTION NONE COMBINE_ATTRIBUTES { RESULT_ONLY } IGNORE_NULLS { <Unused> } QUERYFCT_ATTRIBUTE_PREFIX { <Unused> } COMBINE_GEOMETRY { RESULT_ONLY } ENABLE_CACHE { NO } QUERYFCT_TABLE_SEPARATOR { SPACE } READER_TYPE { POSTGRES } READER_DATASET { ***} QUERYFCT_IDS { public.bh_spr_gidro } READER_DIRECTIVES { META_MACROS,SourceQUERY_FEATURE_TYPES_FOR_MERGE_FILTERS<comma>Yes<comma>SourceREAD_TIME_WITH_TIMEZONE<comma>Yes<comma>SourceNAMED_CONNECTION<comma>Alexander<comma>SourceSCHEMAS_FOR_TABLE_LISTING<comma><comma>SourceWHERE_CLAUSE<comma><comma>SourceEXPOSE_ATTRS_GROUP<comma><comma>SourcePOSTGRES_EXPOSE_FORMAT_ATTRS<comma><comma>SourceADVANCED<comma><comma>SourceFEATURES_PER_FETCH<comma>10000<comma>SourceBEGIN_SQL<comma><comma>SourceEND_SQL<comma><comma>SourceCREATE_FEATURE_TABLES_FROM_DATA<comma>Yes,METAFILE,POSTGRES } QUERYFCT_OUTPUT { BASED_ON_CONNECTIONS } CONTINUE_ON_READER_ERROR YES QUERYFCT_RESULT_TAGS { public.bh_spr_gidro } QUERYFCT_SET_FME_FEATURE_TYPE YES READER_PARAMS_WWJD { CREATE_FEATURE_TABLES_FROM_DATA,Yes,QUERY_FEATURE_TYPES_FOR_MERGE_FILTERS,Yes,NAMED_CONNECTION,Alexander,FEATURES_PER_FETCH,10000,READ_TIME_WITH_TIMEZONE,Yes } TREAT_READER_PARAM_AMPERSANDS_AS_LITERALS YES OUTPUT public.bh_spr_gidro FEATURE_TYPE FeatureReader_public.bh_spr_gidro' is not recognized by the factory 'QueryFactory'

If I'm using the PostgreSQL reader instead of it everything works perfectly, but I can't use it because of necessity of previous steps execution.

 


Hi there! Sorry for writing here, but, for some reasons, I have no rights for creation of topics

I have a project within workbench, which uses some feature readers transformers to get features from database with several constraints which are based on previous steps. Everything works perfectly in Workbench, but when I'm trying to use server instead some problems are identified. The project stops during the execution of FeatureReader with error:

FeatureReader (QueryFactory): The clause 'IGNORE_NULLS <Unused>' within 'FACTORY_DEF {*} QueryFactory FACTORY_NAME FeatureReader INPUT FEATURE_TYPE Creator_CREATED FCTQUERY_INTERACTION NONE COMBINE_ATTRIBUTES { RESULT_ONLY } IGNORE_NULLS { <Unused> } QUERYFCT_ATTRIBUTE_PREFIX { <Unused> } COMBINE_GEOMETRY { RESULT_ONLY } ENABLE_CACHE { NO } QUERYFCT_TABLE_SEPARATOR { SPACE } READER_TYPE { POSTGRES } READER_DATASET { ***} QUERYFCT_IDS { public.bh_spr_gidro } READER_DIRECTIVES { META_MACROS,SourceQUERY_FEATURE_TYPES_FOR_MERGE_FILTERS<comma>Yes<comma>SourceREAD_TIME_WITH_TIMEZONE<comma>Yes<comma>SourceNAMED_CONNECTION<comma>Alexander<comma>SourceSCHEMAS_FOR_TABLE_LISTING<comma><comma>SourceWHERE_CLAUSE<comma><comma>SourceEXPOSE_ATTRS_GROUP<comma><comma>SourcePOSTGRES_EXPOSE_FORMAT_ATTRS<comma><comma>SourceADVANCED<comma><comma>SourceFEATURES_PER_FETCH<comma>10000<comma>SourceBEGIN_SQL<comma><comma>SourceEND_SQL<comma><comma>SourceCREATE_FEATURE_TABLES_FROM_DATA<comma>Yes,METAFILE,POSTGRES } QUERYFCT_OUTPUT { BASED_ON_CONNECTIONS } CONTINUE_ON_READER_ERROR YES QUERYFCT_RESULT_TAGS { public.bh_spr_gidro } QUERYFCT_SET_FME_FEATURE_TYPE YES READER_PARAMS_WWJD { CREATE_FEATURE_TABLES_FROM_DATA,Yes,QUERY_FEATURE_TYPES_FOR_MERGE_FILTERS,Yes,NAMED_CONNECTION,Alexander,FEATURES_PER_FETCH,10000,READ_TIME_WITH_TIMEZONE,Yes } TREAT_READER_PARAM_AMPERSANDS_AS_LITERALS YES OUTPUT public.bh_spr_gidro FEATURE_TYPE FeatureReader_public.bh_spr_gidro' is not recognized by the factory 'QueryFactory'

If I'm using the PostgreSQL reader instead of it everything works perfectly, but I can't use it because of necessity of previous steps execution.

 

I am not familiar with the postgres reader, but if the postgres feature reader is working and the Feature Reader is not I am thinking that maybe your connection is bad. It is hard to tell without being able to see a workspace.


Reply