locked
TDDS session will not be started RRS feed

  • Question

  • Hi

    Using BT 2013 R2 and have problem that TDDS seession not seems to be start.

    I have enabled trace like this

    <system.diagnostics>
         <switches>
          <add name="Microsoft.BizTalk.Bam.EventBus" value="1" />
        </switches>
        <trace autoflush="true" indentsize="4">
        <listeners>
           <add name="Text" type="System.Diagnostics.TextWriterTraceListener" initializeData="c:\temp\tdds.log"/>
        </listeners>
       </trace>
     </system.diagnostics>

    and trace itself look like this: (error are BOLDED)

    In this env there is only one  BT server running and only one host intance marked as "Allow Host tracking".

    Any ideas what could cause this?

    <BizTalk2009> 4/18/2018 11:34:41 AM 1 UnknownClass UnknownMethod Info Starting TDDS
    <BizTalk2009> 4/18/2018 11:34:41 AM 1 UnknownClass UnknownMethod Info Provider has been created
    <BizTalk2009> 4/18/2018 11:34:41 AM 1 UnknownClass UnknownMethod Info Management Provider has been created
    <BizTalk2009> 4/18/2018 11:34:41 AM 1 UnknownClass UnknownMethod Info Session Manager is initialized
    <BizTalk2009> 4/18/2018 11:34:41 AM 1 UnknownClass UnknownMethod Info Session Manager thread is started
    <BizTalk2009> 4/18/2018 11:34:41 AM 17 Microsoft.BizTalk.Bam.EventBus.TDDSSessionManager Microsoft.BizTalk.Bam.EventBus.ITTDSControllable.Start Info Stopping TDDSSessionManager, SeriviceID 4c2d51ab-c9e5-46aa-bfb1-9b27e3248c1b
    <BizTalk2009> 4/18/2018 11:34:41 AM 17 Microsoft.BizTalk.Bam.EventBus.TDDSSessionManager Start Info Loading CustomFormatDecoder:
     FormatID:00000000-0000-0000-0000-000000000000
     DecoderClass:Microsoft.BizTalk.Bam.EventBus.DotNetDeserializer
     DllName:Microsoft.BizTalk.Bam.EventBus.dll
    <BizTalk2009> 4/18/2018 11:34:41 AM 17 Microsoft.BizTalk.Bam.EventBus.TDDSSessionManager Start Info Loading CustomFormatDecoder:
     FormatID:35487fd8-1b14-462f-9a84-673b6c397656
     DecoderClass:Microsoft.BizTalk.Bam.EventBus.DotNetDeserializer
     DllName:Microsoft.BizTalk.Bam.EventBus.dll
    <BizTalk2009> 4/18/2018 11:34:41 AM 17 Microsoft.BizTalk.Bam.EventBus.TDDSSessionManager Start Info Loading CustomFormatDecoder:
     FormatID:d3bffaf9-8291-4b82-9052-707aecab84a3
     DecoderClass:Microsoft.BizTalk.Bam.EventBus.DotNetDeserializer
     DllName:Microsoft.BizTalk.Bam.EventBus.dll
    <BizTalk2009> 4/18/2018 11:34:41 AM 17 Microsoft.BizTalk.Bam.EventBus.TDDSSessionManager Start Info Loading CustomFormatDecoder:
     FormatID:d90b63ba-3eeb-4e8a-a20e-7be683319552
     DecoderClass:Microsoft.BizTalk.Tracking.Deserializer.MessagingDeserializer
     DllName:Microsoft.BizTalk.TrackingService.dll
    <BizTalk2009> 4/18/2018 11:34:41 AM 17 Microsoft.BizTalk.Bam.EventBus.TDDSSessionManager Start Info Loading CustomFormatDecoder:
     FormatID:58e2ab42-51eb-441d-9c93-8795982336b8
     DecoderClass:Microsoft.BizTalk.Bam.EventBus.DotNetDeserializer
     DllName:Microsoft.BizTalk.Bam.EventBus.dll
    <BizTalk2009> 4/18/2018 11:34:41 AM 17 Microsoft.BizTalk.Bam.EventBus.TDDSSessionManager Start Info Loading CustomFormatDecoder:
     FormatID:1a6c57f0-3826-4254-9a91-9813a4cf2fce
     DecoderClass:Microsoft.BizTalk.Bam.EventBus.DotNetDeserializer
     DllName:Microsoft.BizTalk.Bam.EventBus.dll
    <BizTalk2009> 4/18/2018 11:34:41 AM 17 Microsoft.BizTalk.Bam.EventBus.TDDSSessionManager Start Info Loading CustomFormatDecoder:
     FormatID:d1a805a2-b1b5-42bc-a29f-d128131ddcd0
     DecoderClass:Microsoft.BizTalk.Tracking.Deserializer.AgentDeserializer
     DllName:Microsoft.BizTalk.TrackingService.dll
    <BizTalk2009> 4/18/2018 11:34:41 AM 17 Microsoft.BizTalk.Bam.EventBus.TDDSSessionManager Start Info Loading CustomFormatDecoder:
     FormatID:f3179eda-0da5-4f5f-818e-d231c85a52a9
     DecoderClass:Microsoft.BizTalk.Tracking.Deserializer.BamMessagingDeserializer
     DllName:Microsoft.BizTalk.TrackingService.dll
    <BizTalk2009> 4/18/2018 11:34:41 AM 17 Microsoft.BizTalk.Bam.EventBus.TDDSSessionManager Start Info Loading CustomFormatDecoder:
     FormatID:1e83a7dc-435e-49df-ba83-f09ca50dfbe7
     DecoderClass:Microsoft.BizTalk.Tracking.Deserializer.HmDeserializer
     DllName:Microsoft.BizTalk.TrackingService.dll
    <BizTalk2009> 4/18/2018 11:34:41 AM 17 Microsoft.BizTalk.Bam.EventBus.TDDSSessionManager Start Info Service: 4c2d51ab-c9e5-46aa-bfb1-9b27e3248c1b ----> Started Sesison for Source: 8e314c19-821f-4e2f-a8f8-25c49b5e39d2
    <BizTalk2009> 4/18/2018 11:34:41 AM 17 Microsoft.BizTalk.Bam.EventBus.TDDSSessionManager Start Info Service: 4c2d51ab-c9e5-46aa-bfb1-9b27e3248c1b ----> Started Sesison for Source: b489b8df-8c41-41a0-87b3-6a08ec94ed36
    <BizTalk2009> 4/18/2018 11:34:41 AM 19 System.Threading.ExecutionContext RunInternal Info Sleeping for Session timeout period
    <BizTalk2009> 4/18/2018 11:34:41 AM 21 System.Threading.ExecutionContext RunInternal Info Sleeping for Session timeout period
    <BizTalk2009> 4/18/2018 11:34:41 AM 1 UnknownClass UnknownMethod Info Successfully started
    <BizTalk2009> 4/18/2018 11:34:41 AM 18 System.Threading.ExecutionContext RunInternal Enter
    <BizTalk2009> 4/18/2018 11:34:41 AM 20 System.Threading.ExecutionContext RunInternal Enter
    <BizTalk2009> 4/18/2018 11:34:41 AM 20 System.Threading.ExecutionContext RunInternal Info Opened the connection to the source database.
    <BizTalk2009> 4/18/2018 11:34:41 AM 18 System.Threading.ExecutionContext RunInternal Info Opened the connection to the source database.
    <BizTalk2009> 4/18/2018 11:34:41 AM 18 Microsoft.BizTalk.Bam.EventBus.TDDSStartup FullRun Enter
    <BizTalk2009> 4/18/2018 11:34:41 AM 20 Microsoft.BizTalk.Bam.EventBus.TDDSStartup FullRun Enter
    <BizTalk2009> 4/18/2018 11:34:41 AM 20 Microsoft.BizTalk.Bam.EventBus.TDDSStartup FullRun Info Opened connection to the destination database.
    <BizTalk2009> 4/18/2018 11:34:41 AM 18 Microsoft.BizTalk.Bam.EventBus.TDDSStartup FullRun Info Opened connection to the destination database.
    <BizTalk2009> 4/18/2018 11:34:41 AM 20 Microsoft.BizTalk.Bam.EventBus.TDDSStartup FullRun Info TDDS_Lock return value
    <BizTalk2009> 4/18/2018 11:34:41 AM 20 Microsoft.BizTalk.Bam.EventBus.TDDSStartup FullRun Exit
    <BizTalk2009> 4/18/2018 11:34:41 AM 20 System.Threading.ExecutionContext RunInternal Info GrabLock finished successfully.
    <BizTalk2009> 4/18/2018 11:34:41 AM 18 Microsoft.BizTalk.Bam.EventBus.TDDSStartup FullRun Info TDDS_Lock return value
    <BizTalk2009> 4/18/2018 11:34:41 AM 18 Microsoft.BizTalk.Bam.EventBus.TDDSStartup FullRun Exit
    <BizTalk2009> 4/18/2018 11:34:41 AM 18 System.Threading.ExecutionContext RunInternal Info GrabLock finished successfully.
    <BizTalk2009> 4/18/2018 11:34:41 AM 20 Microsoft.BizTalk.Bam.EventBus.TDDSStartup FullRun Error Exception Thrown
    <BizTalk2009> 4/18/2018 11:34:41 AM 20 System.Threading.ExecutionContext RunInternal Error GetNumThreads returned non-positive number. This TDDS session will not be started.
    <BizTalk2009> 4/18/2018 11:34:41 AM 18 Microsoft.BizTalk.Bam.EventBus.TDDSStartup FullRun Error Exception Thrown
    <BizTalk2009> 4/18/2018 11:34:41 AM 18 System.Threading.ExecutionContext RunInternal Error GetNumThreads returned non-positive number. This TDDS session will not be started.
    <BizTalk2009> 4/18/2018 11:34:41 AM 20 System.Threading.ExecutionContext RunInternal Error Exception Thrown
    <BizTalk2009> 4/18/2018 11:34:41 AM 18 System.Threading.ExecutionContext RunInternal Error Exception Thrown
    <BizTalk2009> 4/18/2018 11:34:41 AM 20 Microsoft.BizTalk.Bam.EventBus.TDDSSingleSessionController EventHandler Error Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock.Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock. SQLServer: XXXXXXX, Database: BizTalkDTADb.
    <BizTalk2009> 4/18/2018 11:34:41 AM 18 Microsoft.BizTalk.Bam.EventBus.TDDSSingleSessionController EventHandler Error Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock.Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock. SQLServer: XXXXXXX, Database: BizTalkDTADb.
    <BizTalk2009> 4/18/2018 11:34:46 AM 21 System.Threading.ExecutionContext RunInternal Info Sleeping for Session timeout period
    <BizTalk2009> 4/18/2018 11:34:46 AM 19 System.Threading.ExecutionContext RunInternal Info Sleeping for Session timeout period

    Wednesday, April 18, 2018 8:48 AM

All replies

  • Other than this trace, what problems are you having?

    Is Tracking working normally?

    Wednesday, April 18, 2018 11:46 AM
    Moderator
  • Tracking is not working at all and I think because of thse error in trace.

    Tracking messages stays is msgdb so not moved to tracking db. Job TrackedMessages_Copy_BizTalkMsgBoxDb is running without error.


    • Edited by koltti Wednesday, April 18, 2018 12:24 PM correction
    Wednesday, April 18, 2018 12:23 PM
  • Next step would be to run BizTalk Health Monitor.
    Wednesday, April 18, 2018 12:58 PM
    Moderator
  • No issues there
    Wednesday, April 18, 2018 1:12 PM
  • First attempt: take BTS offline and restart SQL Server(s) to clear uncommited transaction locks
    Could be an transaction abort without rollback which causes the problem

    Check this blog article as a last resort

    Errors during BizTalk TDDS Processing
    https://blogs.msdn.microsoft.com/biztalknotes/2013/05/21/errors-during-biztalk-tdds-processing/

    /Peter

    Wednesday, April 18, 2018 2:03 PM
  • Hi

    We have already tried to create all databases again but still same problem. So I think it is nothing to do with locks.

    That blog did not help either.

    This part of error

    <BizTalk2009> 4/18/2018 11:34:41 AM 20 System.Threading.ExecutionContext RunInternal Error GetNumThreads returned non-positive number. This TDDS session will not be started.

    clearly say that TDDS sessios is not started but really do not understand meaning of "GetNumThreads returned non-positive number." 

    Thanks.



    • Edited by koltti Wednesday, April 18, 2018 3:14 PM correction
    Wednesday, April 18, 2018 2:48 PM
  • Well, you can just 'recreate' the databases.  Do you mean unconfigure and reconfigure BizTalk?
    Wednesday, April 18, 2018 3:04 PM
    Moderator
  • I tried to say that we recreate databases again but that did not help.
    Wednesday, April 18, 2018 3:15 PM
  • Sure, but you can really do that.  Did you unconfigure and reconfigure BizTalk?

    That's the only way to 'recreate' the databases.

    Wednesday, April 18, 2018 3:54 PM
    Moderator
  • yes I did
    Wednesday, April 18, 2018 3:58 PM
  • Did....?  What exactly?  Unconfigure and reconfigure?
    Wednesday, April 18, 2018 5:38 PM
    Moderator
  • 1. Unconfigured using Biztalk Server configuration

    2. Removed all data bases manually

    3. Configure using Biztalk Server configuration

    Thursday, April 19, 2018 8:28 AM