Microsoft Exchange Server has detected that Basic Authentication is being attempted between this server and server ‘%1’. This authentication mechanism is not secure and it is not supported between front-ends and back-ends. If this condition persists, please verify that server ‘%1’ is properly configured to use Integrated Windows Authentication for each virtual directory used by Exchange. After applying any changes it may be necessary to restart Internet Information Services on both the front-end and back-end servers.

Details
Product: Exchange
Event ID: 1001
Source: EXPROX
Version: 6.5.6940.0
Component: Microsoft Exchange Proxy
Message: Microsoft Exchange Server has detected that Basic Authentication is being attempted between this server and server ‘%1’. This authentication mechanism is not secure and it is not supported between front-ends and back-ends. If this condition persists, please verify that server ‘%1’ is properly configured to use Integrated Windows Authentication for each virtual directory used by Exchange. After applying any changes it may be necessary to restart Internet Information Services on both the front-end and back-end servers.
   
Explanation

This event may appear when both of the following conditions are true:

  • Exchange 2003 servers are configured in a front-end/back-end configuration.

  • The back-end Exchange 2003 server is configured to use only Basic authentication.

The text of this message implies that both the front-end server and the back-end server must be configured to use Integrated Windows authentication. This is incorrect. Only the back-end Exchange 2003 server must be configured to use Integrated Windows authentication.

The description of the event should read as follows:

    Microsoft Exchange Server has detected that Basic authentication is being attempted between this server and server %1. This authentication mechanism is not secure and it is not supported between front-end and back-end servers. If this condition persists, verify that server %1 is correctly configured to use Integrated Windows Authentication for each virtual directory used by Exchange. You may have to restart Internet Information Services on both the front-end and back-end servers after any changes are applied.

For details, see the following articles in the Microsoft Knowledge Base:

   
User Action

Verify that the back-end server listed in the event description is configured to use Integrated Windows authentication, and that all front-end servers are configured to use Basic Authentication. If any authentication method changes are made to the front-end or back-end servers, restart the IIS Admin service on the front-end and back-end servers.

Related:

NTFS – Autochk: file system check occurred on startup

Details
Product: Windows Operating System
Event ID: 1001
Source: Winlogon
Version: 5.2.3790.1830
Message: NTFS – Autochk: file system check occurred on startup
   
Explanation

Microsoft® Windows® encountered corrupted file-system metadata during the last Windows session, so Windows marked the file system as “dirty” (corrupt). Windows ran the chkdsk /f command during startup in an attempt to repair the corrupted file system metadata.

Related Events

Chkdsk: Event ID 26180Chkdsk: Event ID 1066

Cause

The file system might have been marked as “dirty” (corrupt) for one of the following reasons:

  • I/O requests that were issued by the file system to the disk subsystem might not have been completed successfully.
  • The operating system was shut down incorrectly. If the volume is formatted with the FAT file system, an incorrect shutdown of Windows will always cause this event (Event ID 1001). FAT is not a journaling file system. In order to maintain metadata consistency, FAT requires the operating system to be shut down properly. An incorrect shutdown (for example, a power failure) forces Windows to run chkdsk in order to ensure that the file-system metadata is consistent.If the volume is formatted with the NTFS file system, running chkdsk is not normally necessary. NTFS is a journaling file system and does not usually require chkdsk to ensure metadata consistency. However, NTFS depends upon the media to guarantee its write-through semantics. If the media does not accept write-through semantics, inconsistencies in the file-system metadata might occur when there is a sudden loss of power or a system failure.
  • The media (hard disk) might have developed bad sectors.
   
User Action

This message is provided to inform you that the chkdsk command was run on the file system. No actions are required, but the corrupted disk might indicate other disk problems. You should do the following:

  • Review the application log and the system log in Event Viewer for additional errors. Event ID 1066 contains the detailed chkdsk log. You should review the chkdsk log to see what problems (if any) chkdsk found on the volume and what fixes (if any) were made.
  • Check related hardware and devices on the shared bus to ensure that the cables are connected and that the hardware and devices are properly terminated.
  • Avoid improper shutdowns. If the volume is formatted with the FAT file system, you can usually avoid Event ID 1001 by properly shutting down Windows.If Event ID 1001 occurs frequently for an NTFS volume (or for a FAT volume, despite proper shutdowns), it is likely that the disk has developed bad sectors. Run chkdsk /r to locate bad sectors on the hard disk.

Related Resources

For more information about chkdsk, see Knowledge Base article 187941, “An Explanation of CHKDSK and the New /C and /I Switches,” at http://go.microsoft.com/fwlink/?LinkId=25770.

Related:

Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address %1. The following error occurred: %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: 1001
Source: DHCP
Version: 5.2
Symbolic Name: EVENT_FAILED_TO_OBTAIN_LEASE
Message: Your computer was not assigned an address from the network (by the DHCP
Server) for the Network Card with network address %1. The following error
occurred: %2.
Your computer will continue to try and obtain an address on its own from
the network address (DHCP) server.
   
Explanation

The DHCP client could not contact the DHCP server.

   
User Action

No user action is required. The DHCP client will automatically try to contact the server again.

If you expect a DHCP address and you still cannot contact the server, verify that the client is on a network that has a DHCP server.

Related:

This address is already in use. Binding: %1

Details
Product: Exchange
Event ID: 1001
Source: MSExchangeTransport
Version: 8.0
Symbolic Name: AddressInUse
Message: This address is already in use. Binding: %1
   
Explanation

This Error event indicates that the specified combination of IP address and port number is being used by another process on the server.

Each Receive connector on a Microsoft Exchange Server 2007 Hub Transport server or Edge Transport server must use a unique combination of IP addresses and port numbers to listen for inbound connections from remote SMTP messaging servers.

If other SMTP messaging services are running on this server, they may be using an IP address and port number combination that conflicts with an existing Receive connector. For example, the default Receive connector on an Edge Transport server is configured to use 0.0.0.0:25. The default Receive connectors on a Hub Transport server are configured to use 0.0.0.0:25 and 0.0.0.0:587.

   
User Action

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

  • Remove or relocate any other SMTP messaging services that are running on this server.

  • Configure any other SMTP messaging services that must run on this Hub Transport server or Edge Transport server to use an IP address and port number combination that doesn’t conflict with any Receive connectors that are configured on the server.

  • Configure the Receive connectors on this Hub Transport server or Edge Transport server to use an IP address and port number combination that doesn’t conflict with any other SMTP messaging services that must run on this server.

For more information, see Receive Connectors.

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: