One of the most common problems that administration teams encounter in a BizTalk environment is while monitoring/diagnosing any issues. If an error or failure happens on different servers, the administration team has to manually log in to each server to view server information or trying to find the root cause of the issue. This is a time-consuming process and it poses severe security risks since team members will have full access permissions to log in to the server and perform any operations to fix the issues. BizTalk360 addresses this problem by providing you the capability to access SQL servers directly from the BizTalk360 user interface.
Follow the below steps to view the BizTalk Server information in BizTalk360:
- Log in to the BizTalk360 application
- Select an environment name on the landing page
- Click to expand the Manage Infrastructure option and select the SQL Servers.
- Add the SQL server type to perform operations.
Once after adding the SQL server user can view the Server details and Nt services. The SQL Server page displays the below information:
- Memory - This section provides information about the SQL Server RAM memory
- CPU - CPU usage information is displayed in this section
- Windows edition - This section provides information about the Windows edition installed on the server
- Hardware - Hardware details of the server is displayed in this section
By clicking the arrow in the upper-right corner of the server tile, more information about the server can be viewed. For an example, see the below screenshot.
By clicking on the NT Service tab in BizTalk360, users can manage NT services across standalone servers, clustered servers, and Always On Availability Group (AG) configurations.
- Standalone server - In a standalone, when the SQL Server is reachable, all NT services associated with the BizTalk environment are listed, allowing users to view their status and perform operations such as start, stop, and restart directly from the BizTalk360. However, if the SQL Server becomes unreachable, BizTalk360 cannot retrieve or display the NT services, preventing users from viewing their status or managing them through the application.
- Clustered SQL Server -, BizTalk360 connects to the active SQL node to retrieve and display NT services associated with the BizTalk environment. Users can monitor their status in real-time and perform operations such as start, stop, or restart directly from the application. BizTalk360 continuously communicates with the active node to ensure smooth monitoring and management. When a SQL Server failover occurs, the passive node takes over as the active node, and BizTalk360 automatically detects this switch. It then re-establishes the connection to the new active node, ensuring uninterrupted access to NT services and maintaining operational continuity.
- when the Cluster SQL server is completely un-reachable then couldn't able to retrive the NT services and user cannot view or manage them.
- Always-On Availability Group lists all available nodes within the group, enabling users to monitor and manage NT services across each node. A Primary Group indication clearly identifies the current primary replica, ensuring users know which node is actively handling operations. The primary replica allows BizTalk360 to continuously retrieve and sync NT service statuses, providing real-time monitoring and management capabilities. Users can start, stop, and restart NT services on any node. During a failover, if the primary replica fails, the secondary replica automatically takes over, and BizTalk360 seamlessly reconnects without requiring user intervention.
"Server=PRIMARY_INSTANCE;Failover Partner=MIRROR_INSTANCE;Database=BizTalk360;Integrated Security=True;"
SQL Server Permissions (SQL Servers)
The SQL Server Permissions feature in BizTalk360 provides administrators with a detailed view of SQL Server access, configuration, and permission settings required for BizTalk360 operations.
It helps verify that the BizTalk360 service and IIS accounts have the necessary rights and connectivity to the SQL Server hosting the BizTalk databases.
This centralized blade simplifies permission validation, connectivity checks, and troubleshooting of SQL-related issues that may impact BizTalk360 monitoring, data collection, or analytics.
Accessing SQL Server Permissions
- Navigate to Administration → Manage Infrastructure → SQL Servers.
- Select a SQL Server from the list.
- Click the Server Permissions button to open the permission details blade.
Details Displayed in the SQL Server Permissions Blade
1. Service Logon Access & Permissions
This section displays the access rights of the BizTalk360 Service Account and the IIS AppPool Account to the SQL Server and its underlying system permissions.
Item | Description |
Local Admin | Indicates whether the BizTalk360 service account is a local administrator on the SQL Server. |
Distributed COM Users / Performance Log Users / Performance Monitor Users | Shows whether the service account is part of key system groups required for remote data access and monitoring. |
WMI Namespace Access | Validates that the account has WMI access on the SQL Server to fetch system and SQL-related metrics. |
Use Case:
When facing issues with SQL connectivity or database access, this section helps confirm whether permission-related configurations are correct.
It also aids in verifying that the BizTalk360 service or IIS accounts have the required rights to execute monitoring queries or retrieve SQL performance counters. Reduces configuration errors and ensures secure, consistent connectivity between BizTalk360 and SQL Server components.
2. Pre-requisites
This section ensures that the SQL Server is reachable, and the required Windows services and ports are running for BizTalk360 to function smoothly.
Pre-requisite | Description |
MSDTC | Verifies if the Microsoft Distributed Transaction Coordinator service is running — crucial for cross-database transactions. |
RPC | Ensures the Remote Procedure Call (RPC) service is active and accessible. |
WMI Service | Confirms that the Windows Management Instrumentation service is running to allow system-level data collection. |
TCP 135 | Validates that port 135 is open for RPC communication. |
SQL Server Ports | Displays the ports used by SQL Server (e.g., 55781, 64439) to check connectivity availability. |
Use Case:
When the SQL Server is not reachable, this section helps identify whether the issue lies in network connectivity, blocked ports, or stopped Windows services.
It also helps diagnose database connection errors or timeouts during BizTalk360 service startup or monitoring. Provides faster root-cause identification of reachability or connection issues without needing manual SQL configuration checks.
3. Feature Accessibility
Displays which data collection features are accessible through WMI or PerfMon interfaces.
Feature | Service Accessibility |
Disks, NT Service, Event Logs Data Collection | Uses WMI to collect data about system disks, SQL services, and event logs. |
System Resource | Uses WMI and PerfMon to monitor server performance (CPU, memory, disk usage). |
Analytics Data Collection | Uses PerfMon to retrieve SQL Server performance counters used for BizTalk360 analytics. |
Use Case:
Useful when troubleshooting SQL performance data not being shown in BizTalk360 dashboards. You can determine if the issue is due to missing permissions, restricted PerfMon access, or stopped system services. It helps ensure accurate performance and analytics data collection from SQL Servers, improving visibility across your BizTalk environment.
Notes:
- Green Indication – Access, permission, or service is correctly configured and available.
- Red Indication – Access or permission is not available, or the service is stopped.