Intermittent errors on single grid node

We have 2 identical grid nodes configured. Occasionally one of them will display this error (but not for everyone using it).

A restart of the node or the client usually resolves it. The project in question is a single NETSTANDARD library in a solution full of .NET 4.7.2 projects. It doesn't depend on any of the others (It's at the bottom of the dependency hierarchy, so most of the others depend on it)

NCrunch: The build results for this project are not consistent across all computers within the grid.

This project was successfully built on computers: (local), lsbuild1
This project failed to build on computers: lsbuild2

Associated tests will continue to run on computers that are able to build this project successfully.  Please ensure all computers within the grid are configured correctly with all required SDKs installed.

****************** BUILD OUTPUT FROM '(local)' ******************


****************** BUILD OUTPUT FROM 'lsbuild2' ******************

..\..\..\..\..\matthews\AppData\Local\Temp\.NETStandard,Version=v2.0.AssemblyAttributes.cs (4, 20): The type or namespace name 'System' could not be found in the global namespace (are you missing an assembly reference?)
obj\Debug\netstandard2.0\Ledgerscope.Utilities.AssemblyInfo.cs (14, 12): The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?)
obj\Debug\netstandard2.0\Ledgerscope.Utilities.AssemblyInfo.cs (15, 12): The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?)
obj\Debug\netstandard2.0\Ledgerscope.Utilities.AssemblyInfo.cs (16, 12): The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?)
obj\Debug\netstandard2.0\Ledgerscope.Utilities.AssemblyInfo.cs (17, 12): The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?)
obj\Debug\netstandard2.0\Ledgerscope.Utilities.AssemblyInfo.cs (18, 12): The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?)
obj\Debug\netstandard2.0\Ledgerscope.Utilities.AssemblyInfo.cs (19, 12): The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?)
obj\Debug\netstandard2.0\Ledgerscope.Utilities.AssemblyInfo.cs (20, 12): The type or namespace name 'System' could not be found (are you missing a using directive or an assembly reference?)
..\..\..\..\..\matthews\AppData\Local\Temp\.NETStandard,Version=v2.0.AssemblyAttributes.cs (4, 71): Predefined type 'System.String' is not defined or imported
..\..\..\..\..\matthews\AppData\Local\Temp\.NETStandard,Version=v2.0.AssemblyAttributes.cs (4, 100): The type or namespace name 'FrameworkDisplayName' could not be found (are you missing a using directive or an assembly reference?)
..\..\..\..\..\matthews\AppData\Local\Temp\.NETStandard,Version=v2.0.AssemblyAttributes.cs (4, 123): Predefined type 'System.String' is not defined or imported
obj\Debug\netstandard2.0\Ledgerscope.Utilities.AssemblyInfo.cs (14, 55): Predefined type 'System.String' is not defined or imported
obj\Debug\netstandard2.0\Ledgerscope.Utilities.AssemblyInfo.cs (15, 61): Predefined type 'System.String' is not defined or imported
obj\Debug\netstandard2.0\Ledgerscope.Utilities.AssemblyInfo.cs (16, 59): Predefined type 'System.String' is not defined or imported
obj\Debug\netstandard2.0\Ledgerscope.Utilities.AssemblyInfo.cs (17, 68): Predefined type 'System.String' is not defined or imported
obj\Debug\netstandard2.0\Ledgerscope.Utilities.AssemblyInfo.cs (18, 55): Predefined type 'System.String' is not defined or imported
obj\Debug\netstandard2.0\Ledgerscope.Utilities.AssemblyInfo.cs (19, 53): Predefined type 'System.String' is not defined or imported
obj\Debug\netstandard2.0\Ledgerscope.Utilities.AssemblyInfo.cs (20, 55): Predefined type 'System.String' is not defined or imported

Hi, thanks for sharing this issue.

Can you check whether you have precisely the same versions of .NET Core installed on this grid node as you do on your client machines? And whether there is any mismatch in versions being used between your client machines? This looks like there may be a package versioning or restoration issue appearing on the grid node. It's possible that it may be triggered by clients with different package requirements reconnecting to the grid node and fighting over their required versions.

Looks like we had someone missing the ".NET Core Cross Platform Development" pieces in VS

MatthewSteeples wrote:Looks like we had someone missing the ".NET Core Cross Platform Development" pieces in VS

I wish I could think of a better way of getting NCrunch to report that. Not a fun thing to track down.