ASP causing sporadic error

[SEOMike]

I occasionally get the following error from an ASP document:

msxml3.dll error '80070005'

Access is denied.

/document.asp, line 15

Here is the code from document.asp which causes the problem:

1 <%
2 Response.Buffer = True
3 Dim objXMLHTTP, xml, cid, dtype
4
5 cid = Request.QueryString("cid")
6 dtype = Request.QueryString("type")
7
8 'Create an xmlhttp object:
9 Set xml = Server.CreateObject("MSXML2.ServerXMLHTTP")
10
11 ' Opens the connection to the remote server.
12 xml.Open "GET", "http://www.example.com/d?cid=" & cid & "&type=" & dtype, False
13
14 ' Actually Sends the request and returns the data:
15 xml.Send
16
17 Response.Write xml.responseText
18
19 Set xml = Nothing
20 %>

The strange thing is that this only happens occasionally on the pages. I don't understand. I'm no expert coder so if I forgot to post something that would help, please let me know what you need to help diagnose the problem. Any help would be appreciated.
The server is Server 2003 w/ IIS6.

[SEOMike]

Nobody? huh. I'll post a fix if I ever find one.

[Matt_C]

Are you sure it has sufficient permissions (Set under IIS)?

and

Are you sure the path on line 12 is valid everytime? What is in the query strings when the page fails (Maybe something in there is causing the issue)

[edited by: Matt_C at 3:53 pm (utc) on Nov. 4, 2008]

[SEOMike]

Are you sure it has sufficient permissions (Set under IIS)?

I guess not since it doesn't work correctly all the time. It loads just fine upon refresh and any other page visit. It's just the first time to the site it doesn't work. Any specific permissions I should look at?

Are you sure the path on line 12 is valid everytime?

Hmmm... maybe not. I wonder if the value isn't being set on the first visit for some reason. Works on ever other site implementation but this one though, and then works upon refresh.

What is in the query strings when the page fails

Nothing... Maybe that's the problem but it works when refreshed and the strings aren't there.

[Matt_C]

I would *guess* that it's more likely to be an issue with the URL rather than permissions as I would *guess* that is wouldn't work at all if it was permissions.

So I would agree with you that it does look like more likely to be the URL on line 12.

I'd like to know how you sort this out.

Matt

[edited by: Matt_C at 4:42 pm (utc) on Nov. 4, 2008]

[Response]

SEOMike,
My encounters with errors associated with the msxml series of dll's have been related to the permissions set on the dll. I cannot say I have had this problem with IIS6 and this might explain the odd issue of it clearing up on refresh. What I have seen are permission issues with the IWAM and IIS Anonymous users. Because this is a security policy issue, I am hesitant of making direct recommendations for changes. Hey it is your security at stake here ;)

But you might want to Google DCOM Configuration and Local Security Policies. The 80070005 error is a notoriously ambiguous error. But I would start with those two.

If your skills permit, I did notice a work around using the ServerXMLHTTP component instead. Google keywords msxml3 [phone] +.Send
Good Luck

[SEOMike]

Got it! Thanks for the references Response. The registry hack for ServerXMLHTTP worked just fine. Finally got that weird thing cleared up. Been driving me nuts!