locked
Host instances are not getting started ? RRS feed

  • General discussion

  • Hi All,

    1. I am using BizTalk server2013.
    2. I had a VM in which BizTalk applications are running vary well.
    3. Now I have created a clone of that VM.
    4. The moment I am starting any of the application at my Clone VM , it is giving error and host instances are not getting started. 
    5. Apart from that I did necessary changes required  at server and in BiztAlk & SSO database tables also.
    6. I have also checked in configuration file (BTSNTSvc.exe.config) and everything is fine .

    ERROR DESCRIPTION:

    0x80131604 Error source: mscorlib Error description: Exception has been thrown by the target of an invocation.

    WARINING:
    The target principal name is incorrect.  Cannot generate SSPI context.
    Error source: .Net SqlClient Data Provider
     
    BizTalk host name: BizTalkServerApplication
    Windows service name: BTSSvc$BizTalkServerApplication

    Thanks,
    John


    • Edited by John(Daniel) Thursday, July 28, 2016 10:23 AM more information added
    Thursday, July 28, 2016 10:18 AM

All replies

  • Hi John

    In a cloned BizTalk VM, you have to uninstall MSDTC, delete the MSDTC regkeys, and re-install MSDTC. Have you done that? Refer-

    https://danrosanova.wordpress.com/2012/06/20/installing-biztalk-on-cloned-virtual-machines/

    Also you mentioned changes in step 5. What are those specifically?


    Thanks Arindam


    Thursday, July 28, 2016 10:23 AM
    Moderator
  • Hi Arindam ,

    Thanks for the reply !

    I have done below changes in the database table by replacing the VM name with the Clone VM name

    1. [BAMPrimaryImport]
      Bam_metadata_properties
      Bam_metadata_configuration
      TDDS_StreamStatus

      2. [BizTalkDTADb]
          dta_MessageBox
          TDDS_StreamStatus

     3. [BizTalkMgmtDb]
         Adm_messagebox
         Adm_group,
         Adm_otherbackupdatabases,
         Adm_otherdatabases,
         Adm_receiveLocation

         TDDS_sources,
         Btsmon_inconsistancies,
         adm_Server,
        adm_HostInstance

     4.   [SSODB]
          SSOX_GlobalInfoSSOX_AuditAppDelete
          SSOX_AuditMappingDelete
          SSOX_AuditNtpLookup
          SSOX_AuditTable
          SSOX_AuditXpLookup

    Also,

    1. SSO –updated server name at regeidt HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ENTSSO\SQL
    2. And ssomanage.exe –updateDB with respective values

    Thanks,

    Thursday, July 28, 2016 11:21 AM