BizTalk | WSE and the fabulous "Server is unavailable, Please try again later" exception ...
So I followed all the best practices for returning Fault messages from my Orchestration Request-Response port as found documented here ...
I then published my orchestration as a WSE service.
Then I built this funky little test driver console application that submits SoapEvenlopes to the service and ultimately to BizTalk ... all good until a fault is returned.
All you get is "Server is unavailable, Please try again later". Great!
No SoapException detail. No SoapFault. Nudda.
So where did all my hard work in creating custom Fault messages go? Seemed to have vanished into the ether.
Finally I stumbled upon a blog post by Michael Stephenson, here, that has a great comparison between how the various adapters handle this very thing.
Turns out either the WSE adapter is just dodgy or we're missing the plot somewhere along the way ...
Why do the simple Http & SOAP adapters work great and put the detail where it is meant to be, but the "more sophisticated" WSE adapter requires some nasty string manipulation to retrieve the detail embedded deeply inside a string?
Seems they've fixed this in the WcfHttp adapter. So now the question is ...
How difficult / easy is it to :
a) Upgrade my 2006 server in place to R2?
b) To change my service to a wcf service?
c) To consume this new wcf service? Will the consumers of this service have to update their code if i change this to a wcf service?
Guess I get to play a bit ... 
.
Watch this space; I'll post an update answering each of the questions above.