View Single Post
Old 23rd January 2011, 11:30   #7
DigiBC
Junior Member
 
Join Date: Dec 2007
Location: Europe
Posts: 28
Quote:
Originally Posted by DrO View Post
DigiBC: maybe the page is being queried too fast or the DNAS is busy at the time and so by the time it gets around to responding the ASP aspect has timed out. if you look at the server logs, it should indicate (might need to enable some debugging options of web connections) if the page request was received and if it succeeded or not.
Frankly speaking I don't think it's an ASP problem, because these interruptions do last for much more than a few milliseconds. (I've never had similar problems with earlier DNAS versions.)
When I open the above mentioned link in my browser I can reproduce the problem by simply refreshing the page. After several tries the browser will display an error: "XML Page Cannot Be Displayed".
DigiBC is offline