Configuring BizTalk 2006 R2 on cluster

Then you try to configure BizTalk 2006 R2 in cluster environment, you can get error similar to:

The SQL Server 'SERVERNAME' cannot be used with the SSO Administrator account 'SSO Administrators'. Local accounts cannot be used with clustered SQL Servers. (SSO)

To fix this (which worked for me) add you domain to user groups like "DOMAIN\SSO Administrators" and "DOMAIN\SSO Affiliate Administrators". Of course you also must use domain user which belongs to both this groups. And here comes nasty trick, you need to deselect and select again "Enable Enterprise Single Sign-On on this computer" checkbox, only then error goes away.

Holographic code

Wow, this is great article. I've worked with such code, but always wasn't sure how to call it.

PowerShell: script permissions

If you try to run a PowerShell script you can get something like Script.ps1 cannot be loaded because the execution of scripts is disabled on this system. Yet after running:

Set-ExecutionPolicy Unrestricted

you still get the same message! Then I bet you are running x64 system. That's because there is two versions of PowerShell on the x64 systems, both x64 and x86. And both must be set to desired execution policy to achive desired effect.

SharePoint: Service unavailable

If you receive "Service unavailable" then you try to open SharePoint 2007 Central Administration then it means your application pool for it (usually "SharePoint Central Administration v3") is stopped. But if you start it and it stops again, as you try to open administration page, then it means that you farm credentials are corrupted. This worked for me as a fix:

stsadm -o updatefarmcredentials -userlogin DOMAIN\login -password password

then run:

iisreset /noforce

and have a nice day.

How to force full backup for BizTalk backup job

Sometimes you need to force a full backup of BizTalk backup job. For example, then you reconfigure BizTalk, you can receive an error on some of the BizTalk jobs saying something about that backup is not possible without full backup. To trigger full backup on next job run you need to execute BizTalkMgmtDb.dbo.sp_ForceFullBackup stored procedure. More details can be found here.

Yet another BizTalk error

Your BizTalk installation worked like a charm, but suddenly you receive errors like this?

There was a failure executing the receive pipeline: "PipelineName, PipelineAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=..." Source: "Init Message Processing Properties" Receive Port: "..." URI: "..." Reason: Loading property information list by namespace failed or property not found in the list. Verify that the schema is deployed properly.

In my case, and, as it seems, some others, this was caused by corrupted installation of third party adapters for BizTalk. Reinstallation of adapters solved the problem.

BizTalk tools: LoadGen 2007

The Microsoft BizTalk LoadGen 2007 Tool is the tool you want for load and performance testing of your BizTalk Server instance. It can do all you want and don't ;-). It's very intuitive and simple, despite being made by Microsoft ;-). One nasty thing, though it uses XML files for configuration it will not work if you add standard (!)

<?xml version="1.0"?>

 declaration at the beginning of the file. Except for that I didn't encountered any problems so far.

P.S. This dead blog is still very helpful if you doing your first steps in BizTalk server performance tuning.