After installing 8.03, I attempted a couple Problem Reports and received this message:
Server Error in '/SendReport' Application.
--------------------------------------------------------------------------------

The transport failed to connect to the server.

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.Runtime.InteropServices.COMException: The transport failed to connect to the server.


Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[COMException (0x80040213): The transport failed to connect to the server.
]

[TargetInvocationException: Exception has been thrown by the target of an invocation.]
System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters) +0
System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams) +337
System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args, CultureInfo culture) +36
System.Web.Mail.LateBoundAccessHelper.CallMethod(Type type, Object obj, String methodName, Object[] args) +66
System.Web.Mail.LateBoundAccessHelper.CallMethod(Object obj, String methodName, Object[] args) +49

[HttpException (0x80004005): The transport failed to connect to the server.
]
System.Web.Mail.LateBoundAccessHelper.CallMethod(Object obj, String methodName, Object[] args) +99
System.Web.Mail.CdoSysHelper.Send(MailMessage message) +1738
System.Web.Mail.SmtpMail.Send(MailMessage message) +351
SendReport.WebForm1.Page_Load(Object sender, EventArgs e) in C:\inetpub\wwwroot\Archive\LivingSoft\SendReport\Start.aspx.cs:60
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +14
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +35
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Control.LoadRecursive() +50
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627




--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3082

Bob is away for the weekend on a scouts leader obligation- I am unable to give a response to this- Thank you for submitting the error message- Im sure it will help.

Earliest response will be sometime Monday.

Kaaren

quote:

After installing 8.03, I attempted a couple Problem Reports and received this message:
Server Error in '/SendReport' Application.

The problems with problem reports just now is not related to Dress Shop 8.03, but rather with your Internet Service Provider blocking emails from our ISP. For email, we use a large service provider that includes many other users. Some among those appear to be spammers. When they spam, other ISPs (such as yours) block our ISP.

This has been an on-going problem for us, but appears to be getting much worse lately. Today, we have asked that our account be moved to a dedicated server. More expensive, but we will no longer share the burden of other's spamming efforts. The change is supposed to be done by Wednesday, after which we SHOULD no longer have problems getting our automated emails sent out.

The same problem has applied to other automated emails including email offers, newsletters, password requests, and activation code requests. All of these should work better once we are on a dedicated server.

Hope this makes sense...

I again attempted to send a problem report, and had the same error message as before, as of this morning. So problem is continuing. I appreciate the move to the dedicated server. Maybe that's not quite ready yet? thanks