Event ID 2 — DNS Server Service Status

Event ID 2 — 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: 2
Source: Microsoft-Windows-DNS-Server-Service
Version: 6.0
Symbolic Name: DNS_EVENT_STARTUP_OK
Message: The DNS server has started.

Resolve

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

Related Management Information

DNS Server Service Status

DNS Infrastructure

Related:

The %1 was unable to open ODBC Data Source %2, Table: %3, under User Name [%4]. The ODBC Error description is: %5.

Details
Product: Internet Security and Acceleration Server
Event ID: 2
Source: DNS Intrusion Detection Filter
Version: 4.0.3443.594
Component: ISA Server Services
Message: The %1 was unable to open ODBC Data Source %2, Table: %3, under User Name [%4]. The ODBC Error description is: %5.
   
Explanation
Open Database Connectivity (ODBC) allows applications to access data in a database management system (DBMS). It uses a data source to maintain connection information for the database. The ODBC-specified data source could not be opened because it does not exist or because the table and user name information is incorrect.
   
User Action
Check the log properties to verify that the ODBC Data Source, Table name, User Name, and Password are correct in the corresponding logging service. To do this, in the console tree of ISA Server Management, select the server or array name, and then click Monitoring. In the details pane click the Logging tab, and then use the options in the task pane to view the properties where logging is enabled for this service.

Related:

A required application setting is missing from the Web.config file.

Details
Product: MapPoint Location Server
Event ID: 2
Source: Microsoft MapPoint Location Server
Version: 1.0.0.0
Message: A required application setting is missing from the Web.config file.
   
Explanation
If this error occurs the first time you start MapPoint Location Server, the installation may be corrupt; otherwise, someone may have tampered with the file.
   
User Action
If you receive this message after starting MapPoint Location Server for the first time, uninstall and then reinstall MapPoint Location Server Web Service.If you have been running MapPoint Location Server successfully and then receive this message, check the message to determine which setting is missing, and then add the setting to the Web.config file. The default location for the Web.config file is C:\Program Files\Microsoft MapPoint Location Server\MMLS\Web Service\Web.config. The default application settings are as follows:

yourSQLServerInstance]”/>
YourMapPointLocationServerDatabase]”/>
YourDomain]”/>
YourMLSWebServiceAccountName]”/>
!–Note:The password is stored in encrypted format. You must use the Set Password tool to change it.– >

   
Description
RequiredSettingMissing

Related:

Unable to get device object pointer for port object.

Details
Product: Windows Operating System
Event ID: 2
Source: parvdm
Version: 5.0
Symbolic Name: PAR_CANT_FIND_PORT_DRIVER
Message: Unable to get device object pointer for port object.
   
Explanation

ParVdm depends on previous naming conventions for identifying parallel ports, and in this case it cannot find a port with a name that matches.

Port names can be changed by the user or in response to basic input/output system (BIOS) settings.

   
User Action

No user action is required.

Related:

Anonymous Request received from HostAddress:”%1″, HostName:”%2″. Invalid Autodiscover site configuration. To fix the problem remove Anonymous access.

Details
Product: Exchange
Event ID: 2
Source: MSExchange Autodiscover
Version: 8.0
Symbolic Name: ErrWebAnonymousRequest
Message: Anonymous Request received from HostAddress:”%1″, HostName:”%2″. Invalid Autodiscover site configuration. To fix the problem remove Anonymous access.
   
Explanation

This Error event indicates that the Microsoft® Exchange Autodiscover service was unable to process anonymous requests from an Autodiscover client, for example, an Outlook® client. An invalid Autodiscover site configuration and an anonymous client request could cause this error. ‘HostName’ in the error message text refers to the Domain Name System (DNS) name of the remote client.

Autodiscover requires authenticated clients to connect by using either of these methods:

  • The client may use a Secure Sockets Layer (SSL) connection to perform Active Directory® directory service lookups to find the requested mailbox database.

  • The client may provide URLs of Exchange services such as the Availability service.

We do not recommend that you enable anonymous authentication as this will give spammers access to e-mail addresses. A HTTP 403 error is sent to the client.

   
User Action

To resolve this error, do the following:

  • Check the Autodiscover virtual directory site configuration settings on the Exchange Client Access server (CAS) and make sure SSL is selected for Basic or Windows Integrated Windows authentication (also known as NTLM or Kerberos authentication).

  • Follow these steps to disable Anonymous access in the Autodiscover virtual directory on the Client Access server.

    1. In Internet Information Services (IIS) Manager, locate the Autodiscover virtual directory.

    2. Right-click Autodiscover virtual directory and select Properties.

    3. On the Directory Security tab, under Authentication and access control, click Edit.

    4. In the Authentication Methods screen, clear Enable anonymous access.

For more information about the Autodiscover service, see Managing Autodiscover.

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: