Server Error in '/' Application.

An asynchronous call is already in progress. It must be completed or canceled before you can call this method.

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.InvalidOperationException: An asynchronous call is already in progress. It must be completed or canceled before you can call this method.

Source Error:

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" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

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.

Stack Trace:


[InvalidOperationException: An asynchronous call is already in progress. It must be completed or canceled before you can call this method.]
   System.Net.Mail.SmtpClient.Send(MailMessage message) +1800
   PDI.Mail.Utility.SendMail(MailMessage mail, SendMailOptions options) in D:\FrameworkPDI\FrameworkPDI-Core-PDI\Mail\Utility.cs:175
   PDI.Mail.Utility.SendMail(String from, String to, String subject, String body, Boolean isHtml, MailPriority priority, AttachmentCollection attachments) in D:\FrameworkPDI\FrameworkPDI-Core-PDI\Mail\Utility.cs:144
   PDI.Diagnostic.ExceptionService.Alert(String source, String message) in D:\FrameworkPDI\FrameworkPDI-Core-PDI\Diagnostic\ExceptionManager.cs:42
   TemplateW3C.PaginaBase.DetectError(Object testo) in F:\FrameworkPDI-Core-TemplateW3C\sorgente\TemplateW3C\PaginaBase.cs:491
   TemplateW3C.PaginaBase.DetectError(Exception ex) in F:\FrameworkPDI-Core-TemplateW3C\sorgente\TemplateW3C\PaginaBase.cs:496
   TemplateW3C.PaginaBase.Errore(Object o, EventArgs e) in F:\FrameworkPDI-Core-TemplateW3C\sorgente\TemplateW3C\PaginaBase.cs:760
   System.Web.UI.TemplateControl.OnError(EventArgs e) +8795362
   System.Web.UI.Page.HandleError(Exception e) +84
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6776
   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +242
   System.Web.UI.Page.ProcessRequest() +80
   System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +21
   System.Web.UI.Page.ProcessRequest(HttpContext context) +49
   ASP.servizi_eventi_cerca_fase03_aspx.ProcessRequest(HttpContext context) +4
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +181
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75


Version Information: Microsoft .NET Framework Version:2.0.50727.9061; ASP.NET Version:2.0.50727.9062