Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

Some Users Unable to Expand Public Folders

Posted on 2016-09-08
4
Medium Priority
?
121 Views
Last Modified: 2016-10-28
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
Comment
Question by:JeffMatthias
3 Comments
 
LVL 43

Expert Comment

by:Adam Brown
ID: 41790426
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
 
LVL 17

Expert Comment

by:Ajit Singh
ID: 41791221
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
 
LVL 3

Accepted Solution

by:
JeffMatthias earned 0 total points
ID: 41794869
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

Featured Post

Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Today as you open your Outlook, you witness an error message: “Outlook is using an old copy of your Outlook Data File…”. Probably, Outlook is accessing an old OST file.
MS Outlook undoubtedly is the most widely used email client.Its user-friendliness, cost effectiveness, and availability with Microsoft Office Suite make it the most popular email application.  Its compatibility with Microsoft applications like Exch…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month20 days, 23 hours left to enroll

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question