Tag: Event 1001

Event ID 1001 — DNS Server Service Status

PCIS Support Team Leave a comment

Event ID 1001 — DNS Server Service Status

Updated: November 13, 2007

Applies To: Windows Server 2008

The DNS Server service responds to requests from DNS client computers for name resolution services. Domain Name System (DNS) is a protocol that enables a computer to obtain the numeric IP address of another computer by submitting the target computer’s name to a DNS server. Problems with the DNS Server service can cause network performance to degrade or even prevent network computers from being able to locate each other.

Event Details

Product: Windows Operating System
ID: 1001
Source: Microsoft-Windows-DNS-Server-Service
Version: 6.0
Symbolic Name: DNS_EVENT_FILE_NOT_MAPPED
Message: The DNS server could not map file %1 to memory. Either close other applications that are not in use or reboot the computer to reclaim additional memory for the server to use.

Resolve
Free memory or other system resources

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Close any unnecessary applications or services, and then try the operation again.

If the operation fails again, restart the DNS Server service.

To restart the DNS Server service:

  1. On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager.
  2. In the console tree, double-click Roles, double-click DNS Server, and then double-click DNS.
  3. Right-click the DNS server, click All Tasks, and then click Restart.

If the problem continues, restart the computer and then use Server Manager to verify that the DNS Server service has started.

To restart the computer:

  • Click Start, click the arrow next to the Lock button, and then click Restart.

To verify that the DNS Server service has started:

  1. On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager.
  2. In the console tree, expand Roles, and then click DNS Server.

The System Services list shows the state of the DNS Server service.

If the problem persists, one or more applications running on the server might be causing memory problems.

Verify

To verify that the DNS Server service is running properly, ensure that the DNS Server event log contains Event ID 2 and that the event log does not contain the following Domain Name System (DNS) error events:

  • 111
  • 403-407
  • 1001
  • 3151-3153
  • 6533
  • 7502-7504

Related Management Information

DNS Server Service Status

DNS Infrastructure

Related:

Event ID 1001 — Network PnP Device Installation

PCIS Support Team Leave a comment

Event ID 1001 — Network PnP Device Installation

Updated: January 7, 2009

Applies To: Windows Server 2008 R2

Plug and Play Extensions (PnP-X) enables a computer to discover networked devices and install them on the local system using Plug and Play (PnP). In Windows Vista and Windows Server 2008, PnP-X allows network-connected devices to be discovered and installed on a client computer as if they were connected physically. A device driver is installed in the Windows operating system to support the detected device.

 

Event Details

Product: Windows Operating System
ID: 1001
Source: Microsoft-Windows-IPBusEnum
Version: 6.1
Symbolic Name: deviceremove
Message: The network device %1 was successfully removed from this computer.

Resolve

This is a normal condition. No further action is required.

Related Management Information

Network PnP Device Installation

Networking

Related:

Event ID 1001 — Windows Installer Application Installation

PCIS Support Team Leave a comment

Event ID 1001 — Windows Installer Application Installation

Updated: December 11, 2007

Applies To: Windows Server 2008

Microsoft Windows Installer is used to install applications on a computer.

Event Details

Product: Windows Installer – Unicode
ID: 1001
Source: MsiInstaller
Version: 4.0
Symbolic Name: EVENTLOG_TEMPLATE_DETECTION
Message: Detection of product ‘%1’, feature ‘%2’ failed during request for component ‘%3’

Resolve
Review the system log file

Microsoft Windows Installer encountered an error while installing, updating, or removing an application. For more information about the error, you will need to open Event Viewer and examine the System log file.

To review the system log file for Windows Installer events:

  1. Click Start, point to Administrative Tools, and then click Event Viewer.
  2. In the navigation pane, find the System event log.
  3. In the Actions pane, click Filter current log…
  4. In the Filter Current Log dialog box, select the Filter tab and then select MsiInstaller from the Event Sources drop-down.
  5. Review the most recent Windows Installer events to determine the cause of the issue. In addition to the Windows Installer events, you should also review the other system events to determine if a related issue may be the cause of the Windows Installer error.
  6. If you cannot resolve the issue based on the information in the event log, try reinstalling the application.

Note: If Windows Installer logging is not enabled, no information will be available in Event Viewer. For more information about Windows Installer logging, see http://support.microsoft.com/kb/223300.

Verify

You can use Programs and Features to verify an application is installed, uninstall applications, and change the application’s configuration by adding or removing options. If the application is not listed, it may not be configured properly or written for a different version of Windows. Reinstalling the application may resolve a configuration problem. To reinstall the application, consult the information that came with the application.

To verify the application is installed:

  1. Click Start, and then click Control Panel.
  2. Double-click Programs and Features.
  3. Verify the application appears in the list of installed programs.

Note: Only applications that are written for Windows will appear in Programs and Features. If you don’t see the application listed and you want to uninstall the application, check the information that came with your software, or go to the manufacturer’s website. Most programs install themselves in the C:\Program Files folder. Check this folder because some programs also include an uninstall program that you can use to remove the software.

Related Management Information

Windows Installer Application Installation

Windows Installer Service

Related:

Microsoft Exchange couldn’t read the server configuration. The service will be stopped.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 1001
Source: MSExchange Message Security
Version: 8.0
Symbolic Name: ReadServerConfigFailed
Message: Microsoft Exchange couldn’t read the server configuration. The service will be stopped.
   
Explanation

This Error event indicates that a Microsoft Exchange server cannot read the server configuration information. The Microsoft Exchange Transport service will be stopped.
   
User Action

To resolve this error, do one or more of the following:

  • If this error occurs on a Hub Transport server, verify that the Exchange server object exists in the Active Directory directory service.

  • If this error occurs on an Edge Transport server, verify that the Exchange server object exists in the Directory Application Mode (ADAM) directory service.

  • Restart the Microsoft Exchange Transport service.

  • Review other related Error and Warning events in the Application log. These related events may help you find the root cause of this error.

  • If the recommended steps do not resolve this error, contact Microsoft Customer Support Services. For more information about how to contact support, visit the Microsoft Help and Support Web site.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

An error occurred while loading the configuration for the Journaling agent. The configuration may be corrupt, or the Active Directory directory service may be down or unreachable. The last known good configuration will be used, and the Journaling agent will attempt to read the configuration again later.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 1001
Source: MSExchange Messaging Policies
Version: 8.0
Symbolic Name: JournalingRulesConfigurationLoadError
Message: An error occurred while loading the configuration for the Journaling agent. The configuration may be corrupt, or the Active Directory directory service may be down or unreachable. The last known good configuration will be used, and the Journaling agent will attempt to read the configuration again later.
   
Explanation

This Error event indicates that configuration information for the Journaling agent is invalid or corrupted. The configuration information for the Journaling agent is stored in Active Directory.

Note   For more information about the Journaling agent, see Overview of Journaling in the Exchange 2007 Online Help.
   
User Action

To resolve this error, follow one or more of these steps:

  • Make sure that Exchange server that logged this event can communicate with one or more Active Directory servers available in the organization.

  • Increase the diagnostic logging level on the Journaling counter of the MSExchange Messaging Policies performance object. You can increase logging by running the following Exchange Management Shell command:

    Set-EventLogLevel “MSExchange Messaging Policies\Journaling” -Level High

For more information about increasing logging, see Changing Process Logging Levels.

  • Review other related Error and Warning events in the Application log. These related events may help you find the root cause of this error.

    Important   After you have completed troubleshooting this issue, return logging to the default level by running the following command:

    Set-EventLogLevel “MSExchange Messaging Policies\Journaling” -Level Lowest

  • If the recommended steps do not resolve this error, contact Microsoft Customer Support Services. For more information about how to contact support, visit the Microsoft Help and Support Web site.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

The computer has rebooted from a bugcheck. The bugcheck was: %1. A dump was saved in: %2.

PCIS Support Team Leave a comment
Details
Product: Windows Operating System
Event ID: 1001
Source: Save Dump
Version: 5.2
Symbolic Name: EVENT_BUGCHECK_SAVED
Message: The computer has rebooted from a bugcheck. The bugcheck was:
%1.
A dump was saved in: %2.
   
Explanation

The computer has restarted from a bugcheck. The event log contains details about the cause of the bugcheck.
   
User Action

If an error report was generated for this error, you might be able to obtain more information about the error by sending the report to Microsoft for analysis.

What to expect

Microsoft actively analyzes all error reports and prioritizes them based on the number of customers affected by the error signature contained in the report. When a report is submitted, Microsoft will try to determine the cause of the error, categorize it according to the type of issue encountered, and send you relevant information when such information is available. However, because error reports do not always contain enough information to positively identify the source of the issue, Microsoft may might need to collect a number of similar reports from other customers before a pattern is discovered. Although Microsoft might not be able to provide a solution for your particular error at this time, all information submitted is used to further improve the quality and reliability of our products.

Related:

The UM worker process (UMWorkerProcess.exe) was unable to start. More information: %1.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 1001
Source: MSExchange Unified Messaging
Version: 8.0
Symbolic Name: UMWorkerProcessStartFailure
Message: The UM worker process (UMWorkerProcess.exe) was unable to start. More information: %1.
   
Explanation

This Error event indicates that the Microsoft® Exchange Unified Messaging Worker Process (UMWorkerProcess.exe) was unable to start on the computer that is running the Unified Messaging server role. This event may be caused by one or more of the following:

  • A SocketException occurred when the UM Worker Process allocated a socket from the operating system. The socket is used by the UM server to perform network communications with the IP/VoIP gateway.

  • The Globcfg.xml or UMconfig.xml configuration data file does not exist. The default location is C:\Program Files\Microsoft\Exchange Server\bin.

  • The directories that store the UMconfig.xml configuration data file, speech grammar files, or the prompt files do not exist.

  • There are initialization failures on the fax subsystem. The fax service loads the fax service provider to create and initialize the virtual fax devices. The devices are used by the UM server to receive faxes.

  • The finite state computer files, for example, Logon.fsm, Fax.fsm, and DtmfMainMenu.fsm, do not exist. Alternatively, an exception occurred when the files were being loaded. The UMConfig.xml file contains references to the name of all the finite state computer files.

  • The semaphore object that the UM Worker Process tries to access does not exist or the access is denied. Semaphore object is an operating system object that is used to control access to a pool of shared resources.
   
User Action

To resolve this error, do one or more of the following:

  • Replace the missing Globcfg.xml or UMconfig.xml with the default files that are located in the \Setup\Server Roles\Common folder of the Exchange 2007 CD. The default location to replace these files on your UM server is C:\Program Files\Microsoft\Exchange Server\bin.

  • Make sure that the directory exists that stores the UMconfig.xml configuration data file, speech grammar files, or the prompt files. The default location for the UMconfig.xml is C:\Program Files\Microsoft\Exchange Server\bin. The default location for the speech grammar files is C:\Program Files\Microsoft\Exchange Server\UnifiedMessaging\grammars\<language>. The default location for the prompt files is C:\Program Files\Microsoft\Exchange Server\UnifiedMessaging\prompts\<language>. The locations for the files are defined in Globcfg.xml.

  • Replace the missing finite state machine files (*.fsm) with the default files that are located in the \Setup\Server Roles\Common folder of the Exchange 2007 CD. The default location to replace these files on your UM Server is C:\Program Files\Microsoft\Exchange Server\bin.

  • If this error frequently occurs, contact Microsoft Product Support. For more information, visit the Contact Us page of the Microsoft Help and Support Web site.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

The SNMP Service has started successfully.

PCIS Support Team Leave a comment
Details
Product: Windows Operating System
Event ID: 1001
Source: SNMP
Version: 5.2
Symbolic Name: SNMP_EVENT_SERVICE_STARTED
Message: The SNMP Service has started successfully.
   
Explanation

The Simple Network Management Protocol (SNMP) service is now running.
   
User Action

No user action is required.

Related:

Fault bucket %1.

PCIS Support Team Leave a comment
Details
Product: Windows Operating System
Event ID: 1001
Source: Application Error
Version: 5.2
Symbolic Name: DW_BUCKET_LOG
Message: Fault bucket %1.
   
Explanation

A fault bucket identification number is a number assigned by the system to identify specific types of errors. This number is used by Microsoft to identify a particular program error when you send an error report.
   
User Action

If an error report was generated for this error, you might be able to obtain more information about the error by sending the report to Microsoft for analysis.

What to expect

Microsoft actively analyzes all error reports and prioritizes them based on the number of customers affected by the error signature contained in the report. When a report is submitted, Microsoft will try to determine the cause of the error, categorize it according to the type of issue encountered, and send you relevant information when such information is available. However, because error reports do not always contain enough information to positively identify the source of the issue, Microsoft might need to collect a number of similar reports from other customers before a pattern is discovered. Although Microsoft may not be able to provide a solution for your particular error at this time, all information submitted is used to further improve the quality and reliability of our products.

Related: