--- title: "BizTalk360 Application Launching Issues" slug: "first-launch-issues" tags: ["BizTalk", "BizTalk360"] updated: 2026-11-05T06:45:38Z published: 2026-11-05T06:45:38Z canonical: "docs.biztalk360.com/first-launch-issues" --- > ## 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. # BizTalk360 Application Launching Issues This section contains the description and resolution of issues you might run into when launching the BizTalk360 after the installation for the first time. The errors have been grouped under three categories as follows: - Windows - IIS - SQL Server - Active Directory ## Windows ### 1. 500 Internal Server Error When you upgrade windows server to a newer version (such as Windows Server 2019 to Windows Server 2022) and install BizTalk360 on the new set up, you may see an error message as follows: *Backend server error. Response Code: 500, Message: Internal Server Error.* ### **Solution:** To resolve this issue, download and install the .NET Framework 4.6.2 version (and above) again. After upgrading the Windows server, the .NET Framework might not be updated along with the Windows server upgrade. Therefore, a fresh installation of .NET Framework will help to resolve this issue. ### 2. HTTP error 404.0 - Not Found If you run into below error while launching BizTalk360 UI, it means that the HTTP activation feature is not installed on the BizTalk360 server. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-VIIHNOKV.png) **Solution:** Please make sure HTTP Activation for WCF is enabled as shown below: ![BizTalk360-First-Launch-Enable-HTTP-Activation.png](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/a515ed33-291e-45a8-9538-79819e13e30a.png) ### 3. Error Type: Unable to generate a temporary class **Error Type:** Unable to generate a temporary class (result=1). error CS2001: Source file ‘C:\WINDOWS\TEMP\filename.cs’ could not be found error CS2008: **Solution:** You can fix this problem by providing **read/write** **access** to the **BizTalk360 service account** configured for the BizTalk360 IIS application pool for the folder C:\Windows\Temp ## IIS ### 1. HTTP Error 503 - Service Unavailable The HTTP Error 503 occurs when the "BizTalk360" App pool is in stopped state. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-1779706978388.png) **Solution:** To resolve this issue, it is required to start the BizTalk360 app pool from IIS and then try launching BizTalk360 site. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-O3FNZYU2.png) ### 2. Authentication failed for user The Authentication failed for user is a straight forward exception as it means that the logged in user is not added to the BizTalk360 Team Management. Adding this user in BizTalk360 would resolve this challenge. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/base64-converted-image-1780580080003.png) ### 3. Incorrect IIS Configurations![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-MLVP6VIY.png) **Solution:** The error suggests that the .NET CLR version and Managed Pipeline Mode of BizTalk360 Application pool are not set correctly under IIS. It has to be configured as shown in the below screenshot in order to overcome this issue. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-UVFZ8L4J.png) Additionally, it is required to ensure that the default binding value exist for the BizTalk360 site under IIS as missed values can also cause similar launching issue. 1. ### **IIS Error 403.1 - Forbidden** ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-WIG64BKQ.png) The above error occurs when the Static File of Handler mappings is given only the “Read“ access for either Default Website/BizTalk360 site. To overcome this issue, it is required to choose “Read” and “Script” permission on the Static File as shown below: ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-GF45KB3J.png) ### 5. Negotiate Provider missing from IIS Windows Authentication If the **Negotiate** provider is not available under the following IIS configuration: **Default Website → Authentication → Windows Authentication → Providers**, you may encounter issues when accessing the BizTalk360 application. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-SYAI0LOG.png) **Solution** To resolve this issue, add the **Negotiate** provider to the BizTalk360 website in IIS. Follow these steps: 1. Open **IIS Manager**. 2. Navigate to **Sites → Default Web Site → BizTalk360**. 3. Open IIS **→** **Authentication**. 4. Select **Windows Authentication**. 5. In the **Actions** pane, select **Providers**. 6. Click **Add** and add the **Negotiate** provider. 7. Once added, move **Negotiate** to the **top** of the provider list. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-BPNH46I0.png) After making the changes, perform an IIS reset. Once IIS has restarted, try accessing the BizTalk360 application again. ### 6. The collection already contains an Address with HTTP After installing BizTalk360, you may encounter the following error when accessing the BizTalk360 application: > [!CAUTION] > **Server Error in '/BizTalk360' Application** This collection already contains an address with scheme http. There can be at most one address per scheme in this collection. > [!TIP] > If your service is being hosted in IIS, you can fix the problem by setting `system.serviceModel/serviceHostingEnvironment/multipleSiteBindingsEnabled` to `true` or specifying `system.serviceModel/serviceHostingEnvironment/baseAddressPrefixFilters`. **Exception Details:** `System.ArgumentException: This collection already contains an address with scheme http. There can be at most one address per scheme in this collection.` #### Cause This issue occurs when **multiple bindings are configured for the IIS website** under which BizTalk360 is installed. To verify this, open **IIS Manager** and select the website where BizTalk360 is installed. In the **Actions** pane on the right, click **Bindings.** ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-FNQSTZ4J.png) If multiple bindings using the same HTTP scheme are configured for the website, BizTalk360 may encounter the above exception. ### Resolution There are two possible solutions. #### Solution 1: Configure the BizTalk360 Application Pool to Use ASP.NET 4.0 If **ASP.NET 4.0** is installed on the server, configure the BizTalk360 IIS application pool to use ASP.NET 4.0. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-T3WGDMLW.png) After configuring the application pool, add the following configuration to the BizTalk360 `Web.config` file: ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-K61SJ194.png) Save the changes and restart IIS. Then try accessing the BizTalk360 application again. #### Solution 2: Install BizTalk360 on a Dedicated IIS Website If ASP.NET 4.0 is not available on the server, create a [**dedicated IIS website for BizTalk360**](/v12/docs/installation-guides#install-biztalk360-on-a-custom-website) using a custom port. For example, you can create a website using port **90**. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-F4BMZ4GU.png) After installation, access BizTalk360 using the URL configured for the dedicated IIS website. #### Recommendation If the existing IIS website has multiple bindings and you do not want to modify its configuration, we recommend **Solution 2**. Installing BizTalk360 on a dedicated IIS website with a unique port avoids binding conflicts with other applications hosted on the server. ## SQL Server ### 1. Network related or Instance specific error ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/base64-converted-image-1780580080008.png) ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/base64-converted-image-1780580080011.png) The Network related or Instance specific error is quite obvious that the SQL server hosting BizTalk360 database is not reachable from BizTalk360 server. To fix this error, please ensure that the concerned SQL server instance is reachable from BizTalk360 server. ### **2. Unable to access environment:** ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-EMTV0EAO.png) The above screenshot states that the BizTalk360 service account does not have access to the BizTalkMgmtDb and BizTalkMsgboxDb. Kindly note that it is mandatory to assign necessary permission to the BizTalk360 service account on the SQL server level so that the respective BizTalk environment can be accessed and monitored without any challenges. Please refer to the [this document](https://docs.biztalk360.com/v12/docs/prerequisites#post-installation-requirements) to know the SQL server related permission for the service account. ### Dependent Ports and Protocols: There are some Ports and Protocols that BizTalk360 expects to be enabled among BizTalk360, SQL and BizTalk servers for efficient performance. The critical dependencies are mentioned below: - RPC - 135 - SQL Server - 1433 and 1434 - TCP - Telnet/Ping You can refer to [this blog](https://www.biztalk360.com/blog/biztalk360-dependent-ports-protocols/) to know the detailed information of ports and protocols that needs to be open for smooth communication among the servers. ## Active Directory ### 1. Unable to Log In When the AD User Belongs to a Distribution Group After installing BizTalk360, you can create additional **Super Users** who are members of your **Active Directory (AD)** and grant them access to BizTalk360. However, when a newly added AD user attempts to log in to BizTalk360, they may encounter an error similar to the one shown below: ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-SDRGZSD5.png) #### Cause If the AD user is a member of a **Distribution Group** in Active Directory, the user will not be able to access BizTalk360. This restriction is implemented for **security reasons**. You can verify the user's group membership from the Active Directory server by checking the user's group properties. #### Solution Once the user is removed from the **Distribution Group** and added to the appropriate **Security Group**, the user should be able to log in to BizTalk360 successfully. To allow the user to log in to BizTalk360 successfully: 1. Open **Active Directory Users and Computers** on the AD server. 2. Locate the affected user account. 3. Open the user's **Properties** and check the group memberships. 4. Remove the user from the **Distribution Group**. 5. Add the user to the appropriate **Security Group**. 6. Also, make sure the Group scope is **Global**. 7. Save the changes. 8. Try logging in to BizTalk360 again. ![](https://cdn.document360.io/253f6006-3994-42d0-98cd-fdc637f51791/Images/Documentation/image-Q2TKCQZC.png)