Technical Assistance: Graph does not contain matching nodemodel (2.0.2)

I have a serious problem with my dynamo 2.0.2.

Any script I save from 2.0.2 with the node “List.create” breaks on opening it in dynamo or dynamoplayer.
The node dissapears with the following warning.

“This graph has a nodeview with id:28a4f52c-1366-4eac-b39e-83b6ac43357c and name:List Create, but does not contain a matching nodeModel”

When I create my script in 1.3.4 however, I can open it and run it in 2.0.2 just fine.
( see attached scripts )

I’ve tried the following:
Uninstall 2.0.2 and reinstall 2.0.2
Uninstall 1.3.4 and reinstall 1.3.4

I suspect that my dynamo core is damaged, but I have no idea how to proceed.

testscript134 was created in 1.3.4
testscript134.dyn (1.5 KB)
testscript202 was created in 2.0.2
testscript202.dyn (3.8 KB)

I tried opening and running the script but I don’t have any problems in Dynamo 2.0.2.

Mabye a reinstall of Dynamo?

Thanks for the response.

But no, reinstalling Dynamo doesn’t solve the problem.

How did you uninstall Dynamo

I would recommend to deinstall use a other tool like the Revo uninstaller. With this way you remove all the files from Dynamo. If you use your standard uninstall program it will not properly remove dynamo from your PC.

If this doesn’t work I don’t have the solution maybe someone else.:sweat_smile:

After some digging I think I’ve found the cause of the problem.
Earlier today I installed the pyRevit plugin, which comes bundled with Microsoft .NET runtime 2.0.7
image
after uninstalling both Dynamo seemed to work properly again.

yeah, latest pyrevit doesn’t work for me too :frowning:
but previous version works, I think 4.6.8 if I remember correctly so give it a try

I doubt this has to do with the net core -
can you look for any green notifications in dynamo’s menu bar when pyRevit is installed?

something stopped the nodeModel from deserializing correctly from the graph.

Any chance you have nodes which share the List. namespace (there are many).

Hi All,

I am also having this issue, it seems to be unsolved here also?
i have tried;

-uninstalling all Dynamo versions including cores, deleting all packages and user specific information

I do not have Pyrevit installed, nor do i have this version of Net.Framework.

I am pretty stumped, looked all over for answers but nothing :frowning:

Hi @Fasher are you using Revit or Civil3d, can you provide as much info as possible so we can help you track down whats causing the conflict?

Revit.

However, all the above information in the thread is still relevant.
the only additional information is that i do not have pyrevit installed.

Try removing all Revit add-ins as they can cause similar issues. Also confirm you can launch Dynamo Sandbox.

1 Like

All removed, but i think im just going to compeltetly re-install revit and see how we go from there.

So ahh, re-installing Revit 2018 & 2019 did not work…
but i can confirm that i cannot launch dynamo sandbox.

I have looked online and can find what seems to be a sandbox version for 2020 but not older versions?

Sandbox should install with every Dynamo install since like 1.2. Just gotta find the .exe. If you can’t manage to find it let me know and I’ll try to find the typical path tomorrow.

Ah ha! at least some progress.
i found the dynamo sandbox.exe (C:\Program Files\Dynamo\Dynamo Core\2)

And when i opened it i opened an existing workflow with success!! (well except for missing packages but that’s not a problem)

But opening it with Revit still proves illusive for me :frowning: picture below for reference.

SANDBOX VERSION

REVIT VERSION

ADDITIONAL INFORMATION
Unsuccessful methods tried so far;

-Re Install of Revit 2018 & 2019
-Removal of all Revit Addins
-Removal of all Dynamo Packages
-Uninstall / re-install graphics drivers (Nvidia)
-Check windows updated fully
-Uninstall and re-install Dynamo (Both Core & Revit versions)

Log from Dynamo Revit.
Dynamo log started 2019-08-01 20:43:37Z

Requesting version update info…
Dynamo – Build 2.0.3.8810
Duplicate migration type registered for SunPathDirection
Dynamo will use the package manager server at : https://www.dynamopackages.com
DynamoPackageManager (id: FCABC211-D56B-4109-AF18-F434DFE48139) extension is added
Backup files timer is started with an interval of 60000 milliseconds
SYSTEM:Environment Path:C:\Program Files\Autodesk\Revit 2019\AddIns\SteelConnections;C:\Program Files\Autodesk\Revit 2019\en-US;C:\Program Files\Autodesk\Revit 2019;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Windows\System32\OpenSSH;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Microsoft SQL Server\120\Tools\Binn;C:\Program Files\Common Files\Autodesk Shared;C:\Program Files (x86)\Google\Google Apps Sync;C:\Program Files (x86)\Google\Google Apps Migration;C:\Program Files\dotnet;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\Program Files (x86)\Intel\Intel® Management Engine Components\DAL;C:\Program Files\Intel\Intel® Management Engine Components\DAL;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0;%SYSTEMROOT%\System32\OpenSSH;C:\Users\m.fasher\AppData\Local\Microsoft\WindowsApps;;C:\Program Files\Dynamo\Dynamo Core\2
RENDER : Rendering Tier: 2
RENDER : Pixel Shader 3 Supported: True
RENDER : Pixel Shader 4 Supported: False
RENDER : Software Effect Rendering Supported: True
RENDER : Maximum hardware texture size: 16384,16384
RENDER : Rendering Tier: 2
RENDER : Pixel Shader 3 Supported: True
RENDER : Pixel Shader 4 Supported: False
RENDER : Software Effect Rendering Supported: True
RENDER : Maximum hardware texture size: 16384,16384
DynamoManipulationExtension (id: 58B0496A-E3F8-43D9-86D2-94823D1D0F98) view extension is added
LibraryUI (id: 85941358-5525-4FF4-8D61-6CA831F122AB) view extension is added
NotificationsExtension (id: ef6cd025-514f-44cd-b6b1-69d9f5cce004) view extension is added
PackageManagerViewExtension (id: 100f5ec3-fde7-4205-80a7-c968b3a5a27b) view extension is added
Welcome to Dynamo!
00:00:00.5492159 elapsed for loading Dynamo main window.
WPF Render Mode: SoftwareOnly
Dynamo is up to date.
ERR_ABORTED
connector 25ccfea6-a3d4-4adf-80ce-6de5cf8b7949 could not be created, start or end port does not exist
connector b1f170fa-970c-4975-9ec0-3cd19b8103b7 could not be created, start or end port does not exist
connector 8203b7cd-7fed-43a8-b193-51e9baf2328b could not be created, start or end port does not exist
connector 320756ed-202f-45c8-8652-bd6fde0ee086 could not be created, start or end port does not exist
connector 75113bb9-cd5f-4117-b3b9-c7b98c48c6cc could not be created, start or end port does not exist
connector 1fde8c3d-0729-4af4-bbb7-bcebecb8da5b could not be created, start or end port does not exist
connector 78ad02f8-c728-4b5c-8d6f-3f411780056d could not be created, start or end port does not exist
connector 75cff632-4058-48d9-98b9-6f7c7546a380 could not be created, start or end port does not exist
connector 1e62c007-49fe-431c-b613-6d7971f4689c could not be created, start or end port does not exist
connector 8c884614-6200-4863-9706-efc905a9e505 could not be created, start or end port does not exist
connector 7457f68e-6f8c-4906-bc45-223b1478cfab could not be created, start or end port does not exist
connector e219d320-4627-4c2d-aced-fd0f98b881b2 could not be created, start or end port does not exist
connector d5da31f6-f54b-4f8b-afad-fb548647a16c could not be created, start or end port does not exist
connector 7a2854c2-65ad-4e9a-aaf2-97c72ca74147 could not be created, start or end port does not exist
Active view is now eCubed Landing Page
This graph has a nodeview with id:7341edec-a915-40c3-87e8-d32d6f29fd30 and name:Boolean, but does not contain a matching nodeModel
This graph has a nodeview with id:e9d26958-9747-48f6-ba97-98151c05b8f4 and name:Categories, but does not contain a matching nodeModel
This graph has a nodeview with id:1b6ad1cb-361f-4fc8-bd8e-7ff1d0e91e7d and name:All Elements of Category, but does not contain a matching nodeModel
This graph has a nodeview with id:db0a8f73-798d-40b2-b737-a71cb5aa01b0 and name:Watch, but does not contain a matching nodeModel
This graph has a nodeview with id:aa1385d4-0b2b-4497-b2b1-2577af7779f5 and name:Watch, but does not contain a matching nodeModel
This graph has a nodeview with id:f290c1d3-00d4-4f5c-8658-e08e051f8be2 and name:Watch, but does not contain a matching nodeModel
This graph has a nodeview with id:76ec8539-b18e-4507-93c2-7972e3d822f8 and name:String, but does not contain a matching nodeModel
This graph has a nodeview with id:58f10aad-dd5b-45c8-b9cc-3ea3ad6943d7 and name:Watch, but does not contain a matching nodeModel
This graph has a nodeview with id:5f748cbe-bb89-40a4-9ebf-f7dceb0bc5ea and name:Watch, but does not contain a matching nodeModel
This graph has a nodeview with id:8592925a-e0e0-45b1-9bce-ef457980326e and name:Watch, but does not contain a matching nodeModel

I have only seen this resolved by:

  1. A complete uninstall of all things dynamo
  2. Double check the registry to confirm there is nothing left, deleting any keys you find hanging on.
  3. Restart your CPU.
  4. Re-install Dynamo as per the instructions here: Working with Dynamo in Revit 2016 and Revit 2019 Simultaneously - Dynamo BIM, or just install only Dynamo 2.0.2 (which works with all currently supported Revit versions except 2020).

If you have Revit 2020 you may need to repair that installation as well.

Hi Fasher,

  1. does this happen every time you open the file?
  2. do you open the file immediately upon opening Revit?
  3. Did you install the advanced steel connections or or other Revit extensions? Can you also try removing these?
  4. when you uninstall Dynamo - look carefully in the folders and make sure everything is actually removed - make sure Revit is closed when you uninstall and reinstall.
  5. do you see any green notifications in the Dynamo menu bar?
  6. What exact versions of Revit with anything else installed?

something is likely throwing an exception when Dynamo tries to resolve the types for its builtin types - it is likely to be something in the revit process -