.NET Questions and Solutions

Symptoms
When you try to activate Windows Vista or Windows Server 2008 over the Internet, the activation may be unsuccessful. Additionally, you may experience one or more of the following symptoms: Activation fails with error code 0×8004FE33. The following Error events may be recorded in the Application log:

Log Name: Application
Source: Software Licensing Service
Event ID: 8198
Level: Error Description: License Activation (SLUI.exe) failed with the following error code: 0×80004005

Log Name: Application
Source: Software Licensing Service
Event ID: 1008
Level: Error Description: Acquisition of Secure Processor Certificate failed. Status Code=hr=0×8004FE33Activation is not successful, and you are not prompted for credentials.
Resolution
This issue may occur when you connect to the Internet through a proxy server where Basic authentication is enabled.
When the proxy server is configured for Basic authentication, the server requires that you type a username and a password. However, the activation user interface does not let you enter these credentials. Therefore, the Basic authentication fails, and activation is not successful.

Symptoms
When an unhandled exception is thrown in a Microsoft ASP.NET-based application that is built on the Microsoft .NET Framework 2.0, the application unexpectedly quits. When this problem occurs, no exception information that you must have to understanding the issue is logged in the Application log.
However, an event message that is similar to the following may be logged in the System log:
Event Type: Warning
Event Source: W3SVC
Event Category: None
Event ID: 1009
Date: 9/28/2005
Time: 3:18:11
PM User: N/A
Computer: IIS-SERVER
Description:
A process serving application pool ‘DefaultAppPool’ terminated unexpectedly. The process id was ‘2548’. The process exit code was ‘0xe0434f4d’. Additionally, an event message that is similar to the following may be logged in the Application log:
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 9/28/2005
Time: 3:18:02 PM
User: N/A
Computer: IIS-SERVER
Description:
EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.1830, P3 42435be1, P4 app_web_7437ep-9, P5 0.0.0.0, P6 433b1670, P7 9, P8 a, P9 system.exception, P10 NIL.
Resolution
This problem occurs because the default policy for unhandled exceptions has changed in the .NET Framework 2.0. By default, the policy for unhandled exceptions is to end the worker process.
In the Microsoft .NET Framework 1.1 and in the Microsoft .NET Framework 1.0, unhandled exceptions on managed threads were ignored. Unless you attached a debugger to catch the exception, you would not realize that anything was wrong.
ASP.NET uses the default policy for unhandled exceptions in the .NET Framework 2.0. When an unhandled exception is thrown, the ASP.NET-based application unexpectedly quits.
This behavior does not apply to exceptions that occur in the context of a request. These kinds of exceptions are still handled and wrapped by an HttpException object. Exceptions that occur in the context of a request do not cause the worker process to end. However, unhandled exceptions outside the context of a request, such as exceptions on a timer thread or in a callback function, cause the worker process to end.

Symptoms
The Microsoft Exchange Information Store service crashes intermittently with a stack overflow on a computer that is running Exchange Server 2007. This behavior prevents users from accessing their mailboxes.

This behavior may occur approximately every five minutes on a computer that is running Exchange Server 2007
Additionally, event 9673 with code 0xc00000fd is logged in the Application log:
Event Type: Error
Event Source: MSExchangeIS
Event Category: General
Event ID: 9673
Description:
An exception with code 0xc00000fd was thrown in module; some parameters and their values were <Exception address>. A significant section of the call stack is in the data section.For more information, see Help and Support Center at <http://go.microsoft.com/fwlink/events.asp>.Data:00000: 00 00 00 00 00 00 00 00 ……..00008: 00 00 00 00 00 00 00 00 ……..00010: 00 00 00 00 00 00 00 00 ……..00018: 03 00 00 00 00 00 00 00 ……..00020: 04 00 00 00 00 00 00 00 ……..00028: 00 00 00 00 00 00 00 00 ……..00030: 00 00 00 00 00 00 00 00 ……..00038: 00 00 00 00 00 00 00 00 ……..00040: 00 00 00 00 00 00 00 00 ……..00048: 01 00 00 00 00 00 00 00 ……..00050: 72 81 21 54 00 00 00 00 r?!T….00058: 90 40 a3 39 00 00 00 00 ?@￡9….00060: 00 00 00 00 00 00 00 00 ……..00068: 00 00 00 00 00 00 00 00 ……..
Resolution
Typically, this problem may be resolved after you install Update Rollup 7 for Exchange Server 2007 SP1. If you have not already installed Update Rollup 7, install the update from the link in the “Install Update Rollup 7″ section. However, in some cases this issue may continue to occur after installation of Update Rollup 7.If this situation occurs, you can resolve the problem by configuring two registry entries that are available after you install Update Rollup 7.To configure these registry entries follow the steps in the “More information about Update Rollup 7” section.
Install Update Rollup 7 To enable the two registry entries that help resolve this problem, install Update Rollup 7 for Exchange 2007 Service Pack 1. For more information about Update Rollup 7 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic:
Description of Update Rollup 7 for Exchange Server 2007 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=157083)For more information about how to install the latest Exchange service pack or update rollup, see the following Exchange Help topic:
How to Obtain the Latest Service Pack or Update Rollup for Exchange 2007(http://go.microsoft.com/fwlink/?LinkId=152570)
More information about Update Rollup 7By default, after you install Update Rollup 7 for Exchange Server 2007 SP1, the recurrence search for deep folder search is changed from “unlimited” to a limited value of 50,000. In some circumstances, this value may be too high, and you may still experience a Microsoft Exchange Information Store service crash. However, Update Rollup 7 enables you to use two registry entries to manually change the recurrence search parameters. To do this, follow these steps:Start Registry Editor.Locate and then click the following registry subkey:
HKLM\System\CCS\Services\MSExchangeIS\ParametersSystemCreate or change the value for the following registry entry under the registry subkey, as follows:
Name: Validate Search Folder Restriction
Data type: REG_DWORD
Value data: 1After you change the value for the registry entry, verify that the issue is fixed. If you continue to experience the issue, continue with the remaining steps.In Registry Editor, locate and then click the registry subkey that is mentioned in step 2.Create or change the value for the following registry entry under the registry subkey, as follows:
Name: Search Folder Nesting Level
Data type: REG_DWORD
Value data: 500 (decimal)If you continue to experience the same issue even after the change to the Search Folder Nesting Level registry entry, complete the steps in the “UseIsinteg tool” section.
Notes For the registry changes to take effect, you do not have to do the following:Restart the Microsoft Exchange Information Store service.Restart the Exchange server.Fail over the Exchange server in a clustered environment.Use Isinteg toolIf the Microsoft Exchange Information Store service continues to crash even after the change of values for the two registry entries, you must use the Isinteg tool. To do this, follow these steps.
Note You can run the Isinteg tool from the Drive_Letter:\Program Files\Exchsrvr\bin folder.Identify and unmount the Exchange database that has the problem.Run the Isinteg tool against the database by using the following command:
exchsrvr\bin\isinteg -s Server_Name -fix -test alltestsAfter Isinteg finishes running, view the ISINTEG.pri log file that is created in the MDBDATA folder.Verify that the entry for FIXES is equal to zero. If this entry is not equal to zero, run the Isinteg tool against the database again. You may have to run the Isinteg tool several times until you see that the FIXES entry is equal to zero.

Symptoms
Consider the following scenario:You create a map in a Microsoft BizTalk Server project. The map uses an XSL for Transformations (XSLT) file that is defined inthe Custom XSL Path Grid Properties. The map uses the XSLT fileto transformmessages. You use the map in an orchestration to process messages.In this scenario, messages may be suspended. Additionally, you may receive an error message that resembles the following in the Application log:

Event Type: Error
Event Source: XLANG/s
Event Category: None
Event ID: 10030
Description:Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service ‘BizTalk orchestration’.The service instance will remain suspended until administratively resumed or terminated. If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.InstanceId: instance id
Shape name: shape name
ShapeId: shape id
Exception thrown from: segment number, progress number
Inner exception: Error encountered while executing the transform project name.map name. Error:Unable to create the transform.The “Additional error information” section of the error message contains error information that resembles the following:

Resolving of external URIs was prohibited.
Resolution
This issue can occur if the XSLT file that is definedin the Custom XSL Path Grid Properties uses the<xsl:import> element or the <xsl:include> element to import or to include an external XSLT file.