Get-AzurePublishSettingsFile : Could not find publish settings. Please run Import-AzurePublishSet...
I was trying to Install a new Active Directory forest in Windows Azure and got this error at step 1 part 6 when I tried to run Get-AzurePublishSettingsFile
Upgrading ESB 2.1 to ESB 2.2 – Exception Management Portal Alerting Service
This is a continuation from two other blog posts about upgrading from BizTalk 2010 to BizTalk 2013 Mike who I mentioned previously has given the following tip
Upgrading to BizTalk 2013–Could not load file or assembly "’Microsoft.BizTalk.In...
Our BizTalk team have been trying to complete a in place upgrade from BizTalk 2010 to BizTalk 2013 The first part of this story can be found here We completed
Upgrading to BizTalk 2013 with ESB Toolkit 2.1 and ESB Exception Management Portal in situ
BizTalk 2013 supports an in place upgrade from BizTalk 2010 and we planned to do this on one of the BizTalk 2010 Servers that we support We had used the ESB
Windows Updates for BizTalk 2013
Here is the first windows update for BizTalk I have ever seen I wonder if the updates for HIS 2013 will now come the same
EDIFACT messages that are missing a UNA segment
Shikhar came to me because he could not process an EDIFACT message like this using the out of the box BizTalk 2010
SSIS Error: Element “1” does not exist in collection "SelectedLogProviders"
Recently we tried to make a simple change to a SSIS package and got stuck with this error After must angst we tracked the problem to the way that the SQL
BizTalk and Rest Example from BizTalk Saturday
This is one of my demonstrations from BizTalk Saturday at Auckland on 9/02/2013 This event was organised by Bill Chestnut and Nikolai Blackie I was asked if
BizTalk 2013 and ReST
I am presenting a session on BizTalk 2013 and Rest at BizTalk Saturday - BizTalk 2013 Hands on Days – Auckland on February 9th I was all set to write a
BAM Portal – Service Unavailable 503 Error
We got caught with this error recently when built a new BizTalk server Every time we tried to browse to the web portal we got a 503 error and the application