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.

First Launch Issues

  • Updated on Jun 15, 2026
  • Published on May 27, 2024
  • 2 minute(s) read
Prev Next

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

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.1 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.

Solution:


 Please  make sure HTTP Activation for WCF is enabled as shown below:

BizTalk360-First-Launch-Enable-HTTP-Activation.png

IIS

1. HTTP Error 503 - Service Unavailable

The HTTP Error 503 occurs when the "BizTalk360" App pool is in stopped state.

Solution:

 To resolve this issue, it is required to start the BizTalk360 app pool from IIS and then try launching BizTalk360 site.

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.

3. Incorrect IIS Configurations

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.

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

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:

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:

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 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 to know the detailed information of ports and protocols that needs to be open for smooth communication among the servers.