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: 9095 Source: MSExchangeSA
| Source: MSExchangeSA |
| Type: Error |
| Description: The MAD Monitoring thread was unable to connect to WMI, error <error#>. |
| English: Request a translation of the event description in plain English. |
| Concepts to understand: What is the role of the Microsoft Exchange System Attendant (MSExchangeSA) service? What is WMI? |
| Comments: EventID.Net For error 0x80041006: if there is a running antivirus on the Exchange server, ensure that it's NOT scanning the M drive. If that doesn't resolve the issue, remove the antivirus (especially if it's for Exchange), you'll notice that the issue goes away. The VAPI driver for exchange was updated in E2K SP2, you may need to contact the vendor for an update for your antivirus product to correct the issue.  x
3
|
| Private comment: Subscribers only. See example of private comment |
| 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!