Event ID - 2027

Event Id2027
SourceMSExchangeSA
DescriptionUnable to generate the e-mail address. Unable to load address module C:\Exchsrvr\Address\TYPE\I386\3RDPARTY.dll for address type TYPE. Error 0xc007007e.
Event InformationAccording to Microsoft:
CAUSE:
The issue can occur because of an invalid or missing third-party e-mail address generator. When the Microsoft Exchange System Attendant service starts, it tries to load an address generation .dll file for each address type that the Recipient Update Service requires to generate the third-party proxy address. If the System Attendant cannot load the .dll file for any address type, the Recipient Update Service does not process the accounts. Additionally, the events that are mentioned in the "Symptoms" section are logged in the Event Viewer Application log.
The generator may be present on any recipient policy. If you do not find the address generator in a recipient policy, check remote sites/administrative groups for the invalid or missing e-mail address generator. If such an invalid e-mail address is added to the gatewayProxy attribute of a Recipient Update Service, the Recipient Update Service no longer updates objects.
RESOLUTION:
To resolve this issue, either manually copy the missing .dll file from an existing Exchange Server 5.5 computer, or disable that particular address type so that the Recipient Update Service no longer tries to load the .dll file.
Note Every server that is running Exchange that has a Recipient Update Service must have the correct address generation .dll files.
Copy the third-party address generation .dll files
1. Note the name of the required .dll files that are mentioned in the MSExchangeSA event ID 2027 or 2037.
2. On an existing Exchange Server 5.5 computer, locate the .dll file that is specified in step 1.
3. Create the folder structure that is listed in the MSExchangeSA event ID 2027 or 2037.
4. Copy the .dll file into the location that is specified in the MSExchangeSA event ID 2027 on the Exchange computer that is running the Recipient Update Service.
5. Restart the Microsoft Exchange System Attendant service on the Exchange computer.
6. Monitor t
Reference LinksExchange Recipient Update Service does not stamp proxy addresses in Exchange 2000 Server and in Exchange Server 2003

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.