Dynamic Send Port UNC path bug

I am aware of a bug where you are unable to use a dynamic send port to
write a file to a UNC path; due to BizTalk holding the temporary file
open after it's written and before it renames.

Does anybody know if there is a patch for BizTalk 2006 to fix this bug
- or if this is something that has been fixed in R2?

I haven't been able to find details of the bug on the MS support site.

Thanks,

Alastair.

.

Relevant Pages

  • Service pack 1 introduced a bug
    ... I can't believe I am the only who found this bug. ... Biztalk Server 2002 with SP1 can not verify the sign, ... is not able to parse it (Biztalk exchange it for multiple documents). ... So I think it is a bug introduced with Service Pack 1, ...
    (microsoft.public.biztalk.general)
  • RE: Deployment exception on @namespace parameter
    ... Found the 'bug' in Biztalk. ... Any 'bugs' in the code that prevent deployment should be caught at compile ... If the Prefix (in XSD message schema) is changed by one character we get the ...
    (microsoft.public.biztalk.general)
  • Re: FTP location is randomly stopping
    ... My company is using an old biztalk version. ... All FTP connection were handled ... by custom component. ... Long story short, we were far from cool, the "bug" (I called bug ...
    (microsoft.public.biztalk.general)
  • bug reporting?
    ... Does anyone know a way to report a bug for BizTalk Server 2006? ... A while back I was a Commerce Server MVP. ...
    (microsoft.public.biztalk.general)
  • fat32 corruption
    ... The bug was written against 4.6 but it does not ... slot 31 INTC routed to irq 23 ... <Parallel port bus> on ppc0 ... can't assign resources ...
    (freebsd-questions)