Wonder why I think you will be able to read the forum threads when I cannot BUT I keep getting this error:
The underlying connection was closed: The remote name could not be resolved.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Net.WebException: The underlying connection was closed: The remote name could not be resolved.
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
2) Add the following section to the configuration file of your application:
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
[WebException: The underlying connection was closed: The remote name could not be resolved.]
System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) +140
ASP.tm_aspx.RenderMemberAffiliates(Int32 MEM) +192
ASP.tm_aspx.__Render__control1(HtmlTextWriter __output, Control parameterContainer) +65730
System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +27
System.Web.UI.Control.Render(HtmlTextWriter writer) +7
System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +243
You're unique! Just like everyone else. ;)