ASP.NET调试时显示的错误及原因(VS2005,补充中)_AX

Server Error in '/WebSite3' Application.

---

Value cannot be null.
Parameter name: enumType

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.ArgumentNullException: Value cannot be null.
Parameter name: enumType

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.

【练习使用Webparts时出现】
【原因】
未知,enumType错误,刚刚还好的,日
还以为是枚举类型的问题,结果是:个性化设置发生了混乱(乱调权限,增加verbs等).把aspnet_PersonalizationAllUsers/aspnet_PersonalizationPerUser表的纪录删除就OK了.

---

VS2005连接不上SQL2005
http://www.cnblogs.com/user34j/archive/2007/03/11/670954.html

---

 

Server Error in '/' Application.

---

Type 'System.Web.HttpApplication+CancelModuleException' in assembly 'System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' is not marked as serializable.

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.Serialization.SerializationException: Type 'System.Web.HttpApplication+CancelModuleException' in assembly 'System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' is not marked as serializable.

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:

[SerializationException: Type 'System.Web.HttpApplication+CancelModuleException' in assembly 'System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' is not marked as serializable.]
            System.Threading.Thread.GetAbortReason() +0
            System.Threading.Thread.get_AbortReason() +18
            [InvalidOperationException: Thread.ExceptionState cannot access an ExceptionState from a different AppDomain.]
            System.Threading.Thread.get_AbortReason() +80
            System.Threading.ThreadAbortException.get_ExceptionState() +22
            System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +380
            System.Web.ApplicationStepManager.ResumeSteps(Exception error) +594
            System.Web.HttpApplication.ResumeSteps(Exception error) +29
            System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) +149
            System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +565
            

---

 

Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
【原因】
参见:http://dotnetframework.blogspot.com/2007/03/thread-was-being-aborted-when-using.html
光看這一段，抓不太到問題，所以打開event log看了一下，竟然是HttpRequest Timeout了。
原因是出在當IIS active 一個singlecall object時，該object的執行時間超過IIS預設的等待時間。
要解決這個問題，必須在remoting所使用的web.config中改變request time..
像這樣..
executionTimeout 以秒計費，300就是300秒..
【解决方案】

WebConfig添加如下节点

    </system.web>    
        <!--executeTime:单位(″) maxRequestLength:单位(KB)-->
        <httpRuntime executionTimeout="20" maxRequestLength="8192"  />
    </system.web>

【解决方案补充】

上面是从Web上搜的,不管用,Solution关了再重新打开就OK了........无语~!