Try one of these solutions:
First a registry hack
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\windows\CurrentVersion\Internet Settings]
"Security_HKLM_only"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet 
Settings\Zones\3]
"1601"=dword:00000000

MSXML4.0 SP2 had some security "enhancements" that broke some existing SP1 
functionality.

If the above doesn't work, then try downloading and running this "Hot fix" 
patch from MS. (you'll have to search for it, don't remember the link offhand)
KB832414_MSXML4.0_x86.exe

There was a Window Update to IE6.0 that, again, tightened security and broke 
some of MSXML4.0 SP2's functionality - this patch was released to address 
that.

Hope the above helps.


"Dewayne Mikkelson" wrote:

> I am migrating a Working ASP Web Application from a Windows 2000
> Server to Windows 2003 Server.
> 
> On the Windows 2K server this application works correctly.
> After migration to Windows 2K3 server this application gets the error
> in the Subject line.
> 
> I have tried multiple KB articles to resolve this issue without
> success.
> 
> I was able to get past this error when I substitued
> WinHTTP.WinHTTPRequest.5.1 for MSXML2.XMLHttp.4.0 but that opened a
> whole new can of worms which I would prefer not to pursue at this
> point.
> 
> This code base is approx. 4 years old and I really want to avoid
> rewriting it as much as possible.
> 
> Thanks,
> Dewayne Mikkelson
> Dewayne.Mikkelson@G...
> Blog: http://www.shadowcentral.net/
>