MikeMiller
asked on
Access Denied - msxml4.dll (0x80070005)
Error Type:
msxml4.dll (0x80070005)
Access is denied.
/test/test.asp, line 70
Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)
set objSrvHTTP = Server.CreateObject("MSXML
objSrvHTTP.open "POST", URL, false
objSrvHTTP.SetRequestHeade
objSrvHTTP.send(strxml) <--- Line 70
I am using MS XML 4.0 SP2
I've read other places that the solution to fix this is to use the resultant pokicy snap in and import the settings from IE to it. I can open that snapin, but everything is greyed out. I made sure the "submit nonencrpyted form data" was enabled for all zones in IE. I also went in and manually enabled it for all zones in the registry.
I have tried testing it on a Windows 2000 Server SP4 web server / Windows XP SP1 client and with the WindowsXP SP1 system hosting the file in IIS and accessing it via http:/localhost/. The error happens on both.
What can I do?
Mike Miller
msxml4.dll (0x80070005)
Access is denied.
/test/test.asp, line 70
Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)
set objSrvHTTP = Server.CreateObject("MSXML
objSrvHTTP.open "POST", URL, false
objSrvHTTP.SetRequestHeade
objSrvHTTP.send(strxml) <--- Line 70
I am using MS XML 4.0 SP2
I've read other places that the solution to fix this is to use the resultant pokicy snap in and import the settings from IE to it. I can open that snapin, but everything is greyed out. I made sure the "submit nonencrpyted form data" was enabled for all zones in IE. I also went in and manually enabled it for all zones in the registry.
I have tried testing it on a Windows 2000 Server SP4 web server / Windows XP SP1 client and with the WindowsXP SP1 system hosting the file in IIS and accessing it via http:/localhost/. The error happens on both.
What can I do?
Mike Miller
ASKER
No, I had the page working with the original Microsoft.XMLHTPP (or something similar) but when I updated to MS XML 4.0 SP2, this access denied on msxml4.dll started happening.
It's a fairly well known problem. I have read a lot of stuff on the net about it but none of the solutions has worked for me. I tried the IE settings on the web server. I tried the registry modifications for "submit nonencrpyted form data". I tried giving the IIS IUSR_MachineName full admin rights.
I did manage to get the page working with MS XML 3.0. I unistalled 4.0 and then installed 3.0. I had to change the lines to read:
set objSrvHTTP = Server.CreateObject("MSXML
set xmlDoc = Server.CreateObject("MSXML
I just want to know how to fix it so that I can be using the latest version. You'd think that Microsoft would have the bugs worked out considering its SP2.
Points Increased... I'll try to attract a little more attention.
It's a fairly well known problem. I have read a lot of stuff on the net about it but none of the solutions has worked for me. I tried the IE settings on the web server. I tried the registry modifications for "submit nonencrpyted form data". I tried giving the IIS IUSR_MachineName full admin rights.
I did manage to get the page working with MS XML 3.0. I unistalled 4.0 and then installed 3.0. I had to change the lines to read:
set objSrvHTTP = Server.CreateObject("MSXML
set xmlDoc = Server.CreateObject("MSXML
I just want to know how to fix it so that I can be using the latest version. You'd think that Microsoft would have the bugs worked out considering its SP2.
Points Increased... I'll try to attract a little more attention.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Wow that worked!
I've tried a few other MS support solutions but none of them worked. None of the resources I found on the net pointed to that Knowledge Base article. It looks like it is doing the same thing as the Resultant Policy snap-in solution although it was all greyed out when I tried to do it through that snap-in. By using the Group Policy snap-in, the options were availble. I didnt have to change any of the settings, but merely importing them into Group Policy fixed the problem.
Thanks!
Mike Miller
I've tried a few other MS support solutions but none of them worked. None of the resources I found on the net pointed to that Knowledge Base article. It looks like it is doing the same thing as the Resultant Policy snap-in solution although it was all greyed out when I tried to do it through that snap-in. By using the Group Policy snap-in, the options were availble. I didnt have to change any of the settings, but merely importing them into Group Policy fixed the problem.
Thanks!
Mike Miller
objSrvHTTP.open "POST", URL, false, "myUserName", "foobar"
Regards,
Mike Sharp