none
There is no MTS object context

    Question

  • We have 6 Biztalk 2006 environments that have been running and configurable for years on Window 2003 Enterprise Edition Service Pack 2.  Sometime in the past 6 months or so, I have lost the ability to configure (ex. enable/disable recieve location) in 3 of our environments.  All 3 problem enviroment have the following symptons.

    I have sucessfully run DTC Tester.

    How to I fix this problem?

     

    When running BizTalk Srver 2006 Administration Console and When I select the following:

      Platform Settings -> Adapters -> FILE (or any of the specific adapters)

    I get the following error:
    TITLE: BizTalk Server 2006 Administration Console
    ------------------------------

    Unable to load adapter handlers for FILE adapter. (Microsoft.BizTalk.Administration.SnapIn)

    ------------------------------
    ADDITIONAL INFORMATION:

    There is no MTS object context
     (WinMgmt)

    ------------------------------
    BUTTONS:

    OK
    ------------------------------
     


    the Application Event log contains the following 3 warnings (event id = 10536, Source = ENTSSO, Category = Enterprise Single Sign-On):

    SSO AUDIT
     Function: GetConfigInfo ({5EA5DE22-AE7E-4EA3-992F-BFABCA4288BD})
     Tracking ID: 8b216e10-fb41-4e78-8368-ece5e5300527
     Client Computer: GAMPLS401M.Na.Corp.Cargill.com (wmiprvse.exe:2660)
     Client User: NA\sdumonce
     Application Name: {5EA5DE22-AE7E-4EA3-992F-BFABCA4288BD}
     Error Code: 0x8004E004, There is no MTS object context


    SSO AUDIT
     Function: GetConfigInfo ({5EA5DE22-AE7E-4EA3-992F-BFABCA4288BD})
     Tracking ID: 8b216e10-fb41-4e78-8368-ece5e5300527
     Client Computer: GAMPLS401M.Na.Corp.Cargill.com (wmiprvse.exe:2660)
     Client User: NA\sdumonce
     Application Name: {5EA5DE22-AE7E-4EA3-992F-BFABCA4288BD}
     Error Code: 0x8004E004, There is no MTS object context


    SSO AUDIT
     Function: GetConfigInfo ({5EA5DE22-AE7E-4EA3-992F-BFABCA4288BD})
     Tracking ID: 8b216e10-fb41-4e78-8368-ece5e5300527
     Client Computer: GAMPLS401M.Na.Corp.Cargill.com (wmiprvse.exe:2660)
     Client User: NA\sdumonce
     Application Name: {5EA5DE22-AE7E-4EA3-992F-BFABCA4288BD}
     Error Code: 0x8004E004, There is no MTS object context

     

    Tuesday, April 07, 2009 5:24 PM

Answers

  • Weird errors like this happen sometimes when Windows Updates get applied and COM+ permissions get reset or the update changes something about Enterprise Services that interacts with BizTalk. Do you know if the servers recently got updated to .NET 1.1 SP1 or .NET 2.0 SP1, etc. when they already had .NET 3.0? I think I saw this kind of thing happen when a .NET update like the SP1 for 1.1 or 2.0 was run after .NET 3.0.

    I would try doing a repair on the BizTalk installs to see if this resolves it. Go to Add/Remove programs, click on BizTalk, click Modify and then click Repair.
    If this does not work, you should call Microsoft Support because it sounds like something outside of BizTalk itself that has broken that is affecting BizTalk.

    Thanks,
    If this answers your question, please use the "Answer" button to say so | Ben Cline
    Tuesday, April 07, 2009 6:28 PM
    Moderator
  • This error can also happen if the ENTSSO Server COM+ application is a missing. Running a Repair or reinstall of BizTalk may recreate it. The ENTSSO Server COM+ application uses the SSOCSTX.dll in \Program Files\Common Files\Enterprise Single Sign-On folder.
    Wednesday, April 08, 2009 7:37 PM

All replies

  • Weird errors like this happen sometimes when Windows Updates get applied and COM+ permissions get reset or the update changes something about Enterprise Services that interacts with BizTalk. Do you know if the servers recently got updated to .NET 1.1 SP1 or .NET 2.0 SP1, etc. when they already had .NET 3.0? I think I saw this kind of thing happen when a .NET update like the SP1 for 1.1 or 2.0 was run after .NET 3.0.

    I would try doing a repair on the BizTalk installs to see if this resolves it. Go to Add/Remove programs, click on BizTalk, click Modify and then click Repair.
    If this does not work, you should call Microsoft Support because it sounds like something outside of BizTalk itself that has broken that is affecting BizTalk.

    Thanks,
    If this answers your question, please use the "Answer" button to say so | Ben Cline
    Tuesday, April 07, 2009 6:28 PM
    Moderator
  • This error can also happen if the ENTSSO Server COM+ application is a missing. Running a Repair or reinstall of BizTalk may recreate it. The ENTSSO Server COM+ application uses the SSOCSTX.dll in \Program Files\Common Files\Enterprise Single Sign-On folder.
    Wednesday, April 08, 2009 7:37 PM