It can also be an indication that you have some malware or rootkits on the Exchange server, you might want to try running Rootkitrevealer on the server http://www.sysinternals.com/Utilities/RootkitRevealer.html and see what that comes up with. Mark Fugatt Dedicated Supportability Engineer (Exchange) Microsoft Limited Desk: +44 (0)118 909 5630 Mobile: +44 (0)7966 858108 MSN IM: markfu@xxxxxxxxxxxxxxxxx Blog: http://blogs.technet.com/mfugatt Dedicated to proactively supporting Microsoft's enterprise Customers If you have any feedback about my work, please let either myself or my manager Andy Gitsham know at andygi@xxxxxxxxxxxxx <mailto:andygi@xxxxxxxxxxxxx?subject=Feedback%20on%20Mark%20Fugatt%20(Ex change%20DSE)> or telephone +44 118 909 3233 ________________________________ From: Tony Afriyie [mailto:Tony.Afriyie@xxxxxxxxxxxx] Sent: 03 March 2006 11:03 To: [ExchangeList] Subject: [exchangelist] RE: Maximum number of simultaneous registrations for MAPI notifications http://www.MSExchange.org/ Here is the info I came accros from www.eventid.net <http://www.eventid.net/> : "As per Microsoft: "When a MAPI client (such as Outlook) starts and connects to an Exchange server, the client registers itself with the Information Store. The client registers its User Datagram Protocol (UDP) post and an IP address so that the server can use this information to communicate to the client when a new message is received by the store for the client. This is called a PUSH NOTIFICATION because the Server PUSHes this information to the client. The server saves the client's Push Notification Registrations in its memory. When a new message is received for a particular client, the server looks up that client's registration information (UDP port and IP address) and informs the client that a new message is waiting in the store. It is then the client's responsibility to download the information so that the user sees the new mail. Exchange Server now has a limit on the default number of registrations (and context size settings) that can be set up by a particular client. This is set on the server by adding a registry entry and prevents clients from registering more push notifications than set. In such a situation, if the client attempts to set more than the expected number of Push notification registrations an MSExchangeIS event 9671 is logged in the server's application log". " ________________________________ From: Mark Meelhuysen [mailto:Mark@xxxxxxxxxxxx] Sent: Friday, March 03, 2006 3:51 AM To: [ExchangeList] Subject: [exchangelist] Maximum number of simultaneous registrations for MAPI notifications http://www.MSExchange.org/ Hello all, On an Server 2003 (SP1) machine with Exchange 2003 (SP2) i get the following error: Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 9671 Date: 2-3-2006 Time: 5:01:57 User: N/A Computer: DC-VERTON Description: User SYSTEM has exceeded the allowed maximum number of simultaneous registrations for MAPI notifications. The configured maximum number of event notification registrations is 8. For more information, click http://www.microsoft.com/contentredirect.asp. Data: 0000: 31 00 30 00 2e 00 32 00 1.0...2. 0008: 30 00 30 00 2e 00 31 00 0.0...1. 0010: 34 00 2e 00 31 00 00 00 4...1... Can anyone tell me what I should do? I followed the link and it says: The administrator can set the maximum number of registrations and the context size setting by adding the following REG_DWORD values to HKLM\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem: * Maximum Allowed Client Context Size (default is 16 bytes). * Maximum Allowed Notification Registrations Per Client (default is 8). But these values are not present. Thanks in Advance. Mark ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange <http://www.webelists.com/cgi/lyris.pl?enter=exchangelist%0bExchange> Newsletters: http://www.msexchange.org/pages/newsletter.asp ------------------------------------------------------ Visit TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You <http://www.techgenix.com%0b-------------------------------------------- ----------%0bYou> are currently subscribed to this MSExchange.org Discussion List as: Tony.Afriyie@xxxxxxxxxxxx To <mailto:Tony.Afriyie@xxxxxxxxxxxx%0bTo> unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report <http://www.webelists.com/cgi/lyris.pl?enter=exchangelist%0bReport> abuse to info@xxxxxxxxxxxxxx ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange <http://www.webelists.com/cgi/lyris.pl?enter=exchangelist%0bExchange> Newsletters: http://www.msexchange.org/pages/newsletter.asp ------------------------------------------------------ Visit TechGenix.com for more information about our other sites: http://www.techgenix.com ------------------------------------------------------ You <http://www.techgenix.com%0b-------------------------------------------- ----------%0bYou> are currently subscribed to this MSExchange.org Discussion List as: markfu@xxxxxxxxxxxxx To <mailto:markfu@xxxxxxxxxxxxx%0bTo> unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report <http://www.webelists.com/cgi/lyris.pl?enter=exchangelist%0bReport> abuse to info@xxxxxxxxxxxxxx