Closed VerdiSw closed 9 months ago
VerdiSw
commented
11 months ago Update: After placing the issue in Dynamobim I got a tip to install the package locally on all machines. So far I have installed it locally on these 3 machines and all the nodes except the DC node work.
erfajo
commented
11 months ago This is an interesting case for me, could I ask for the Orchid version? the current version is 2.6.7.6080
However, I have an idea that your problem is due to assemblies being blocked if they come from somewhere "untrusted"... try to see the error page -> https://github.com/erfajo/OrchidForDynamo/blob/master/Error.md ...read about unblocking assemblies.
VerdiSw
commented
11 months ago Orchid 2.6.7.6065. I have downloaded it on 24 november 2023.
Thank you for the response. I will check the error page and check if the local location is trusted.
erfajo
commented
11 months ago Thanks... I am especially interested in errors just now since I made a completely new way to code my package. I have refactored my entire environment lately (your version is included), so if there are any errors I have to figure out if this is due to the "new way" or something else.
However, one of the great new things is, that I only have one executable that installs all versions or the specific selected version(s).
And with the new way of doing it, I could also release Orchid for Revit 2019 and 2020, but I chose not to. However, I am considering that in the next version to maintain my package for Revit 2021. Meaning, I am considering having my package for Revit 2021, 2022, 2023, 2024, and 2025.
However, your latest image tells me something is wrong, but I think is is not saving the graph file. If you do that I think the nodes will work :-)
Lastly, I think that Windows will see all assemblies as “not trusted” if they are not installed locally, even when installed locally, if it is done by unzipping the zipped version, you might end up that assemblies are not trusted. Using the executable locally makes them trusted. I am not sure how I can do that in a network environment, I think that would demand administrator rights used when installing. But there is so much more at stake in a network environment that is is a kind of jungle… :-)
VerdiSw
commented
11 months ago You are right! I have saved the graph and closed and opened it and it works.
To bad that it doesnt work if the package is installed on the network and we just fill in the path it is installed to. But the executable makes up for it that its very easy to install eventhough we will now do it on all our revit-machines. 2minutes/machine on maybe 15machines, well worth the time!!
On windows 10 there is an easy way to trust a local folder but on windows 11 I have not found it yet. For now we'll pauze with putting packages on the server. We'll just let everyone install it at a training or send a A4 with some simple instructions.
Amazing work with the package btw! Helps a lot.
erfajo
commented
11 months ago I am not sure if I can solve this by running assemblies in a network environment. Nearly all kinds of software are installed locally on computers and run that way. Even thin clients are installed in an environment that sees the client machine as a local machine. But if you can test if the assembly files are protected in some way in your network I would like to know about it. Try to ask your network administrator if this is a kind of security level that exists in the network. I can understand why it should be rejected to run assemblies from outside the individual computer in the network, it could open up some serious holes in fencing a company towards attack.
Thanks for your kind words about the package :-)
velichkoleg
commented
10 months ago Hello. I have the same problem. The error still persists. Some nodes are not working. And some are not added to the screen at all, they have an icon like in the screenshot
Operating system
Windows 10 and Windows 11
Revit and Dynamo version
(Which version of Revit, Dynamo and Orchid are you using? Go to Help > About if you're not sure. for Orchid version, go to Packages > Manage Packages) Revit: 21.1.1.109 Dynamo: 2.6.1.8786 Orchid: 2.6
What did you do?
Installed Orchid on PC 1 (windows 11) and copied the C:\Users#name\AppData\Roaming\Dynamo\Dynamo Revit\2.6\packages folder\Orchid to a server. Added this server path to Dynamo on different machines (Windows 10 &11). Ran a script with the nodes:
What did you expect to see?
The different nodes working correctly
What did you see instead?
On PC1 (windows 11) where the packages are on the local pc and server the DC node gives a null without becoming yellow and the other nodes work perfectly. On PC2 (windows 11) where it only reads packages from the server the DC node also doesnt work. DLF & SPA gave the warning 0x00000007 contact author. When installing Orchid on the pc itself DLF & SPA worked correctly. DC did not. On PC3 (windows 10) where the package is on the server DC doesnt work and DLF and SPA give the contact author warning.