JeffMatthias
asked on
Some Users Unable to Expand Public Folders
We have around 700 employees and about 50 of them have trouble expanding public folders. I have ruled out it being a client issue or a desktop or version of outlook issue. It seems to happen to all flavors of outlook but is mailbox related. I have entered a professional support case with Microsoft and a Microsoft online o365 case for the same thing. Neither group has been of any help and I have trouble getting them to escalate the case.
So here is the problem. We have two Exchange 2013 with a DAG running CU9 and we have two newly built exchange 2013 CU13 with a DAG. Whenever I move the public folders mailbox to the database on the new exchange 2013 cu13 dag we have 50 or so users that will never be able to access public folders. The rest can access it no problem.
We are running a hybrid deployment where we are keeping public folders on-premise and all of our users are in office 365.
I have combed through the logs and these two error messages flood the server 18 at a time when you try to expand public folders on a users account where it is unable to expand.
Watson report about to be sent for process id: 8016, with parameters: E12IIS, c-RTL-AMD64, 15.00.1210.003, M.E.RpcClientAccess.Servic e, M.E.RpcClientAccess.Server , M.E.R.S.RpcDispatch.Update ActivitySc opeMetadat a, System.NullReferenceExcept ion, 1e9, 15.00.1210.002.
ErrorReportingEnabled: False
Watson report about to be sent for process id: 8016, with parameters: E12IIS, c-RTL-AMD64, 15.00.1210.003, M.E.RpcClientAccess.Servic e, unknown, M.E.R.S.U.User.GetExOrgInf oFlags, System.NullReferenceExcept ion, 66bb, unknown.
ErrorReportingEnabled: False
I also get this gem of an error message in the RPC Access Log.
2016-09-06T18:50:46.840Z,1 5805,0,/o= ExchangeLa bs/ou=Exch ange Administrative Group (FYDIBOHF23SPDLT)/cn=Recip ients/cn=0 67479fdfb4 442a19f4c7 c20fb71067 a-Alex Diehl,,,16.0.6741.6564,,17 2.16.6.70, ,fe80::4db d:d2d:99f3 :bebf%12,n cacn_http, ,fe4a0e64- 47d6-4236- a60f-cca49 cf83339,"" "{45B0B75F -933A-4F11 -9DC8-F66F B9969478} Outlook=16.0.6741.6564 OS=6.1.7601 CPUArchitecture=9""",Conne ct,fault,0 0:00:00,"S ID=S-1-5-2 1-87475923 9-81018897 6-24835005 52-44036, Flags=None","Watson: [NullReferenceException] Object reference not set to an instance of an object. at M.E.R.Server.UserManager.U ser.GetExO rgInfoFlag s() at M.E.R.Server.UserManager.U ser.Update PrincipalC acheIfNeed ed() at M.E.R.Server.UserManager.U ser.Update PrincipalC acheWrappe d(Boolean ignoreCrossForestMailboxEr rors) at M.E.R.Server.UserManager.G et(Securit yIdentifie r authenticatedUserSid, String actAsLegacyDN, String userDomain) at M.E.R.Server.RpcDispatch.< >c__Displa yClassc.<E cDoConnect Ex>b__8() at M.E.R.Server.RpcDispatch.E xecute(Fun c`1 getExecuteParame
I believe the problem is likely CU13 related but don't know that for sure.
Looking for some help on this one..
So here is the problem. We have two Exchange 2013 with a DAG running CU9 and we have two newly built exchange 2013 CU13 with a DAG. Whenever I move the public folders mailbox to the database on the new exchange 2013 cu13 dag we have 50 or so users that will never be able to access public folders. The rest can access it no problem.
We are running a hybrid deployment where we are keeping public folders on-premise and all of our users are in office 365.
I have combed through the logs and these two error messages flood the server 18 at a time when you try to expand public folders on a users account where it is unable to expand.
Watson report about to be sent for process id: 8016, with parameters: E12IIS, c-RTL-AMD64, 15.00.1210.003, M.E.RpcClientAccess.Servic
ErrorReportingEnabled: False
Watson report about to be sent for process id: 8016, with parameters: E12IIS, c-RTL-AMD64, 15.00.1210.003, M.E.RpcClientAccess.Servic
ErrorReportingEnabled: False
I also get this gem of an error message in the RPC Access Log.
2016-09-06T18:50:46.840Z,1
I believe the problem is likely CU13 related but don't know that for sure.
Looking for some help on this one..
Check the permissions on the public folder hierarchy. The one time I had to deal with this issue when redirecting public folders on-prem, it was only resolvable by granting read permissions to the Anonymous group. Granted, that was with Exchange 2010, which didn't have the best Public Folders implementation. It's possible that the server to server mailbox move has changed permissions in some way, though. That's basically where I'd start.
Outlook users cannot access public folders in Exchange Server 2013 or Exchange Server 2016:
https://support.microsoft.com/en-in/kb/2788136
Also check this link:
https://support.microsoft.com/en-in/kb/2834139
Hope this helps!
https://support.microsoft.com/en-in/kb/2788136
Also check this link:
https://support.microsoft.com/en-in/kb/2834139
Hope this helps!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.