Netcool/Impact 7.1.0 Fix Pack 8: SNMPGetAction PolicyProcessingException: Lexical error

Upgrade to Impact 7.0.1.8 reports error with Policy using SNMPGetAction function:

ERROR [PolicyManagerController] Failed to trigger policy ” PolicyName “. Please refer to server log for more information about the error.com.micromuse.response.common.soap.SoapResponseServerException: com.micromuse.response.common.PolicyProcessingException: Lexical error at line n, column n. Encountered: “_” (n), after : “” in PolicyName
Can one use underscores in MIBs?

Related:

An interoperability error occurred. Primitive related error reported by directory name, error code: error code. Contact Microsoft Technical Support. [valuevaluevaluevalue] (14)

Details
Product: Exchange
Event ID: 4285
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: An interoperability error occurred. Primitive related error reported by directory name, error code: error code. Contact Microsoft Technical Support. [valuevaluevaluevalue] (14)
   
Explanation
The diagnostics logging levels of the message transfer agent (MTA) interface and interoperability categories should be increased to create interoperability logs.

These logs are text logs that consist of the binary contents of communication among MTAs in different sites and between MTA and client applications within a site. They are stored in the \Exchsrvr\Mtadata directory. The current log is always named Bf0.log. Prior logs are named Bfx.log, where x increases as the age of the log increases.

   
User Action
To help Microsoft Product Support Services track down the problem, create log files. For more information, see Knowledge Base articles Q163032 and Q168906.

To create Ap*.log files, in the Diagnostics Logging tab of the Server Properties dialog box, select MSExchangeMTA and set the logging level of the Interoperability and Interface categories to Maximum.

To create Bf*.log files, set the logging level of the APDU and X.400 Service categories to Maximum.

Save all MTA log files (mtadata\*.log), Event Viewer output, and database files. Contact Microsoft Product Support Services

You can enable text event log files (Ev*.log) by modifying the Registry. Contact Microsoft Product Support Services for assistance

Related:

A service specific error occurred: %1.

Details
Product: Windows Operating System
Event ID: 3547
Source: System
Version: 5.0
Symbolic Name: APE_ServiceSpecificError
Message: A service specific error occurred: %1.
   
Explanation

A service-specific error occurred.

   
User Action

Refer to the Help or documentation for that service to determine the problem.

Related:

The computer has rebooted from a bugcheck. The bugcheck was: %1. A dump was saved in: %2.

Details
Product: Windows Operating System
Event ID: 1001
Source: Save Dump
Version: 5.2
Symbolic Name: EVENT_BUGCHECK_SAVED
Message: The computer has rebooted from a bugcheck. The bugcheck was:
%1.
A dump was saved in: %2.
   
Explanation

The computer has restarted from a bugcheck. The event log contains details about the cause of the bugcheck.

   
User Action

If an error report was generated for this error, you might be able to obtain more information about the error by sending the report to Microsoft for analysis.

What to expect

Microsoft actively analyzes all error reports and prioritizes them based on the number of customers affected by the error signature contained in the report. When a report is submitted, Microsoft will try to determine the cause of the error, categorize it according to the type of issue encountered, and send you relevant information when such information is available. However, because error reports do not always contain enough information to positively identify the source of the issue, Microsoft may might need to collect a number of similar reports from other customers before a pattern is discovered. Although Microsoft might not be able to provide a solution for your particular error at this time, all information submitted is used to further improve the quality and reliability of our products.

Related:

An MTA database server error was encountered. The object object name could not be rolled out to disk due to a disk error. Database error code: error code. [valuevaluevaluevaluevalue] (14)

Details
Product: Exchange
Event ID: 2151
Source: MSExchangeMTA
Version: 6.5.0000.0
Message: An MTA database server error was encountered. The object object name could not be rolled out to disk due to a disk error. Database error code: error code. [valuevaluevaluevaluevalue] (14)
   
Explanation
The Microsoft Exchange Server disk may be full or a disk error may have occurred. The message transfer agent (MTA) service will stop if the disk is full.
   
User Action
If the Microsoft Exchange Server disk is full, delete any unnecessary files. If you suspect a disk error, run Chkdsk.

Verify that the \Exchsrvr\Mtadata directory exists. Stop and restart the MTA service. If the error persists, run the Mtacheck.exe utility. Stop the MTA service, open a command prompt, and type Mtacheck/v /f c:\mta.txt.

If Mtacheck removes objects from a database queue, it places each damaged object in a Db*.dat file in \Exchsrvr\Mtadata\Mtacheck.out. Contact Microsoft Product Support Services for assistance.

Related:

An error occurred.Function name or description of problem: Error:

Details
Product: Exchange
Event ID: 1233
Source: MSExchangeIS
Version: 6.5.6940.0
Component: Microsoft Exchange Information Store
Message: An error occurred.Function name or description of problem: <name>Error: <error code>
   
Explanation

This is a generic event id that is generated when an error occurs in the Microsoft Exchange Information Store service. Often it is related to permissions.

   
User Action

Check for other MSExchangeIS events in the event log. Additionally, note the following:

  • The database that had the problem.
  • The function name or problem description.
  • The error code.

Search the Microsoft Knowledge Base for the description and error code. Contact Microsoft Product Support Services.

Related:

Reporting queued error: faulting application %1, version %2, faulting module %3, version %4, fault address 0x%5.

Details
Product: Windows Operating System
Event ID: 1004
Source: Application Error
Version: 5.2
Symbolic Name: ER_QUEUEREPORT_LOG
Message: Reporting queued error: faulting application %1, version %2, faulting module %3, version %4, fault address 0x%5.
   
Explanation

The indicated program stopped unexpectedly. The message contains details on which program and module stopped. A matching event with Event ID 1001 might also appear in the event log. This matching event displays information about the specific error that occurred.

   
User Action

If an error report was generated for this error, you might be able to obtain more information about the error by sending the report to Microsoft for analysis.

What to expect

Microsoft actively analyzes all error reports and prioritizes them based on the number of customers affected by the error signature contained in the report. When a report is submitted, Microsoft will try to determine the cause of the error, categorize it according to the type of issue encountered, and send you relevant information when such information is available. However, because error reports do not always contain enough information to positively identify the source of the issue, Microsoft may need to collect a number of similar reports from other customers before a pattern is discovered. Although Microsoft might not be able to provide a solution for your particular error at this time, all information submitted is used to further improve the quality and reliability of our products.

Related: