--- title: "Configuring the BizTalk environment getting ''Compatibility error''" slug: "configuring-biztalk-getting-compatibility-error-1" updated: 2026-11-05T06:45:38Z published: 2026-11-05T06:45:38Z canonical: "docs.biztalk360.com/configuring-biztalk-getting-compatibility-error-1" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.biztalk360.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring the BizTalk environment getting ''Compatibility error'' While you are trying to add a new environment in BizTalk360, and if you come across the message: ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-1722510705602.png) The reason it occurs is that the installed BizTalk server components version is mismatched with the configured BizTalk360. **Please check for the following:** For instance, you need to monitor an environment from a non -BizTalk machine, where you would have installed BizTalk components alone. In this situation, you might have faced the following scenarios: **Scenario 1:** You would have changed the installed version of BizTalk Server. Before, it might have been BizTalk 2016, and now it can be changed to BizTalk 2020 on the already configured BizTalk360 machine. **Suggestion**: Please remember you should install the same BizTalk components (as you installed on the BizTalk Server) on the stand-alone machine where BizTalk360 is installed. So, even after installing the latest components, if you face the same compatibility problem again, you have to cross-verify the BizTalk version available in the BizTalk360 Database for a couple of tables as follows and update the version in both tables: 1.b360_admin_BizTalkEnvironment - Column name " BizTalkVersion" 2.b360_admin_GlobalProperties - Column name " MS_BIZTALK_VERSION - Setting Value" **Scenario 2**: You would have already installed the proper BizTalk components and the BizTalk360 database would also have the correct BizTalk version. But even though you face the "compatibility error" as mentioned above, eg., you have installed BizTalk 2016 and its components and are trying to add a new environment (BizTalk 2020) for monitoring. **Suggestion**: You cannot monitor different versions of the BizTalk server in one instance of BizTalk360. With BizTalk360, you can manage multiple BizTalk environments from a single installation as long as all the environments are running on the same version of BizTalk Server. If you want to manage different versions of BizTalk Server, then you need to install BizTalk360 multiple times. Example: One for managing the BizTalk 2016 version and one for managing the BizTalk 2020 version on two different machines. For more information, find the blog: [https://blogs.biztalk360.com/monitoring-multiple-version-biztalk-environments-biztalk360/](https://blogs.biztalk360.com/monitoring-multiple-version-biztalk-environments-biztalk360/) Migration Error - The database or the database version is incompatible ![image.png](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image%28168%29.png) If you have migrated your BizTalk Server from perhaps 2016 to BizTalk Server 2020 from one machine to another machine, you just missed changing the SQL Server name. Follow the steps to change the environment details by referring to the document [link here](https://docs.biztalk360.com/shared/4cfc66ce-7429-4387-a225-6b15b61f9294). However, this is not a simple Environment server name change or Database name change. **Note: Before changing the environment details, please deactivate the license and then change the details. Once after change the details, you can activate the license back.** You know that if you are monitoring the BizTalk server, the exact server version of Administrator Tools must be installed on the BizTalk360 server. In this case, you may have forgotten to upgrade the BizTalk360 server while migrating the BizTalk server to a higher version. Once the Admin components are upgraded, the issues will be resolved.