.NET Questions and Solutions

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries for May, 2010

Event ID 1010, 1008, 1011, and 4005 with CIM and Perflib

Symptoms
The Windows NT Event Viewer Application log may generate Event ID 1010 logs every two to three seconds. The event description is as follows:

Event ID:1010Source:PerflibDescription:The Collect Procedure for the “SnaServr” service in DLL”C:\SNA\system\snaperf.dll” generated anexception or returnedan invalid status. Performance data returned by counter DLL will be notbe returned in Perf Data Block. Exception or status code returned isDWORD 0. Other related events descriptions that may follow are:

Event ID:1008Source:PerflibDescription:The Open Procedure for service “Tcpip” in DLL “Perfctrs.dll” failed.Performance data for this service will not be available. Status codereturned is DWORD 0.Event ID:1011Source:PerflibDescription:The library file “tapiperf.dll” specified for the “TapiSrv” servicecould notbe opened. Performance data for this service will not beavailable.Status code is data DWORD 0.Event ID:4005Source:perfctrsDescription:Load of INETMIB1.DLL failed. Make sure the DLL file is in the PATH.WIN32 Error number is returned in the data.
Resolution
It has been confirmed that versions earlier than version 3.5 of Compaq’s Insight Manager (CIM) conflict with Performance Counters, thereby causing these errors to occur.

Event 9673 with code 0xc00000fd occurs when the Microsoft Exchange Information Store service crashes on a computer that is running Exchange Server 2007

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.

Errors TF30171 and TF30004 arise during Project Creation

Symptoms
Source: Microsoft Support
Resolution
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION.THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Error when you use the SharePoint Migration Tool to try to restore a Windows SharePoint Services Web site: “Error getting manifest for http://localhost (fatal)”

Symptoms
When you use the Microsoft SharePoint Migration Tool (Smigrate.exe) to try to restore aMicrosoft Windows SharePoint Services 2.0 Web site, the restore operation fails. You also receive the following error message:

Error getting manifest for http://localhost (fatal)Progress: An error occurred accessing your Windows SharePoint Services site files.This issue occurs after you use Smigrate.exeto back up a Windows SharePoint Services 2.0 Web site.
Additionally, when you rename the Backup.fwp file to Backup.cab to view the contents of the backup file, the Manifest.xml file is 0 bytes.
Resolution
This problem typically occurs on Windows SharePoint Server 2.0 Web sites if one of the following conditions is true:The Web sitecontains many lists.The Web site containslists that have large items.The Web site backup contains many files.Note Only file metadata is stored in the Manifest.xml file. The files are exported separately.
During the backup process, two contiguous memory blocks are required to create the Manifest.xml file. The memory blocks must be large enough to accommodate the manifest data. If one sufficient memory block is available to create the Manifest.xml file but a second sufficient block is unavailable, the copy operation fails silently. Then, a Manifest.xml file that is 0 bytes is created.

Error when you try to call the Prepare method before you add parameters: “An unhandled exception of type ‘System.Data.SqlClient.SqlException’ occurred in system.data.dll”

Symptoms
When you create a parameterized command against Microsoft SQL Server 7.0, if you call the Prepare method before you add parameters to the command, you receive the following error message:

An unhandled exception of type ‘System.Data.SqlClient.SqlException’ occurred in system.data.dll.
Additional information: System error. This problem does not occur in SQL Server 2000.
Resolution
This problem occurs in SQL Server 7.0 because, by design, you cannot run the Prepare method before you add parameters. This applies to most database systems.
SQL Server 2000 does not generate the above-mentioned exception because it does not run Prepare until the first command is executed. This optimization prevents the overhead of Prepare if no commands are subsequently executed.

Error messages when you use Live Meeting Intranet Portal: “Exception_1013: The Directory Service returned an exception” and “Inner Exception(1): Index was out of range”

Symptoms
When you use Microsoft Live MeetingIntranet Portal, you may receive the following error messages:

Exception_1013: The Directory Service returned an exception

Inner Exception(1): Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: indexThe call stack trace that is generated when this issue occurs may resemble the following call stack trace:

at System.Collections.ArrayList.get_Item(Int32 index)at System.DirectoryServices.ResultPropertyValueCollection.get_Item(Int32 index)at Microsoft. LiveMeeting.DirectoryService.GetDirectoryUser(AuthenticatedUser authUser)at Microsoft.LiveMeeting.Services.GetDirUser(AuthenticatedUser authUser)
Resolution
This issue occurs if you do not use Microsoft ASP.NET version 1.1.4322.
Additionally, this issue may occur if the Live Meeting Intranet Portal virtual directory is not set to use ASP.NET version 1.x.