Event Error 9646
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Event 9646, MSExchangeIS - Mapi session exceeded the
Event Id 9646 Exchange 2010 Objtfolder
maximum - Exchange 2010 SP1 w/ Update Roll Up 2 Previous event id 9646 exchange 2010 objtmessage Versions of Exchange > Exchange Server 2010 Question 0 Sign in to vote Based on the older version
Event Id 9646 Exchange 2003
of this article here: http://support.microsoft.com/kb/2009942 I created the ParameterSystem Subkey, with the Maximun Polling Frequency key and set the Decimal value to 45000. This was to mitigate the mapi session exceeded the maximum of 32 objects of type session exchange 2010 delay issues in Outlook 2003. Ever since then I receive this error message in my event viewer. Event 9646, MSExchangeIS Mapi session "13fbc88b-c9fc-4b9c-9efd-14de7957eee4: /o=MYDOMAIN/ou=First Administrative Group/cn=Recipients/cn=MYUSER" exceeded the maximum of 32 objects of type "session". Another user get this: Mapi session "2e5673f1-a3bd-4d56-b988-03c1267012b2: /o=MYDOMAIN/ou=First Administrative Group/cn=Recipients/cn=MYUSER" exceeded the maximum of 250 objects of type "objtMessage". I have received about event id 9646 exchange 2007 6 of these. I'm not saying this started as a result of me creating the subkey...Microsoft would have to confirm that. I'm just saying that this is when I started to notice it. My system specs are: Exchange 2010 SP1 Enterprise - Update Roll Up 2 Windows Server 2008 R2 - All updated up until December 12, 2010. Any ideas?Treadstone Friday, March 11, 2011 8:18 PM Reply | Quote Answers 1 Sign in to vote @m.salah, I am not sure why would want to delete that Registry entry!!!!!!!!! Try this and it will fix the issue. Click Start, click Run, type regedit in the Open box, and then click OK. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem If the Maximum Allowed Sessions Per User entry does not exist, do the following: On the Edit menu, point to New, and then click DWORD Value. Type Maximum Allowed Sessions Per User as the entry name, and then press ENTER. Right-click the Maximum Allowed Sessions Per User entry, and then click Modify. Clic
» How to Resolve Exchange Event Error 9646? Exchange server is one of the most popular mail servers now- a -days. Its various advanced features such as: Connection filtering, Recipient filtering, Intelligent Message Filter and social
Airsync Exceeded The Maximum Of 250 Objects Of Type Message
collaboration makes it even more all the rage. Instead of having such phenomenal features, mapi session exceeded the maximum of 16 objects of type "session". sometimes you have to face hurdles in the smooth functioning of the application, the issues can occur due to hardware, software or
Maximum Allowed Service Sessions Per User
some other reasons. While working with Exchange a user can have to face different kind of errors. Event ID 9646 is one of the common error IDs received while working with Exchange. Resolve Exchange Errors & https://social.technet.microsoft.com/Forums/exchange/en-US/91922b60-38b7-4af3-ba13-3b44949cc9f7/event-9646-msexchangeis-mapi-session-exceeded-the-maximum-exchange-2010-sp1-w-update-roll-up-2?forum=exchange2010 Restore Mail Items withMicrosoft Exchange Recovery Software There can be several possible scenarios when Event ID 9646 can occur: You have just installed Microsoft Exchange Server. A third party application has been installed or a service account is created for the application, that conflicts with the Exchange server then, this error can be raised. The Number of opened MAPI sessions has exceeded the specified maximum default unit. The server that is running http://recover-email.blogspot.com/2013/08/how-to-resolve-exchange-event-error-9646.html is running in a forest or it is in the resource forest. If the resource forest have enabled accounts that ate linked with Disabled accounts in the resource forest then also this error can be raised. This event in the application log is commonly seen by Exchange users. If the event ID is raised due to any of the first three scenarios then you need to grant "View Information Store status" permission to the service account, so that it can open unlimited number of sessions. Run the following command to grant the permission: If the event ID occurs due to last two of the above mentioned scenarios, then the "View Information Store status" permission is to be granted at administrative group level. While using Outlook 2003 when a user receives the Event ID 9646 sometimes, the following error is also prompted. The above error ID may occur due to one of the following reasons: The issue can occur Microsoft Exchange Server 2003 Service Pack 1 (SP1) has been installed on your Exchange server system If many MAPI sessions are being run by any program on the client system, then the number of MAPI sessions to the Exchange Server computer can increase beyond the permitted maximum count. This can also cause the above iss
9646 and some seen this many times. An example might look like this. Mapi session /o=Exchange_orgname/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user with client type MOMT exceeded the maximum of 500 objects of type Folder. another example might end with http://anewmessagehasarrived.blogspot.com/2014/01/the-famous-9646-error-on-exchange.html this: .. exceeded the maximum of 250 object of type Folder View. Why does this happen? Exchange has some built-in thresholds for various things that try to stop bad user behavior or a client behaving badly to not use all resources on the server to make other users suffer. You can try to change client configuration for users experiencing this problems by changing cached mode on/off and also for extra mailboxes opened, outlook add-ons might also cause this. upgrading event id clients to newer version might also help, but sometime you cant change what users do and you must change limits instead. How to change limits You change limits by registry values and Microsoft has a TechNet article that describe these values Exchange Store Limits. The key here is to read the error text and find what threshold exceeded its limit, then read the TechNet article and implement a new threshold by editing registry values. One problem here is to event id 9646 decide what limits you should set, unfortunately you have to set a value and then see if its working or not. To have it all working you must restart Exchange services so don't count on this working until a restart is done. Article don't cover Exchange server 2013 but the same limits apply and also the same solution to add/edit registry values on your mailbox servers. Posted by Lasse Pettersson at 17:06 Labels: Exchange 2013 Newer Post Older Post Home Subscribe to: Post Comments (Atom) About Me Lasse Pettersson Kind of geeky guy that is excited about Exchange and Lync. I am a Microsoft Certified Solution Master and Exchange Server MVP View my complete profile Microsoft Certified Solutions Master Microsoft Certified Solutions Master Visitors to my site Blog Archive ► 2015 (3) ► August (1) ► July (1) ► March (1) ▼ 2014 (12) ► December (1) ► November (1) ► August (2) ► July (1) ► June (1) ► May (1) ► April (1) ► March (1) ► February (2) ▼ January (1) The famous 9646 error on Exchange servers ► 2013 (10) ► November (2) ► September (1) ► August (1) ► July (1) ► May (2) ► April (1) ► March (1) ► February (1) ► 2012 (14) ► December (2) ► November (2) ► October (2) ► August (2) ► July (1) ► June (1) ► May (1) ► March (1) `