Error – “Microsoft .NET Framework 3.5 Service Pack 1 is required”- Specify an alternate source path

Hello Everyone.

Recently, I wanted to setup BizTalk 2013 R2 system and while installing SQL Server 2014 I ran into below error –

Error Message – “Microsoft .NET Framework 3.5 Service Pack 1 is required”.

Setup failed to find “Microsoft .NET Framework 3.5 Service Pack 1” and therefore we can’t proceed with the installation.

Setup failed to find "Microsoft .NET Framework 3.5 Service Pack 1" and therefore we can't proceed with the installation.

So, I went ahead and tried to install this Feature from Server Manager by following below steps –

  1. Open Server Manager and click on “Add roles and features”

Add Roles and Features Wizard

2. Select “Role-based or feature-based installation”

Add Roles and Features Wizard 2

3. Select appropriate server from the Server Pool

Add Roles and Features Wizard_ChooseServer

4. Select .Net Framework 3.5

Add Roles and Features Wizard_Select.NETFramework 3.5

5. Now you just need to confirm your selection and proceed with installation. But for me it showed below warning –

Warning – “Do you need to specify an alternate source path? One or more installation selections are missing source file on the destination server.”

Add Roles and Features Wizard_SpecifyAlternateSourcePath

If you ignore this warning and proceed with the installation, it will fail with below error.

Error Message – The source files could not be found. Try installing the roles, role services or features again in a new Add Roles and Features Wizard session, and on the Confirmation page of the wizard, click “Specify an alternate source path” to specify a valid location of the source files that are required for the installation. The location must be accessible by the computer account of the destination server.


So, the question against me was how to find and where to find an alternate source for .Net Framework 3.5 Feature. So, I spent lots of time on internet attempting to find same without any luck.

Finally I got a SQL expert who guided me with the solution, which is as below-

The alternate source path can be found in Windows Operating System media within below location –

<OS Media Drive>:\sources\sxs

Add Roles and Features Wizard_SpecifyAlternateSourcePath2

Simply say “OK” and proceed with the installation. It should be successful this time.

Add Roles and Features Wizard_FeatureInstallSuccessful

Later, proceed with SQL Installation, this time you will not receive the same error and installation will be smooth.

Hope this helps.

Contact Me:-

@Gmail@Facebook@LinkedIn@MSDN Technet Profile@My Personal Blog Site


BizTalk Server Migration from 2010 to 2013 R2- Why & How

This document is intended to give an overview of why & how migration from BizTalk Server 2010 to 2013 R2 can be accomplished. It also attempts to aggregate known issues or probable challenges which can erupt during this process.

Why to Migrate

Mainstream Lifecycle of BizTalk 2010 is going to end on 1/12/2016 post which Microsoft Support is limited and for extended support you will have to purchase Extended Support within 90 days of mainstream support end (which can be missed easily).

BizTalk Version Mainstream Support End Extended Support End
BizTalk Server 2010 1/12/2016 1/12/2021
BizTalk Server 2013 7/10/2018 7/11/2023
BizTalk Server 2013 R2 7/10/2018 7/11/2023

Read more about Lifecycle Information for Microsoft Server Products Support

There are lots of disadvantages of being in extended support:

  • Non-Security hotfix support will require extended hotfix agreement, purchased within 90 days of mainstream support ending
  • You incident support will be chargeable
  • You cannot make warranty claims
  • You cannot request design changes and feature requests

You probably do not want to run your business on limited support, so it’s better to upgrade if your current version is already in extended support or your mainstream support is coming.

Planning Migration

Microsoft always claims that the upgrade will be seamless and will not affect anything. However, there is always a big risk of something going wrong. Because the stack we are upgrading has lots of things like Operating System, .Net Framework, SQL, BizTalk etc. so we need to be super careful.

Upgrade vs. Migration

Two approaches can be considered:

· Upgrading of the existing BizTalk Server 2010 Infrastructure to BizTalk Server 2013 R2(In House Upgrade)

· Building a new BizTalk Server 2013 R2 Infrastructure to co-exist with the existing BizTalk Server 2010 Infrastructure to allow for gradual migration of BizTalk Applications

Benefits of In-House Upgrade

This allows you to upgrade BizTalk within the existing infrastructure. For ex- If you have a standalone BizTalk Server 2010 server, you can upgrade Operating System, SQL, BizTalk etc. just by clicking on the installer and proceeding with Upgrade option.

For more details refer In-house BizTalk Upgrade or Upgrading to BizTalk Server 2013 from BizTalk Server 2010-2009


Disadvantages of In-house upgrade

· As many softwares like Windows OS, SQL, Visual Studio, BizTalk etc. needs to be upgraded, there is higher risk of failure.

· Generally we would like to upgrade/enhance the hardware as well (better CPU, RAM, OS to 64bit etc.) which is not possible in this case.

This approach is only suitable for small businesses with simpler integration.


Here the BizTalk environment must be recreated on an operating system supported by BizTalk Server 2013 R2 and later all other upgraded applications needs to be deployed.

Steps to perform Migration

1) Recreate BizTalk Servers 2013 R2 environment with desired and supported Hardwares and Softwares.

BizTalk Server 2013 R2 Supported Softwares

Microsoft Windows Windows Server 2012 R2, Windows Server 2012, Windows 8.1, Windows 7 SP1.
Internet Information Services (IIS) The version that comes with the operating system. KB 224609 lists the versions.
Microsoft .NET Framework .NET Framework 4.5
Microsoft Visual Studio Visual Studio 2013
Microsoft SQL Server SQL Server 2014 or SQL Server 2012 SP1

Refer Hardware and Software Requirements for BizTalk Server 2013 and 2013 R2 for more details.

Follow How to install & Configure BizTalk Server 2013 R2 document for installing and configuring BizTalk.

2) Upgrade existing BizTalk Applications to latest version

a) Copy all the existing projects(folders) to newly created BizTalk 2013 R2 Servers

b) Open each solution one by one which needs to be migrated in Visual Studio 2013, this will automatically open a migration wizard. Make sure Target Framework is .Net Framework 4.5 for all projects. Finally a “Migration Report” will be generated, as shown in pic below. Go through the report to see if it has any error message.


Migration Report

c) Ensure to change the .Net Framework versions for all related class libraries (helper class/dlls) manually to .NET 4.5 versions, by default Helper classes (Class Library) will not be upgraded.


d) Rebuild all the applications and fix any build errors.

e) Upgrade/Replace any obsolete method with their latest version. Ex- Use “System.Configuration.ConfigurationManager.GetSection” instead of “System.Configuration.ConfigurationSettings.GetConfig”.

f) You may also have to upgrade/modify your code to incorporate changes occurred in Standard External Libraries.

Ex-In our case we were using older version of “Microsoft Enterprise Library” dll which was later upgraded to 6.0 which made us to change our implementation/code as well.

g) Ensure to modify deprecated Adapters. For example SQL & SOAP adapters are deprecated in BizTalk 2013 R2, so they must be replaced by their corresponding WCF Adapters.

Note: – Deprecated doesn’t mean non-availability, it means that though you are able to use these adapters in current version of BizTalk but in future version they might get removed. Microsoft even may deny providing support. Ex- SQL adapter was deprecated with BizTalk Server 2009 was released and is now unsupported in BizTalk Server 2010 onwards.

Read here for more details.

h) Take necessary steps for upgrading any other dependencies if required.

Later these applications can be used for regular deployment in any BizTalk environments.

Note: – All Applications should be thoroughly tested in all Pre-PROD environments.

Ideally Migration Effort is minimal as most of the work is done by the wizard, but BizTalk being a middleware depends on many external systems like Databases, SAP, SFTP etc. and so the main cost/effort is of Thorough Testing.

Also, if you decide to perform Code Refactor/Enhancement efforts will be increased accordingly. For example- If you have any SOAP Web Service (.asmx) and you want to upgrade it to WCF (.svc) it will need extra efforts.

Hope it helps.

Contact Me:-

@Gmail, @Facebook, @LinkedIn, @MSDN Technet Profile, @My Personal Blog Site

The map name was not provided and is required.

Recently while working on my first ESB POC I faced one strange issue. I was using BRE Resolver to resolve the map name for transformation, however I was getting below error.

Error Message:- There was a failure executing the receive pipeline: “Microsoft.Practices.ESB.Itinerary.Pipelines.ItinerarySelectReceiveXml, Microsoft.Practices.ESB.Itinerary.Pipelines, Version=, Culture=neutral, PublicKeyToken=31bf3856ad364e35” Source: “ESB Dispatcher” Receive Port: “GetEmpRequest_RP” URI: “E:\Prashant\POC\IN\*Copy*.xml” Reason: The map name was not provided and is required.

I tested my Rule using “Test Policy” functionality in “Business Rule Composer” which was giving the expected output. I even looked into the ESB Traces using Debug View but all in vain.

I was using “Microsoft.Practices.ESB.ResolverProviderMessage” as Document Type as suggested in many tutorials and videos.

After struggling for hours and I found the below blog-

Which suggests that the type of the incoming message is mistakenly determined to be “Microsoft.Practices.ESB.ResolveProviderMessage” i.e. Resolve instead of Resolver.


Later by making Document Type as above things started working.

But this proves how little time and money Microsoft has invested in development of ESB Toolkit.

Contact Me:-

@Gmail, @Facebook, @LinkedIn, @MSDN Technet Profile, @My Personal Blog Site

Step by Step Guide to Install & Setup ESB Toolkit and Management Portal (Standalone Machine)

Installing and Configuring ESB Portal is really hectic & cumbersome task. I myself faced many roadblocks so thought to document it here, hope it’s useful.


1. Install Both VS 2012 and 2013 (BT 2013 Dev tools & ESB toolkit 2.3 requires some components from VS 2012 which I haven’t figure out yet if you can figure out please share it across).

2. Install SQL Server with Analysis Services and ensure it’s running under the LocalSystem account

3. Install BizTalk Server 2013 R2, LOB WCF Adapters and ESB Toolkit.

4. Configure BizTalk with full BAM configuration. Ensure to check “Enable Analysis Services for BAM aggregations”, give the Server Name and Apply Configurations.

5. Install Enterprise Library 5.0 from below link-

6. Install Microsoft Report Viewer Redistributable 2008 from below link-

Add Roles & Features:-


a) IIS with IIS 6 compatibility Tools(complete)

b) Windows Authentication & Basic Authentication(Under : Web Server(IIS) -> Security)


a) WCF & HTTP Activation for both .Net 3.5 and 4.0/4.5

Setting up the ESB Samples and BAM

1. Add the System Account to the BAM STAR Database

a. Open SQL Management studio and connect to server having BAM Star Schema database

b. Run the following command:

use BAMStarSchema

EXEC sp_addrolemember ‘db_owner’, ‘NT AUTHORITY\SYSTEM’

2. Create a folder named: C:\Projects\Microsoft.Practices.ESB

3. Unzip C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit\ file into this folder

4. Remove Read-only attribute from all files in C:\Projects\Microsoft.Practices.ESB folder.

5. Open an elevated Visual Studios command prompt

a. Setup BAM

i. Navigate to C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\Tracking

ii. Run Bm.exe deploy-all -DefinitionFile:”C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit\Bam\Microsoft.BizTalk.ESB.BAM.Itinerary.xml”

    iii. Run Bm.exe deploy-all -DefinitionFile:”C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit\Bam\Microsoft.BizTalk.ESB.BAM.Exceptions.xml”

b. Re-register the Itinerary Visual Studio templates

i. Run devenv.exe /setup

c. Create the strong name key for the Samples

i. Run sn -k c:\Microsoft.Practices.ESB.snk

ii. Copy this to C:\Projects\Microsoft.Practices.ESB\Keys

6. Fix the WCF Resubmit Port

a. Navigate to C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit\Web\ESB.ItineraryServices.WCF

b. Open the web.config file

c. Locate: <soapHeaderMetadata enabled=”true”> and Update to be <soapHeaderMetadata enabled=”false”>

Configure ESB

1) Run ESB Configuration Tool as administrator

2) In the ESB Configuration Tool, from the left pane, select ESB Configuration. On the right pane, for Database Server, specify the database server name where the databases required for ​BizTalk ESB Toolkit will be created.

3) In the IIS Web Services box, specify the user credentials under which the applications required for BizTalk ESB Toolkit are created. Also specify the name of the website in IIS under which the applications are created.

Note: – At this stage, you can click Apply Configuration towards the top of the ESB Configuration Tool to configure the BizTalk ESB Toolkit with the default settings. However, if you want to do a custom configuration, you can perform the remaining steps as well. In such a case, the values you specify in the subsequent steps take precedence over the default values.

4) From the left pane, expand Exception Management, and do the following:

5) Click the Database node, and clear the Enable Exception Management Database check box if you do not want to configure an exception management database.

6) Similarly, on the Database node, select the Use Existing Database checkbox if you want to use an existing database instead of the configuration tool creating a new database. You can also specify the database server name and the database name.

7) On the Exception Web Services node, clear the Enable Exception Services check box if you do not want to configure these services. Alternatively, if you want to run these services under a different website, you can specify that here too.

8) From the left pane, expand ESB Core Components, and do the following:

9) Click the Itinerary Database node, and clear the Itinerary Database check box if you do not want to configure an itinerary database.

10) Similarly, on the Itinerary Database node, select the Use Existing Database checkbox if you want to use an existing database instead of the configuration tool creating a new database. You can also specify the database server name and the database name.

11) On the Core Web Services node, clear the Enable Core Services check box if you do not want to configure these services. Alternatively, if you want to run these services under a different website, you can specify that here too.

12) From the left pane, click Configuration to specify the SSO configuration. If you are installing and configuring the BizTalk ESB Toolkit in a single server environment, you should select File Configuration Source, which is the default selection. However, if you are setting up a multiple-machine deployment, you must select the SSO Configuration Source, and then provide the following values.

13) SSO Server: Name of the SSO server.

14) Configuration file: Click the ellipsis button (…), and then browse to the Esb.config file, which is included in the ​Microsoft BizTalk ESB Toolkit

15) Application Name: Type a name for the SSO application. For example, ESB Toolkit.

16) Contact Information: Type the appropriate contact information in the following format:

17) Administrator Group Name: Click the ellipsis button (…), and then browse to the appropriate name

18) User Group Name: Click the ellipsis button (…), and then browse to the appropriate name

19) Click Apply Configuration. Open IIS and notice that the applications required for ​BizTalk ESB Toolkit are now created under the website you specified while configuring ​BizTalk ESB Toolkit.

20) In the ESB Configuration Tool, on the ESB BizTalk Applications node, from the right pane, do the following:

21) Select the Enable ESB Core Components in BizTalk Server check box to create the application in the BizTalk Server Administration console. Select the Use Default Binding to bind this application to the default host. Select the Do not use Default Binding if you do not want to bind the application to the default host. In such a case, you must explicitly bind the application to a host, once the application is created.

22) Select the Enable ESB JMS/WMQ Components in BizTalk Server check box to create the application in the BizTalk Server Administration console. Select the Use Default Binding to bind this application to the default host. Select the Do not use Default Binding if you do not want to bind the application to the default host. In such a case, you must explicitly bind the application to a host, once the application is created.

23) Click Apply Configuration to create the applications you selected. Verify that the applications are created in the BizTalk Server Administration console.

Note: – Status of the configuration will be visible on the bottom left of this tool. Wait till it displays message – EsbBizTalkApplication: Configured

Refer: – for more details

Configuring ESB Management Portal

  1. In Visual Studio 2012, open ESB.Portal.sln found in C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal
  2. Click OK to the dialog pop up about the solution being unsupported by Visual Studio 2012
  3. Close the Migration Report IE window that opens once migration is complete
  4. In the ESB.BAM.Service.Implementation C# project add a reference to Microsoft.Practices.ServiceLocation.dll. This can be found at C:\Program Files (x86)\Microsoft Enterprise Library 5.0\Bin
  5. Open web.config file found in ESB.Portal project. Comment out the following section if present(ideally shouldn’t be there in BizTalk 2013 R2):

<sectionGroup name=”scripting”>…

  1. Save all
  2. Select the ESB.Portal project, right-click rebuild this project (note the full Solution will not build)
  3. Close visual studios
  4. Open a 32-Bit PowerShell windows as Administrator
  5. Type: Set-ExecutionPolicy –ExecutionPolicy Unrestricted (confirm Y when promoted)
  6. Run Management_Install.cmd file found in C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\Install\Scripts

If everything is good, there shouldn’t be anything in RED.

  1. Finally Open http://localhost/ESB.Portal

Ensure you click on the Gray Gear Icon and change the selection to All Applications

Note: – Add the User (Identity) for which ESB Application Pools is configured and “Network Service” to BizTalk Isolated Host Users group. This will allow these websites to post messages in BizTalkMessageBox.

BizTalk Tracing

ESB processing can get complicated, so I would always suggest you to enable tracing.

1. In Notepad open the machine.config file for both 32 & 64 bit, placed at below locations

C:\Windows\Microsoft.NET\Framework\v4.0.30319\CONFIG\machine.config for 32-bit
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\CONFIG\machine.config for 64-bit

2. Locate the line with the closing configSections tag.

3. Under that line paste the following section:



<add name=”BizTalkESBToolkit” value=”4″/>



4. Save and close machine.config.

5. Start the DebugView program (Download)

6. In DebugView, on the Capture menu, click Capture Global Win32 to make sure that it is checked.

7. In the BizTalk Server Administration console, restart the BizTalkServerApplication host instance.

Refer below link for more details: –

Known Issues:-

1) ESB Toolkit BRE Itinerary Resolver Fails with Exception:-

The following exception is thrown with ESB 2.2 & 2.3 on Microsoft BizTalk Server 2013 when the ItinerarySelectReceiveXML receive pipeline is used to call the Business Rules Engine to dynamically select an itinerary (using the ESB BRI Resolver).

Error Message:-

Exception has been thrown by the target of an invocation.

Source: Microsoft.Practices.ESB.Resolver.ResolverMgr

Solution: – It requires some changes in ESB.Config file, please check the below link about this issue.

Contact Me:-

@Gmail, @Facebook, @LinkedIn, @MSDN Technet Profile, @My Personal Blog Site

Very Strange behavior of XML Disassembler- Property Promotion not happening properly

While working on a pipeline component I encountered a very strange behavior of XML disassembler. I had few promoted properties which I was trying to access in a pipeline component in Validate stage after the execution of XML Disassembler. As we all know that the Pipelines are executed in sequential manner and the output of one pipeline component is used as input to the next one in the sequence(except in Disassemble stage). ( Read more- Understanding Pipeline Execution). So, ideally after execution of XML Disassembler, Promoted Properties should be accessible in later stages. But shockingly there value was NULL. Now let’s have a look into my sample BizTalk application for better understanding. I have a simple schema in which both the properties are promoted- Source&PropertySchema Emp & Property Schema Image I created a simple pipeline component where I tried to read values of ID and Name from message context using below code and later promoted “ReceiveFileName” FetchingPromotedProps Fetching Promoted Properties in Pipeline Component Image Created a simple Custom Receive Pipeline with XML Disassembler and later used my pipeline component in Validate Stage. ReceivePipeline Receive Pipeline Image But strangely when I tried to fetch the promoted properties found out that it’s returning NULL as shown below. PromotedPropsAsNullAfterCommentingTheReadOperation Promoted Properties as NULL in Pipeline component Image Cause:- After some research got to know that it’s a known behavior. Basically, the XmlDisassembler does not read through the incoming message immediately.  It waits until some later component or the MessageBox reads it.  This is done for various performance reasons like memory consumption, etc. So, since my custom pipeline component is next in line, when it gets the Message, data has not yet been read by the XmlDisassembler even though it passed that Stage in the Pipeline, so it hasn’t had a chance to Read and Promote any Context Properties.  This is by design, and what you are seeing is a known side-effect. Its accomplished by wrapping the data in a custom Stream class.  That is why it only gets read and processed when some other component reads it. Solution/Workaround:- The easiest option would be to just do you work with the Properties in an Orchestration. If you absolutely have to use a Pipeline Component, then you will have to somehow force a Read by the XmlDisassembler. For example in our pipeline component we have read the values using below code and forced a Read/Promote by the XmlDisassembler. //Reading message data using XML Document. System.Xml.XmlDocument xmlDoc = new System.Xml.XmlDocument(); xmlDoc.Load(originalStream); Using XMLDoc can have performance implication as the complete message will be loaded in memory, so you can use the below code as well. //Reading message data using Stream, this will not have any performance implication. System.IO.MemoryStream ms = new MemoryStream(); originalStream.CopyTo(ms); ms.Position = 0; inmsg.BodyPart.Data = ms; As shown in below image.  PromotedPropsAfterReadingTheValueUsingStream  Promoted Properties containing Value After performing Forced Read by XML Disassembler Image   Check the discussion over the same issue- XML Diassembler component is not doing property promotion   Hope it helps.   Download the sample application from here. Word version of this blog is here.  

Contact Me:-

@Gmail, @Facebook, @LinkedIn, @MSDN Technet Profile, @My Personal Blog Site

Implementing Correlation (Property Promotion) without any Common Element

I recently encountered a scenario where I had to implement correlation without any common element between the outgoing and incoming messages. Generally we implement correlation by Initializing and following correlation on the same element.

Let’s come to our sample for better understanding.

We have two schemas “Candidate” with fields as CandidateID, Name City and Status and “Employee” schema with fields as EmployeeID, Name, ReportingCity and ReportingManager.

We need to initialize correlation for CandidateID and follow correlation on EmployeeID. But as these are two different elements so they can’t become one CorrelationType. However they hold the same value.

Candidate, Employee & PropertySchema

 Candidate, Employee and Property Schema Image

Solution: – I created a PropertySchema with one element as “UniqueID” and promoted CandidateID and EmployeeID against it.

How to achieve it:-

  • Create on property schema with one element as “UniqueID”
  • In Candidate schema, Right click on CandidateID-> show promotion ->Property Fields -> Click on top right corner a folder like icon (Add new Property Schema) and select the property schema created in first step.
  • Now click on the CandidateID and “Add”. This will add the property for CandidateID field as shown below.


Property Promotion Image

  • Perform the same steps to promote EmployeeID field as well present in Employee Schema.

Let’s have a look into the final schemas. If you notice in the Properties section you will find PropertyName = “UniqueID”. It means EmployeeID or CandidateID will be promoted against UniqueID field present in Property Schema.

Employee Schema


Employee Schema Image

Candidate Schema


Candidate Schema Image

Let’s create our Orchestration to meet our requirement. Only important thing to notice is how the correlation set is created and later used.


Creating Correlation Set Image

Later in Orchestration I have initialized Correlation while sending the Candidate information for approval and followed the same while receiving the Employee Info (Approved Candidates)


 Orchestration Image

Some interesting things:-

Created a test file with CandidateID = 1 and processed the same.


Promoted Properties of Candidate Schema Image

Subscription Filter on Correlated Receive shape:-

https://CorrelationWithoutCommonElement.PropertySchema.UniqueID == 1  And == {6D17881D-4468-4EFD-A4EB-A05327E8DAE7}  And == http://CorrelationWithoutCommonElement.Employee#Employee

Correlated Receive shape has an instance subscription i.e. an instance of Orchestration is waiting for a particular type of message.

The main motive of this sample is to demonstrate how to do property promotion if you don’t have any common element.

Hope it helps.

Download the sample application from here. Word version of this blog is here.


Contact Me:-

@Gmail, @Facebook, @LinkedIn, @MSDN Technet Profile, @My Personal Blog Site

My BizTalk Experiences