Does this package get exposed in your Dynamo library fi you manually place it? If so this message can be ignored - it’s informational in nature. If not, check your Dynamo log file to see if there is a stated reason the package won’t load.
Nope, it doesn’t get exposed (as in: it shows up under “Installed Packages”) if I manually place it.
(I downloaded it from https://www.dynamopackages.com/, made sure the zip-file was “unblocked” (I’ve read that when I was googleing similiar issues) and pasted it to “C:\Users\pumpaij\AppData\Roaming\Autodesk\C3D 2025\Dynamo\3.3\packages\” where the other installed packages reside into a folder that I called Data-Shapes.)
I can however install and uninstall version 2025.3.120 or other Dynamo-packages without problems.
There’s a lot going on in the log-file (see attached) which I can’t really decipher.
Maybe that’s related to my problem?
2026-03-03 14:58:47Z : Ausnahme beim Scannen des Paketverzeichnisses unter C:\Users\pumpaij\AppData\Roaming\Autodesk\C3D 2025\Dynamo\3.3\packages\Data-Shapes
2026-03-03 14:58:47Z : notification:Dynamo.Exceptions.LibraryLoadFailedException: Laden der Bibliothek fehlgeschlagen: C:\Users\pumpaij\AppData\Roaming\Autodesk\C3D 2025\Dynamo\3.3\packages\Data-Shapes
at Dynamo.PackageManager.PackageLoader.ScanPackageDirectory(String directory, Boolean checkCertificates):
Laden der Bibliothek fehlgeschlagen: C:\Users\pumpaij\AppData\Roaming\Autodesk\C3D 2025\Dynamo\3.3\packages\Data-Shapes:
C:\Users\pumpaij\AppData\Roaming\Autodesk\C3D 2025\Dynamo\3.3\packages\Data-Shapes\pkg.json enthält ein Paket mit einem fehlerhaften Header. Es wird ignoriert.
2026-03-03 14:58:47Z : Dynamo.Exceptions.LibraryLoadFailedException:
2026-03-03 14:58:47Z : Laden der Bibliothek fehlgeschlagen: C:\Users\pumpaij\AppData\Roaming\Autodesk\C3D 2025\Dynamo\3.3\packages\Data-Shapes
2026-03-03 14:58:47Z : at Dynamo.PackageManager.PackageLoader.ScanPackageDirectory(String directory, Boolean checkCertificates)
dynamoLog.txt (15.3 KB)
Just tested and it loads for me which means the package itself isn’t the issue. It may be an environment variable (German text getting processed differently), add-in conflict, infosec policy, or something else entirely. Hard to say without some more troubleshooting and sadly there’s enough non-English text in the log to make troubleshooting difficult.
Can you confirm you don’t have any other package paths trying to load an invalid version via another pathway?
1 Like