Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

event id 1016 2

Status
Not open for further replies.

sue77

IS-IT--Management
Sep 26, 2002
26
US
Windows 2000 advanced server with exchange 2000.

Event id 1016
source Perflib
The data buffer created for the "exoledb" service in the
"c:\program files\exchsrvr\bin\exodbpc.dll library not aligned on an 8-byte boundry. This may cause problems for applications that are trying to read the performance data buffer. contact the manufacturer of this library or service to have this problem corrected or to get a newer version of this library.

Tech net does not show this error.

Any ideas?
 
Sue77,

I found this on ExchangeAdmin.com, I hope it helps.

"I'm running Exchange Server 5.5 Service Pack 4 (SP4) on a Windows 2000 Server SP1 computer. I receive event ID 1016 messages for the MSExchangeWeb, MSExchangeMSMI, MSExchangeDS, and MSExchangeCCMC services. The event message says the data in the performance counter isn't aligned on an 8-byte boundary. Why am I getting these messages, and what can I do about them"? (Submitted by reader Greg Heinz.)

"The Microsoft article "XCON: Message Transfer Agent Generates Event 1016 When Logging Performance Monitor Counter in Windows 2000 Server" ( describes this problem. Event ID 1016 is an advisory telling you that the Win2K performance monitoring subsystem is receiving data that's not aligned on 8-byte boundaries. Windows NT didn't care, but Win2K does because 8-byte-aligned access is more efficient on some types of CPUs. The article mentions that Microsoft fixed this problem for the MTA in Exchange Server 5.5 SP4, but the fix evidently didn't make it to some other Exchange components. You can safely ignore these messages, though".

Patty [ponytails2]
 
Were seeing the same exact error on a W2K/sp2 box with E2k/sp3 installed. Did you ever find anything else out about the problem?

Thanks
 
No, I haven't heard anything else. Check out the link mentioned in the other reply. Apparently it just happens.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top