Blogging BizTalk

Lets Discuss BizTalk

Category Archives: Quick Finds

Installing BizTalk Server 2013 R2 and ESB Toolkit


So I recently started getting my hands on BizTalk 2013 R2 version. We are running BizTalk 2013/ 2009 so far. I am sharing some of my personal experiences while installing and configuring the BizTalk 2013 R2 version.

The one go to stop for setting up BizTalk 2013 R2 is following Sandro Pereira’s blog, it isa  series of posts and believe me you are not going to need anything else, a big thanks to him for publishing those, made my life lot easier:
https://sandroaspbiztalkblog.wordpress.com/2015/01/16/biztalk-server-2013-r2-installation-and-configuration-installing-biztalk-adapter-pack-part-12/

Note: If you do not have the proper machine/OS  to set BizTalk  you may want to look at the MS Azure to set up your own BizTalk server machine in no time. Please see this post: https://psrathoud.wordpress.com/2014/12/09/microsoft-azure-creating-your-own-biztalk-sandbox-virtual-machine/

Having said that I bumped into some diffiernt errors while installing and just making a note for all of us at BizTalk community. Please add in if you feel I am missing something here.

1>If you install VS 2012 by mistake that will result in no BizTalk sdk in VS 2012. Hence for BizTalk 2013 R2 you will have to only use VS 2013.

2>BizTalk 2013 solutions can be opened on both VS 2012 and VS 2013.

3>After you are done with installing BizTalk server and before installing Adapter pack you are going to find number of windows update, please make sure you have all of them completed before hitting the install button for Adapter pack.

4>While adding adapter to BizTalk you may bump into this error.
Check that SSO is configured and that the SSO service is running on that server. (RPC: 0x800706D9: There are no more endpoints available from the endpoint mapper
Solution: Go to windows services: Check Enterprise Single Sign On Service is runing or not if not start ist/Do the same with Remote Procedure Call (RPC).

Related post:
https://psrathoud.wordpress.com/2014/10/23/esbbiztalk-error-check-that-sso-is-configured-and-that-the-sso-service-is-running-on-that-server-rpc-0x800706d9-there-are-no-more-endpoints-available-from-the-endpoint-mapper/

5>Another error you may bump into can be
There was an error when trying to connect. Do you want to retype your credentials and try again?
For resolution please go this this post:

https://psrathoud.wordpress.com/2015/02/20/error-there-was-an-error-when-trying-to-connect-do-you-want-to-retype-your-credentials-and-try-again/

6>Another error I bumped into while configuring the BizTalk ESB tool is.
Network path could not be found.
For resolution of this error please go to following post:

https://psrathoud.wordpress.com/2015/02/23/biztalk-2013-r2-installation-esb-tool-kit-installation-error-the-network-path-was-not-found/

Advertisements

Error : There was an error when trying to connect. Do you want to retype your credentials and try again?


You may bump into this error while configuration UDDI service post installing and configuring BizTalk 2013 R2. Also this error will pop up during adapter pack installation. This error will also result in loosing your IIS settings .
—————————
Failed to connect
—————————
There was an error when trying to connect. Do you want to retype your credentials and try again?
Details:
Filename: C:\Windows\system32\inetsrv\config\schema\Microsoft.Adapters.SAP_schema.xml
Line number: 1
Error: Configuration file is not well-formed XML
—————————
Yes No
—————————
IIS error

Most likely is a installation glitch. The error is self explanatory in this case. Please go ahead and check the path “C:\Windows\system32\inetsrv\config\schema\” and notices the xml file sixe was 0 KB.

SAPSchemaMissing

Next open the BizTalk installation ISO file and look for the xml in the following location:
F:\BizTalk Server\AdapterPack_x64\Program Files\Microsoft BizTalk Adapter Pack(x64)\IIS Schemas
Copy over this file to the missing one.

Next type IISRESET in the search box of Windows server 2013 R2 and complete your IIS reset. Go ahead and retry configuring UDDI and installing BizTalk adapter pack and it should be successful.

IISReset

BizTalk 2013 R2 Installation: ESB Tool Kit Installation Error: The network path was not found


While installing the BizTalk 2013 R2 ESB toolkit bumped into the error :
The network path could not be found.

NwPath error

This error should have a corresponding entry in ESB tool kit log. You can find that at the following location ( presuming you are using the default installation path).
C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit\Bin

You will be able to see the error towards the end of the log. The reason for this error is in the user account being used for configuring the ESB tool kit. The id has to be part of the Administrators. Also if you are using a network domain ID you might see this error. In that case you need to go to the ESB configuration file.

C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit\Bin\EsbConfigurationTool.exe.Config

Here you will have to modify the various BizTalk groups to the domain groups that you would like to use.
For example:

Change To:

Once done close and reload the ESB configuration tool one more time and reapply the configuration.

ESB/BizTalk Installation Error: Check that SSO is configured and that the SSO service is running on that server. (RPC: 0x800706D9: There are no more endpoints available from the endpoint mapper


You can get this error under while configuring BizTalk server or ESB.SSOError

To fix this error we need to go to the windows service

Solution: Go to windows services: Check Enterprise Single Sign On Service is running or not if not start it. Please do the same with Remote Procedure Call (RPC).

SSOStop

The Messaging Engine failed to register the adapter for “WCF-BasicHttp” for the receive location


After publishing a BizTalk artifact, while browsing the service you bumped into this error:
The Messaging Engine failed to register the adapter for “WCF-BasicHttp” for the receive location

Error

Solution:

Go to the app pool under which the BizTalk service is configured in IIS and check for the Identity, the id used there should be a part of BizTalk admin group.Once that is set(And it is running under the isolated host) the issue should be gone.

AppPoolSetting

Please leave me a comment in case you have any questions.

BizTalk Error “A Correlation Set Can Be initialized Only Once” : An alternative solution


So you bumped into this error while compiling your BizTalk project. The most obvious reason could be : You have a correlation set set initialized on more than one places by mistake.

Now here is the tricky part: What if you have initialized it only once but still you are getting this error. What could be wrong.

Here are the possible reason:
You are using a long running transaction loop (For example in the resume pattern : https://psrathoud.wordpress.com/2014/02/01/understanding-resume-pattern-in-biztalk/) and have initialized this correlation set in there ONCE :-). You see, even thou it is initialized once at run time it may be called more than one time, thus explaining the error.

Solution:
You need to define your correlation set in a non long running scope contained within your long running scope and that will fix the problem for you.

Let me know if you have questions.

Thanks
Pushpendra

Error: Cannot perform encryption or decryption because the secret is not available from the master secret server. See the event log for related errors.


So, BizTalk is stalled, processing  nothing and we see this error:

The Messaging Engine failed to retrieve the configuration from the database. Details:”c0002a1f”.

If you look up the events it will have more audit entries, one may read following.

Cannot perform encryption or decryption because the secret is not available from the master secret server. See the event log for related errors.

This message tells there is something wrong with the ESSO .

Based on that first we shall go and check for the ESSO service to see if it is in started state.

Note: You may need to see where your ESSO service is configured. In real world scenario the BizTalk msgBox DB is hosted on a separate SQL server and that’s where your ESSO may be configured.

Now suppose if you are unsure of your ESSO server name here is what you should do: On the BizTalk server box  go to services and restart the Enterprise Single Sign On Service. This will not fix the problem for you but will give the name of your ESSO server. There will be an event log entry created with the details.

FindSSO Server

Now once we have identified the SSO server name please check if the SSO service is running. If that looks OK you will be required to restore the SSO.

Go To SSO Adminnistration -> System -> Restore Secret and select the secret file.

It will be available on following location in ESSO server C:\Program Files\Common Files\Enterprise Single Sign-On”.

Select the .bak file and provide the password.

restore

This should possibly resolve the issue.

Error : The following items could not be matched up to hosts due to name and/or trust level mismatches


While trying to import the bindings you bumped into following error:

The following items could not be matched up to hosts due to name and/or trust level mismatches:
TITLE: Import Bindings
——————————
Failed to update binding information. (mscorlib)
——————————
ADDITIONAL INFORMATION:
Cannot update send port “***************************”. (Microsoft.BizTalk.Deployment)
——————————
Cannot update transport information (address “**********”). (Microsoft.BizTalk.Deployment)
——————————
he following items could not be matched up to hosts due to name and/or trust level mismatches: 
Item: ‘FILE’ Host: ‘YourHostName’ Trust level: ‘Untrusted’
You must do one of the following:
1) Create hosts with these names and trust levels and try again
2) Re-export the MSI without the binding files and have a post import script apply a suitable binding file. (Microsoft.BizTalk.Deployment)
There could be two reasons behind this.
1>Check for the name of host. Make sure the spelling matches with what has been provided in the binding file. If there is a mismatch then either change the name in your binding file or correct it on you host name.
2>Check for the receive and send handlers on the adapter settings.Check  on the binding file and see what handler is being used there, once identified go to the adapter settings and look if the handler is created.
 For example
This is the part of the binding file script
<SendHandler Name=”YourAdapterHost” HostTrusted=”false”>
          <TransportType Name=”FILE” Capabilities=”11″ ConfigurationClsid=”” />
  </SendHandler>
This line indicates that in the file adapter we should have a send handler created under the YourAdapterHost. Verify it by going to the adapters on admin console and if the handler is not present we need to create it. See the image below.
AddHandler
 Please leave me a comment if you have any questions

SDK Error: Build Failed.Compiler of the file type ‘*.xsd’ failed


So you got this error:
Build Failed.Compiler of the file type ‘*.xsd’ failed

or your BT project fails to be created in BizTalk and you see the following errors

Error in Template (c:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\ItemTemplates\VisualBasic\Workflow\1033\StateMachineWorkflowCodeSeparation.zip), file (StateMachineWorkflowCodeSeparation.vstemplate).  Unregistered ProjectType (VisualBasic).  This can be caused by an incorrect ProjectType or because the project type package is not installed.

One or more templates do not match any installed project packages.

SDK

This indicates the SDK of your BizTalk installation has corrupted, possibly while applying some patch. This can be corrected by repairing it from Add Remove Programs>>Selecting BizTalk Installation and repairing it.

SDK1

D Goins Insperience

Technological outformation for this day and age

[INACTIVE BLOG] Connected Thoughts - Thiago Almeida

Connected systems and the occasional picture

Uri Katsir's Blog

BizTalk , BizTalk RFID and .NET

prashantbiztalkblogs

My BizTalk Experiences

BizTalk Server Tutorial

BizTalk Server Concepts and Common Errors

Extremely Talented Monkeys

A Technical Blog by Ed Jones: Azure, .NET, BizTalk, WCF, and SQL Server

On All Things Web

Discussing web development without limits

Vikas Bhardwaj's Blog

Articles about BizTalk Server and .NET C#

Cloud develop

a blog about (cloud) development... because I'm a nerd

Hooking Stuffs Together

My learning logs from day to day work experience about Integration platform using Microsoft technologies.

Connected Pawns

Mainly BizTalk & Little Chess

jhelatissimo

a blogger in the process.

MS Innovations Blog

Tips, Tricks, and Workarounds for BizTalk and other Microsoft technologies

srirambiztalks

Katradhu Kaialavu,Kalladhadhu Ulagalavu!

Vijay Microsoft Technical

BizTalk, WCF, ESB ToolKit, Windows Azure

Mind Over Messaging

Musings on BizTalk, Azure, WCF, and Enterprise Integration