There is an article out there that addresses the issue that some of our customers are seeing:828764 "Event 8197" Error Message Is Logged Repeatedly in the Application Eventhttp://support.microsoft.com/?id=828764It says that if you are getting this, there is a good chance that Exchange is trying to authenticate against a GC that doesn't have a trust with the domain that your Exchange 5.5 service account is in. But... How do you verify this? Can you just look at the DSaccess tab on the Exchange server? No. As Jasper Kuria states in his post at http://blogs.technet.com/exchange/archive/2005/07/29/408394.aspx in this instance we don’t look at the output from DSAccess. This is authentication, not an LDAP call. In this case we look at the same GC that you would get if you were to run “nltest /dsgetdc: /gc”. If you are getting 8197s on your Exchange servers, you can run this and see if you are getting a GC in another domain that doesn’t have an explicit trust with the domain that the Exchange 5.5 service account is in. In fact if you have auditing on and look at the GC’s security logs you may see something similar to the following:
Event Type: Failure AuditEvent Source: SecurityEvent Category: Account Logon Event ID: 680Date:Time:User: NT AUTHORITY\SYSTEMComputer: <GC Server Name>Description:Logon attempt by: MICROSOFT_AUTHENTICATION_PACKAGE_V1_0Logon account: <Exchange 5.5 Service Account>Source Workstation: <Exchange 2003 server>Error Code: 0xC0000064
At this moment there are currently two workarounds:
Hopefully this will help someone else who is seeing this...
Just read this in the news: We are releasing SP2 for Office 2004 for Mac today. This includes much needed fixes to Entourage, the Exchange client for Mac.
http://www.microsoft.com/presspass/press/2005/sep05/09-20EnhancedEntourage2004PR.mspx
It is available at http://www.microsoft.com/mac now.
If you have Entourage clients, for your Exchange server 2003 you will want to make sure you have the fix at http://support.microsoft.com/kb/888619 installed.(Edit - SP2 is up there now...)
Here are some things brought out in the document:
This is really just a small part of the great information in the release notes. I strongly encourage you to read it because it is a interesting read.
When running Exchange Best Practices Analyzer (EXBPA) you may get a report saying “The number of free page table entries is low, which can cause system instability”. This may be incorrect if you are running Windows 2003 but don’t have Windows 2003 SP1 installed. The issue is that EXBPA uses the Perfmon counters for the Free System Page Table Entries (FreeSysPTEs) and that counter could be wrong. The Performance tool does not accurately show the available Free System Page Table entries in Windows Server 2003http://support.microsoft.com/default.aspx?scid=kb;en-us;894067This was resolved in Windows 2003 SP1. If you don’t have the ability to install SP1 yet and want to know what the real value is, you could follow the directions in the KB article 894067. That article recommends of getting the tool LiveKD from Sysinternals. Now... should you do this on a mailbox server that is in production? How familiar are you with live kernal debugging? Never done it before? Then I would stick to seeing if I could get the Service Pack installed instead.
The Performance tool does not accurately show the available Free System Page Table entries in Windows Server 2003http://support.microsoft.com/default.aspx?scid=kb;en-us;894067
It looks like Paul Flaherty has updated the Microsoft Platform Support Reporting Utility (MPSReports) for Exchange. We have had this utility available for some time at this location, but the new version is not up there yet. You can download the new version here. The name of the file is MPSRPT_Exchange.zip.
Some of the things it does:
An older version is still online at the downloads site, but if you have an issue and need support, the new version may be the tool that you will want to run to collect information.