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: 2207 Source: MSExchangeMTA
| Source: MSExchangeMTA |
| Type: Warning |
| Description: The MTA database recovery operation has completed successfully. Recovery details can be found in the file: C:\exchsrvr\mtadata\.\MTACHECK.OUT\MTACHECK.LOG. [DB Server MAIN BASE 1 67] (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 This problem may occur because the SMTP Protocol is corrupted or is missing. See ME840469 for details on fixing this issue. See ME812993 and MSEX2K3DB for additional information on this event. 
EventID.Net This message occurs when an Exchange server is powered-off without a proper shutdown. See the following articles for more details: ME163292, ME163295 and ME280449.  x
1
|
| Private comment: Subscribers only. See example of private comment |
| Links: ME163292, ME163295, ME280449, ME812993, ME840469, 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!