- 5 minutes to read

FAQ and Troubleshooting BizTalk Server Logging to Nodinite

Resolve BizTalk Server logging issues with confidence using Nodinite. On this page, you will:

  • ✅ Get expert troubleshooting tips for common BizTalk logging problems
  • ✅ Learn how to resolve SQL Server, deadlock, and tracking issues
  • ✅ Discover best practices for robust, reliable integration monitoring
  • ✅ Find answers to frequently asked questions and next steps for support

If you cannot resolve an issue, contact our Support or email us at support@nodinite.com.

Login failed for user "NT AUTHORITY\ANONYMOUS LOGON"

Review the Trusted for delegation user guide to ensure the Kerberos security protocol works correctly.

"Could not allocate space for object"

A tempdb configuration issue in SQL Server can cause this error. Review the BizTalk Server Logging Recommendations user guide.
When this problem occurs, SQL cannot sort the data to return, so BizTalk logging fails until you resolve the issue.

When you first enable Logging from BizTalk, Nodinite may need to catch up and copy everything from the BizTalk tracking database (BizTalkDTADb). This initial load can exhaust resources and fill the tempdb's primary filegroup (usually on the SQL Server instance with BizTalkDTADb).

Failed to copy/insert Events from BizTalk to Nodinite","exception":"System.Data.SqlClient.SqlException (0x80131904): Could not allocate space for object 'dbo.SORT temporary run storage:  140865700167680' in database 'tempdb' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.\r\n   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)\r\n   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock,

About Deadlocks

  • BizTalk Server acquires locks as part of normal operation. Nodinite allows its thread to become the deadlock victim, which helps SQL Server resolve the deadlock quickly.
    • Nodinite retries the operation shortly, so you do not lose data.
    • Deadlocks indicate a system under high stress.
      • Check if you have exhausted available free memory.
      • Check if CPU load stays above 90%.
  • Review and implement our BizTalk Logging Recommendations to optimize both Nodinite and BizTalk Server environments.

Custom Pipelines

If you miss data in the tracking database (DTA), review this page.

Uninstall

To uninstall, read the information on this page.

Questions to answer and actions to perform

Does the BizTalk Server environment perform well, or do you see performance-related problems?

When did you last split? For example, how old is the current Log Database?

Does the Nodinite Logging Service have problems creating new Nodinite Log Databases? Inspect the Audit Log and Nodinite Logging Service diagnostic files to troubleshoot.

What is the size of the current Log Database?

What is the size of the BizTalk Tracking database?

  • If the database is larger than 20-30 GB, review how many days you keep data in BizTalk.

For how long do you keep events in the BizTalk Tracking database?

  • Nodinite replaces the long-term Logging functionality of BizTalk Tracking. Only keep data in BizTalk for a few days. We recommend 4-7 days to survive system issues over long weekends.
    Use the latest Nodinite version for ongoing performance improvements.
  • Install and Update Tool
  • Update Nodinite

Copying Body and Context has been interrupted

If you notice no processing of logged events from BizTalk, contact our support.
This problem typically occurs if your BizTalk Server environment experiences one or more of the following (not a complete list):

  • You run out of disk space
    • You restored incorrectly
    • You have a referential integrity mismatch between BizTalk MgsBoxDB and BizTalkDTADB
  • You experience extremely high load
    • BizTalk can write thousands of tracked events with the same timestamp (not normal)
  • You enable excessive tracking due to pipeline tracking. Review the Recommended tracking settings for BizTalk Server default pipelines user guide.
  • The system reports a timeout as a system error in the Nodinite Audit Log if you search for DTA as part of the function:
    DTA
    If any of these functions time out, you may have a problem with BizTalk logging.

If you need an instant resolution, follow these steps.

  1. Stop the Nodinite Logging Service
  2. Execute the script below:
    1. Open SSMS
    2. Open a new query with the Nodinite Configuration Database
    3. Copy, modify, and execute as appropriate

Note1: Replace the value for @logAgentValueId as appropriate for your configuration. Verify the actual value using the Configure Microsoft BizTalk Server Logging Agent section.
Note2: Double the initial default value 5000 until the output returns a successful transfer of bodies or context.

DECLARE @temp DTADataTableType, @logAgentValueId INT = 1;
INSERT INTO @temp EXEC [Log_DTAGetTrackedData] 5000, @logAgentValueId , null, 0, 1;
EXEC [Log_DTAInsertTrackedData] @temp, @logAgentValueId, @printText=1
  1. Attach the output to your support request so we can document and investigate the situation to find the root cause.
  2. Restart the Nodinite Logging Service

What is the largest size for logged Context in BizTalk?

To find the largest context, run the following command in SSMS using the BizTalk tracking database (BizTalkDTADB):

SELECT MAX(datalength(imgpart)) FROM Tracking_Parts1 WITH (NOLOCK)

You can then find the message Id, either in BizTalkDTADB or from the Admin Log View within Nodinite.