Error tekla live link 2025 - rhino 8

Grasshopper Tekla
1

Hello, I’m having trouble getting the Tekla LiveLink 2025 to work with Rhino 8. I’m getting the following error message. I’ve reinstalled the software, but I’m still getting this message. @sebastian.lindholm Can you help me please?

image
image790×450 34.5 KB

2

Hi vaher,

That sounds like the link doesn’t connect to the Tekla API.

If you insert e.g. a [Create] Beam component, does it turn red? In that case, what does the balloon tip say?

image
image472×226 10.9 KB

Here are some pointers to check first:

Cheers,

Sebastian

3

Hello Sebastien, yes the balloon ltip is indeed red and the text is identical to your screenshot. I’ve already tried all the suggested solutions.

image
image1404×190 21.7 KB

4

I’m leaning towards some other plugin that has copied Tekla DLLs to somewhere where Grasshopper can see them. Could be the Libraries folder but also in places like C:\Users\[username]\AppData\Roaming\McNeel\Rhinoceros\8.0\Plug-ins\

Can you check if the API works from a C# component? Use this definition:

TestTeklaAPIConnection.gh (10.8 KB)

If Tekla isn’t running (=no API connection) I get this:

image
image944×522 45.5 KB

If the connection is good, you should just get Connected = true and it creates a beam in the model.

-b

5

Fix Check List

  1. In Rhino 8: run SetDotNetRuntime → choose NETFramework → restart Rhino. You only need to do this once per installation
  2. Reinstall the Grasshopper–Tekla Link package that explicitly targets Tekla 2025 (from Tekla Warehouse), with Rhino & GH closed during install. After install, you should see a “Tekla [2025]” tab in Grasshopper.
  3. Open Tekla Structures 2025 and a model first. Then start Rhino, then Grasshopper.
  4. If you rely on Hops component, be aware its background Rhino processes may still use .NET Core, causing the persistent error dialog even when the foreground link works.
  5. Temporarily move all third‑party GH libraries out of %AppData%\Grasshopper\Libraries except the GH–Tekla Link.
6

I tried but it didn’t work

7

I’ve already done these steps several times.

8

I’ve been using Tekla Live Link since Tekla 2022; before that, the path for the .dll files was this one.

image
image865×583 39.9 KB

But in version 2025 of Tekla, the folders are no longer the same.

image
image669×393 18.5 KB

image
image967×299 16.2 KB

9

Hi

Do You have installed ggTekla plugin? I had a same problem and when I uninstalled ggTekla everything was working.

10

Hi

Yes, it is installed.

11

And just to confirm, removing it didn’t help?’

The core API dll:s are all directly under the bin\ folder and these are what will get used. Some plugins might ship with their own copies of some dlls but that’s probably redundant.

12

Hi

I uninstalled GG Tekla and reinstalled Live Link, and it works. Strange, because I always had GG Tekla on older versions and never had this problem. Thanks everyone for your help, and happy holidays!

13

Good to hear!

Things changed in version 2024 when Tekla became “gacless”, meaning Tekla dlls are resolved in a different way. If the GG plugin gets loaded first, any Tekla dlls that ship with that will get used by Grasshopper. And if these dlls don’t match the exact Tekla service pack you have, you’ll easily run into trouble.

I think we can try to detect from where the dlls have been loaded and show a more accurate error message in the next version.

Happy holidays! :fireworks: