Skip to main content
Solved

TCL startup script fails on server (runs on desktop)

  • October 17, 2017
  • 4 replies
  • 114 views
dfresh
Forum|alt.badge.img

probably a permission issue, but not sure what it is failing. I continuously get this error.

2017-10-18 10:22:55 A SAFE license service was detected running on port ##### on server ABC (##.##.##.##) and offering FME licenses. Please ensure that fmelicensingassistant is configured to use it (enter either 'ABC' or 'ABC:#####' for the Server Name), and that it has sufficient licenses for you.

the startup script is

lappend sysString $FME_MacroValues(FME_HOME_UNIX)/fme;
lappend sysString {Generate};
lappend sysString {GEODATABASE_FILE};
lappend sysString {NULL};
lappend sysString $FME_MacroValues(SRC_GDB);
lappend sysString $env(TEMP)/temp.fme;
lappend sysString {--RESOLVE_DOMAINS};
lappend sysString {YES};
lappend sysString {2>@1};
eval exec $sysString;

Any thoughts? I am actively working on this, so will hopefully have it resolved.

Best answer by daveatsafe

Hi @dfresh,

That TCL code starts a command line FME to generate a mapping file, from which the domain information is read. This works fine on Desktop, but in the Server environment, the FME Engines are constantly running, and have used up all the available licenses. So the command line FME will always fail with a licensing error.

This was written quite a few years ago, and newer versions of FME have another way to get the domain information. The FeatureReader transformer can be set to output only a Schema feature, and the schema for Geodatabases include the domain definitions, if the reader setting Resolve Domains is enabled.

I would recommend using the FeatureReader instead the TCL code.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

dfresh
Forum|alt.badge.img
  • dfresh
  • Author
  • 19 replies
  • October 17, 2017

I solved it, I needed ArcGIS installed on the server to read the GEODATABASE_FILE...

UPDATE - this did not solve it, it only allowed me to login to the server and run a local .FMW.

dfresh
Forum|alt.badge.img
  • dfresh
  • Author
  • 19 replies
  • October 18, 2017
The server is licensed, the fme local desktop version is licensed and able to run, not sure why its causing this issue @DaveAtSafe

 

daveatsafe
Safer
Forum|alt.badge.img+19
  • daveatsafeSafer
  • Safer
  • 1637 replies
  • Best Answer
  • October 18, 2017

Hi @dfresh,

That TCL code starts a command line FME to generate a mapping file, from which the domain information is read. This works fine on Desktop, but in the Server environment, the FME Engines are constantly running, and have used up all the available licenses. So the command line FME will always fail with a licensing error.

This was written quite a few years ago, and newer versions of FME have another way to get the domain information. The FeatureReader transformer can be set to output only a Schema feature, and the schema for Geodatabases include the domain definitions, if the reader setting Resolve Domains is enabled.

I would recommend using the FeatureReader instead the TCL code.

dfresh
Forum|alt.badge.img
  • dfresh
  • Author
  • 19 replies
  • October 19, 2017

Hi @dfresh,

That TCL code starts a command line FME to generate a mapping file, from which the domain information is read. This works fine on Desktop, but in the Server environment, the FME Engines are constantly running, and have used up all the available licenses. So the command line FME will always fail with a licensing error.

This was written quite a few years ago, and newer versions of FME have another way to get the domain information. The FeatureReader transformer can be set to output only a Schema feature, and the schema for Geodatabases include the domain definitions, if the reader setting Resolve Domains is enabled.

I would recommend using the FeatureReader instead the TCL code.

Thanks @DaveAtSafe you are the best, I owe you a beer.

Community Stats

32,093
Posts
121,872
Replies
39,731
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.