Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • Video Library
    • Books We Like
    • >> Go to DataMiner Docs
  • Expert Center
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Markets & Industries
      • Media production
      • Government & defense
      • Content distribution
      • Service providers
      • Partners
      • OSS/BSS
    • Agile
      • Agile Webspace
      • Everything Agile
        • The Agile Manifesto
        • Best Practices
        • Retro Recipes
      • Methodologies
        • The Scrum Framework
        • Kanban
        • Extreme Programming
      • Roles
        • The Product Owner
        • The Agile Coach
        • The Quality & UX Coach (QX)
    • DataMiner DevOps Professional Program
      • About the DevOps Program
      • DataMiner DevOps Support
  • Downloads
  • More
    • DataMiner Releases & Updates
    • Feature Suggestions
    • Climb the leaderboard!
    • Swag Shop
    • Contact
    • Global Feedback Survey
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Deal Registration
  • >> Go to dataminer.services

DIS Validation Error difficult to interpret

Solved1.03K views21st November 2023Connector DIS
5
Robin Becker [DevOps Advocate]1.40K 16th November 2023 0 Comments

I’m having a difficult time understanding what this DIS Validation error means, it shows up as “Critical” and when trying to publish the DIS Output shows a stack trace (below).

I’ve gone trough all my QAction files and neither them or protocol.xml shows any errors.

Restarting VS2022 does not help.

DIS Output:

2023/11/16 04:40:06.854|Could not compile protocol:
System.MissingMethodException: Method not found: ‘Void NuGet.Packaging.Core.PackageIdentity..ctor(System.String, NuGet.Versioning.NuGetVersion)’.
at SLDisCompiler.Protocol.ProtocolBuilder.<BuildQActionDllImports>d__21.MoveNext()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1.Start[TStateMachine](TStateMachine& stateMachine)
at SLDisCompiler.Protocol.ProtocolBuilder.BuildQActionDllImports(QActionsQAction qa, Project project, IQActions allQActions, PackageReferenceProcessor packageReferenceProcessor, BuildResultItems buildResultItems, ICompliancies compliancies)
at SLDisCompiler.Protocol.ProtocolBuilder.<BuildQAction>d__19.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at SLDisCompiler.Protocol.ProtocolBuilder.<BuildQActions>d__18.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SLDisCompiler.Protocol.ProtocolBuilder.<BuildResultsAsync>d__16.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at SLDisCompiler.Protocol.ProtocolBuilder.<BuildAsync>d__15.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Skyline.VSX.ProtocolEditor.Documents.ProtocolDocument.<CompileProtocolAsync>d__27.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Threading.JoinableTask.CompleteOnCurrentThread()
at Microsoft.VisualStudio.Threading.JoinableTask`1.CompleteOnCurrentThread()
at Skyline.VSX.ProtocolEditor.Margin.PublishDropDownButton.<>c__DisplayClass19_0.<PublishProtocol>b__0(DoWorkEventArgs a)
2023/11/16 04:40:06.872|Protocol published!

Critical DIS Validation error:

Critical: Unexpected exception in Test ‘CSharpSLProtocolCheckTrigger’: System.ArgumentException: Syntax node is not within syntax tree
at Microsoft.CodeAnalysis.CSharp.CSharpSemanticModel.CheckSyntaxNode(CSharpSyntaxNode syntax)
at Microsoft.CodeAnalysis.CSharp.CSharpSemanticModel.GetTypeInfo(ExpressionSyntax expression, CancellationToken cancellationToken)
at Microsoft.CodeAnalysis.CSharp.CSharpExtensions.GetTypeInfo(SemanticModel semanticModel, ExpressionSyntax expression, CancellationToken cancellationToken)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynHelper.GetFullyQualifiedName(SemanticModel semanticModel, ExpressionSyntax expression)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynHelper.TryParseValue(ExpressionSyntax expression, SemanticModel semanticModel, Solution solution, Value& value)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynHelper.TryGetVariableValue(ExpressionSyntax expression, SemanticModel semanticModel, Solution solution, Value& value)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynHelper.TryParseValue(ExpressionSyntax expression, SemanticModel semanticModel, Solution solution, Value& value)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynHelper.TryParseValue(ExpressionSyntax expression, SemanticModel semanticModel, Solution solution, Value& value)
at SLDisCSharpAnalysis.CSharpAnalyzer.Classes.Argument.TryParseToValue(SemanticModel semanticModel, Solution solution, Value& value)
at SLDisValidator2.Tests.Protocol.QActions.QAction.CSharpSLProtocolCheckTrigger.QActionAnalyzer.CheckCallingMethod(CallingMethodClass callingMethod)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynVisitor.VisitInvocationExpression(InvocationExpressionSyntax node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.Visit(SyntaxNode node)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynVisitor.Visit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.DefaultVisit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.Visit(SyntaxNode node)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynVisitor.Visit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.DefaultVisit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.Visit(SyntaxNode node)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynVisitor.Visit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.DefaultVisit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.Visit(SyntaxNode node)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynVisitor.Visit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.DefaultVisit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.Visit(SyntaxNode node)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynVisitor.Visit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.DefaultVisit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.Visit(SyntaxNode node)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynVisitor.Visit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.DefaultVisit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.Visit(SyntaxNode node)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynVisitor.Visit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.DefaultVisit(SyntaxNode node)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynVisitor.VisitMethodDeclaration(MethodDeclarationSyntax node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.Visit(SyntaxNode node)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynVisitor.Visit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.DefaultVisit(SyntaxNode node)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynVisitor.VisitClassDeclaration(ClassDeclarationSyntax node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.Visit(SyntaxNode node)
at SLDisCSharpAnalysis.CSharpAnalyzer.RoslynVisitor.Visit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.DefaultVisit(SyntaxNode node)
at Microsoft.CodeAnalysis.CSharp.CSharpSyntaxWalker.Visit(SyntaxNode node)
at SLDisValidator2.Tests.Protocol.QActions.QAction.CSharpSLProtocolCheckTrigger.CSharpSLProtocolCheckTrigger.Validate(ValidatorContext context)
at SLDisValidator2.Validator.RunValidateTest(IValidate test, ValidatorContext context, List`1 results) (line 0 col 0) [0.0.0]

Robin Becker [DevOps Advocate] Selected answer as best 21st November 2023

2 Answers

  • Active
  • Voted
  • Newest
  • Oldest
1
Michiel Oda [SLC] [DevOps Enabler]3.60K Posted 21st November 2023 0 Comments

With the latest Visual Studio 2022 update (17.8.0), DIS 2.44 has become incompatible. Our current advice is to update to the latest insider release (2.45) for now: DataMiner Integration Studio – Downloads – DataMiner Dojo

We’re in the process of releasing 2.46, so 2.45 will become the main release as well.

Robin Becker [DevOps Advocate] Selected answer as best 21st November 2023
3
Tom Waterbley [SLC] [DevOps Catalyst]8.89K Posted 16th November 2023 2 Comments

Hi Robin, this is actually an internal error that happens within DIS which is not necessarily caused by something in your connector or QActions.

Would it please be possible to check if you have the latest version of Visual Studio 2022 installed? Currently that’s version 17.8.0. In many cases updating Visual Studio solves this kind of issues.

If the issue remains I would propose to send an email to dis@skyline.be so that the team can follow this up further.

Robin Becker [DevOps Advocate] Unselected an answer 21st November 2023
Robin Becker [DevOps Advocate] commented 20th November 2023

I’m running the latest version of Visual Studio 2022 and just recently update DIS to the insider preview to fix an unrelated issue. Upgrading DIS however did not fix this issue so I’ll send an email to support.

Amer Hodzic [DevOps Member] commented 20th November 2023

Hi Tom,

I am experiencing the same issue which occured after a visual studio update.

everything is on the latest version but still the same error

Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs