Nebular Blog

Some great bloke out there just made my day way better :

http://gacbrowser.blogspot.com/

Accurate, searchable etc. whats not to love

.Net, BizTalk Server, Tools Tools

Hi,

Just found this great link regarding know "issues" in the BizTalk 2010 console (funny, i would call them errors )

http://social.technet.microsoft.com/wiki/contents/articles/common-issues-and-resolutions-with-the-biztalk-server-administration-console.aspx

BizTalk Server

Error when receiving Rosettanet http request errors : "Retrieving the COM class factory for component with CLSID {254B4004-2AA7-4C82-BB2E-18BA7F22DCD2} failed due to the following error: 80040154."

From the pipeline error message we get something like this:

The main issue, is that a 32bit com component is beeing loaded into a 64 bit process.

On the BizTalk enviroment, we investigated the isolated host adapter (since this is the ONLY one able to receive http request). And here is the funny fact. it ALWAYS runs 32bit mode. ! So how could the pipeline "not run under 32 bit" ?

Well somethings rotten in the state of BizTalk !

The Root Cause is in the application pool of the webhosted BTSHTTPReceive.dll must have the "Enable 32-Bit applications" set to true

BizTalk Server, Rosettanet BizTalk Rosettanet

HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because 
the related configuration data for the page is invalid.

Dont you just hate it.. you ran everything by the book and it still doesn't work.. well you dont have to do much BizTalk before this is business as usual ;) 

Anyway, in this combination hosting Bam on SharePoint 2010 Foundation, the SharePoint BAM portal is running .net 4.0 

And the error happens because the BAM site is inheriting handlers, that are also installed in your BAM web.config. Hence the Duplicate message.

One solution is to manually outcomment the specific handlers:

And you will be back in business. 

Best guess, is that the Biztalk 2010 release team didnt get to re-test installation and configuration with the latest releases of SharePointFoundation. Hence the BAM installation includes the above handlers.

BizTalk Server BizTalk Server, BAM

Finally, the cat is out of the bag.

Next release of BizTalk server, is just the usual platform upgrade with some minor additions.

Details : http://blogs.msdn.com/b/biztalk_server_team_blog/archive/2011/12/08/biztalk-server-2010-r2.aspx

BizTalk Server BizTalk Server

We are using the Powershell BizTalk Adapter when deploying our BizTalk solution.

And since we depend on a lot of external services and expose som WCF-services as well, we might as well do a quick test to see if the respond properly. Even a simple check to see if the URL responds with HTTP 200-OK will catch a lot of configuration and setup related errors.

The following script will iterate through all WCF receive and send port and try a simpe HTTP get. Perfect as the last step of any BizTalk deployment :-)

function GetStatusCodeFromURL
{
    param([string]$serviceName,[string]$url)

    try
    {
        Write-Host "$serviceName => " -NoNewline
       
        $req=[system.Net.HttpWebRequest]::Create($url);
        $res = $req.getresponse();
        $stat = $res.statuscode;
        $res.Close();
               
        if ($stat -eq "OK")
        {
            Write-Host "$stat" -ForegroundColor:Green
        }
        else
        {
            Write-Host "$stat" -ForegroundColor:Red
        }
       
    }
    catch [System.Exception]
    {
        $exceptionMessage = $url + ": " + $_.Exception.Message
        Write-Host $exceptionMessage -ForegroundColor:Red       
    }
   
}

Write-Host "Testing HTTP send- and receiveports" -ForegroundColor:Green

## All receive locations
foreach ($bizApplication in Get-ChildItem "BizTalk:\Applications" | Where-Object {$_.Status -ne "NotApplicable"})
{
    $bizApplicationName = $bizApplication.Name

    foreach ($bizReceiveLocation in Get-ChildItem "BizTalk:\Applications\$bizApplicationName\Receive Locations" | Where-Object {$_.Address.EndsWith(".svc")})
    {
        $desc = $bizApplicationName + ": " + $bizReceiveLocation.Name
        GetStatusCodeFromURL $desc "http://localhost" + $bizReceiveLocation.Address
    }

    foreach ($bizSendPort in Get-ChildItem "BizTalk:\Applications\$bizApplicationName\Send Ports" | Where-Object {$_.IsTwoWay -eq $true})
    {
        $desc = $bizApplicationName + ": " + $bizSendPort.Name
        GetStatusCodeFromURL $desc $bizSendPort.PrimaryTransportAddress
    }
   
}

BizTalk Server, Sharepoint Server

Sandro created a nice and neat list of BizTalk updates.

http://sandroaspbiztalkblog.wordpress.com/2011/11/22/biztalk-server-list-of-service-packs-and-cumulative-updates-available/

Thx Sandro ;)

BizTalk Server BizTalk

While testing settings in a development enviroment, i needed a simple way to reflect and discover shared runtime ressources, with powershell of cause!

[System.Reflection.Assembly]::LoadWithPartialName(“Microsoft.Solutions.BTARN.Shared”)

$runtimeValue = [Microsoft.Solutions.BTARN.Shared.RuntimeGlobal]::DataDbConnectionString

Write-Host $runtimeValue

easy  ;)

Sharepoint Server PowerShell

Recently (with more and more development enviroments beeing virtualized) I have experienced a tendency to share the underlying servers on a SQL server cluster. In a shared instans.

This does work in some basic BizTalk scenarios. But I have recenltlyy experienced an issue where the unique name on BAM dts packagesand the underlying deployment could not be shared. Similar to this issue : http://social.msdn.microsoft.com/forums/en-US/biztalkediandas2/thread/0e5b3380-601c-44cb-b599-91b699d557b4. This might only be an issue for EDI solutions, but we expect to see it with the rosettanet adapter too. 

So as a general reminder of development better practice : ISOLATE DEVELOPMENT. Even when the operations guys(or girls) are trying to make there life easier with more shared ressources.

BizTalk Server BizTalk Server

Tyring to install sharepoint services 3.0 for a BizTalk 2009 BAM feature, I ran into an error regarding IIS running in 32 bit emulation mode. To change this use the following command:

CScript "%SystemDrive%\InetPub\AdminScripts\adsutil.vbs" set w3svc/AppPools/Enable32bitAppOnWin64 0

And perform an iisreset.

BizTalk Server, Sharepoint Server