What Causes Event ID 9646 32 And How Can I Fix It?

 

Approved: Fortect

1. Download Fortect and install it on your computer

2. Launch the program and click "Scan"

3. Click "Repair" to fix any issues that are found

Speed up your computer's performance now with this simple download.

Here are some simple methods to help you troubleshoot Event ID 9646 32. The root cause. This issue persists because the default maximum number of bindings that an account can open has been reached. By default, the account can functionally open a maximum of 32 EIS connections.

 

 

Exchange has several restrictions on objects and sessions, which in turn causes problems with the client. They can usually be identified by the msexchangeis server element error event ID 9646.

• Not all Outlook ring folders have been updated.
• Some folders are not visible (but visible in OWA).
• Issues with categories
• â €

Most of the time, users hit their limits when they have a full size folder structure (over 500 folders) or just have multiple shared mailboxes attached.

Outlook may display the status “This folder is finally updated …”. All folders have been updated.

MSExchangeIS Event ID 9646: mapi night “/ o = First Organization / ou = Administrative Group / cn = Recipients / cn = user “has exceeded the maximum number of items of type MSExchangeIS” objtfolderview “of 500,
with event ID 9646.: Mapi Session” / o = First Organization / ou = Administrative group / cn = Recipients / cn = user “has exceeded your current maximum of 500 design and style objects” objtFolder “.

MSExchangeIS Event 9646: Mapi session ID ‘sessionid’ has exceeded the maximum number of 32 session objects.

While some restrictions are session restrictions, others are open.

Resolution

You can solve this problem by making changes to the register (must be done on each trade page of the organization):

1. Open Registry Editor (regedit.exe).
2. Go to the path HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services MSExchangeIS ParametersSystem
3. Create a new DWORD value (32 bits) specific in ParametersSystem
4. Rename the key to ” The maximum number of sessions allowed for one user. ”
5. Set this new limit to 100 (32 by default, you can set it to 50 or maybe 100, but also to much more)
6. To increaseshrinking sessions on the Client Access server, the RCAMaxConcurrency value must also be increased in its restriction policy.
7. Open Exchange Management Shell and create an organization-wide throttling policy (Exchange since 2013):

    New-ThrottlingPolicy -Name AllUsersPolicy -ThrottlingPolicyScope Organization -RCAMaxConcurrency 4000 - EwsMaxConcurrency 80 -OutlookServiceMaxConconnections 80 -OutlookServiceMaxConnections 80 -OutlookServiceO utlookO utlookO utlookO utlookO utlookO utlook .ServiceMaxConnection 80 -Outlook .Service evice 24 

8. If a dedicated policy is assigned to a significant user, the settings for that policy will be determined. The ice market requirements need to be adjusted.
9. Ensure that the owners of the modified throttling policy are assigned to the specific affected mailbox or to all mailbox users, depending on your needs.

1. Open Registry Editor (regedit.exe).
2. Go to the path HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services MSExchangeIS ParametersSystem
3. Create a section called MaxObjsPerMapiSession
4. Create a new DWORD value (32 bit) in MaxObjsPerMapiSystem
5. Rename the key to objtFolder and set the exact data value to 1000 (500 is de facto, much higher values ​​are possible). )
6. Repeat steps 1 and 5 for each type of object the person wants to extend (objtFolderView, objtMessage, objtMessageView, objtAttachment, objtAttachmentView)

Restart the Microsoft Information Store to remove the changes.

Mapi Session / o = First Organization / ou = Exchange Administrative Group (FVDIC0HF32SPDLT) / cn = Recipients / cn = 0f04a7eb750242018571d473ecc78ed4-Marin with AirSync client type exceeded the maximum number of message type objects – 250.

StrongYour error “with the AirSync client type has exceeded the maximum of 250 pieces”type Messageâ €, I found the document