|
|
 Cluster
DOS
IBM - AS400
MOM
Performance Counters
Service Broker
 SQL Server
Temporary Database
Views
Backup
SQL Mail
DTS - Data Transformation Services
Memory
Security
Excel
Jobs SQL Agent
MSDE
Install
DBCC
User Management
System Databases
BCV
Deadlocks
Temp Tables
 Find the physical se...
Enable xp_cmdshell
Intermittent Connect...
Connection String Pr...
Login Error ( State)...
Turn Default Tracing...
Re-index fails when ...
SMO AND DMO
Tracing of Errors
Extra carriage Retur...
Query to find Object...
Named Instance Port ...
Adding Domain Login ...
Rename Logical File ...
Error 3624 Delete st...
SQL DMO Error 21776
NetworkConnections
SQL Server Service m...
Trace Flags for Dead...
Change Server Name
Alternate to Count(*...
Windows OS
Will be added as a sub-category of, SQL Server
|
|
Tracing of Errors
|
|
Here is details. Log is at (%systemroot%\temp\microsoft operations manager)
HKLM\Software\Mission Critical Software\TraceLevel.
You can increase the logging level of MOM, if needed, for troubleshooting
purposes. By default, the logging level in MOM is set to collect error data
only (1). However, if the logging level is increased, the volume of data
that is generated can dramatically decrease the performance of MOM. By
default, the MOM Management Pack generates an alert if the logging level is
set to 4 or greater.
The logging level is determined by the value of the following registry key:
HKLM\Software\Mission Critical Software\TraceLevel.
The following table summarizes the logging results based on a range of
possible values.
Table 8 MOM 2005 Logging Levels
Logging level
Logging results
-1
Logging is disabled.
0 or greater
Log error-level data.
3 or greater
Log error and warning data.
6 or greater
Log error, warning, and information data.
9
Log error, warning, information, and debug data.
|
|
|
|
|