none
BAM Tools Configuration Fails on SQL Tasks RRS feed

  • Question

  • Hello all,

    We have been working on this issue for over 2 weeks without resolution.  We have tried many solutions including security changes, MSDTC changes and pre-creating the BAMPRIMARYIMPORT.MDF without success.  The same error(s) keep occurring.  We also tried using alternate database names to the defaults... same error(s).

    We started the thread in the SQL Forum:

    https://partnersupport.microsoft.com/en-us/par_servplat/forum/par_sqlserv/biztalk-2016-single-server-installation-bam-tools/669d8e89-df29-4155-b8e3-72da44cf0696

    The issue seems to be something related to BizTalk attempting to create the tables.  We can see BizTalk is able to connect to SQL and SQL functions properly with the account IDs we are using.

    HIGHLIGHTS FROM THE INSTALL LOG:

    2018-06-12 17:05:33:6768 [Info] BAMTools Source:
    2018-06-12 17:05:33:6768 [Info] BAMTools .Net SqlClient Data Provider
    2018-06-12 17:05:33:6768 [Info] BAMTools Error messages:
    2018-06-12 17:05:33:6768 [Info] BAMTools 
    2018-06-12 17:05:33:6768 [Info] BAMTools Cannot open database "BAMPrimaryImportx" requested by the login. The login failed.
    2018-06-12 17:05:33:6768 [Info] BAMTools Login failed for user '<domain>\<useracct>'.
    2018-06-12 17:05:33:6768 [Info] BAMTools 
    2018-06-12 17:05:33:6768 [Info] BAMTools Call stack:
    2018-06-12 17:05:33:6768 [Info] BAMTools    at System.Data.SqlClient.SqlInternalConnectionTds..ctor

    Also earlier in the log:

    2018-06-12 11:25:54:8235 [Info] CfgExtHelper Checking the connection to the BizTalk Management Database: BizTalkMgmtDb on server NETSVR
    2018-06-12 11:25:54:8415 [Info] CfgExtHelper Connecting to the BAM Primary Import Table Database
    2018-06-12 11:25:54:8425 [Info] CfgExtHelper The BAM Primary Import Database found from the BizTalk Management Database BizTalkMgmtDb on server NETSVR is not compatible.
    2018-06-12 11:25:54:8435 [Info] CfgExtHelper Connecting to the BAM Primary Import Table Database BAMPrimaryImport on server NETSVR
    2018-06-12 11:26:04:8933 [Info] CfgExtHelper The BAM Primary Import Database found from the BizTalk Management Database BAMPrimaryImport on server NETSVR is not compatible.

    Help is appreciated.  Thanks!

    -Steve


    Regards, Steve W.

    Thursday, June 21, 2018 1:53 PM

Answers

  • Hi Everyone,

    Infotect has been helping us with this issue but I wanted to let you all know we found the solution to the issue. We added NT Service\MSSQLSERVER to the DB folders. We were then able to install BAM Tools, BAM Portal, and EDI/AS2 Runtime successfully. Also, I was able to complete the installation with SQL Server Standard.

    Thanks.




    • Edited by MobileTec Friday, June 29, 2018 9:30 PM
    • Marked as answer by Infotect Wednesday, July 15, 2020 8:57 PM
    Friday, June 29, 2018 9:27 PM

All replies

  • Please OS version and BTS + MSSQL Version, and CU levels on both

    /Peter

    Thursday, June 21, 2018 3:37 PM
  • Could be a failed installation pulling your around by the nose

    http://geekswithblogs.net/edmundzhao/archive/2007/02/13/106204.aspx

    Check if you have any records in BizTalkDBVersion (BAM Primary Import Database)

    /Peter

    Thursday, June 21, 2018 3:44 PM
  • What is the stack you are using? As Peter suggested let us know the complete stack.

    Have you tried unconfigure and clean reconfigure of the BAM features?

    Another Pointer : Please do not manually create any database artefats related to BizTalk, the configuration tool only should take care of that


    Mandar Dharmadhikari


    Friday, June 22, 2018 3:27 AM
    Moderator
  • Hi Everyone,

    Infotect has been helping us with this issue but I wanted to let you all know we found the solution to the issue. We added NT Service\MSSQLSERVER to the DB folders. We were then able to install BAM Tools, BAM Portal, and EDI/AS2 Runtime successfully. Also, I was able to complete the installation with SQL Server Standard.

    Thanks.




    • Edited by MobileTec Friday, June 29, 2018 9:30 PM
    • Marked as answer by Infotect Wednesday, July 15, 2020 8:57 PM
    Friday, June 29, 2018 9:27 PM
  • Just to clarify, NT Service\MSSQLSERVER was given Full Control to the DB folders.
    Friday, June 29, 2018 9:52 PM