Event ID 1003 — IIS Web Site Availability

Event ID 1003 — IIS Web Site Availability

Updated: January 20, 2010

Applies To: Windows Server 2008

Internet Information Services (IIS) Web sites that use HTTP rely on several important IIS components for their availability. The Windows Process Activation Service (WAS), the World Wide Publishing Service (W3SVC), the HTTP service, all must be running correctly. In addition, a properly running application pool must be available for the Web site’s applications. If any of these components is not functioning, the Web site will not be available.

Event Details

Product: Internet Information Services
ID: 1003
Source: Microsoft-Windows-IIS-W3SVC
Version: 7.0
Symbolic Name: W3SVC_EVENT_BINDING_FAILURE_INVALID_URL
Message: The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The URL may be invalid. The site has been disabled. The data field contains the error number.

Resolve
Check a URL binding

An invalid URL may cause prevent a Web site from starting. To resolve this:

1. Make sure that all URLs specified for your applications are valid and do not break URL normalization (canonicalization) rules. For more information, see RFC 3986.

2. Restart the site.

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

To restart the site:

  1. Click Start, click Control Panel, and then click Administrative Tools.
  2. Right-click Internet Information Services (IIS) Manager and select Run as administrator.
  3. In the Connections pane, select the Web site that you have to start.
  4. In the Actions pane, click Start to start the site.

Verify

To verify that a Web site is started, you can use either IIS Manager or the appcmd command line utility.

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

To verify that the Web site is started by using the appcmd command line utility:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Change the directory to %SystemDrive%\Windows\System32\inetsrv.
  3. Run the following command: appcmd.exe list site -site.name:”Site Name”. If the Web site is started, the output will resemble the following:

        SITE “Default Web Site” (id:1,bindings:http/*:80:,state:Started)

To verify that the Web site is started by using IIS Manager:

  1. Click Start, click Control Panel, and then click Administrative Tools.
  2. Right-click Internet Information Services (IIS) Manager and select Run as administrator.
  3. In the Connections pane, expand the computer name.
  4. In the Connections pane, click the Sites node.
  5. In Features View, look for the Web site name. The Web site status will be indicated under the Status column. If the Web site is started and is using the HTTP protocol, Started(http) will appear.

Related Management Information

IIS Web Site Availability

Internet Information Services (IIS) 7.0

Related:

Event ID 1003 — Windows Installer Application Installation

Event ID 1003 — Windows Installer Application Installation

Updated: December 16, 2008

Applies To: Windows Server 2008 R2

Windows Installer is used to install applications on a computer.

Event Details

Product: Windows Installer – Unicode
ID: 1003
Source: MsiInstaller
Version: 5.0
Symbolic Name: EVENTLOG_TEMPLATE_BAD_CONFIGURATION_KEY
Message: Unexpected or missing subkey ‘%1’ in key ‘%2’

Resolve
Review the system log file

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://go.microsoft.com/fwlink/?LinkId=136341.

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 Web site. 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:

The configuration of one of the Receive connectors is invalid. The configuration change will be ignored. The description of the configuration error is: %1

Details
Product: Exchange
Event ID: 1003
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: ReceiveConnectorConfigDataError
Message: The configuration of one of the Receive connectors is invalid. The configuration change will be ignored. The description of the configuration error is: %1
   
Explanation

The configuration of the affected Receive connector must be fixed before it can be used.

This Error event indicates that there is a configuration error in a Receive connector. A required parameter is missing or corrupted, or it contains invalid data.

   
User Action

To resolve this error, use the Set-ReceiveConnector cmdlet in the Exchange Management Shell to correct the specified configuration error.

For more information, see the following topics:

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:

TraceFileName parameter not located in registry; Default trace file used is %1.

Details
Product: Windows Operating System
Event ID: 1003
Source: EvntAgnt
Version: 5.0
Component: Application Event Log
Symbolic Name: SNMPELEA_NO_REGISTRY_TRACE_FILE_PARAMETER
Message: TraceFileName parameter not located in registry; Default trace file used is %1.
   
Explanation

No debug tracing output file is generated. This is the default condition of the system. Debug tracing should only be turned on when you are debugging software.

These error events will continue to be logged when you restart the computer, unless you reconfigure the Evntagnt.dll.

   
User Action

No user action is required; however, you can stop Windows from displaying these messages in Event Viewer by reconfiguring the evntagnt.dll in the system registry.

Caution The following procedures change system registry settings. If Registry Editor is used incorrectly, serious system problems can occur, and the operating system may need to be reinstalled.

To stop displaying EvntAgnt 1015 messages in Event Viewer

  1. Before starting SNMP, open Registry Editor.
  2. Navigate to the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SNMP_EVENTS\EventLog\Parameters
  3. Add the following registry values:
    TraceFileNameType: REG_SZValue: null (blank)TraceLevelType: REG_DWORDValue: 32

Related:

No valid Transport Layer Security (TLS) certificate was found. Microsoft Exchange can’t update the Active Directory Application Mode (ADAM) credentials.

Details
Product: Exchange
Event ID: 1003
Source: MSExchange Message Security
Version: 8.0
Symbolic Name: TlsCertificateNotFound
Message: No valid Transport Layer Security (TLS) certificate was found. Microsoft Exchange can’t update the Active Directory Application Mode (ADAM) credentials.
   
Explanation

This Error event indicates that a valid Transport Layer Security (TLS) certificate was not found on the server where this event occurs. A TLS certificate is required for a Hub Transport server to use and update the EdgeSync replication account credentials.

   
User Action

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

  • Create a new TLS certificate for the server and then resubscribe the Edge Transport server. You do not have to remove the Edge Subscription to resubscribe. Run the New-EdgeSubscription cmdlet in the Exchange Management Shell on both the Edge Transport server and the Hub Transport server to overwrite the existing Edge Subscription. For more information, see New-EdgeSubscription.

  • 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:

TraceFileName parameter not located in registry; Default trace file used is %1.

Details
Product: Windows Operating System
Event ID: 1003
Source: EvntAgnt
Version: 5.2
Symbolic Name: SNMPELEA_NO_REGISTRY_TRACE_FILE_PARAMETER
Message: TraceFileName parameter not located in registry;
Default trace file used is %1.
   
Explanation

No debug tracing output file is generated. This is the default condition of the system. Debug tracing should only be turned on when you are debugging software.

These error events will continue to be logged when you restart the computer, unless you reconfigure the Evntagnt.dll.

   
User Action

No user action is required; however, you can stop Windows from displaying these messages in Event Viewer by reconfiguring the evntagnt.dll in the system registry.

Caution The following procedures change system registry settings. If Registry Editor is used incorrectly, serious system problems can occur, and the operating system may need to be reinstalled.

To stop displaying EvntAgnt 1015 messages in Event Viewer

  1. Before starting SNMP, open Registry Editor.
  2. Navigate to the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SNMP_EVENTS\EventLog\Parameters
  3. Add the following registry values:
    TraceFileNameType: REG_SZValue: null (blank)TraceLevelType: REG_DWORDValue: 32

If you want to enable debug tracing of eventagnt.dll on this computer, reconfigure eventagnt.dll in the system registry. This will also stop Windows from displaying these messages in Event Viewer.

To configure the evntagnt.dll file for debug tracing

  1. Open Registry Editor.
  2. Navigate to the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SNMP_
    EVENTS\EventLog\Parameters
  3. Add the following registry values:
  4. TraceFileNameType: REG_SZValue: c:\evntagnt.logTraceLevelType: REG_DWORDValue: 1

Related:

Process %1 (PID=%2). Temporarily unable to connect to Active Directory to read configuration data for object %3 (%4). Will wait for %5 seconds and retry.

Details
Product: Exchange
Event ID: 1003
Source: MSExchangeFDS
Version: 08.01.0106.000
Symbolic Name: ADUnavailable
Message: Process %1 (PID=%2). Temporarily unable to connect to Active Directory to read configuration data for object %3 (%4). Will wait for %5 seconds and retry.
   
Explanation

This Warning event indicates that there is no suitable Active Directory directory service server available to read the configuration data for the object specified in the event description. The Microsoft Exchange File Distribution service must read the configuration data from Active Directory to distribute offline address book and custom Unified Messaging prompts.

This event may occur because of intermittent network issues.

   
User Action

If this Warning event frequently occurs, follow these steps:

  • Use the Ping or PathPing command-line tools to test basic connectivity with the domain controller. Use Ping to isolate network hardware problems and incompatible configurations. Use PathPing to detect packet loss over multiple-hop trips. For more information, see Microsoft Knowledge Base article 325487, How to troubleshoot network connectivity problems.

  • Run the Dcdiag command line tool to test domain controller health. To do this, run dcdiag /s:<Domain Controller Name> at a command prompt on the Exchange Server. Use the output of Dcdiag to discover the root cause of any failures or warnings that it reports. For more information, see the Microsoft Windows Server TechCenter article, Dcdiag Overview.

  • Review other related events in the Application log and System log for Warning events and Error events. These related events may provide more information about the root cause of this Warning event.

This Warning event may be ignored if occurred during known network issues.

Note  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:

Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address %1. The following error occured: %2. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.

Details
Product: Windows Operating System
Event ID: 1003
Source: DHCP
Version: 5.0
Component: System Event Log
Symbolic Name: EVENT_FAILED_TO_RENEW
Message: Your computer was not able to renew its address from the network (from the DHCP Server) for the Network Card with network address %1. The following error occured: %2. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.
   
Explanation

The DHCP Client service on your computer did not receive a response from the DHCP server to renew your computer’s IP address lease. The client still has a valid IP address and periodically will try to get an address lease extension.

This could be caused by network connectivity issues, a DHCP server or relay malfunction, firewall issues, or a malfunction of your computer’s network interface card or driver.

   
User Action

If your computer is connected to the network by cable, confirm that the cable is plugged in. If you have a wireless network connection, confirm that you have a signal and the proper credentials for the wireless network.

The DHCP Client service will continue trying to get an IP address lease extension until it succeeds, so DHCP might establish communications on its own.

If communication between the DHCP client and the DHCP server is not established automatically, check the following possible causes and take corrective action:

  • The DHCP server is down or not responding.
  • The DHCP relay is not functioning correctly.
  • The network is down.
  • The firewall on your computer is blocking out network broadcast traffic.
  • Your computer’s network interface card or driver is not functioning correctly.

Related: