Bentley Map and Safe FME

We have both Bentley Map and Safe FME installed on our PCs and the work fine.  But when I open Bentley Map it tries to grab a FME license even though we are not using that functionality.  We have more Bentley Map installations than we do FME licenses, so it prevents other people from working with FME.

My question is this, how do I disable this behavior?

Can we set Bentley Map to only get a FME license when we are using that functionality?

We don't normally use the FME functionalty within Bentley Map.

Any ideas??

Regards, Ian

Parents
  • Ian,

    In the current Bentley Map release, I don't believe there is a good way to prevent FME license consumption if the Bentley Map FME Extension has been installed. For users that have no need for the FME Extension, perform a custom Bentley Map installation and disable the FME Extension install option. For other users that have the need to run the FME Extension on occassion some configuration changes might help. **

    For example, as a temporary solution, in msgeo.cfg you could conditionally wrap the inclusion of the FME Extension configuration...

    ...with something similar to the following...

    ...then add -wsUSE_FME_EXTENSION command line argument to any shortcut used to start a Bentley Map session needing FME Extension capabilities.

    ** Now in full disclosure I've not tested this particular configuration change and realize that at the top of msgeo.cfg we include a warning to never modify the contents of the file. I only offer this a one potential temporary solution knowing your background and long history of working with Bentley products. Please let me know if this helps.

    If there is sufficient user demand, I would gladly file a Bentley Map change request to have the license allocation behavior modified in a future release to better suite organizations such as yours where there are many Bentley Map seats and few pooled FME licenses.

    Regards,

    Jeff Bielefeld [Bentley]



  • Hi Jeff,

    I tried renaming the "FmeExtension.cfg" file to "NoFmeExtension.cfg", but this didn't make any difference to the FME license usage.

    I will keep trying a few things, but so far the only thing that has worked is not having both products on the same machine.  Currently I have avoided a custom installation.

    Thanks,

    Ian

Reply Children