none
Problems configuring BizTalk Server 2013 on Windows 2012 RRS feed

  • Question

  • I am receiving the following errors in my configuration log file even though I am not installing any of the BAM related features.  Has anyone else run into this issue?  Were you able to resolve it?

    [2013-08-27 10:11:41:0109  Error BAMConfigWizExt] d:\bt\4338\private\source\monitoring\configuration\extention\helpers.h(2083): FAILED hr = 80004005

    [2013-08-27 10:11:41:0109  Info BAMTools] Built feature XML: <Configuration><Feature Name="BAMTools" DisplayName="Business Activity Monitoring tools" Version="1.0" Description="Tools for  the creation and maintenance of the SQL Server and Analysis Server (OLAP) infrastructure for Business Activity Monitoring."><SQL ID="{E1FC3106-8DD4-4f12-9EB6-849DD8BDD605}" DisplayName="BAM Primary Import Database" Description="SQL database used to store the events from the Business Activities and then query for the progress and data of the activity instances. This database is also used for real-time aggregations." ReadOnly="false"><Server></Server><Database>BAMPrimaryImport</Database><WindowsSecurity Editable="no">yes</WindowsSecurity><UserName></UserName><Password></Password></SQL><SQL ID="{1D372BCB-DF59-43b6-A4A9-87082B5727B0}" DisplayName="BAM Archive Database" Description="SQL database used for archiving the Business Activity data which is too old. It is recommended to create the BAM Archive database to minimize the accumulation of Business Activity data in the BAM Primary Import Database." ReadOnly="false"><Server></Server><Database>BAMArchive</Database><WindowsSecurity Editable="no">yes</WindowsSecurity><UserName></UserName><Password></Password></SQL><Question ID="{12A38787-6B24-40ab-8888-5FE8ABA87B26}" Text="Enable A&amp;nalysis Services for BAM aggregations" Answers="Yes,No" Default="No" ReadOnly="false"><Answer Value="Yes" GUID="{902F7E20-D6AE-453f-9D23-935ED7AF94C3}"><SQL ID="{16567D1E-6946-4f4e-BB3F-900DE2648328}" DisplayName="BAM Analysis Database" Description="Analysis Services database that keeps the aggregated historical data for Business Activities" ReadOnly="false" MSOLAPServer="Yes"><Server></Server><Database></Database><WindowsSecurity Editable="no">yes</WindowsSecurity><UserName></UserName><Password></Password></SQL><SQL ID="{B973DB76-BA7F-4a2e-A57E-07EEF54B37A8}" DisplayName="BAM Star Schema Database" Description="SQL database used to transform the data collected from the Business Activity Monitoring for OLAP Processing. This database is required when the BAM Analysis database is used." ReadOnly="false"><Server></Server><Database></Database><WindowsSecurity Editable="no">yes</WindowsSecurity><UserName></UserName><Password></Password></SQL></Answer><Answer Value="No" GUID="{FC612DFE-1273-4f57-8EE3-95216638A67B}" Selected="Yes"/></Question><Question ID="{308cc88b-9e51-4103-ae4c-73300e02a7eb}" Text="&amp;Enable BAM alerts" Answers="Yes,No" Default="No" ReadOnly="false"><Answer Value="Yes" GUID="{458e1878-eae6-4e09-8e5c-ba516548ceac}"><Name ID="{8B3212A1-44EA-46bc-A06C-75E289D1F840}" DisplayName="S&amp;QL Server for Alerts Databases:" Description="Notification Services server for BAM Alerting." Hidden="false" ReadOnly="false"><Value></Value></Name><Name ID="{1DAFDF2D-4377-415a-B1CA-2C5B3729A244}" DisplayName="Prefix for Alerts Database &amp;Names:" Description="Notification Services database root name for BAM Alerting." Hidden="false" ReadOnly="false"><Value></Value></Name><NTService ID="{c116ba3f-06d0-48cf-b0a1-4b263b07250e}" DisplayName="BAM Alerts User" Description="Windows account that will have permissions to access the data in the BAM Notification Services databases during Business Activity searches." ReadOnly="false"><UserName></UserName><Domain></Domain><Password></Password></NTService><Name ID="{33c8fd0a-c89d-4dd0-8b2b-2ddacc6620e6}" DisplayName="BAM Alerts &amp;SMTP Server:" Description="SMTP server to use for sending out BAM Alerting messages." Hidden="false" ReadOnly="false"><Value></Value></Name><Name ID="{335b35f5-ffc4-4c7e-8cfc-582ec6bab9e0}" DisplayName="BAM Alerts File &amp;Location:" Description="File system location to use for writing out BAM Alerting messages.  If you accept this default location for delivering alerts by file, Configuration will create the file share and grant write permissions to the SQL NS service account and the current logged-on user." Hidden="false" ReadOnly="false"><Value></Value></Name></Answer><Answer Value="No" GUID="{3d95a679-aa37-403f-bf64-194e6aa2d993}" Selected="Yes"/></Question><Question ID="{FC99D786-2D26-489b-A748-42AE4DD0F6FC}" Text="&amp;Remove the Business Activity Monitoring tools for this Biztalk Group" Answers="Yes,No" Default="No" ReadOnly="true"><Answer Value="Yes" GUID="{4CF85429-F0DA-4ca3-8068-D125506A3FD9}"/><Answer Value="No" GUID="{5823E008-032F-4917-9EE5-B0AB4A18325C}" Selected="Yes"/></Question></Feature></Configuration>


    David Downing... If this answers your question, please Mark as the Answer. If this post is helpful, please vote as helpful.

    Tuesday, August 27, 2013 5:32 PM

Answers

All replies

  • Can you just cross check the configuration part ?

    Create & Configure BizTalk Server 2013 VM in Windows Azure

    13 Mar 2013 10:41 PM 

    1.       Overview

    The objective of this document is to provide a step-by-step guidance for creating a new virtual machine using the BizTalk Server 2013 beta image available in Windows Azure platform images gallery and then using the same VM to configure single server BizTalk Server environment. Finally, the page provides step by step guide to create and test a simple message routing scenario using the same BizTalk Server environment.

    2.       Pre-requisites

    You need to have Windows Azure subscription for Windows Azure Virtual Machine (preview) features. You may sign-up for Virtual Machines & Virtual Networks preview feature through the signup options available onWindows Azure Website.

    3.       Create BizTalk Server 2013 Virtual Machine

    After signing up for Windows Azure subscription, login to the Windows Azure Management Portal.

      I.            In the command bar (at the bottom-left of the portal), select New -> Compute -> Virtual Machine -> From Gallery.

     

          II.            This brings up the Create Virtual Machine wizard. In the first step of the wizard, select Microsoft BizTalkServer 2013 Beta image from all images. Microsoft BizTalk Server 2013 Beta (64-bit) on Windows Server 2012 image contains the Beta version of BizTalk Server 2013.

     

    Click Next (arrow icon on the bottom right of the wizard).

        III.            On the next page, provide virtual machine configuration details:

    • Virtual Machine Name: This is the name of the BizTalk Server virtual machine. You should consider using a name for the virtual machine that is descriptive enough to tell what it is used for, but short enough to make it easy to use e.g. BTS2013Demo.

    The length of the name must be between 3 and 15 characters. The name can contain only letters, numbers, and hyphens. The name must start with a letter and must end with a letter or a number.

    • New User Name: This is the username with administrator privileges that will be used to connect to the virtual machine. You may not change the initial user name – Administrator. However, you could create additional login or service user accounts after the virtual machine is created.
    • Password: This is the password for the Administrator user account. It should be at least 8 characters.
    • Size: Virtual machine may be created with different sizes. Each size has an associated CPU cores, memory, disk space etc. For demonstration purpose, you may select the Small size which comes with 1 core and 1.75 GB memory.

     

    Click Next.

        IV.            On the next page, provide virtual machine mode details:

    In this lab, we will create a standalone virtual machine. However, it is possible to connect multiple virtual machines to balance the load of traffic to your application. For standalone virtual machine, provide following details:

    • DNS Name: Specify the name of the cloud service that will be created for the virtual machine. The DNS name can contain only letters, numbers and hyphens. The DNS name must start and end with a letter or a number.
    • Storage Account: Name of the Windows Azure storage account in the current subscription that will be used for storing the virtual machine image that gets created. You may specify to create a new storage account or select an existing one, if available.
    • Region/ Affinity Group/ Virtual Network: Select the name of the region, affinity group, virtual network where the virtual machine will be created.

     

    Click Next.

          V.            On the next page, provide virtual machine options:

    An availability set is a group of virtual machines that are deployed across fault domains and update domains. An availability set makes sure that your application is not affected by single points of failure, like the network switch or the power unit of a rack of servers.

    For this scenario, leave the default selection – None for availability set.

     

    Click Submit (Tick icon).

    At this point, Windows Azure will start provisioning the virtual machine, as per the configuration details provided through the wizard.

    Windows Azure Management Portal will show the status as Starting (Provisioning), as shown below:

     

    Similarly, you would see the storage account status (based on whether you selected to create a new storage account or use an existing storage account

     

    In roughly 4-5 minutes the virtual machine should be created. You would also see the virtual hard disk file created in the storage account (navigate to storage account -> Containers -> select container), as shown below:

     

        VI.            To start virtual machine select the virtual machine in Windows Azure Management Portal and clickStart in the command bar on the bottom.

      VII.            To remote desktop into virtual machine, click Connect in the command bar on the bottom.

     

    VIII.            Provide user name and password to connect to the virtual machine. You need to use same username (Administrator) and password that was provided in the wizard, during creation of virtual machine.

     Upon completion of this, you should now be connected to the newly created BizTalk Server virtual machine.

     4.       Configure BizTalk Server 2013

    In this section, we will configure BizTalk Server environment on the single machine.

            I.            Open BizTalk Server Configuration wizard.

    Tip: You may locate the BizTalk Server Configuration by searching for BizTalk in the sidebar on remote BizTalk Server.

     

          II.            Select Basic Configuration.

        III.            Provide Database server name - same as BizTalk Server machine as we are setting up single box environment, username and password. You may choose to use the same administrator account or create a local account with less-privileges to configure BizTalk Server, to avoid the following warning message. If selecting the administrator account, then select Yes to proceed ahead.

     

     

        IV.            Click Next. BizTalk Server will start configuring, as shown below.

     

    Upon successful completion, you should see following features configured in your BizTalk Server machine.

     

    Also following databases should be created on the SQL Server:

     

          V.            Open BizTalk Server Administrator Console.

      

        VI.            By default, the administrator console will not be connected to any BizTalk Server Group. Since we already have BizTalk Server configured, choose Connect to existing group.

     

      VII.            This will bring up the following dialog box. Specify the SQL Server name (local server name) and Database name as BizTalkMgmtDb. Click OK.

     

    This would show the BizTalk Server artifacts, as shown in the figure below:

     

    5.       Configure Receive and Send Ports

    In this step, we will create and configure send and receive ports for a simple pass-thru message routing scenario.

    I. Expand existing application – BizTalk Application 1. Right click Receive Ports and select New -> One-way Receive Port…

    This brings up the Receive Port Properties dialog box.

    ii.                   Provide receive port name as FileReceivePort.

    iii.                  Select Receive Locations and click New.

    This brings up Receive Location Properties dialog box.

    iv.                 Specify receive location name as File Receive Location.

    Select Transport Type as FILE.

    Select Receive pipeline as PassThruReceive. This means that BizTalk Server will not do any processing on the incoming message and save the same into BizTalk MessageBox as-is.

     

    v.                   Click Configure. This brings up File Transport Properties dialog box.

     

    vi. Specify Receive Folder Path.

    Make sure that receive folder exists on the server.

    Also change the file mask to * so that BizTalk can pick up any file irrespective of the file extension type.

    Click OK to save the changes and close the dialog boxes.

     vii.                To create a new send port, right click Send Ports. Select New -> Static One-way Send Port.

     viii.              Specify send port name as FileSendPort

    Select Transport Type name as FILE.

    Select Send pipeline as PassThruTransmit.

     

    ix. Click Configure. This brings up File Transport Properties dialog box.

    x. Specify Destination Folder path.

    Make sure that the destination folder exists on the server. Also change the file name to %MessageID%.

    Click OK.

    xi.                 We will now specify the routing filter conditions on the send port.

    Select Filters.

    Select Property as BTS.ReceivePortName and Value as FileReceivePort.

    This creates a BizTalk subscription so that every message that is picked up by the receive port named ‘FileReceivePort’ is sent to this send port.

     xii.                Click OK to save the changes and close the dialog boxes.

     6.       Start BizTalk Application

    Although we have created and configured BizTalk receive and send ports, the subscriptions are not activated until the ports are enabled. You could enable the ports one-by-one or start the BizTalk application at once.

    I. To start the BizTalk application, right click BizTalk Application 1 and select Start.

     This brings up Start ‘BizTalk Application 1’ Application dialog box.

     

    ii.                   Click Options >> for more details. Click Start.

     

    iii.                  Make sure that receive location, send port and host instance are enabled and started, as shown below:

     7.       Test Scenario

    To test the scenario, drop a file in the receive location folder that you specified while creating the receive port/ location. The file can be of any type e.g. xml, txt, exe, etc. because it is a simple pass thru messaging scenario, where no message validation is performed by BizTalk server.

     

    BizTalk Server should pick up the file you dropped and create a new file named as a unique identifier in the destination folder.

     

    Tuesday, August 27, 2013 5:39 PM
  • Thank you, but I am not using Azure.  I am configuring this as a POC.  There are 2 BizTalk Servers that will host orchestrations, send and receive operations.  One SQL Server which contains all of the BizTalk databases.  The SSO is hosted in one of the BizTalk Servers.  All of the servers are Virtual with Windows Server 2012.


    David Downing... If this answers your question, please Mark as the Answer. If this post is helpful, please vote as helpful.

    Tuesday, August 27, 2013 6:12 PM
  • Can you give us the entire log file from the configuration? It seems like we're missing a few point here..

    Best regards

    Tord Glad Nordahl
    Bouvet ASA, Norway
    http://www.BizTalkAdmin.com | @tordeman

    Please indicate ”Mark as Answer” if this post has answered the question.

    Wednesday, August 28, 2013 9:09 AM
  • Sorry for the late reply... I was OOF.  The cleansed log file can be accessed here: https://skydrive.live.com/redir?resid=C67CDD0F83700D8E!105


    David Downing... If this answers your question, please Mark as the Answer. If this post is helpful, please vote as helpful.

    Thursday, August 29, 2013 6:11 PM
  • Hi David,

    In the logs found "To configure the server, run the BizTalk Server Configuration wizard and configure the Group feature"

    Can you please have look at following link, should help:

    http://preps2.wordpress.com/2012/05/28/biztalk-feature-group-failed-to-configure-with-error-message-error-2147217394-occurred-configuring-feature-wmi/



    I hope this helps!!!!!!

    Maheshkumar S. Tiwari|BizTalk Developer Interview Questions and Answers

    http://tech-findings.blogspot.com/


    • Marked as answer by Pengzhen Song Tuesday, September 3, 2013 11:08 AM
    Thursday, August 29, 2013 8:27 PM
  • The issue turned out to be a network routing issue when connecting to the SQL server during configuration.

    Thank you for your feedback.


    David Downing... If this answers your question, please Mark as the Answer. If this post is helpful, please vote as helpful.

    Tuesday, September 3, 2013 2:29 PM
  • Hi devid ,

    can you tell me how did you resolve this network issue with SQL?

    Saturday, October 12, 2013 8:58 PM
  • The error was due to a DNS name resolution failure for SQL server. This was resolved by adding the IP and Host_name entry for the sql server to the hosts file.

    The DTC ping utility can be used to assist in troubleshooting connections to the SQL Sever(s).  For further information and a download link, see the following:

    http://support.microsoft.com/kb/918331


    David Downing... If this answers your question, please Mark as the Answer. If this post is helpful, please vote as helpful.


    Tuesday, October 15, 2013 4:46 PM