• Print
  • Share

First Launch issues

  • Updated on 01 May 2018
  • 9 minutes to read
  • Contributors

This section contains the description and resolution of issues you might run into, when launching BizTalk360 for the first time.

Cause of the Problem If you see the error as shown before while loading BizTalk360, it is mainly due to some missing DLLs.

Solution Follow the steps as shown below to overcome this issue -

  • Select the IIS manager
  • Remove the Service.REST file (if you have set that file as virtual)

Error Type: Backend server error. Response Code: 500, Message: Internal Server Error

Cause of the Problem Once you have upgraded from one version of Windows Server to a newer version (say, for example, Windows 2008 R2 to Windows 2012), and installed BizTalk360 on the new set up, you may see an error message as follows:

Backend server error. Response Code: 500, Message: Internal Server Error,

and when trying to reach http://localhost/BizTalk360/Services.REST/AdminService.svc, you see the following error:

Could not load type 'System.Runtime.Diagnostics.ITraceSourceStringProvider' from assembly ...

Solution Download and install the .Net Framework 4.5 version (and above) again this should solve your issue. After upgrading the Windows server, .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.

Configured Disk No Longer Exists In The Server

Cause of the Problem There may be situations when you are forced to move a disk to different server. If you have enabled monitoring of the disk through BizTalk360, you will see a warning message appearing under "Errors and Warnings" screen under "Monitoring and Notifications" section (once you have moved the disk). For instance, lets say, you have your disk on Server A, and you have moved it to Server B. Once you have performed the migration process, BizTalk360 will show a warning for the disk status in the monitoring and notification screen.

Solution Follow the steps as shown below to solve the problem:

  • Navigate to Monitoring and Notifications screen in BizTalk360
  • Select BizTalk Servers from the left menu
  • Choose the server name of the new server where you have moved the disk (in our case, Server B)
  • Select Disks. Choose the alarm name from the top right corner of the page for which you need to make the change.
  • Try to disable monitoring and re-enable the monitoring. This will clear the reference to the old disk and remove the error from BizTalk360. Please note that you need to do these steps for all alarms that refer to server 1 under disk monitoring. Failing to do this will result in BizTalk360 to display warning messages for the remaining alarms.

Error Type: HTTP Error 403.14 – Forbidden - The Web server is configured to not list the contents of this directory

Cause of the Problem This is an IIS configuration error due to some handler mapping issues

Solution To overcome this issue, you need to install a hotfix for Windows Server 2008 to allow MVC to work as expected. For more information, refer this KB article.

You need to reset IIS after making the changes

Error Type: HTTP Error 404.3 - Not Found (..add a MIME map)

Cause of the Problem This problem will occur if ASP.NET is not installed correctly in your server.

Solution Please follow the steps below to rectify this issue:

  • Navigate to C:\Windows\Microsoft.NET\Framework64\v4.0.30319
  • Type the command aspnet_regiis -iru
  • -iru - Install this version of ASP.NET. If there are any existing applications that uses ASP.NET, it will not change IIS configuration to use this version.
  • aspnet_regiis -iru
  • Make sure BizTalk360 application pool is configured to run .NET Framework 4.0 and Integrated mode
  • Reset IIS

For customers using Windows Server 2012 and later, if the error is encountered in the operating system then the HTTP activation needs to be turned on in the Windows features in Server Manager by navigating to .Net Framework 4.5 Features> WCF Services> HTTP Activation.

Error Type: HTTP Error 404.17 - Not Found. The requested content appears to be script and will not be served by the static file handler

Cause of the problem This error can happen for couple of reasons, either IIS is not installed correctly or script maps are overwritten.

Solution Please execute the following commands and reset IIS. C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -ir C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation>Service ModelReg.exe -i Remember to reset IIS after executing the previous commands.

If you are using Windows 8/2012 IIS 8, then please make sure HTTP Activation for WCF is enabled as shown below

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

Error Type: HTTP Error 500.19 - Internal Server Error with Error Code 0x800700c1

Cause of the problem With the installation of WSUS (Windows Server Update Services) on the same server causes a conflicting issue with two new IIS Modules installed at the top level (from WSUS being installed). These modules then propagate down through IIS websites thus affecting other sites ability to operate, thus resulting in HTTP Error 500.19 - Error Code 0x800700c1. The two modules in question are locked by default and propagate down within IIS. The Modules added globally are DynamicCompressionModule and StaticCompressionModule.

Solution We recommend to remove DynamicCompressionModule from IIS. Follow the steps as shown below to remove the module from IIS -

  • Open up the IIS Manager
  • Click on your Server Node (top level). In the right-pane, look for Modules and double-click Modules.
  • Within Modules, look for DynamicCompressionModule. Select the module, and in the upper-right pane (Actions), choose Unlock.
  • Fall back to the left Pane (Connections), expand the Server Node and then expand Sites. Go ahead and click on BizTalk360.
  • Within BizTalk360 Home in the right pane, locate Modules and double-click Modules. This will display all of the propagated Modules from top level (Server Node).
  • You will notice DynamicCompressionModule in the list of Modules. Right-click and select Remove DynamicCompressionModule.
  • Reset IIS by using iisreset in Admin command prompt

Error Type: HTTP Error 500.21 - Handler "svc-ISAPI-2.0" has a bad module "IsapiModule" in its module list

Cause of the problem This problem will occur if ASP.NET is not installed correctly in your server.

Solution Please follow the steps below to rectify this issue:

  • Navigate to C:\Windows\Microsoft.NET\Framework64\v4.0.30319
  • Type the command aspnet_regiis -iru
  • -iru - Install this version of ASP.NET. If there are any existing applications that uses ASP.NET, it will not change IIS configuration to use this version.
  • aspnet_regiis -iru
  • Make sure BizTalk360 application pool is configured to run .NET Framework 4.0 and Integrated mode
  • Reset IIS

Error Type: Login failed for user "SERVERNAME\ApplicationPoolUser"

Cause of the problem BizTalk360 will try to connect to the underlying BizTalk environment using the IIS application pool identity credentials. If the user does not have enough rights to access the underlying environment, then you'll see this error.

Solution You can easily fix this issue by following the below procedure:

The account under which the BizTalk360 IIS application pool is running must be a member of the following groups

  • Local Administrators Group (in all servers)
  • BizTalk Server Administrators Group
  • BizTalk Application Users Group
  • BizTalk Isolated Host Users Group
  • SSO Administrators Group
  • IIS_IUSRS group

Error Type: Parameter name: strDBServer

Cause of the problem If you encounter this error with the detail as shown below: Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

The chances are your ASP.NET registration is corrupted by some updates. You can correct it by issuing the following command in Visual Studio command prompt: aspnet_regiis -iru

Solution For users running Windows Server 2012 R2, please follow the steps shown below to overcome the error:

  • Open IIS Manager and select the webserver and select Modules (found under header IIS)
  • Remove the module ServiceModel
  • Go back to IIS Manager, select the webserver again in IIS, and select Handler Mappings (found under header IIS)
  • Remove the handler svc-Integrated
  • Restart IIS by using an elevated cmd prompt and issue this command: IISRESET
  • When IIS is running again add WCF by going to "Turn Windows Features On and Off" and enable .NET Framework 4.5 Features > WCF Services > HTTP Activation
  • Restart IIS by using an elevated cmd prompt and issue this command: IISRESET

Error Type: SQL Exceptions (SELECT permission missing) On Some Of The Table In BizTalkMgmtDb

Cause of the problem BizTalk360 makes direct query to some of the BizTalk management database for performance reasons. The following tables by default would not have enough permissions even for a BizTalk Administrator role. For proper functioning of BizTalk360, it is important to assign β€œSELECT” permission to the following tables in the BizTalkMgmtDb:

  • adm_OtherDatabases
  • adm_Server2HostMapping
  • adm_ServiceClass
  • BizTalkDbVersion

Solution You can give permission either by running the following script on the BizTalk management database or by using the SQL Management Studio:

GRANT SELECT ON dbo.adm_OtherDatabases TO BTS_ADMIN_USERS
GRANT SELECT ON dbo.adm_Server2HostMapping TO BTS_ADMIN_USERS
GRANT SELECT ON dbo.adm_ServiceClass TO BTS_ADMIN_USERS
GRANT SELECT ON dbo.BizTalkDbVersion TO BTS_ADMIN_USERS

You may encounter the following error messages in the UI:

The SELECT permission was denied on the object 'adm_OtherDatabases', database 'BizTalkMgmtDb', schema 'dbo'. System.Data.SqlClient.SqlException: The SELECT permission was denied on the object 'adm_OtherDatabases', database 'BizTalkMgmtDb', schema 'dbo'.

Unable to Save. The SELECT permission was denied on the object 'BizTalkDBVersion', database 'BizTalkMgmtDb', schema 'dbo'.

  • You can grant select permission to BizTalk administrators role by following these procedures:
  • Open SQL Server Management Studio
  • Expand BizTalkMgmtDb Tables
  • Right click on adm_OtherDatabases table and select Properties
  • On the permission tab, click Search
  • On the β€œSelect user or Roles” window, click Browse
  • select BTS_ADMIN_USERS and click OK
  • Make sure SELECT check box is selected in the bottom pane. It should look as shown below.

BizTalk360-First-Launch-Add-To-BTS_ADMIN_USERS-Role.png

  • Follow the same procedure for the tables adm_Server2HostMapping and adm_ServiceClass

Error while launching application: Backend Server error 404

Cause of the problem This error can happen for couple of reasons, either IIS is not installed correctly or script maps are overwritten.

Solution Please execute the following commands and reset IIS.

C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -ir C:\Windows\Microsoft.NET\Framework\v3.5\Windows Communication Foundation>Service ModelReg.exe -i

If you are using Windows 8/2012 IIS 8, then please make sure HTTP Activation for WCF is enabled.

Permission Problems When Changing Service Account Details For BizTalk360

If you are facing any problem in changing the service account for BizTalk360, please make sure whether the service account (the one used by IIS Application pool and Monitoring NT Service) has the Administrator rights on each server to fetch the data. The service account will query the NT Services, disk information, and so on from the server.

You also need to reset IIS if in case you add any account to a corresponding group. If you do not reset IIS, the changes will not get effected.

Unable to Access BizTalk360 from a Remote Server

When you try to access BizTalk360 from a remote location, example BizTalk360 is deployed in SERVER1 and you try to access it from SERVER2 using the url http://SERVER1/BizTalk360, you may be constantly challenged by the user name/password.

Cause of the problem The issue is mainly to do with the Kerberos authentication issue.

Solution If you are using IIS 6.0, the work around mentioned in the KB article http://support.microsoft.com/kb/871179 will fix the issue. If you are using IIS 7.0, one of the solution to the problem is by changing the order of authentication providers in IIS. In IIS Manager (inetmgr), click on BizTalk360. On the features page, double click on "Windows Authentication", right click and select "Providers". Make sure the order is as shown in the below screenshot.

BizTalk360-First-Launch-Windows-Authentication-Providers.png