BizTalk Server 2016 and Install SQL Server Integration Services (SSIS) 2016: The specified service does not exist as an installed service

BizTalk Server 2016 and Install SQL Server Integration Services (SSIS) 2016: The specified service does not exist as an installed service

I’m back to writing! With so many talks in recent times and those who still come, and with it all the time necessary to prepare them; with so much work and new projects ongoing (thankfully); with 3 kids at home and recently married… it has been difficult to arrange a free time to concentrate on the writing. But I’m back, and for starting with a smooth topic that I like: “Errors and Warnings, Causes and Solutions” on a problem that actually I faced today while trying to connect with SQL Server Integration Services (SSIS): “The specified service does not exist as an installed service.”

Today, while I was trying to access SSIS from SQL Server 2016 Server, that host and support BizTalk Server 2016 I got the following and bizarre error:

TITLE: Connect to Server

——————————

Cannot connect to ..

——————————

ADDITIONAL INFORMATION:

Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&LinkId=20476

——————————

Connecting to the Integration Services service on the computer “localhost” failed with the following error: “The specified service does not exist as an installed service.”.

This error can occur when you try to connect to a SQL Server 2005 Integration Services service from the current version of the SQL Server tools. Instead, add folders to the service configuration file to let the local Integration Services service manage packages on the SQL Server 2005 instance.

BizTalk Server and SSIS: The specified service does not exist as an installed service

Cause

This was bizarre because again I was trying to access to SSIS directly from SQL Server machine and I was sure that I had Integration Services installed and running on the server as I was able to confirm access to the services (services.msc).

BizTalk Server and SSIS: Services

I’m not a SQL Server specialist, but after careful research into the SSIS documentation it says:

“To connect directly to an instance of the legacy Integration Services Service, you have to use the version of SQL Server Management Studio (SSMS) aligned with the version of SQL Server on which the Integration Services Service is running. For example, to connect to the legacy Integration Services Service running on an instance of SQL Server 2016, you have to use the version of SSMS released for SQL Server 2016.”

BizTalk Server and SSIS: Documentation about versions

That triggered some red lights on my head because:

  • I knew that this was a recent installation and we were using a current version of SQL Server Management Studio (v17.9.1);
  • and I also knew that for example during the BizTalk Server configuration we may face some issues configuring some features if we are using a recent version of SSMS, you should use a compatible and recommended version: SSMS 16.5.3.

Solution

So, to solve this issue, you should:

In my case, I was able to connect to SSIS without any problem from SSMS installed in BizTalk Server 2018 machine because I always installed from day one SSMS 16.5.3 on BizTalk Servers machines.

The post BizTalk Server 2016 and Install SQL Server Integration Services (SSIS) 2016: The specified service does not exist as an installed service appeared first on SANDRO PEREIRA BIZTALK BLOG.

BizTalk Bindings Exportation: How to Export BizTalk Server Resource Bindings by Assembly Name with PowerShell

BizTalk Bindings Exportation: How to Export BizTalk Server Resource Bindings by Assembly Name with PowerShell

Let’s go for the third PowerShell sample in a series of posts that, once again, I will be addressing some of the real case scenarios that we may face daily:

Today’s blog post will be about: How to Export BizTalk Server Resource Bindings by Assembly Name (instead of the FQName) with PowerShell.

This is extremely similar to the previous one, but instead of using the fully qualified name (FQName) of the assembly, we will be using only the assembly name. Nevertheless, this small change will have a significant technical impact on the way we can archive this goal.

Just for getting started, and for you to be aware, this is impossible to do out-of-the-box with the standard tools:

  • BizTalk Server Administration Console
  • Or even with BTSTask command-line tool included with BizTalk Server. This tool provides the option for you to export binding information to a .xml file by using the ExportBindings command:
    • BTSTask ExportBindings /Destination: value [/GroupLevel] [/ApplicationName:value] [/AssemblyName:value ] | [/GlobalParties] [/Server:value] [/Database:value]
      • /ApplicationName: Name of the application from which to export bindings.
      • /AssemblyName: a Locally unique identifier (LUID) of the assembly from which to export bindings.

So, if you want to do something outside the box this is were the fun and challenges really start to appear and the question that we may ask is: Is there any way that we can accomplish this and at the same time improve the experience, similar to the previous examples? The response is that yes, all of this can be fully automated using, for example, PowerShell scripts.

Like the previous samples, we could fully automate this Binding generation for each environment, but once again, let’s keep it simple and address what is mandatory and easily forgotten. With this PowerShell sample, we will be able to generate a binding file for a specific assembly which is deployed in my BizTalk Server environment.

Generate a Binding file for 3 environments DEV, QA and PRD:

  • Changing the NT Group Name for each different environment
  • Generate a Binding file for each version of the assembly name found deployed
function bts-resource-exportbindings-by-assembly-name([string]$bindingFilePath, [string]$appName, [string]$assemblyName, [boolean]$generateDiffEnvBindings)
{
    $list= BTSTask.exe ListApp /ApplicationName:$appName 

    $list |foreach {
	    if ($_ -like '*Resource:*')
        {
            if($_.Split('-')[1].Split('"')[1] -eq "System.BizTalk:BizTalkAssembly")
            {
                $varAssemblyFQName = $_.Split('-')[2].Split('"')[1]
                $verison = $_.Split('-')[2].Split('"')[1].Split("=")[1].Split(",")[0]
                if($varAssemblyFQName -like "*"+ $assemblyName + "*")
                {
                    $taskParams = ” ExportBindings /Destination:$bindingfilePath$appName.$assemblyName.$verison.BindingInfo.xml /AssemblyName:""$varAssemblyFQName"" ”
                    Start-Process "BTSTask.exe" $taskParams -Wait

                    if($generateDiffEnvBindings)
                    {
                        $xml = (Get-Content "$bindingfilePath$appName.$assemblyName.$verison.BindingInfo.xml")
    
                        # QA Binding Info Generation
                        $xml.SelectNodes("//Host") | % { 
                            $_.NtGroupName = $global:qaNTGroupName
                        }
                        $xml.Save("$bindingfilePath$appName.$assemblyName.$verison.QA.BindingInfo.xml")

                        # PRD Binding Info Generation
                        $xml.SelectNodes("//Host") | % { 
                            $_.NtGroupName = $global:prdNTGroupName
                        }
                        $xml.Save("$bindingfilePath$appName.$assemblyName.$verison.PRD.BindingInfo.xml")
                    }
                }
            }
        }
    }
}

THIS POWERSHELL IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND.

You can download the full script from here: Export BizTalk Server Resource Bindings by Assembly Name with PowerShell

The post BizTalk Bindings Exportation: How to Export BizTalk Server Resource Bindings by Assembly Name with PowerShell appeared first on BizTalk360.

Global Azure Bootcamp 2019 Lisbon | April 27, 2019 | How we are using Logic Apps (and/or Microsoft Flow): Real cases scenarios

Global Azure Bootcamp 2019 Lisbon | April 27, 2019 | How we are using Logic Apps (and/or Microsoft Flow): Real cases scenarios

I think I’ve been present since the first edition of this event, except for last year… so, I’m super excited for presenting once again on this fantastic event! In 2015 I spoke for the first time about Logic Apps:

sandro pereira global azure bootcamp lisbon 2015 Logic Apps

And later on in 2016…. And I will return this year with a mix session about Logic Apps and Microsoft Flow on a session about: “How we are using Logic Apps (and/or Microsoft Flow): Real cases scenarios.

sandro pereira global azure bootcamp lisbon 2019 Logic Apps

I have been presenting a similar talk on my last events (online events, Porto.Data, and Madrid) and this may be the last time I do it in this format.

Abstract

We know that all business problem can be solved with a variety of technologies and different solutions. However, sometimes developing that type of solutions has traditionally been too costly and time-consuming for many of the need’s teams and departments face, especially those projects that are internally for organizations to use or for a short period. As a result, many of these projects or solutions will be on the shelf or in the imaginary of the collaborators.

In this session, I will show you real live scenarios on how we at DevScope are using Microsoft Integration features like Logic Apps, API Management, API’s and Microsoft Flows. Using also a variety of related Azure technologies like PowerApps and Power BI to:

  • First, improve our internal processes like expenses reports, time reports and so on;
  • And, secondly, how the first step helps us out to extend our product and our business by exporting these same approaches and concepts to our clients

This will be a lightweight talk addressing some real scenarios and show these in action

Global Azure Bootcamp 2019 Lisbon Agenda

  • 8:30 – 09:00 – Welcome and accreditation
  • 09:00 – 09:15 – Introduction + Housekeeping by Tiago Costa and Virgilio Esteves
  • 09:15 – 09:45 – Best Practices for Real-time Data by Viviane Ribeiro
  • 09:45 – 10:15 – Azure Serverless by Virgilio Esteves
  • 10:15 – 10:30 – Coffee Break
  • 10:30 – 11:00 – ARM your Azure Infrastructure by Tiago Costa
  • 11:00 – 12:00 – Let’s talk about: Azure Monitor by Pedro Sousa
  • 12:00 – 13:00 – TBA by Luis Calado
  • 13:00 – 14:00 – Lunch Break
  • 14:00 – 15:00 – Extend your Identity to the Cloud by Nuno Árias Silva
  • 15:00 – 16:00 – Azure SQL Database Managed Instance is so much more than just a full-fledged SQL Server in the Cloud! by Niko Neugebauer
  • 16:00 – 16:15 – Coffee Break
  • 16:15 – 17:15 – How we are using Logic Apps (and/or Microsoft Flow): Real case scenarios by Sandro Pereira
  • 17:15 – 18:00 – Security? Whose problem is it, really? by Tiago Pascoal
  • 18:00 – 18:30 – Prizes and Closing

This is a free event with very limited seats that you will not want to miss, register now!

We are waiting for you.

The post Global Azure Bootcamp 2019 Lisbon | April 27, 2019 | How we are using Logic Apps (and/or Microsoft Flow): Real cases scenarios appeared first on SANDRO PEREIRA BIZTALK BLOG.

BizTalk Bindings Exportation: How to Export BizTalk Server Resource Bindings by Assembly FQ Name with PowerShell

BizTalk Bindings Exportation: How to Export BizTalk Server Resource Bindings by Assembly FQ Name with PowerShell

This is the second PowerShell sample in a series of samples that I will do on this topic addressing some of the real case scenarios that we may face daily:

Today’s blog post will be about: How to Export BizTalk Server Resource Bindings by Assembly FQ Name with PowerShell.

Exporting a BizTalk Server Application binding is, at first sight, a simple and quick task that can be done using the BizTalk Server Administration Console:

  • Click Start, click All Programs, click Microsoft BizTalk Server 20xx, and then click BizTalk Server Administration
  • In the console tree, expand BizTalk Server Administration, expand the BizTalk Group, and then expand Applications
  • Right-click the application whose assembly is associated, and you want to export the bindings, or simply right-click on the Applications, point to Export, and then click Bindings…
  • On the Export Bindings page, in Export to file, type the absolute path of the .xml file to which to export the bindings
  • Ensure that Export bindings from the select assembly is selected, and then click OK

BizTalk Bindings Exportation: How to Export BizTalk Server Resource Bindings by Assembly FQName with PowerShell

But, again, even in all simple tasks we may encounter challenges that require us to perform some monotonous and boring manual operations that consume some of our precious time and are always subject to failures.

Once again, the steps that I described above only generate the binding files from that specific environment, maybe or normally this all start in development, but we also will need to generate the same bindings for production, and for that we normally need to open the binding file and replace/fix the differences for each different environment… which is normally a tedious operation. What we need to replace is mainly:

  • The URI’s – it should be fixed but it is not mandatory you can fix them directly on the environment after you import the Binding if you know what you are doing
  • The host instances – not mandatory if you have the same host and host instances names across all your different environments as best practices will tell you to do
  • The NT Group Name associated in the Services (Orchestrations) – according to security best practices you shouldn’t use the same BizTalk Groups in different environments, so in this case, if you follow this best practice, you need mandatory to change these parameters in your binding file

Normally, everyone changes the URI’s but neglecting the other parameters may be causing problems during the Binding import.

  • So, the question is: Is there any way that we can improve this experience? And the response is that yes, all of this can be fully automated by using, for example, PowerShell scripts.

Like the previous sample, we could fully automate this Binding generation for each environment, but once again, let’s keep it simple and address what is mandatory and easily forgotten. With this PowerShell sample for a specific assembly, with a fully qualified name, deployed in my BizTalk Server environment, I can easily:

  • Generate a Binding file for 3 environments DEV, QA and PRD
  • Changing the NT Group Name for each different environment
function bts-resource-exportbindings-by-assembly-fqname([string]$bindingFilePath, [string]$appName, [string]$assemblyFQName, [boolean]$generateDiffEnvBindings) 
{ 
    $dllName = $assemblyFQName.Substring(0, $assemblyFQName.IndexOf(',')) 
    $taskParams = ” ExportBindings /Destination:$bindingfilePath$appName.$dllName.BindingInfo.xml /AssemblyName:""$assemblyFQName"" ” 
    Start-Process "BTSTask.exe" $taskParams -Wait 
 
    if($generateDiffEnvBindings) 
    { 
        $xml = (Get-Content "$bindingfilePath$appName.$dllName.BindingInfo.xml") 
     
        # QA Binding Info Generation 
        $xml.SelectNodes("//Host") | % {  
            $_.NtGroupName = $global:qaNTGroupName 
        } 
        $xml.Save("$bindingfilePath$appName.$dllName.QA.BindingInfo.xml") 
 
        # PRD Binding Info Generation 
        $xml.SelectNodes("//Host") | % {  
            $_.NtGroupName = $global:prdNTGroupName 
        } 
        $xml.Save("$bindingfilePath$appName.$dllName.PRD.BindingInfo.xml") 
    } 
}

THIS POWERSHELL IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND.

You can download the full script from here: Export BizTalk Server Resource Bindings by Assembly FQName with PowerShell

The post BizTalk Bindings Exportation: How to Export BizTalk Server Resource Bindings by Assembly FQ Name with PowerShell appeared first on BizTalk360.

BizTalk Bindings Exportation: How to Export BizTalk Server Application Bindings with PowerShell

BizTalk Bindings Exportation: How to Export BizTalk Server Application Bindings with PowerShell

This will be the first blog post in a series of articles that I will do on this topic addressing some of the real case scenarios that we may face daily:

  • How can we easily export a binding file from a BizTalk Application?
  • How can we easily export a binding file from a specific assembly?
  • How can we easily export a binding file from a list of assemblies?
  • How can we easily export a binding file from a Receive Port?
  • How can we easily export a binding file from a Send Port?
  • And many more

The today blog post will be about: How can we easily export a binding file from a BizTalk Application?

Exporting a BizTalk Server Application binding is, at first sight, a simple and quick task that can be done using the BizTalk Server Administration Console:

  • Click Start, click All Programs, click Microsoft BizTalk Server 20xx, and then click BizTalk Server Administration
  • In the console tree, expand BizTalk Server Administration, expand the BizTalk Group, and then expand Applications
  • Right-click the application whose bindings you want to export, point to Export, and then click Bindings…
  • On the Export Bindings page, in Export to file, type the absolute path of the .xml file to which to export the bindings
  • Ensure that Export all bindings from the current application is selected, and then click OK

But even in simple tasks, we may encounter challenges that require us to perform some monotonous and boring manual operations that consume some of our precious time and are always subject to failures.

The steps that I described above only generate the binding files from that specific environment, maybe or normally this all start in development, but we also will need to generate the same bindings for production and for that we normally need to open the binding file and replace/fix the differences for each different environment… which is normally a tedious operation. What we need to replace is mainly:

  • the URI’s – it should be fixed, but it is not mandatory. If you know what you are doing, you can fix them directly on the environment after you import the Binding
  • the host instances – not mandatory, if you have the same host and host instances names across all your different environments (as best practices will tell you to do)
  • the NT Group Name associated in the Services (Orchestrations) – according to securities best practices you shouldn’t use the same BizTalk Groups in different environments, so in this case, if you follow this best practices, you need to change these parameters in your binding file

Normally, everyone changes the URI’s but neglecting the other parameters may be causing problems during the Binding import.

So, the question is: Is there any way that we can do to improve this experience? And the response is that yes, all of this can be fully automated by using, for example, PowerShell scripts.

Again, I could fully automate this Binding generation for each environment, but let’s keep it simple and address what is mandatory and easily forgotten. In this sample let’s see how I can easily:

  • Generate a Binding file for 3 environments DEV, QA and PRD:
  • Changing the NT Group Name for each different environment;
function bts-application-exportbindings([string]$bindingFilePath, [string]$appName, [boolean]$generateDiffEnvBindings)
{
    $taskParams = ” ExportBindings /Destination:$bindingfilePath$appName.BindingInfo.xml /ApplicationName:$appName ”
    #First version: $p = [diagnostics.process]::start(“BTSTask.exe”, $taskParams)
    Start-Process "BTSTask.exe" $taskParams -Wait

    if($generateDiffEnvBindings)
    {
        $xml = (Get-Content "$bindingfilePath$appName.BindingInfo.xml")
    
        # QA Binding Info Generation
        $xml.SelectNodes("//Host") | % { 
            $_.NtGroupName = $global:qaNTGroupName
        }
        $xml.Save("$bindingfilePath$appName.QA.BindingInfo.xml")

        # PRD Binding Info Generation
        $xml.SelectNodes("//Host") | % { 
            $_.NtGroupName = $global:prdNTGroupName
        }
        $xml.Save("$bindingfilePath$appName.PRD.BindingInfo.xml")
    }
}

bts-application-exportbindings 'C:tempBTS' 'BizTalk Application 1' $True

THIS POWERSHELL IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND.

You can download the full script from here: Export BizTalk Server Application Bindings with PowerShell

The post BizTalk Bindings Exportation: How to Export BizTalk Server Application Bindings with PowerShell appeared first on BizTalk360.

MVPDays Microsoft Flow Conference 2018 | How we use Microsoft Flow and PowerApps: Real cases scenarios | Video and slides are available

MVPDays Microsoft Flow Conference 2018 | How we use Microsoft Flow and PowerApps: Real cases scenarios | Video and slides are available

To finalize these sessions resources shared, at least for now because I’m still waiting for other resources to get available. Here is one that I forgot even to mention in my blog that I was speaking at that event: the MVPDays Microsoft Flow Conference 2018 that toked place online on December,12 of last year (http://www.mvpdays.com/?page_id=11493). This was my first session about real case scenarios using PowerApps and Microsoft Flow.

About my session

Session Name: How we use Microsoft Flow and PowerApps: Real cases scenarios

01-Microsoft-Flow-PowerApps-Real-cases-scenarios

Session Overview: We know that all business problem can be solved with a variety of technologies and different solutions. However, sometimes developing that type of solutions has traditionally been too costly and time-consuming for many of the need’s teams and departments face, especially those projects that are internally for organizations to use or for a short time period. As a result, many of these projects or solutions will be on the shelf or in the imaginary of the collaborators.

They are in Dynamics 365, Office 365, on premises, on the cloud… they are everywhere, and they are fantastic! Developers can do it; IT can do it… you can do it!

Microsoft Flow and PowerApps, sometimes together sometimes isolated are here to help you, and in this session, we will show you real live scenarios on how we use these two technologies in our customers and internally at DevScope.

  Microsoft Flow and PowerApps: Real cases scenariosMicrosoft Flow and PowerApps: Real cases scenarios

  Microsoft Flow and PowerApps: Real cases scenariosMicrosoft Flow and PowerApps: Real cases scenarios

Slides and Video

MVPDays Microsoft Flow Conference 2018 | How we use Microsoft Flow and PowerApps: Real cases scenarios

The post MVPDays Microsoft Flow Conference 2018 | How we use Microsoft Flow and PowerApps: Real cases scenarios | Video and slides are available appeared first on SANDRO PEREIRA BIZTALK BLOG.

Integration Use Group | The NoS-addin – your (free) BizTalk Dev buddy! | Video and slides are available

Integration Use Group | The NoS-addin – your (free) BizTalk Dev buddy! | Video and slides are available

Another day, another resource shared! This time regarding my session deliver on Integration User Group or also known as Integration Monday about BizTalk Server NoS add-in – BizTalk NoS Ultimate – that is a Visual Studio add-in for BizTalk developers that aims to improve the experience while developing BizTalk projects. It is an extension to Microsoft Visual Studio that will offer lots of useful functionalities, mainly for developers, by which BizTalk users can save valuable time while working on their day-to-day activities and improve productivity.

About my session

Session Name: The NOS-addin – your (free) BizTalk Dev buddy!

BizTalk Server NoS Ultimate add-in BizTalk Dev Buddy

Session Overview: The NOS-add-in is a tool specifically developed for BizTalk developers. It contains all kind of features to make the life of a BizTalk developer easier and thereby less time-consuming.

In this session, I will show the different capabilities of this tool.

BizTalk Server NoS Ultimate add-in BizTalk Dev Buddy

About Integration User Group

Integration User Group aims to educate, evangelize, inform the community about various integration technologies, and how developers and architects can share and learn about the evolving integration and messaging capabilities of the Microsoft platform.

Website: http://www.integrationusergroup.com/

The post Integration Use Group | The NoS-addin – your (free) BizTalk Dev buddy! | Video and slides are available appeared first on SANDRO PEREIRA BIZTALK BLOG.

Integration Down Under | How we are using Microsoft Integration features and related Azure technologies to improve our processes | Video and slides are available

Integration Down Under | How we are using Microsoft Integration features and related Azure technologies to improve our processes | Video and slides are available

I may be writing less on my blog as I frequently do, this will change soon, but this year of this is being very productive in terms of lectures. 4 in 4 months and more to come:

  • 3/30/2019 – Real case implementations using Azure Logic Apps and/or Microsoft Flows at Global Integration Bootcamp Madrid
  • 2/14/2019 – Integration Down Under | February 14, 2019 | How we are using Microsoft Integration features and related Azure technologies to improve our processes
  • 2/4/2019 – The NOS-addin – your (free) BizTalk Dev buddy! at Integration Monday
  • 1/30/2019 – XLVIII Porto.Data Community Meeting | How we use Microsoft Flow and PowerApps: Real cases scenarios

Now is time to share some resources before I start writing about other things and completely forget about this.

About my session

Session Name: How we are using Microsoft Integration features and related Azure technologies to improve our processes

Microsoft Integration features Session

Session Overview: In this session, I will show you real live scenarios on how we at DevScope are using Microsoft Integration features (Logic Apps, API Management, API’s) and related Azure technologies like PowerApps, Flows and Power BI to:

  • First, improve our internal processes like expenses reports, time reports and so on;
  • And, secondly, how the first step helps us out to extend our product and our business by exporting these same approaches and concepts to our clients
Microsoft Logic Apps and SmartDocumentor-Expenses

This will be a lightweight talk addressing some real scenarios and show them in action.

Integration Down Under – How we are using Microsoft Integration features and related Azure technologies to improve our processes

About Integration Down Under

Integration Down Under serves the Australian / New Zealand community interested in all things Microsoft integration. Endeavoring to have regular webinar presentations, usually on the 2nd Thursday of each month. Organized by a panel of five Australian and New Zealand integration experts, our guest speakers feature various Azure MVPs, members of the Microsoft product teams, and other prominent members of the Microsoft integration community.

Website: http://www.integrationdownunder.com/

Twitter: https://twitter.com/integration_du

YouTube channel: https://www.youtube.com/channel/UC5N-7y5XDeX0IY9mkssqRZQ

The post Integration Down Under | How we are using Microsoft Integration features and related Azure technologies to improve our processes | Video and slides are available appeared first on SANDRO PEREIRA BIZTALK BLOG.

Global Integration Bootcamp 2019 Madrid | May 30, 2019 | Real case implementations using Azure Logic Apps and/or Microsoft Flows

Global Integration Bootcamp 2019 Madrid | May 30, 2019 | Real case implementations using Azure Logic Apps and/or Microsoft Flows

I’m super excited for presenting from the first time in Spain, I been presented in several places all over Europe and North America, but I never had a chance to go to my neighbor country to present a session. I think two years ago I promise to the organizers of this event that I would join them if they want, last year was impossible for me because my son was born more or less in the same period, but this year I’ll fulfill the promise I made and I will be there showing real case scenarios about Logic Apps and Microsoft Flow on a talk with the following title: “Real case implementations using Azure Logic Apps and/or Microsoft Flows

Global Integration Bootcamp 2019 Madrid | May 30, 2019 | Real case implementations using Azure Logic Apps and/or Microsoft Flows

Abstract

We know that all business problem can be solved with a variety of technologies and different solutions. However, sometimes developing that type of solutions has traditionally been too costly and time-consuming for many of the need’s teams and departments face, especially those projects that are internally for organizations to use or for a short time period. As a result, many of these projects or solutions will be on the shelf or in the imaginary of the collaborators.

In this session, I will show you real live scenarios on how we at DevScope are using Microsoft Integration features like Logic Apps, API Management, API’s and Microsoft Flows. Using also a variety of related Azure technologies like PowerApps and Power BI to:

  • First, improve our internal processes like expenses reports, time reports and so on;
  • And, secondly, how the first step helps us out to extend our product and our business by exporting these same approaches and concepts to our clients

This will be a lightweight talk addressing some real scenarios and show these in action

Global Integration Bootcamp 2019 Madrid Agenda

  • 8:45 – 09:00 – Welcome reception
  • 09:00 – 09:30 – “Industry 4.0: Remote and Predictive Maintenance with IoT” by Félix Mondelo and Osman Hawari
  • 09:30 – 10:15 – “Azure API Management y su aplicación práctica” by Luis Ruiz Pavón
  • 10:15 – 11:00 – “Event Grid, Colega, ¿Qué pasa en mi nube?” by Nacho Fanjul
  • 11:00 – 11:45 – Coffee Break
  • 11:45 – 12:00 – “Geoposicionando tus datos con Azure Maps y Cognitive service” by Sergio Hernández y Alberto Díaz
  • 12:00 – 12:45 – “Real case implementations using Azure Logic Apps and/or Microsoft Flows” by Sandro Pereira
  • 12:45 – 13:30 – “TU y Cognitive Services” by Javier Menéndez Pallo
  • 13:30 – 14:15 – “Intercambiando Mensajes con NServiceBus” by José Luque Ballesteros
  • 14:15 – 15:00 – “Arquitecturas basadas en Microservicios” by Francisco Nieto

This is a free event with very limited seats that you will not want to miss, register now!

We are waiting for you.

The post Global Integration Bootcamp 2019 Madrid | May 30, 2019 | Real case implementations using Azure Logic Apps and/or Microsoft Flows appeared first on SANDRO PEREIRA BIZTALK BLOG.

BizTalk Server WCF-* Adapter: Please verify that the receive location exists, and that the isolated adapter runs under an account that has access to the BizTalk databases.

BizTalk Server WCF-* Adapter: Please verify that the receive location exists, and that the isolated adapter runs under an account that has access to the BizTalk databases.

I think in the past I told that do not try to configure anything in BizTalk Server if you are tired. My advice, go to sleep for one hour and come back… unless the client is eager and demands or request things to be done… then the error happens. This was one of these errors in which I usually say that the problem was between the chair and the keyboard. This week I returned to work, after my little honeymoon leave, that I spent part of it working and another part of it with my little kid a little sick (I need to compensate my wife with a proper vacation for being so understanding). So, as you can imagine I return a little tired and the first day was one of those days that I had several clients requiring my presence for several small things at the same time.

One of them was configuring correctly, according to best practices and security the IIS application pools that were being used to run Web Sites with some orchestrations exposed as Web Services that initial was running with BizTalk Server Administration account.

Once I finished configuring the applications pools, I started receiving the following error:

The Messaging Engine failed to register the adapter for “WCF-WebHttp” for the receive location “/ModifyOperationStatus/ModifyOperationStatus.svc”. Please verify that the receive location exists, and that the isolated adapter runs under an account that has access to the BizTalk databases~

BizTalk Server WCF-* Adapter: Please verify that the receive location exists, and that the isolated adapter runs under an account that has access to the BizTalk databases.

Cause

Usually, this can happen for two reasons:

  • There isn’t a receive location created and enabled listening to this web service;
  • Or this is a permission issue! And is typically related by the fact that the account or service account specified on the application pool that the web service is running is not… a member of the BizTalk Isolated Host Users group.

In my case, and because the names of the service accounts were very identical, I improperly configured the application pool to run with the service account that was a member of the BizTalk Host Users group (btsapphostsrv) instead of the service account member of the BizTalk Isolated Host Users group (btsiapphostsrv).

Solution

To solve this issue, you first should check and double-check if the IIS Application Pool Identities are correctly configured.

If yes, guarantee that the user or service account is part of the BizTalk Isolated Host Users group. If not:

  • Make sure you add that user or service account into the BizTalk Isolated Host Users group.
  • Or change the IIS Application Pool Identity for an account that is already a member of the BizTalk Isolated Host Users Group.

And then make sure that there is a receive location configured and to listen to this web service and if it is enabled.

 

In my case, changing to the BizTalk Isolated Host Instance Account that is, of course, a member of BizTalk Isolated Host Users group solved my issue.

The post BizTalk Server WCF-* Adapter: Please verify that the receive location exists, and that the isolated adapter runs under an account that has access to the BizTalk databases. appeared first on SANDRO PEREIRA BIZTALK BLOG.