.NET Questions and Solutions

Symptoms
On a Microsoft Windows XP-, Microsoft Windows Server 2003-, Microsoft Windows Vista- and Microsoft Windows Server 2008-based computer, if you attempt to shutdown the computer when you are running an application that uses the Remote Access Connection Manager, or the Telephony service, the Remote Access Connection Manager or the Telephony service may not be stopped properly and an unexpected error may occur.
In addition, even if you try to stop the Remote Access Connection Manager service or the Telephony service, the following error massage is displayed and the service cannot be stopped.

When running the Remote Access Connection Manager service Windows XP and Windows Server 2003

Cannot stop the Remote Access Connection Manager service on a local computer.
The service did not return an error. This could be an internal Windows error or an internal service error.
If the problem persists, contact your system administrator. On Windows Vista and Windows Server 2008, you cannot click the Stop button once the service is in use and an error message will not be displayed.
When running the Telephony service Windows XP and Windows Server 2003

Cannot stop the Telephony service on a local computer.
Error 1053:The service did not respond to the start or control request in a timely fashion. Windows Vista and Windows Server 2008

Cannot stop the Telephony service on a local computer.
Error 1052:The requested control is not valid for this service.
Resolution
Because the Remote Access Connection Manager or the Telephony service cannot be stopped properly, an application that uses these services may return an unexpected error.

Symptoms
Consider the following scenario: A printer is shared on a computer that is running one of the following:Windows XPWindows Server 2003Windows VistaWindows Server 2008 The “Keep printed documents” option is enabled in the Properties dialog box of the shared printer.Some print jobs stay in the print queue after they are printed.You right-click one of the print jobs and then click Restart to resubmit the print job.In this scenario, the handle count of the print spooler service increases by 1. If the print queue is under heavy stress, the handle count of the print spooler service keeps increasing. Finally, the system may stop responding or crash. Or, another unexpected behavior may occur becausethe resources are exhausted.
Resolution
When a print job is restarted in a print queue, the print spooler service has to create a new EVENT object forsynchronization purposes. However, the print spooler service cannot release a previously created EVENT object before the service creates the new EVENT object. Therefore, a handle leak occurs in the print spooler service.

Symptoms
Consider the following scenario. An orchestration is published as a Web service. The Web service redirects the SOAP request to an external Web service. The external Web service returns a SOAP exception. In this scenario, the negative acknowledgement (NACK) message in Microsoft BizTalk Server 2006 does not contain the details of the original exception. If the hotfix in Microsoft Knowledge Base article 927492 has been installed, the NACK message may be correct. However, the message format may be incorrect. This may cause a NullReferenceException error message.
Resolution
Hotfix information A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or tocreate a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesYou must have BizTalk Server 2006 installed to apply this hotfix.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.File information The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMicrosoft.biztalk.webservices.serverproxy.dll3.5.1714.054,34428-Sep-200717:42×86Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Symptoms
When you use a Collaboration Data Objects (CDO) 1.21-based application to call the Respond method on the parent of a recurring meeting request, the application will throw the following CDO exception:

[MAPI_E_NOT_FOUND (8004010F)]
Resolution
Hotfix information A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or tocreate a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Prerequisites Because of file dependencies, this hotfix requires Microsoft Exchange Server 2003 Service Pack 2.
For more information about the latest service packs for Exchange Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
836993?(http://support.microsoft.com/kb/836993/) How to obtain the latest service packs for Exchange Server 2003Restart requirementYou do not have to restart thecomputer after you apply this hotfix. Hotfix replacement informationThis hotfixdoes not replace any other software updates.File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformCdo.dll6.5.7651.38717,82426-Jul-200616:29×86

Symptoms
An application exception (trap) may occur on the SNA Server computer when you use the Rumba 5.2 TN5250 client to connect to the TN5250 Service. If you have Dr. Watson (Drwtsn32.exe) configured as the default debugger, a Drwtsn32.log file is created in the [NTROOT] directory. The following events are created in the Application event log of the Event Viewer:

Event ID: 5
Source : SNA TN5250 ServerDescription:
The SNA TN5250 Service detected an internal error.
File = ..\shared\tn5tnspm.c
Line = 3477
Fail = ((NB_IPS *)dsi5_data)->buf_size >= ((NB_IPS *)dsi5_data)->ips_length
Parm = 0×0
Event ID: 4097
Source: DrWatson
The application, exe\tn5250.dbg, generated an application error The error occurred on1/25/2000 @ 20:58: 3.406.
The exception generated was 80000003 at address 77f76274 (DbgBreakPoint).The following is an example of the exception in DbgBreakPoint:

Application exception occurred:App: exe\tn5250.dbg (pid=326)When: 1/25/2000 @ 20:58:3.406Exception number: 80000003 (hardcoded breakpoint)function: DbgBreakPointFAULT ->77f76274 ccint377f76275 c3ret77f76276 8bc0moveax,eax
Resolution
To resolve this problem, obtain the latest service pack for SNA Server 4.0. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
215838?(http://support.microsoft.com/kb/215838/EN-US/) How to Obtain the Latest SNA Server Version 4.0 Service Pack

Symptoms
After you configure a Collect Specific Events (Collection) rule in Microsoft Operations Manager (MOM) 2005, the following symptoms occur:The MOM service (MOMservice.exe) stops unexpectedly. If you try to start the MOM service, you receive the following error message:

Could not start the MOM service on Local Computer.Error 1067:The process terminated unexpectedly. The following events are logged in the Application log:
Event Type:Error
Event Source:Microsoft Operations Manager
Event Category: None
Event ID:9014
Date:date
Time:time
User:N/A
Computer: ComputerName
Description: The Microsoft Operations Manager service (MOMService.exe) terminated due to an unhandled exception.Itwill attempt to restart itself.
For more information, see Help and Support Center at<http://go.microsoft.com/fwlink/events.asp>.
Event Type:Error
Event Source:Microsoft Operations Manager
Event Category: None
Event ID:9015
Date:date
Time:time
User:N/A
Computer: ComputerName
Description: The Microsoft Operations Manager service (MOMService.exe) received an unexpected exception.
Thread Id: 0xf40
Thread Name: MSB3904
Exception code: 0×00000000c0000005
Exception description: Access Violation
Exception address: 025EB79C
Exception flags: 0×0
For more information, see Help and Support Center at<http://go.microsoft.com/fwlink/events.asp>.
Resolution
This problem may occur if the Collect Specific Events (Collection) rule is configured to collect security event parameters. In this scenario, the Collect Specific Events (Collection) rule may occasionally collect more parameters than requested. This behavior may cause the MOM service to stop.