.NET Questions and Solutions

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
This article describes critical update 886185. This update helps narrow the definition of the My network (subnet) only, or local subnet, scope option in Windows Firewall. This is helpful in situations where Windows Firewall would consider a large network to be on the local subnet because of how the dial-up software configured the route tables. After you install critical update 886185, you may have to restart your computer.
Resolution
After you set up Windows Firewall in Microsoft Windows XP Service Pack 2 (SP2), you may discover that anyone on the Internet can access resources on your computer when you use a dial-up connection to connect to the Internet. For example, after creating an exception in Windows Firewall for File and Printer Sharing, you may discover that anyone can access shared files and printers.
Note Windows Firewall automatically selects the My network (subnet) only scope option when you create an exception for File and Printer Sharing.

Symptoms
You may find that you cannot create a portal site in Microsoft Office SharePoint Portal Server 2003.When you try to create a portal site, you may experience one or more of the following symptoms: You receive an error message that is similar to the following:

System.NullReferenceException: Object reference not set to an instance of an objectEntries that are similar to the following are logged to the log file:

Time Start- Add custom roles to fine-grained lists
Time End- Add custom roles to fine-grained lists
Time Exit InitCategories()
Time Failed to create portal successfully
Time cmd.CommandText set as: Update dbo.orgle_errormsg set LocalizedMsg = N’User’ where ErrorID=’-1′ Update dbo.orgle_errormsg set LocalizedMsg = N’Target Audiences’ where ErrorID=’-2′ Update dbo.orgle_errormsg set LocalizedMsg = N’Select Audience’ where ErrorID=’-3′ Update dbo.orgle_errormsg set LocalizedMsg = N’Select’ where ErrorID=’-4′ Update dbo.orgle_errormsg set LocalizedMsg = N’Compilation failed to start due to an error connecting to the database. Please check the AudienceJob log file for details.’ where ErrorID=’1′ Update dbo.orgle_errormsg s
Resolution
This issue may occur in situations when there arenetwork connectivity problems that prevent you from connecting to the server that is running Microsoft SQL Server 2000, and the server that is running SQL Server 2000 uses the following configuration:The server is configured to use named pipes.The server is not configured to use TCP/IP.