.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 November, 2011

An event may be logged after you restart Windows Server 2008: “Event ID: 5 Message: The Virtual Storage Filter Driver is disabled through the registry. It is inactive for all disk drives”

Symptoms
After you restart Windows Server 2008, the following event may be logged in the System log:

Log Name:System
Source:storflt
Event ID:5
Level:Warning
Task Category:None
Message:The Virtual Storage Filter Driver is disabled through the registry. It is inactive for all disk drives.
Resolution
This event is logged when one of the following scenarios is true:The virtual storage filter driver cannot attach to the virtual storage device. The virtual storage filter driver is included in Windows Server 2008. This driver optimizes the performance of disk I/O if Windows Server 2008 is running on a Microsoft Hyper-V Server.Windows Server 2008 is installed as the host operating system or as the guest operating system before the most recent version of Hyper-V Server is installed.

An End User Defined Character (EUDC) font that was created in Windows XP cannot be deployed to a Windows Vista-based computer or to a Windows Server 2008-based computer

Symptoms
Consider the following scenario:You are running a Windows XP-based computer.You create an End User Defined Character (EUDC) font.You deploy the EUDC font to a Windows Vista-based computer or to a Windows Server 2008-based computer. In this scenario, you cannot enter the EUDC characters by using the Pinyin (phonetic) Input Method Editor (IME) or the Changjie IME.
This issue also occurs if you upgrade a Windows XP-based computer to Windows Vista.
Resolution
This problem occurs because the format ofEUDC-related files in Windows Vista differs from the format of EUDC-related files in Windows XP. Therefore, the EUDC-related files that were created in Windows XP are notrecognized, and they cannot be automatically migrated to Windows Vista.

An application that uses the ADO interface may malfunction, or data loss may occur when the application connects to SQL Server in Windows Vista, in Windows XP, or in Windows Server 2008

Symptoms
Consider the following scenario:An application connects to one of the following products: Microsoft SQL Server 2005 Microsoft SQL Server 2005 Express EditionMicrosoft SQL Server 2000SQL Server Desktop Engine (also known as MSDE 2000)The application uses the SET NOCOUNT ON statement for the connection. The application uses a Microsoft ActiveX Data Objects (ADO) client-side cursor toinsert a row into a table that has an identity column. When the application queries the identity column value of the newly inserted row, the value “0″ is returned incorrectly. When this value is returned, an application that uses the ActiveX Data Objects (ADO) interfacemay malfunction, or data loss may occur. Whether a malfunction or data loss occurs depends on how the application handles this scenario.
Note This problemoccurs only if the application uses a client-side cursor. If the application uses a server-side cursor, the application is not affected.
This problem occurs in the Microsoft Data Access Components (MDAC) components of the following Windows operating systems: Windows Vista Service Pack 1 (SP1)Windows XP Service Pack 2 (SP2) with hotfix 940569 Windows XP Service Pack 3 (SP3) Windows Server 2008
Resolution
To resolve this issue, install the hotfix that is described in the following Microsoft Knowledge Base article:
961451?(http://support.microsoft.com/kb/961451/) FIX: You receive an incorrect value when you query the last-inserted identity value after you use a client-side cursor to insert data to a table that contains an identity column in an application that uses ActiveX Data ObjectsNote The hotfix that was described in the “Resolution” section in the earlier version of this article is superseded by the hotfix that is described in 961451.