.NET Questions and Solutions

Symptoms
If you run the command “Net Statistics Server” from a Command Prompt on a Windows Server 2008 system with or without Service Pack 1 or Service Pack 2 installed, the output is displayed as follows:
Server Statistics for \\Computer_Name
Statistics since 1/1/1980 12:00:00 AM
The time stamp “1/1/1980 12:00:00 AM” continues to remain the same even if the server was recently rebooted or the server service on the server was recently restarted.
Resolution
This is a limitation of this command on Windows Server 2008 with or without Service Pack 1 or Service Pack 2. This command gives the desired output on systems running Windows Server 2003, Windows Server 2003 R2 and Windows Server 2008 R2. By contrast, the command “Net Statistics Workstation” gives the desired results on Windows Server 2008 with or without Service Pack 1 or 2.

Symptoms
You experience out of memory exception errors on a Web server that has Microsoft ASP.NET 1.1 installed. ASP.NET 1.1 is installed as part of the Microsoft .NET Framework 1.1 and the Microsoft .NET Framework 1.1 Service Pack 1 (SP1).
Resolution
This problem occurs because the MobileCapabilities object does not expire from the cache as expected. You can use an instance of the MobileCapabilities object to read the capabilities of the requesting browser and device.

Symptoms
When you migrate a Microsoft Transaction Server (MTS) application to COM+, and you do not call the SetComplete or SetAbort method, an Access Violation may occur, and the application may fail (crash). This problem occurs in COM+ (Windows 2000 Service Pack 1) and not in MTS.
Resolution
This problem occurs when non-root transactional objects release the object reference to their parent object and do not call SetComplete or SetAbort explicitly at the end of the method.
This problem is caused by a difference in the activation and deactivation mechanisms between COM+ and MTS. In COM+, if the child object does not set the done bit to true (if it does not call the IObjectControl::SetComplete or the IObjectControl::SetAbort method, does not call the IContextState:setCompletion method, or does not use Auto-Completion), the COM+ interception layer deactivates the parent object before the child object. In fact, you do not need to set the done bit, even if it is preferred in most situations.

Symptoms
The Exchange IMAP4 worker process crashes intermittently on a computer that is running Microsoft Exchange Server 2007. When this problem occurs, an event is logged that resembles the following:

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Description: EventType clr20r3, P1 microsoft.exchange.imap4.exe, P2 8.1.278.2, P3 481f7feb, P4 microsoft.exchange.imap4, P5 8.0.0.0, P6 481f7feb, P7 a6, P8 17, P9 system.nullreferenceexception, P10 NIL.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Resolution
To resolve this problem, install Update Rollup 4 for Exchange Server 2007 Service Pack 1 (SP1) on the Exchange server.For more information about Update Rollup 4 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic:
Description of Update Rollup 4 for Exchange Server 2007 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=152556)For more information about how to obtain 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)

Symptoms
When you run the Set-AttachmentfilterListConfig command together with the -ExceptionConnectors option on an Exchange Server 2007-based server, the command doesnot run successfully. Additionally, an exception is generated.
For example, you may run the following command:
Set-AttachmentfilterListConfig -ExceptionConnectors d18f518a-38e3-4349-9697-bc2ac318461f When you run this command, you receive the following error message:

WARNING: An unexpected error has occurred and debug information is being generated: Unable to cast object of type ‘System.Collections.Generic.List`1[Microsoft.Exchange.Data.Directory.SystemConfiguration.ReceiveConnector]‘ to type ‘Microsoft.Exchange.Data.Directory.SystemConfiguration.ReceiveConnector[]‘. Set-AttachmentfilterListConfig : Unable to cast object of type ‘System.Collections.Generic.List`1[Microsoft.Exchange.Data.Directory.SystemConfiguration.ReceiveConnector]‘ to type ‘Microsoft.Exchange.Data.Directory.SystemConfiguration.ReceiveConnector[]‘. At line:1 char:31 + Set-AttachmentfilterListConfig? <<<< -ExceptionConnectors d18f518a-38e3-4349-9697-bc2ac318461f Additionally, the follow event is logged in the Application log:
Event Type:?Error
Event Source:?MSExchange Common
Event Category:?General
Event ID:?4999
User:??N/A
Computer:?Servername
Description: Watson report about to be sent to dw20.exe for process id: <ID>, with parameters: E12, c-RTL-x86, <version>, powershell, M.E.Management, M.E.M.M.A.SetAttachmentFilterListConfig.InternalProcessRecord, System.InvalidCastException, 4e90, <version>.? ErrorReportingEnabled: False For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Resolution
To resolve this problem, install Update Rollup 2 for Exchange Server 2007 Service Pack 1. For more information about Update Rollup 2 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic:
Description of Update Rollup 2 for Exchange Server 2007 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=152558)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)

Symptoms
In Microsoft Windows Server 2003 with Service Pack 1 (SP1), a program that uses structured exception handling may stop responding for several seconds. Programs that use structured exception handling include Microsoft SQL Server.
Resolution
This problem occurs because Windows Server 2003 SP1 includes a change to the memory manager. This change may make the validation process of exception handling routines take a long time if the following conditions are true:The computer has lots of physical RAM.The process loader lock is held by one thread.Multiple exceptions occur at the same time.In these conditions, several threads wait for the memory manager, and the program stops responding for several seconds.