.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 Tagged ‘event’

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.

Description of the Outlook 2007 hotfix package: June 12, 2007

Symptoms
This article describes the Microsoft Office Outlook 2007 issues that are fixed in the Outlook 2007 hotfix package that is dated June 12, 2007.
This article describes the following items about the hotfix package:The issues that the hotfix package fixes.The prerequisites for installing the hotfix package.Whether you must restart your computer after you install the hotfix package.Whether the hotfix package is replaced by any other hotfix package.Whether you must make any registry changes. The files that the hotfix package contains.
Resolution
Issues that the hotfix package fixesThis hotfix package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:You try to open a user’s shared calendar in Outlook 2007. If the user’s mailbox is in a different administrative group, the shared mailbox cannot be synchronized correctly. Additionally, an eventthat resembles the following event is logged in the Application log:
Event Type:Warning
Event Source:MSExchangeSA
Event Category:RFR Interface
Event ID:9234
Date:date
Time:time
User:N/A
Computer:server_name
Description: Referral Interface was not able to find an msExchExchangeServer object with legacyExchangeDN ‘/o=Organization_Name/ou=Exchange Administrative Group (group)/cn=Configuration/cn=Servers/cn=server_name’ in the Active Directory.You use a custom solution in a trusted simple MAPI environment to send e-mail messages in Outlook 2007. If an e-mail message contains more than five recipients, the e-mail aliases are not resolved. Additionally, the Outlook security dialog box unexpectedly appears. You have multiple appointments scheduled for a day in the calendar in Outlook 2007. When you print the calendar in Monthly style, only two appointments are printed for the day.
This issue may occur even though there is sufficient room for all the appointments to print for that day. A delegate for your mailbox accepts a meeting request on your behalf. Then,the meeting is updated. When you view the updated meeting request, the No response required button is not displayed. As meeting requests and meeting updates are processed in Outlook, the tracking status and the attendee changes for the meeting requests may cause new style conflicts.
When this issue occurs, the tracking status and the attendee changes are not updated automatically. Therefore,many items may be added to the “Sync Issues” folder and to the Conflicts folder. You send a meeting request that contains anattendee to which youcannot send requests, such as a meeting room. When you reopen the meeting request, the free/busy time for this attendee is not displayed. You send a recurring meeting request to attendees. Then, you update the meeting time for the recurring meeting and then send the update. When you reopen the recurring meeting, the meeting time reverts to the original meeting time. You open a second instance of a recurring meeting. Then, you update the recurring meeting and then send the update. When you do this, the meeting update is sent as expected. However, the changes to the meeting are not saved. You accept an all-day event request. Then, youschedule another all-day event that spans the same times as theall-day event that you accepted. When you switch between events, theevent that you scheduled may disappear. When you switch to the accepted event and then switch back to the scheduled event, the scheduled event reappears.You delete attendees from a recurring meeting and then send the meeting update. When you do this, the update is sent to all attendees. This includes the deleted attendees. You create a meeting exception for a recurring meeting. Then, you restart Outlook and then open the meeting exception. When you do this, the body of the exception message is blank. You are the organizer of a recurring meeting. When you open the recurring meeting, the meeting opens as a Send Cancellation action. You accept a meeting request in Cached Exchange Mode. When you do this, the meeting request is deleted and the meeting acceptance is not sent. Additionally, you may receive the following error message:

Cannot save free/busy information.You create a meeting exception for a recurring meeting. Then,you reopen the meeting exception. When you do this,one of the following symptoms may occur: If the body of the recurring meeting message is small, the body of theexception message is now large.If the body of the recurring meeting message is large, the body of the exception message is now blank.Note A large message body for a personal folders (.pst) file is 8 kilobytes (KB) or larger.When you try to propose a new time for a meeting request, you receive the following error message:

The end date you entered occurs before the start date.You change an existing meeting request. When you click Save and Send Update, the changes to the meeting request are sent as expected. However, the meeting request closes unexpectedly.

BUG: “0×80070057 (E_INVALIDARG – The parameter is incorrect)” error message when you use an ATL to catch an event when an enum is used as a parameter of the event

Symptoms
An ATL event sink defined with SINK_ENTRY or SINK_ENTRY_EX will fail to catch an event when an enum is used as one of the parameters for the event. The failure code returned by IDispatch::Invoke is “0×80070057 (E_INVALIDARG – The parameter is incorrect).” The event will succeed in another container, such as Visual Basic.
Resolution
IDispEventImpl’s GetFuncInfoFromID method checks the type of the event parameters and, on encountering type VT_USERDEFINED, calls GetUserDefinedType. This method currently checks only for TKIND_ALIAS (“typedef struct” data types) and not TKIND_ENUM.

Application Exception When AppleTalk Clients Try Connecting

Symptoms
The SNA Server stops responding (hangs) and Appletalk client computers areunable to attain session connections. In the Event Viewer, the followingapplication events appear:

Event ID: 624
Source: SNADUMP.LOG
Description: A process SNABASE.EXE ended abnormally due to a protectionviolation, or similar condition.
Event ID: 4097
Source: Dr. Watson Log
This application, SNABASE.DBG generated an applicaiton error. The error
occurred on <date>. The exception generated was C0000005 at address <address>.A portion of the DRWTSN32.LOG file states the following:

App: snabase.DBG (pid=160)When: <date> @ <time>Exception number: c0000005 (access violation) NOTE: Your DRWTSN32.LOG file will appear somewhat different than thisexample.
Resolution
The SNAAT.DLL send routine is not checking to see if the L-Table is alreadyin a closing state. Therefore, it tries to access its pending queue, whichhas been released. This causes the application exception in SNABASE.EXE.

Although the MSSQLServer service does not stop, there is a “The MSSQLServer service terminated unexpectedly” Critical Error severity alert in the Microsoft Operations Manager 2005 Operator Console

Symptoms
Although the MSSQLServer service does not stop, the Microsoft Operations Manager (MOM) 2005 Operator Console contains a Critical Error severity alert that is similar to the following alert:

Name: The MSSQLServer service terminated unexpectedlySeverity: Critical ErrorResolution State: NewDomain: WORKGROUPComputer: ComputerNameTime of First Event: TimeTime of Last Event: TimeAlert latency: 1 secProblem State: InvestigateRepeat Count: 3Age:Source: MSSQLSERVERAlert Id: 390da845-d0c7-4570-b895-cb265d13addaRule (enabled): Microsoft SQL Server\SQL Server 2000\SQL Server 2000 Event Collection\SQL Server General\The MSSQLServer service terminated unexpectedlyDescription: SqlDumpExceptionHandler: Process 56 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
Resolution
This issue occurs when the following conditions are true: You enable the The MSSQLServer service terminated unexpectedly event rule. This event rule has the following criteria in the MOM 2005 Administrator Console: The Event Number event property matches the following code:

regex ^(17052|17055)$The Source Name event property matches the following code:

wildcard MSSQL*The Description event property matches the following code:

substring Error: 0, Severity: 19, State: 0You receive an error message that has a severity level 19 in Microsoft SQL Server 2000 that is similar to the following error message:

ODBC: Msg 0. Level 19, State 1SqlDumpExceptionHandler: Process 56 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.Connection Broken

Access Violation in PerfMgr Thread

Symptoms
The Microsoft Operations Manager (MOM) OnePointService stop working because there is an access violation in the Performance Manager (PerfMgr) thread on MOM agents. The service attempts to restart but it may or may not succeed. The following two events are typically logged in the Application event log if you experience this problem:

Event ID: 9015Event Type: ErrorEvent Source: OnePoint OperationsDescription:The Microsoft Operations Manager 2000 service (OnePointService.exe) received an unexpected exception. Thread Name: PerfMgr Exception code: 0xc0000005 Exception description: Access Violation Exception address: 77DF7D88

Event ID: 9014Event Type: ErrorEvent Source: OnePoint OperationsUser:NT AUTHORITY\SYSTEMDescription:The Microsoft Operations Manager 2000 service (OnePointService.exe) terminated due to an unhandled exception.It will attempt to restart itself.If the “Thread Name”, “Exception code”, and the “Exception address” match these errors, you are most likely affected by this issue. Also, the OnePointService log file may log entries that are similar to the following entries:

“12015“`0`3044`39`1`PerfMgr`PerformanceManager::execute`236775672`29425836“Event logging is disabled (this is normal for GUIs).Suppressed logging of event 9015(Error) args = “0xbe4″ “0×00000000c0000005″ “Access Violation” “77DF7D88″ “0×0″ “PerfMgr” “12016“`0`3044`39`1`PerfMgr`PerformanceManager::execute`236775672`29425836“Event logging is disabled (this is normal for GUIs).Suppressed logging of event 9014(Error) args = “12017“`0`3044`39`0`PerfMgr`PerformanceManager::execute`236931925`29425836“}PerformanceManager::execute: exiting.“12018“`0`3044`39`0`PerfMgr“239275720`29425836“VERIFY FAILURE:T:\Dev\EEM\V3\Ship\Providers\PerfProvider\PerformanceManager.cpp(51): Destroying mutex locked at this location!After you receive these errors, the OnePointService service may appear to be running when it stops responding (hangs). To recover from this, you must restart the computer.
Resolution
This problem occurs because there is a timeout issue when the PerfMgr thread requests performance data from the computer.