Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 1000 Source: MicrosoftManagementConsole

The description for Event ID ( 1000 ) in Source ( Microsoft Management Console ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: mmc.exe 5.2.3790.3959 kernel32.dll 5.2.3790.4062 000000000000dd10.
This event is typically recorded when the following error message is show when MMC is used:

Appname MMC.exe      Appver: 5.2. 3790. 3959    Modename: kernal32.dll
Modever: 2. 5. 3790. 4062          Offset: 000000000000dd10

This provides some details about what the data recorded in the event means (the name of the application that crashed, its version, the module that was involved in the crash and its version and the memory offset where the crash happened).
In my case, I renamed the file dsa.msc to dsa1.msc and the problem was gone.
I found a small workaround that may or may not work for you. For reasons unknown to me the shortcut that is placed in Administrative Tools does not have "Domain Admins" in the security tab. I simply added them and gave them full control over the shortcut and now everything works without problems.
I also had this problem when trying to run the Exchange 2007 Managment Console. It turned out to be a memory issue. The Backup exec remote agent was using all the memory. Once I stopped this service the memory was freed up and all was ok.
To resolve the problem:
1 - Click Start -> Run and Type "mmc -32 dsm.msc". This will open the ADU&C Console
2 - Click View
3 - Click Add/Remove Columns
4 - Click Restore Defaults
5 - Click Ok.

Re-open the console with the standard shortcut. This worked for me.

This seems to be a bug in Windows 2003 R2 x64. I could not open Active Directory Users and Computers with the Administrators account (I would get an error message). I could open it from a MMC snap-in as well as with other user accounts with sufficient permissions. This event was logged each time I attempted to open Active Directory Users and Computers (I also received a low virtual memory error).
Open ADU&C using "mmc -32 dsa.msc" from the run command. Then open AD users and computers like you normally would. This seemed to fix it.
Came across the solution on a very unrelated discussion thread and tried it. I have no idea why this workaround worked or what was causing the original problem.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to



Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.