ASP.NET 1.1 debug=false

[msnews.microsoft.com]

We are deploying a large .NET 1.1 web app. We are using SP1 of the .NET 1.1
framework. Our build system compiles all of our components in release mode.
We deploy on Windows Server 2003 Enterprise SP1

We noticed the other day that our web.config said debug=true. We read some
articles and decided we should release with debug=false.

I stopped IIS, cleared out the ASP.NET temporary folder, changed the flag to
false, and restarted IIS.

After this, sometimes we started getting a GPF in w3wp.exe executing code in
our data tier through out data aceess layer. Since we host on multiple
horizontally scaled web apps, we decided to see if we could dupe this on
other apps and we could.

We changed the flags back to true, cleared out the ASP.NET temp folder, and
restarted and they have been humming along just fine.

I'm really scratching my head on this on. Below is are the output of the
error chain.

Faulting application w3wp.exe, version 6.0.3790.1830, faulting module
kernel32.dll, version 5.2.3790.1830, fault address 0x00015dea.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.



The system has called a custom component and that component has failed and
generated an exception. This indicates a problem with the custom component.
Notify the developer of this component that a failure has occurred and
provide them with the information below.

Component Prog ID: Powerway.Common.DataAccess.CommonDataAccessClass

Method Name: IObjectControl:eactivate()

Server Application ID: {D10CAB2A-7732-4E1E-8172-CA0B1CC36F44}

Server Application Instance ID:

{114DE4F9-1C41-410E-B5FB-143617FB22A7}

Server Application Name: PDP v3.0

Exception: E0434F4D

Address: 0x77E55DEA

Call Stack:

kernel32!RaiseException + 0x3c

mscorsvr!GetAssemblyMDImport + 0x2e1d4

mscorsvr!GetAssemblyMDImport + 0x2e157

mscorsvr!GetAssemblyMDImport + 0x2e10b

mscorsvr!GetAssemblyMDImport + 0x2e0b2

mscorsvr!GetMetaDataPublicInterfaceFromInternal + 0x6255

mscorsvr!CoEEShutDownCOM + 0x6135

mscorsvr!ReleaseFusionInterfaces + 0x1c7ff

comsvcs!DllUnregisterServer + 0x3f3b5

comsvcs!DllUnregisterServer + 0x40756

ole32!CoGetApartmentID + 0x16b0

ole32!CoGetCallContext + 0xc3c

ole32!CoQueryAuthenticationServices + 0x1f7f

ole32!CoQueryAuthenticationServices + 0x2b1b

ole32!CoQueryAuthenticationServices + 0x3548

ole32!CoQueryAuthenticationServices + 0x3a52

ole32!GetHGlobalFromStream + 0x46a

ole32!CoCreateObjectInContext + 0x1042

mscorsvr!CoEEShutDownCOM + 0x1db97

+ 0x1a9a045

+ 0xd144eae

+ 0x231297c



For more information, see Help and Support Center at



General Information

*********************************************

Additional Info:

ExceptionManager.MachineName: ALPHA-WEB1

ExceptionManager.TimeStamp: 4/27/2006 11:09 PM

ExceptionManager.FullName: Microsoft.ApplicationBlocks.ExceptionManagement,
Version=3.0.0.0, Culture=neutral, PublicKeyToken=3d0dc145a66e9e9a

ExceptionManager.AppDomainName:
/LM/W3SVC/1672928981/Root-1-127906466737283552

ExceptionManager.ThreadIdentity:

ExceptionManager.WindowsIdentity: NT AUTHORITY\NETWORK SERVICE

1) Exception Information

*********************************************

Exception Type: System.Threading.ThreadAbortException

ExceptionState: System.Web.HttpApplication+CancelModuleException

Message: Thread was being aborted.

TargetSite: System.Runtime.Remoting.Messaging.IMessage
DoCallback(System.Object, System.Runtime.Remoting.Messaging.IMessage,
IntPtr, Boolean, System.Reflection.MemberInfo, Boolean)

HelpLink: NULL

Source: System.EnterpriseServices

StackTrace Information

*********************************************

at System.EnterpriseServices.Thunk.Callback.DoCallback(Object otp, IMessage
msg, IntPtr ctx, Boolean fIsAutoDone, MemberInfo mb, Boolean bHasGit)

at System.EnterpriseServices.ServicedComponentProxy.CrossCtxInvoke(IMessage
reqMsg)

at System.EnterpriseServices.ServicedComponentProxy.Invoke(IMessage request)

at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&
msgData, Int32 type)

at
Powerway.Common.DataAccess.CommonDataAccessClass.RunSPReturnDataSet(String
storedProcedureName, Object[] parameters)

at Powerway.PDP.IssueManagement.IssueRead.GetIssuesForWorkList(Int32 UserID,
Int32 ProcessID, Int32 OverdueStatus, Int32 ViewType, String LanguageCode)

For more information, see Help and Support Center at

 

[Jim Cheshire]

We are deploying a large .NET 1.1 web app. We are using SP1 of the .NET 1.1
framework. Our build system compiles all of our components in release mode.
We deploy on Windows Server 2003 Enterprise SP1

We noticed the other day that our web.config said debug=true. We read some
articles and decided we should release with debug=false.

I stopped IIS, cleared out the ASP.NET temporary folder, changed the flag to
false, and restarted IIS.

After this, sometimes we started getting a GPF in w3wp.exe executing code in
our data tier through out data aceess layer. Since we host on multiple
horizontally scaled web apps, we decided to see if we could dupe this on
other apps and we could.

You definitely want to set debug to false in a production environment.
For more information, see my blog entry here:

http://blogs.msdn.com/jamesche/archive/2005/12/20/506195.aspx

As for your crash, your symbols don't line up in the stack trace
you've got (and it's likely you don't have access to the symbols you
really need anyway), so your best bet is to open a case with Microsoft
and we can look into it for you.
Jim Cheshire
Blog: http://blogs.msdn.com/jamesche

 

[msnews.microsoft.com]

Will do Jim...

Thanks...

You definitely want to set debug to false in a production environment.
For more information, see my blog entry here:

http://blogs.msdn.com/jamesche/archive/2005/12/20/506195.aspx

As for your crash, your symbols don't line up in the stack trace
you've got (and it's likely you don't have access to the symbols you
really need anyway), so your best bet is to open a case with Microsoft
and we can look into it for you.
Jim Cheshire
Blog: http://blogs.msdn.com/jamesche

 

[Zulfiqar Ali]

I am getting the same error/exception in .net 2.0. is it fixed?
kindly post your solution/suggestion to fix this issue.