Exchange 2016 - Event 1023, Perflib

Question

_{Monday, April 16, 2018 3:03 PM}

I am attempting to follow the corrective action as described https://social.technet.microsoft.com/wiki/contents/articles/38123.exchange-2016-event-1023-perflib.aspx for event id 1023 "Windows cannot load the extensible counter DLL MSExchangeIS. The first four bytes (DWORD) of the Data section contains the Windows error code." however same as comment left earlier on same page, I am unable to identify the files "md*" and "perfnm.h" being referred to in exchange 2016 or exchange 2016 CU9 iso. Can somebody guide on way forward to error or an alternative as I have been unable to identify the files being referred to.

All replies (4)

_{Tuesday, April 17, 2018 6:53 AM ✅Answered | 2 votes}

Hi Grayman,

You can download Exchange 2010 SP3 and extract the files, then find the files "md*"&"perfnm.h" under the path:

"\setup\serverroles\common\perf\amd64"

Hope it helps,

Best Regards,
Niko Cheng
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact [email protected].

Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

_{Tuesday, April 17, 2018 9:10 AM | 1 vote}

Thank you, this helps. Files being referred to were found and carried over to Exchange 2016 CU9 installation.

To get rid of another error event ID 1008 as described https://support.microsoft.com/en-us/help/307613/error-messages-are-logged-when-you-try-to-collect-performance-counters  ,  after copying files to C:\Program Files\Microsoft\Exchange Server\V15\Bin\perf\AMD64\ the following commands were run from the admin prompt;

lodctr.exe C:\Program Files\Microsoft\Exchange Server\V15\Bin\perf\AMD64\Mdbperf.ini

lodctr.exe /e:MSExchangeIS

_{Monday, February 25, 2019 5:13 PM}

Thank you for posting this.

_{Thursday, April 4, 2019 8:42 AM}

Your reply suggested that he or she download Exchange 2010 SP3 though the problem is on Exchange 2016,does it mean the 2010 Exchange files are compatible to 2016 and why you suggested 2010 SP3,Why not exchange 2016?