Event ID 632 — Trust Policy and Configuration

Event ID 632 — Trust Policy and Configuration

Updated: February 27, 2008

Applies To: Windows Server 2008

The Active Directory Federation Services (AD FS) trust policy file defines the set of parameters that a Federation Service requires to identify partners, certificates, account stores, claims, and the various properties of these entities that are associated with the Federation Service.

Event Details

Product: Windows Operating System
ID: 632
Source: Microsoft-Windows-ADFS
Version: 6.0
Symbolic Name: CustomModuleExceptionLoading
Message: The Federation Service encountered an error while loading the trust policy. An exception was thrown during loading of a custom module assembly. Assembly path: %1 If this error occurs startup of the during Federation Service, the Federation Service will be not be able to start, and all requests to the Federation Service will fail until the configuration is corrected. If this error occurs while the Federation Service is running, the Federation Service will continue to use the last trust policy that was loaded successfully. This error may be generated by a non-Microsoft module that is not part of AD FS. User Action Ensure that the assembly path is correct and that the assembly file has appropriate permissions. Additional Data Exception information: %2

Resolve
Review the claim transform module setting

When you specify the dynamic-link library (DLL) file that the claim transform module will use to modify claims, make sure that the file path is valid and that the user has permission to access this file.

To perform this procedure, you must be a member of the local Administrators group, or you must have been delegated the appropriate authority.

To review the file path that is specified for the claim transform module setting in the trust policy:

  1. On the federation server, click Start, point to Administrative Tools, and then click Active Directory Federation Services.
  2. In the console tree, under Federation Service, right-click Trust Policy, and then click Properties.
  3. Click the Transform Module tab, and then review the file path that is specified in DLL file.

Verify

Verify that you can access the Active Directory Federation Services (AD FS)-enabled application from a client browser and that the resource can be accessed.

Related Management Information

Trust Policy and Configuration

Active Directory Federation Services

Related:

Event ID 633 — Trust Policy and Configuration

Event ID 633 — Trust Policy and Configuration

Updated: February 27, 2008

Applies To: Windows Server 2008

The Active Directory Federation Services (AD FS) trust policy file defines the set of parameters that a Federation Service requires to identify partners, certificates, account stores, claims, and the various properties of these entities that are associated with the Federation Service.

Event Details

Product: Windows Operating System
ID: 633
Source: Microsoft-Windows-ADFS
Version: 6.0
Symbolic Name: CustomModuleExceptionInstantiating
Message: The Federation Service encountered an error while loading the trust policy. An exception was thrown during instantiation of a custom module class from a custom module assembly. Assembly path: %1 Class name: %2 If this error occurs during startup of the Federation Service, the Federation Service will be not be able to start, and all requests to the Federation Service will fail until the configuration is corrected. If this error occurs while the Federation Service is running, the Federation Service will continue to use the last trust policy that was loaded successfully. This error may be generated by a non-Microsoft module that is not part of AD FS. User Action Verify that the appropriate assembly and class are configured. Contact the module vendor for further troubleshooting steps. Additional Data Exception information: %3

Resolve
Configure the appropriate assembly and class

Make sure that the appropriate assembly and class are configured. When you point to a custom transform module dynamic-link library (DLL) file, make sure that the Class name that is specified on this tab exists in that DLL file.

To perform this procedure, you must be a member of the local Administrators group, or you must have been delegated the appropriate authority.

To specify the file path for the transform module settings in the trust policy:

  1. On the federation server, click Start, point to Administrative Tools, and then click Active Directory Federation Services.
  2. In the console tree, under Federation Service, right-click Trust Policy, and then click Properties.
  3. Click the Transform Module tab, and then type the file path in DLL file.

For further troubleshooting, contact the module vendor.

Verify

Verify that you can access the Active Directory Federation Services (AD FS)-enabled application from a client browser and that the resource can be accessed.

Related Management Information

Trust Policy and Configuration

Active Directory Federation Services

Related:

Initialization failed because the dynamic-link library %1 returned an incorrect version number.

Details
Product: Windows Operating System
Event ID: 3255
Source: System
Version: 5.0
Symbolic Name: NELOG_Wrong_DLL_Version
Message: Initialization failed because the dynamic-link library %1 returned an incorrect version number.
   
Explanation

This message should occur only on a workstation. Any action to correct the problem should be performed on that computer. The Remoteboot service could not start because the listed dynamic-link library returned the incorrect version number.

   
User Action

Be sure you are using the correct versions of the dynamic-link libraries.

Related:

The file version of ‘%1’ installed on the local server is not current. Looking at servers in the site for a current version.

Details
Product: Exchange
Event ID: 2036
Source: MSExchangeSA
Version: 6.5.7596.0
Message: The file version of ‘%1’ installed on the local server is not current. Looking at servers in the site for a current version.
   
Explanation

This Information event can occur if Microsoft® Exchange Server determines that the version of the file specified in the description of this event does not match the version specified in the corresponding dynamic-link library (DLL).

   
User Action

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

  • Search the Microsoft Knowledge Base for information about the file specified in the description of this event. If you determine that the file mentioned in the description of this event is a file installed by a third-party application, contact the vendor of the application for more information.

  • Check any events that come before or follow this events message to determine whether they explain the underlying cause for the event.

Related:

Unable to generate the e-mail address. Unable to load address module ” for address type ”. Error .

Details
Product: Exchange
Event ID: 2027
Source: MSExchangeSA
Version: 6.5.6940.0
Component: Microsoft Exchange System Attendant
Message: Unable to generate the e-mail address. Unable to load address module ‘<DLL name>‘ for address type ‘<address type>‘. Error <error code>.
   
Explanation

This event indicates that the System Attendant was unable to generate an email address that was defined in the Recipient Policy because the mentioned third-party DLL file was not accessible.

  • This issue can occur because of an invalid or third-party e-mail address

    generator. When the System Attendant starts, it attempts to load an address

    generation dynamic-link library (DLL) file for each address type that the

    Recipient Update Service is responsible for stamping. If the System Attendant

    is unable to load the DLL for any address type, the Recipient Update Service

    fails to stamp any e-mail addresses and the 2027 event is logged.

  • This issue can also occur if the third party DLL file is present but the

    SYSTEM Account does not have full control rights to it.

   
User Action
  • Create the folder structure mentioned in the 2027 event and place the

    third-party DLL file in that directory. Update the Recipient Update Service.

  • Give the SYSTEM Account Full Control rights to the EXCHSRVR directory and

    all sub-directories.

Related:

Unable to generate the e-mail address. Unable to load address module ‘DLL name’ for address type ‘address type’. Error error code.

Details
Product: Exchange
Event ID: 2027
Source: MSExchangeAdmin
Version: 6.5.0000.0
Message: Unable to generate the e-mail address. Unable to load address module ‘DLL name’ for address type ‘address type’. Error error code.
   
Explanation
This event indicates that the System Attendant was unable to generate an email address that was defined in the Recipient Policy because the mentioned third-party DLL file was not accessible.

  • This issue can occur because of an invalid or third-party e-mail address

    generator. When the System Attendant starts, it attempts to load an address

    generation dynamic-link library (DLL) file for each address type that the

    Recipient Update Service is responsible for stamping. If the System Attendant

    is unable to load the DLL for any address type, the Recipient Update Service

    fails to stamp any e-mail addresses and the 2027 event is logged.

  • This issue can also occur if the third party DLL file is present but the

    SYSTEM Account does not have full control rights to it.

   
User Action
  • Create the folder structure mentioned in the 2027 event and place the

    third party DLL file in that directory. Update the Recipient Update Service.

  • Give the SYSTEM Account Full Control rights to the EXCHSRVR directory and

    all sub-directories.

Related:

The print processor is unknown.

Details
Product: Windows Operating System
Event ID: 1798
Source: RPC
Version: 5.0
Component: System Resources
Symbolic Name: ERROR_UNKNOWN_PRINTPROCESSOR
Message: The print processor is unknown.
   
Explanation

The print processor is a dynamic-link library (DLL) which calls the printer driver. An application has tried to use a print processor which has not been installed on your computer.

   
User Action

Contact your system administrator to check the software installed on your computer. If the required DLL cannot be installed on your system, you might have to contact the supplier of the running application.

Related:

The Inter-Site Messaging Service SMTP Transport plug-in depends on the COM DLL %1. One or more classes from this library are not registered. Please verify that this DLL is present and registered. You may wish to try registering this DLL using following commands: regsrv32 /u %1 regsrv32 %1 If this problem persists- you may have an obsolete version of this library. Please verify the version using the following command: filever %windir%\system32\%1 Please stop and restart the ISM service. The error message is as follows: %2 The record data is the status code.

Details
Product: Windows Operating System
Event ID: 1469
Source: Active Directory
Version: 5.0
Symbolic Name: DIRLOG_ISM_SMTP_CLASS_MISSING
Message: The Inter-Site Messaging Service SMTP Transport plug-in depends on the COM DLL %1. One or more classes from this library are not registered. Please verify that this DLL is present and registered. You may wish to try registering this DLL using following commands: regsrv32 /u %1 regsrv32 %1 If this problem persists- you may have an obsolete version of this library. Please verify the version using the following command: filever %windir%\system32\%1 Please stop and restart the ISM service. The error message is as follows: %2 The record data is the status code.
   
Explanation

One or more classes from the specified Component Object Model (COM) DLL are not registered. The Intersite Messaging service using the SMTP transport depends on this DLL.

   
User Action

Verify that this DLL is present and registered, and then restart the Intersite Messaging service.

If the DLL is not registered, use the following commands:regsrv32 /u %1regsrv32 %1

If this event continues to occur, you might have an obsolete version of this DLL. To determine which version of the DLL you are using, use the following command:filever %windir%\system32\%1

Related: