Event ID 25 — NPS Proxy Configuration

Event ID 25 — NPS Proxy Configuration

Updated: February 21, 2008

Applies To: Windows Server 2008

When Network Policy Server (NPS) is configured as a RADIUS proxy, remote RADIUS server IP addresses must be configured correctly so that the NPS proxy can forward connection requests to the remote RADIUS servers. If the NPS proxy is configured with incorrect IP addresses for the remote RADIUS servers, connection requests cannot be forwarded and authentication will fail.

Event Details

Product: Windows Operating System
ID: 25
Source: NPS
Version: 6.0
Symbolic Name: PROXY_E_LOCAL_SERVER
Message: The address of remote RADIUS server %1 in remote RADIUS server group %2 resolves to local address %3. The address will be ignored.

Resolve
Enter the correct IP address for the RADIUS server in an NPS Remote RADIUS Server Group

To perform this procedure, you must be a member of Domain Admins.

To enter the IP address for the RADIUS server in a NPS Remote RADIUS server group:

  1. Click Start, Administrative Tools, Network Policy Server. The Network Policy Server Microsoft Management Console (MMC) opens.
  2. In the console tree, double-click RADIUS Clients and Servers, and then double-click Remote RADIUS Server Groups.
  3. Open each remote RADIUS server group and look at the IP address of each group member. When you find the RADIUS server that is configured with the IP address of the local computer, change it to the IP address of the remote RADIUS server.

Verify

To verify the configuration of the NPS proxy:

  1. Click Start, Administrative Tools, Network Policy Server. The Network Policy Server MMC opens.
  2. In the console tree, double-click RADIUS Clients and Servers, and then double-click Remote RADIUS Server Groups.
  3. Open each remote RADIUS server group and examine the IP address configuration of each group member to confirm that there are no remote RADIUS servers that are configured with the IP address of the local computer.

Related Management Information

NPS Proxy Configuration

Network Policy Server Infrastructure

Related:

An internal error occurred while transferring a message or report. [ ] (14)

Details
Product: Exchange
Event ID: 25
Source: MSExchangeMTA
Version: 6.5.6940.0
Component: Microsoft Exchange Message Transfer Agent
Message: An internal error occurred while transferring a message or report. [<value><value> <value> <value> <value> <value> <value>] (14)
   
Explanation

The association will be stopped and restarted if necessary. Associations are paths that are opened to other systems. Each association is contained within a connection and is used to transfer messages to a system. You may have multiple associations in each connection.

   
User Action
  1. Use network Monitor to capture Network Traces, and then view these traces from Network Monitor for network issues.
  2. If the error persists, stop and restart the message transfer agent service.
  3. If the error still persists, restart Microsoft Exchange Server.

Related:

Not used Unable to start the router on adapter “%2” because a node could not be acquired.

Details
Product: Windows Operating System
Event ID: 25
Source: AppleTalk
Version: 5.0
Component: Services for Macintosh
Symbolic Name: EVENT_ATALK_ROUTER_COULDNOTGETNODE
Message: Not used Unable to start the router on adapter “%2” because a node could not be acquired.
   
Explanation

The server might be out of memory. Or, even though it is unlikely, the AppleTalk network might have too many computers in it. If this is the case, all the node addresses are in use by other computers.

   
User Action

Check the server’s available disk space. If the server requires more memory, try stopping other running applications and services. You might also need to remove unused files and applications from the server’s disk. If the disk has sufficient memory, try shutting down some other computers and then try starting the AppleTalk Protocol using the Devices option in Control Panel.

Related:

The service could not be started because it was unable to access the Microsoft Exchange Information Store. This is either due to the Microsoft Exchange Information Store service not running or the Microsoft Exchange Connector for Lotus cc:Mail not configured correctly. If the Microsoft Exchange Information Store is not running, please start it. If the Microsoft Exchange Information Store is running, then using REGEDT32.EXE verify that the Organization, OrgUnit, and CommonName values under the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeCCMC\Parameters key are correct. If they are correct then reboot the server.

Details
Product: Exchange
Event ID: 25
Source: MSExchangeCCMC
Version: 6.0
Component: Connector for Lotus cc:Mail
Symbolic Name: MSG_STARTUP_MAPI_LOGON
Message: The service could not be started because it was unable to access the Microsoft Exchange Information Store. This is either due to the Microsoft Exchange Information Store service not running or the Microsoft Exchange Connector for Lotus cc:Mail not configured correctly. If the Microsoft Exchange Information Store is not running, please start it. If the Microsoft Exchange Information Store is running, then using REGEDT32.EXE verify that the Organization, OrgUnit, and CommonName values under the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeCCMC\Parameters key are correct. If they are correct then reboot the server.
   
User Action
If the problem persists, reinstall Connector for Lotus cc:Mail.

Related:

Outlook Web Access was unable to initialize.File “%1” in theme folder “%2” could not be parsed. There was an error parsing the XML file. Line “%3”, Position “%4”.

Details
Product: Exchange
Event ID: 25
Source: MSExchange OWA
Version: 8.0
Symbolic Name: ThemeInfoErrorParsingXml
Message: Outlook Web Access was unable to initialize.File “%1” in theme folder “%2” could not be parsed. There was an error parsing the XML file. Line “%3”, Position “%4”.
   
Explanation

This Error event indicates that Microsoft® Office Outlook® Web Access did not initialize because the system could not correctly parse the XML file referenced in the event description. The event may occur if any of the following conditions is true:

  • The file is corrupted.

  • The file contains invalid format or entries that are not allowed by Outlook Web Access themes.

   
User Action

To resolve the error, follow these steps:

  • Replace the themes folder and the default subfolders with the files and folders that are located on the Microsoft Exchange Server 2007 DVD. By default, those files and folders are located in the \Setup\ServerRoles\ClientAccess\owa\version\ folder of the Exchange 2007 DVD.

  • If a custom Outlook Web Access theme is used, re-create all the files that are associated with the custom theme.

  • Make sure that the entries and format that are used in the custom themes files, such as themeinfo.xml, is correct.

For more information about Outlook Web Access themes, see How to Create a Theme for Outlook Web Access.

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 driver has detected a device with old or out-of-date firmware. The device will not be used.

Details
Product: Windows Operating System
Event ID: 25
Source: SBP2Port
Version: 5.2
Symbolic Name: IO_ERR_BAD_FIRMWARE
Message: The driver has detected a device with old or out-of-date firmware. The
device will not be used.
   
Explanation

The driver received incorrect configuration data.

Possible causes include:

  • A faulty device.
  • An old device that does not conform to the Serial Bus Protocol 2 (SBP-2) device specifications.
   
User Action

To resolve the problem, try to reset the device by turning it on and off. If this action does not resolve the problem, the device is probably not supported.

Related: