| Yves Peneveyre 2004-06-26, 10:51 am |
| Thank you very much for the help Vladimir !
It was the Hotfix 831575 which caused the problem.
For other people who would be interested, the hotfix link is the following :
http://support.microsoft.com/defaul...kb;en-us;831575
And here :
http://www.dotnet247.com/247referen.../51/255188.aspx
Is a newsgroup thread with some workarounds.
I just uninstalled this hotfix to try and it is working fine.
Best Regards
Yves Peneveyre
"Vladimir Tchalkov" <vlado@act-soft.nspam.com> wrote in message
news:uzYYD%23cWEHA.500@TK2MSFTNGP09.phx.gbl...
> This is a known bug in one of the updates of .NET framework (probably
> BizTalk isntalls this update).
> There is a posting in the microsoft.public.dotnet.framework newsgroup -
> serach there for
> "Internal problem on XmlDocument.Load( )."
>
> You can either change the URI to file or unc path or set the connection
> limit for localhost manually. I had the same problem and changed the web
> site to load the xmls from local file paths.
>
> Vladimir
>
>
> "Yves Peneveyre" <ypeneveyre at lookware dot ch> wrote in message
> news:eA4eqRcWEHA.208@TK2MSFTNGP10.phx.gbl...
have[vbcol=seagreen]
> all.
> The
argument[vbcol=seagreen]
value[vbcol=seagreen]
Type[vbcol=seagreen]
> +145
>
>
|