| =?Utf-8?B?S2FybCBFbmd2b2xk?= 2004-01-28, 7:32 pm |
| Hi Martin,
OK, someone upgrades our server to SQL 2000 SP 3.0 and BOOOM... access denied / the server name or address cannot be resolved is here. The problem was fixed on one server, but not the other.
I am having the same error as Ken, even after upgrading to MSXML 4.0 SP2 and SQLXML 3.0 SP2 and SOAPXML 3.0... nothing seems to work. I even tried using the "proxycfg -d" to remove the proxy dependency AND rebooted the server (all advise I found in the Kn
owledge base article 289481 - INFO: You May Need to Run ProxyCfg Utility for ServerXMLHTTP to Work). I also came accross the readme for MSXML 4.0 SP2 Realease Notes where it mentions "Security tightened when posting data using the ServerXmlHttp Object". T
he recommended steps to use MMC do not make any sense in that I can NOT find a snap-in for the "Resultant Set of Policy" to choose when Adding Snap-In!!! ??
Finally, FYI... I did have the access denied error on another Windows 2000 Server for development testing, but after doing the "Proxycfg -d" and rebooting it works fine!
Now, if I can only make our live Server work properly!
Any assistance is greatly appreciated. As well, you may send emails to me at engvold@hotmail.com
Sincerely,
Karl Engvold
----- Martin Honnen wrote: -----
Ken Kolda wrote:
[QUOTE][color=darkred]
> We use the XMLHTTP component to fetch XML data from a remote server within
> our product. But, on one client's machine, we're running into a problem
> that we can easily reproduce in a trvial VBS script. The error we get is:
> Code: 80070005
> Source: msxml3.dll
> the last line):
> Set HTTP = CreateObject("MSXML2.XMLHTTP")
> HTTP.SetRequestHeader "CustomHeader", "ABCDEFG"
> HTTP.Send
> users with proxies who have had no problem (which goes along with my
> understanding that the XMLHTTP component uses IE's proxy settings). I've
> seen lots of discussion regarding this kind of error for the ServerXMLHTTP
> component, but that's not the issue here.
I have run once into an access denied error with msxml3 that went away
when I switched to msxml4 (and used MSXML2.XMLHTTP.4.0). Not sure
whether it is an option for you (and whether it helps in this case).
--
Martin Honnen
http://JavaScript.FAQTs.com/
|