And... On another note
-
I have a client with an ASP.NET web page that was created using c#. It has run for over a year and a half just fine, and now generates an error on the server. The site is www.delcarpenter.com. The error is not always the same error. Now... If you look, it is erroring out trying to get the xml file. If you type the xml file directly as www.delcarpenter.com/homepage.xml... it comes up fine. The server can even open it up fine that way from a web browser. BUT... the page has this issue. TIA...
-
I have a client with an ASP.NET web page that was created using c#. It has run for over a year and a half just fine, and now generates an error on the server. The site is www.delcarpenter.com. The error is not always the same error. Now... If you look, it is erroring out trying to get the xml file. If you type the xml file directly as www.delcarpenter.com/homepage.xml... it comes up fine. The server can even open it up fine that way from a web browser. BUT... the page has this issue. TIA...
I get the error
The underlying connection was closed: The remote name could not be resolved.From the stack trace, it looks like the code is accessing some sort of saved xml dataset, not the XML file you mention. It then receives an error when trying to resolve some reference within the file (perhaps the namespace).
-
I get the error
The underlying connection was closed: The remote name could not be resolved.From the stack trace, it looks like the code is accessing some sort of saved xml dataset, not the XML file you mention. It then receives an error when trying to resolve some reference within the file (perhaps the namespace).
BTW... I am a systems guy too LOL Steven Campbell wrote: I get the error The underlying connection was closed: The remote name could not be resolved. From the stack trace, it looks like the code is accessing some sort of saved xml dataset, not the XML file you mention. It then receives an error when trying to resolve some reference within the file (perhaps the namespace). Well.. I thot of that. If I copy the site to my local server, it works as is... so It is, as myself and the system admin at the host belive, a system problem. The code hasn't changed since it was installed. And all calls are to the local xml file. If you check around, you may find some of the other pages (they use the same codeing) work. It is one of those.... ephemiral errors. The only reason the content is xml is to save money on the SQL side and to allow the user to change the text. (Not webpage programmers are they) Sooooo.... I am stumped still... Sorry I wasn't more specific about my prior troubleshooting. but if it works on one server and not another... and the code hasn't changed... and it worked for over a year... My bet is system issues... And if you try it a few times... you will eventually get a timeout error.
-
BTW... I am a systems guy too LOL Steven Campbell wrote: I get the error The underlying connection was closed: The remote name could not be resolved. From the stack trace, it looks like the code is accessing some sort of saved xml dataset, not the XML file you mention. It then receives an error when trying to resolve some reference within the file (perhaps the namespace). Well.. I thot of that. If I copy the site to my local server, it works as is... so It is, as myself and the system admin at the host belive, a system problem. The code hasn't changed since it was installed. And all calls are to the local xml file. If you check around, you may find some of the other pages (they use the same codeing) work. It is one of those.... ephemiral errors. The only reason the content is xml is to save money on the SQL side and to allow the user to change the text. (Not webpage programmers are they) Sooooo.... I am stumped still... Sorry I wasn't more specific about my prior troubleshooting. but if it works on one server and not another... and the code hasn't changed... and it worked for over a year... My bet is system issues... And if you try it a few times... you will eventually get a timeout error.
Of course it is a system issue -- that was obvious from your first post. (Probably some port has been closed on a firewall, or a new firewall was installed, or a proxy added). Still, it should still be of interest to you to know the actual details of the problem. The error also occurs on the Testimonials link -- so it should be easy to find what is common with the code in these two places (Home and Testimonials).
-
I have a client with an ASP.NET web page that was created using c#. It has run for over a year and a half just fine, and now generates an error on the server. The site is www.delcarpenter.com. The error is not always the same error. Now... If you look, it is erroring out trying to get the xml file. If you type the xml file directly as www.delcarpenter.com/homepage.xml... it comes up fine. The server can even open it up fine that way from a web browser. BUT... the page has this issue. TIA...
Hi, I'm not sure this will help, but you'll never now. Check if the rights on the folder are set correctly. The server has special rights for ASP.NET users (and different ones for normal users). This could explain the difference between using just the webbrowser and using your (ASP.NET) application. It's just an idea, but I hope it helps. "If I don't see you in this world, I'll see you in the next one... and don't be late." ~ Jimi Hendrix
-
Of course it is a system issue -- that was obvious from your first post. (Probably some port has been closed on a firewall, or a new firewall was installed, or a proxy added). Still, it should still be of interest to you to know the actual details of the problem. The error also occurs on the Testimonials link -- so it should be easy to find what is common with the code in these two places (Home and Testimonials).
Thanx for your help. I guess I just have to rely on the ISP.
-
Hi, I'm not sure this will help, but you'll never now. Check if the rights on the folder are set correctly. The server has special rights for ASP.NET users (and different ones for normal users). This could explain the difference between using just the webbrowser and using your (ASP.NET) application. It's just an idea, but I hope it helps. "If I don't see you in this world, I'll see you in the next one... and don't be late." ~ Jimi Hendrix