Event ID/Source search
Keyword search
Example: Windows cannot unload your registry file
EvLog 3.0 – Monitor an unlimited number of servers with $49/year
With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of them. If ten years ago it was still common to see an entire company using just one server, these days that's no longer the case.New computers are added to the network with the understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers.
read more...
Event ID: 2171 Source: MSExchangeMTA
| Source: MSExchangeMTA |
| Type: Warning |
| Description: An MTA database server error was encountered while reading an attribute. Called from PLATFORM. Procedure: 142. Database error code: 2110. Object at fault: 0600045A. Attribute identifier: 2. Value number: 1. Referenced object: 06000454 (00000000 => N/A). Referenced object error 2110. [DB Server RTSE 31 26] (14) |
| English: Request a translation of the event description in plain English. |
| Concepts to understand: What is the role of the Exchange MTA Service? |
| Comments: EventID.Net As per Microsoft: "This issue can occur if one or more .dat files from the \Exchsrvr\MTAData (MTA Database) directory are missing when you attempt to start the MTA". See ME274285 and MSEX2K3DB for details on this problem. If the Mtacheck utility is run against a database that was not shut down properly, Mtacheck deletes files that are greater than Db007fff.dat file, and when the MTA starts, it logs this event. See ME271600 for details on this issue. See ME157214 for additional information about this event. 
EventID.Net Apply the latest service pack. Don't stop any services before updating. There are several Microsoft articles with information about this event: ME159305, ME165093, ME177886, ME193049, ME253718.
Elliott Fields Jr This is caused by bad or corrupt .dat files (message) in the MTADATA directory. See ME231685 for details on correcting this issue.
|
| Private comment: Subscribers only. See example of private comment |
| Links: ME157214, ME159305, ME165093, ME177886, ME193049, ME231685, ME253718, ME271600, ME274285, MSEX2K3DB |
| Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... |
| Feedback:
Send comments or solutions
- Notify me when updated
|
| Printer friendly |
Subscribe to EventID.Net now!