- 4 minutes to read

Release Notes

Troubleshooting the BizTalk Server Monitoring Agent

If you have any issues that you can not solve, contact our Support, read more on the Support page. We're here to help you maximize the value of Nodinite and keep your BizTalk Server environment running smoothly.

Frequently Asked Questions

Cannot start/stop ports using the Scheduled Task Adapter

If you have trouble starting or stopping ports with the Scheduled Task Adapter, ensure you:

Cannot start the agent

If the Nodinite BizTalk Server Monitoring agent fails to start, it may be due to unmet security or runtime dependencies. Common causes include:

  • Insufficient rights to run as a Windows Service. See: How to set Logon as a Service right
  • Shared port error. Solution: Shared Port 8000
  • Missing prerequisites. Review the Prerequisites page.
  • Database update required. After some updates, the Monitoring Database may need to be upgraded for compatibility.
    Update Monitoring Database
    Example: Updating the Monitoring Database to resolve agent startup issues.
  • Visual Studio diagnostic extensions causing ConfigurationErrorsException errors. This rare edge case occurs when Visual Studio was installed and later removed, leaving incompatible entries in machine.config. See: Visual Studio Diagnostic Extension Conflict

If the Nodinite BizTalk Server Monitoring agent fails with MissingMethodException and references Newtonsoft.Json, the machine may have a non-compatible newtonsoft.json.dll in the Global Assembly Cache (GAC).

Important risk warning
Changing assemblies in the GAC is a high-risk operation. Customer environments may include custom BizTalk pipelines, custom components, or other deployed solutions that depend on a specific Newtonsoft.Json binary. Removing or replacing the wrong assembly can break unrelated runtime behavior.

Newtonsoft.Json GAC warning
Nodinite BizTalk components require Newtonsoft.Json 13.0.4 or later. Do not install an older Newtonsoft.Json 13.x build in the GAC. Different Newtonsoft.Json 13.x binaries can share AssemblyVersion 13.0.0.0, which may cause .NET Framework to load an older GAC binary even when a newer NuGet package is deployed.

Common symptoms include:

  • Agent startup failure with MissingMethodException in logs.
  • Runtime behavior where expected Newtonsoft.Json APIs appear to exist, but calls still fail.

Recommended actions:

  • Contact Support before changing GAC content, and perform an impact assessment for custom BizTalk artifacts.
  • Create a backup of the currently installed newtonsoft.json.dll so you can restore the previous state if required.
  • Remove incompatible Newtonsoft.Json assemblies from the GAC on nodes running the agent only after backup and support guidance.
  • Ensure all BizTalk nodes use the same supported Newtonsoft.Json version.
  • Reinstall or repair the BizTalk Monitoring agent package to restore the expected runtime dependencies.
  • Restart the service and verify normal startup.

Missing Resources

  • The agent may be configured with Filters that remove all resources from BizTalk Applications. Review and adjust your filters as needed to restore visibility.

There are no Actions available

Where do I install the agent?

You can install your Nodinite environment on-premises, in Azure Virtual Machines, or in the cloud with your sourcing partner. Hybrid scenarios are fully supported, giving you flexibility and control.

How do I uninstall the BizTalk Server Monitoring Agent?

  • Stop the Agent before running the MSI package. See the uninstallation user guide for step-by-step instructions.
  • You must be a local administrator to remove Windows Services.

How do I get the latest version?

Download the latest release from the Nodinite portal.

How do I know when there's a new version available?

Subscribe to updates through our Support portal to stay informed about new releases and features.

How do I know where the agent is installed and running?

Check the Nodinite Overview and the Monitor Agent Run-time Information section for details on agent deployment and status.