none
Biztalk 2016 Configuration errors RRS feed

  • Question

  • Hi,

    We are trying to configure BizTalk 2016 on one of our first servers and the configuration fails with following error.

    Current BizTalk databases, and jobs in SQL 2016 are renamed before trying the BizTalk configuration.

    OS: 2016, BizTalk software: 2016 CU7, SQL server: 2016 (on a different machine).

    Appreciate any suggestions. Thanks

    1) this is the error with custom configuration with the groups or accounts from corporate directory.

    2) here is the error message bout SSO with the basic configuration selected.

    sql server xxxxxxxx cannot be used with the SSO administrator account 'SSO Administrators'. Local accounts cannot be used with clustered SQL servers.

    • Edited by AmanDev1 Monday, May 18, 2020 4:36 PM Included error images for basic and custom config
    Monday, May 18, 2020 4:13 PM

Answers

  • Worked with Microsoft to troubleshoot the issue.

    In our scenario we were trying to do  a new setup for SSO and other BizTalk databases in the SQL server. Current databases in the server were renamed (without renaming the underlying database and log files). Hence BizTalk configuration threw the errors.

    After completely renaming these objects configuration was successful. Thought of sharing this for those who may run into this scenario.

    • Marked as answer by AmanDev1 Wednesday, June 24, 2020 3:27 PM
    Wednesday, June 24, 2020 3:26 PM

All replies

  • Maybe add your domain name before the SSO Administrators account when configuring.
    Monday, May 18, 2020 7:53 PM
  • Groups were added including the domain name.

    Never experienced similar issue with my previous setup activities with v2010, and 2013 R2.

    Not sure what's so different about BizTalk v2016.

    Thanks

    Monday, May 18, 2020 8:07 PM
  • Worked with Microsoft to troubleshoot the issue.

    In our scenario we were trying to do  a new setup for SSO and other BizTalk databases in the SQL server. Current databases in the server were renamed (without renaming the underlying database and log files). Hence BizTalk configuration threw the errors.

    After completely renaming these objects configuration was successful. Thought of sharing this for those who may run into this scenario.

    • Marked as answer by AmanDev1 Wednesday, June 24, 2020 3:27 PM
    Wednesday, June 24, 2020 3:26 PM