• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 150
  • Last Modified:

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.Service, M.E.RpcClientAccess.Server, M.E.R.S.RpcDispatch.UpdateActivityScopeMetadata, System.NullReferenceException, 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.Service, unknown, M.E.R.S.U.User.GetExOrgInfoFlags, System.NullReferenceException, 66bb, unknown.
ErrorReportingEnabled: False

I also get this gem of an error message in the RPC Access Log.

2016-09-06T18:50:46.840Z,15805,0,/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=067479fdfb4442a19f4c7c20fb71067a-Alex Diehl,,,16.0.6741.6564,,172.16.6.70,,fe80::4dbd:d2d:99f3:bebf%12,ncacn_http,,fe4a0e64-47d6-4236-a60f-cca49cf83339,"""{45B0B75F-933A-4F11-9DC8-F66FB9969478} Outlook=16.0.6741.6564 OS=6.1.7601 CPUArchitecture=9""",Connect,fault,00:00:00,"SID=S-1-5-21-874759239-810188976-2483500552-44036, Flags=None","Watson: [NullReferenceException] Object reference not set to an instance of an object.   at M.E.R.Server.UserManager.User.GetExOrgInfoFlags()     at M.E.R.Server.UserManager.User.UpdatePrincipalCacheIfNeeded()     at M.E.R.Server.UserManager.User.UpdatePrincipalCacheWrapped(Boolean ignoreCrossForestMailboxErrors)     at M.E.R.Server.UserManager.Get(SecurityIdentifier authenticatedUserSid, String actAsLegacyDN, String userDomain)     at M.E.R.Server.RpcDispatch.<>c__DisplayClassc.<EcDoConnectEx>b__8()     at M.E.R.Server.RpcDispatch.Execute(Func`1 getExecuteParame

I believe the problem is likely CU13 related but don't know that for sure.

Looking for some help on this one..
0
JeffMatthias
Asked:
JeffMatthias
1 Solution
 
Adam BrownSr Solutions ArchitectCommented:
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.
0
 
Ajit SinghCommented:
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!
0
 
JeffMatthiasAuthor Commented:
So I believe I have solved it.   The problem we were having and I don't have the slightest clue as to how it happened but around 83 of our users were missing the MSExchMailboxGUID in AD.  

I collected them from exchange online and added them in and public folders was again expandable.  

Like I said I have no idea why this randomly occurred.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now