Unhandled IIS Exception - How can I track it down

Question

I am seeing the following error in the event log. It is coming from our ASP.Net application. I am having trouble tracking down what is causing the error. Any suggestions appreciated!

• OS: Windows Server 2000
• WebServer: IIS 6
• Application: ASP.Net v3.5

Error Log

[MachineName] has logged the following Error for IIS

Details: ComputerName=[ComputerName] User=Not specified Logfile=Application Type=Error EventType=1 SourceName=ASP.NET 2.0.50727.0 Category=0 CategoryString=Not specified EventCode=1334 EventID=-1073740490 TimeGenerated=20091125101806.000000-360 TimeWritten=20091125101806.000000-360 Message=An unhandled exception occurred and the process was terminated.

Application ID: DefaultDomain Process ID: 1440 Exception: System.Runtime.Serialization.SerializationException Message: Unable to find assembly 'Company.Common, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'.

StackTrace: at System.Runtime.Serialization.Formatters.Binary.BinaryAssemblyInfo.GetAssembly() at System.Runtime.Serialization.Formatters.Binary.ObjectReader.GetType(BinaryAssemblyInfo assemblyInfo, String name) at System.Runtime.Serialization.Formatters.Binary.ObjectMap..ctor(String objectName, String[] memberNames, BinaryTypeEnum[] binaryTypeEnumA, Object[] typeInformationA, Int32[] memberAssemIds, ObjectReader objectReader, Int32 objectId, BinaryAssemblyInfo assemblyInfo, SizedArray assemIdToAssemblyTable)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectWithMapTyped(BinaryObjectWithMapTyped record) at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run() at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage) at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage) at System.Runtime.Remoting.Channels.CrossAppDomainSerializer.DeserializeObject(MemoryStream stm) at System.AppDomain.Deserialize(Byte[] blob) at System.AppDomain.UnmarshalObject(Byte[] blob)

Answer 1

I created a custom unhanded exception module, which allowed retrieval of more information about the origin of the bug, and the eventual resolution of the issue.

Here is a link to a codeplex project that has code for an unhanded exception module: http://unhandledexception.codeplex.com/SourceControl/changeset/view/80132

Answer 2

Try the IIS Debug Diagnostics tools

http://support.microsoft.com/kb/919789