.NET Questions and Solutions

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.

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
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.

Symptoms
When you try to start theSearch service in Microsoft Office SharePoint Server 2007, you receive the following error message:

An unhandled exception occurred in the user interface. Exception Information: OSearch (AccountName) In this error message, AccountName is the account name that is used as the Farm Search Service account.
Resolution
This behavior occurs ifyou do not use the “domain_name\user_name” format when enter an account namein the User name field.This field isnext to Farm Search Service Account on the Configure Office SharePoint Server Search Service Settings on server ServerName page.