Thursday, August 24, 2006


Well, today was the day where I passed the 70-235 exam in BizTalk Server 2006.

So now I have passed all three BizTalk exams - BizTalk 2000, BizTalk 2004, and BizTalk 2006. Anyone else who has done that? :-)

I wonder how soon I can order my welcome kit at :-)



Thursday, August 24, 2006 10:29:21 PM (Romance Daylight Time, UTC+02:00)  #    Comments [2]  | 
Tuesday, August 22, 2006


Today I ran into a problem configuring the WSS Adapter for BizTalk 2006. In the configuration wizard I just couldn't choose a web site for the adapter that would satisfy the configuration wizard. I got this error:

And I was pretty tired of it :-) Especially because I was sure WSS was installed on this web site, the web site was extended with WSS and everything should have been ok.

Anyway, some searching on the net gave me a hint as to what was going on. I found an article on that helped me. In short, I had installed Windows Sharepoint Services on a web site I had created for this purpose, but I had forgotten to make sure the web site was running ASP.NET 2.0 before installing WSS. This made WSS run on .NET 1.1 and BizTalk 2006 has a requirement that it must run under .NET 2.0.

So in order to register ASP.NET 2.0 with IIS and upgrade my WSS installation to use .NET 2.0, I ran the following two commands:

"c:\windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe" -i

"c:\program files\common files\Microsoft Shared\web server extensions\60\BIN\STSADM.exe" -o upgrade -url http://localhost:4242 -forceupgrade

The :4242 is because my WSS web site is configured to run on this port.

After this, there were no problems, and I could then configure the WSS adapter. I didn't need to restart the configuration wizard - I just had to select the default web site and then select my WSS Site again.

Hope this helpes someone. Should you have comments, please go ahead.



Tuesday, August 22, 2006 4:37:56 PM (Romance Daylight Time, UTC+02:00)  #    Comments [3]  | 
Sunday, August 20, 2006

I ran into this one a while ago. I couldn't find any information about the error on the internet, so I tried the microsoft public newsgroups. Again, no help (although those newsgroups are a GREAT place for getting help...). Anyway, I found out, what the error was, and it can probably be found in google groups by now, but I thought I'd just share it here as well.

Basically, the problem was that BizTalk 2004 SP1 apparently has a bug. If you have a "Call Orchestration"-shape (or a "Start Orchestration"-shape) in your orchestration, and this shape is placed in some particular unreachable code, you get this error.

I had a decision shape in my orchestration, but I hadn't gotten around to deciding what the rule in the decision shape was going to be. So I entered "1 == 1" in order for the assembly to compile and then I could deploy it and test it for that branch of my decision shape. Then, I wanted to test the other branch, still not knowing what the final rule would be. So I modified the orchestration to have the rule to be "1 != 1" - but then I couldn't compile - weird, eh?

Below is my orchestration.

So, as you can see - no funny stuff. Another weird thing is, that I can compile just fine with my "Call Orchestration"-shape after a Terminate-shape. But that is unreachable code as well.

I don't know what is happening, but it sure is weird.

I hope this posting has helped some of you.

You can find a copy of my project here: (59.09 KB)

Let me know if you have any comments.

Sunday, August 20, 2006 3:04:37 PM (Romance Daylight Time, UTC+02:00)  #    Comments [1]  | 
Saturday, August 19, 2006
Hi everyone!

Three weeks ago, my second son was born. So now I am the proud father of two sons.

They have a homepage, my sons... it can be found at

It is only in Danish, I'm afraid.

Oh yeah, and it is my first attempt at making anything in ASP.NET 2.0 - and I've even used the Masterpage functionality :-)


Saturday, August 19, 2006 11:27:55 PM (Romance Daylight Time, UTC+02:00)  #    Comments [0]  | 

Theme design by Jelle Druyts