Conflict in Archi-lab.net

Packages
1

I’m still getting a conflict error in 1.3 using archi-lan.net 2016.13.4
> System.IO.FileLoadException
Here’s the Notification message: (full details below)

Dynamo has detected a conflict with a dependency and may be unstable. If any issues are detected, please uninstall addins or packages and contact the provider.

I thought perhaps I might have had some other package that didn’t get along, so I emptied my Dynamo\Packages\1_3 folder except for archi_lab, uninstalled archi_lab and reinstalled.
That’s to only package I have installed, and I’m still getting the error.
In fact, I get two notifications. One refers to archi-lab_Grimshaw (below) and the other to archilabUI
Same message, different file name

Full Notification details:
While loading assembly Archi-lab_Grimshaw, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null, Dynamo detected that the dependency RevitNodes, Version=2.0.0.4981, Culture=neutral, PublicKeyToken=null was already loaded with an incompatiable version. It is likely that another Revit Addin has loaded this assembly, please try uninstalling other Addins, and starting Dynamo again. Dynamo may be unstable in this state.
It is likely one of the following assemblies loaded the incompatible version:
DynamoRevitDS, DynamoRevitDS, DynamoRevitDS, DynamoRevitDS, DynamoRevitDS, DynamoRevitDS, DynamoRevitDS, DynamoRevitDS, DynamoRevitDS, DynamoRevitDS, DynamoRevitDS, RevitServices, RevitServices, RevitServices, DynamoCoreWpf, DynamoCoreWpf, DynamoCoreWpf, DynamoCoreWpf, DynamoCoreWpf, DynamoCoreWpf, DynamoCoreWpf, DynamoCore, DynamoCore, DynamoCore, DynamoCore, DynamoCore, DynamoCore, DynamoCore, DynamoCore, DynamoCore, DynamoApplications, DynamoApplications, ProtoCore, ProtoAssociative, ProtoImperative, Microsoft.GeneratedCode, DynamoUnits, DynamoPackages, DynamoPackages, VMDataBridge, VMDataBridge, DSCoreNodes, DSCoreNodes, DSOffice, DSOffice, DSOffice, DSIronPython, DSIronPython, DynamoConversions, Tessellation, Analysis, Analysis, Analysis, Display, Display, Display, RevitNodes, RevitNodes, RevitNodes, RevitNodes, RevitNodes, RevitNodes, ProtoScript, ProtoScript, ProtoScript, CoreNodeModels, CoreNodeModels, CoreNodeModels, CoreNodeModels, CoreNodeModels, CoreNodeModels, CoreNodeModels, CoreNodeModelsWpf, CoreNodeModelsWpf, CoreNodeModelsWpf, CoreNodeModelsWpf, CoreNodeModelsWpf, CoreNodeModelsWpf, GeometryUI, GeometryUI, GeometryUI, GeometryUI, GeometryUIWpf, GeometryUIWpf, GeometryUIWpf, GeometryUIWpf, Migrations, PythonNodeModels, PythonNodeModels, PythonNodeModels, PythonNodeModels, PythonNodeModelsWpf, PythonNodeModelsWpf, PythonNodeModelsWpf, UnitsUI, UnitsUI, UnitsUI, UnitsUI, UnitsUI, UnitsUI, Watch3DNodeModels, Watch3DNodeModels, Watch3DNodeModels, Watch3DNodeModels, Watch3DNodeModelsWpf, Watch3DNodeModelsWpf, Watch3DNodeModelsWpf, Watch3DNodeModelsWpf, Watch3DNodeModelsWpf, DSRevitNodesUI, DSRevitNodesUI, DSRevitNodesUI, DSRevitNodesUI, DSRevitNodesUI, DSRevitNodesUI, DSRevitNodesUI, DSRevitNodesUI, DSRevitNodesUI, DSRevitNodesUI, DSRevitNodesUI, DSRevitNodesUI, Archi-lab_Grimshaw

1 Like
2

You seem to have a version of archi lab that was built using the 2.0 version of DynamoRevit, and you are running Dynamo 1.3… those are semantically different versions. 2.0 > 1.3. via the major version number.

3

That makes sense, but I uninstalled everything and reinstalled archi-lab 2016.13.4 from the download Package Manager.
So where could another old version be hiding?
I only have one path in my Settings

4

I’m thinking maybe @Konrad_K_Sobon may have uploaded a build built on top of 2.0…

5

I have absolutely no idea what happened, but it seems to be behaving now.
I uninstalled everything (for about the third time) and removed all my paths.
I searched my C: drive for any “archi-lab” files an deleted them
Then I reinstalled archi-lab (same version as I had several times before) and now I’m not getting the error.
:head_bandage:
I swear I’ve done this multiple times over the last week.

6

There’s a Dynamo 2.0?
I’m still struggling with all the changes in 1.3!
And my entire user base is on 1.2

7

Dynamo 2.0 is unreleased, but the code is open source, so @Konrad_K_Sobon maybe be building his package against it.

8

I have more faith in Konrad than that. I doubt it’s his mistake. Much more likely mine.
The change from 1.2 to 1.3 has really tied me in knots. Somehow I got crossed versions and it’s taking a LONG time to unwind everything. I just hope this doesn’t happen when I roll 1.3 out to the office.

9

Idk, @Michael_Kirschner2 might be correct. I do have 2.0 on my machine and I wouldn’t be surprised if I managed to build my package against it (unknowingly). :slight_smile: I am glad it’s working for you. If I get more reports that this behavior is happening, I will investigate this to provide a fix.

Cheers!

10

AARGHHH!!
It’s back!
I’m getting the System.IO.FileLoadException again this morning.
I haven’t changed anything!
That line about RevitNodes. Version 2.0.0 make me think there IS something from Dynamo 2.0 in there.

The error went away yesterday, but now I’ve got two Notifications again
While loading assembly Archi-lab_Grimshaw, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null, Dynamo detected that the dependency RevitNodes, Version=2.0.0.4981, Culture=neutral, PublicKeyToken=null was already loaded with an incompatiable version.

11

Hi @DaveP

Uninstall archi-lab 2016.13.4 version and install 2016.13.3 which should i believe would fix your issue.

image.png668×771 304 KB

3 Likes
12

Getting same error:

with archi-lab 2016.13.4 installed.

Installing 2016.13.3 fixed it.

13

I also bumped into this problem with 2016.13.4. However, when I tried 2016.13.3 and 2016.13.2, I didn’t have any luck. I don’t get the error message for the two latter ones, but something in the packages makes all my custom functions in code blocks useless. Is there any solution on the way? I am running Dynamo 1.3.1.1736 on Revit 2017.

14

I am having the same issue.

https://imgur.com/a7SbwVn

15

same here, and not only with @Konrad_K_Sobon package…

16

I am working on a small update to mine that will remove the errors. Yes, that’s not the first time that I saw that. Unfortunately that happens with my other package as well - Mandrill. It has to do with things that are out of my control.

1 Like
17

Hi @Jean-Marc_Couffin

I have solved this similar issue for @awilliams by removing all custom packages and installing first archi-lab package. Hope it helps for you also.

3 Likes
18

that is what I understood. thanks for taking the time to explain and reply.

19

Hi @Kulkul,
the thing is that I have 10 of those errors.
Archilabs makes it 3/4, the rest by other nodes. useful ones. and I would not know in which sequence to install custom nodes again so that it works.

I hoped the 2018.2 update would solve this issue… well…

thanks

20

Konrad released an update (2018.0.6) this week.
I installed it and no longer see those conflicts. :+1:

1 Like