Skip to main content
Solved

Can't connect to G3 Smallworld using the SBS Plugin for Smallworld in FME.

  • August 23, 2023
  • 2 replies
  • 126 views

laurentp
Contributor
Forum|alt.badge.img+8

I am working as a consultant for Consortech Solutions and I have a client who is trying to make his G3 Smallworld connection work in FME using the SBS Plugin for Smallworld. Unfortunately, the reader in FME doesn't work all the time. When it fails to show the table to choose from for reading data using the SBS plugin for Smallworld reader, the error message returned is "Bad or Invalid License for feature: spatialbiz_read [-12]". What's weird is that sometimes he is able to read his data in FME using that same reader but sometimes it fails to read the data.

 

Is that something people have experienced in the past and if so, is there a way to solve this issue?

Best answer by laurentp

Hello, we found the solution to the problem:

 

We added the HostID to the license file on the client side.

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.

2 replies

j.botterill
Influencer
Forum|alt.badge.img+53
  • Influencer
  • 386 replies
  • August 24, 2023

Hi laurentp, according to SPATIALBIZ installation documentation FlexErrors

  • Check that the version of FlexLM is compatible with your FME version.
  • Does your license server also act as an FME license server?

Launch LMtools on the license server

SBS license serverCheck the servicename = SBS license server has the correct paths. Save if changes and restart service

Then perform a status enquiry on SBS (and FME licenses)....

PerformStatusEnquiryDoes the enquiry specify more about the error.


laurentp
Contributor
Forum|alt.badge.img+8
  • Author
  • Contributor
  • 3 replies
  • Best Answer
  • August 30, 2023

Hello, we found the solution to the problem:

 

We added the HostID to the license file on the client side.