| BeanTownJoe 2005-01-18, 5:50 pm |
|
I was hoping to get the hot fix before then. I have to hold off the client
implementation because they will lose too much money because they cannot
identify the SOAP exception to properly bill. Is there any way anyone knows
where I can get this fix, this seems to be a huge bug considering the big
push on webservice connectivity within BizTalk 2004. BizTalk can connect
with external webservices but it cannot tell you what goes wrong if you call
it?
"Nabeel Prior" wrote:
> According to this post:
> http://blogs.conchango.com/matthall...01/18/841.aspx, that fix is
> included in SP1 due out before the end of January.
>
>
> --
>
> Kind Regards,
>
> Nabeel Prior
> Web: http://www.brainjar.co.za
> Blog: http://www.brainjar.co.za/blog.aspx
>
>
> "BeanTownJoe" <BeanTownJoe@discussions.microsoft.com> wrote in message
> news:D10B4A24-EC8F-42B7-9CAF-445026AB6588@microsoft.com...
>
>
>
|