Exchange 2013 User cannot view public folders

Good morning,
User was able to view public folders, then lost connection to public folders. User cannot view public folders in OWA.
Verified proper permissions. No changes have been made to the user account in AD, exchange.

Did you do a fresh install of Exchange, meaning there was no version of Exchange installed previously? If not, have you moved Public Folders over to Exchange 2013 yet? If the answer to this question is no, then you will not be able to view Public
Folders in OWA until they are migrated over Exchange 2013.

Similar Messages

Exchange 2013 users cannot open public folders on exchange 2010

Migrating from Exchange 2010 SP3 to Exchange 2013 CU3 in same forest and domain
client version is outlook 2013
outlook any where is disable (default) on exchange 2010 which must be disabled as organization policy
outlook any where external host name field is blank (we need to keep outlook any where disable for external)
outlook anywhere internal authentication is set to NTLM and Client require SSL to false
I have moved a mailbox from Exchange 2010 to Exchange 2013, user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010. I have been stuck on this kindly suggest

Hello,
Please explain the sentence "The user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010". Do you mean the moved user can't see the public folder or the user has no permission to see the public folder?
If the moved user can't see the public folder, please check if the moved user can see the public folder via owa. When you use outlook to view public folder, you can following the method: Open outlook, click folder list at the bottom of left panel.
If the user has no permission to see the public folder, please check the permission.
=============================================================
1. Open ADSIEDIT.
2. Navigation to CN=Configuration, DC=Your domain name -> CN=Services ->CN=Microsoft Exchange ->CN=Your organization name ->CN=Administrative Groups ->CN=Exchange
Administrative Group ->CN=Databases ->CN= PF Database.
3. Right-click the PF Database, and then select Properties. Under Security, check if everyone has read permission.
Besides, please check if public folder replication is ok. You can use Get-PublicFolderStatistics cmdlet to compare item count, size.
Additional article for your reference.
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2013 Users cannot access Public folder in Exchange 2007 SP3

Dears,
i am working in Upgrading Exchange 2007 to Exchange 2013 CU7,, I came to know with CU7 we have new way for coexistence with legacy Public Folder
https://technet.microsoft.com/en-us/library/dn690134(v=exchg.150).aspx
i did the steps exactly as it is in the article, but now users in Exchange 2013 always prompt for username /password when opening outlook and i found they still trying to connect to Exchange 2007 PF Server using HTTPS and failed..
BTW, Outlook anywhere is disabled in EX2007 and as per this article Q/A , it is no more needed
http://blogs.technet.com/b/exchange/archive/2014/11/07/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond.aspx
the issue now, still users getting prompted and cannot connect to PF in EX2007,,
your help is appreciated
thanks
Mufleh

I ran into the same situation recently, and found out that you need to make sure InternalClientsRequireSSL is set to false.
To verify: Run Get-OutlookAnywhere | fl Identity, *ssl
If it is true, try setting it to false.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Outlook - One user cannot expand public folders

I have one user who is having an issue with expanding Public Folders. They are the only one in their area who cannot expand it and I'm running out of troubleshooting steps. Here is a list of what I've tried/found for this issue. The Public
Folders are on Exchange 2007 and we have our mailboxes on Exchange 2013. Outlook version is 2010. This also does not work in our Citrix environment either.
Repaired email account
Removed/re-added Outlook profile
Log off/log on
Reboot PC
Confirmed that she can’t get to them in Citrix either
Checked the Outlook connection status, no Public Folders connection is listed there.
Rebooted the Public Folder server.
Removed/re-added PF permissions AD groups, log off/log
Move the mailbox do a different mailbox database
RPC Client Access service is running on the mailbox server
I am pretty much at a loss here and I am not sure what else to do. Thanks!

Hi,
From your description, only one user can't expand public folders in Exchange 2007 after you migrate users to Exchange 2013.
Could this user send or receive message normally?
Please use the Test E-mail Autoconfiguration to check result, compare with other normal users to see if there is any difference.
Please click on the link below to make sure your Microsoft Outlook is up to date.
http://support.microsoft.com/kb/2625547
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2013 user cannot mail 2010 user

Hello All, I am migrating from 2010 to 2013. The Exchange Server Deployment Assistant is proving very helpful thus far. I created a mailbox in 2013 and attempted to email a 2010 user. No luck - the email gets stuck in the queue "Last Error: 400 4.4.7
Message delayed". I can see that it is attempting to send the email to the correct database in 2010 but that is the extent of my troubleshooting knowledge.
I have yet to complete the step "Enable and Configure Outlook Anywhere" which states: "To allow your Exchange 2013 Client Access server to proxy connections to your Exchange 2010 servers, you must enable and configure Outlook Anywhere
on all of the Exchange 2010 servers in your organization." - I haven't yet done this because I didn't want anything destructive to happen to the current 2010 server, but perhaps to enable a 2013 user to send to a 2010 user this step needs to be completed
- thoughts? Btw, 2010 can successfully email a 2013 user. Is it a particular receive connector that I need to modify?
Cheers, db.

Hi Dennis,
if you go to your Ex 2010 Server, please install Telnet-Client ; you can do this from Powershell using "install-windows-Feature telnet-client".
1. run a Powershell or CMD
2. telnet exchange2013server 25
Does it connect using the Exchange 2013 CAS / Transport Server Name?
If no, please check
1. is there any anti Virus / Firewall Software blocking the Connection?
2. is there any Firewall on the Network blocking the SMTP Connection?
3. does your receive connector include the subnet of your Exchange 2013 CAS server?
If you cannot connect verify please the remote IP range includes your new servers , check it running
Get-ReceiveConnector | fl name,binding,remoteipranges
from Powershell. If required, use set-receiveconnector to Change it.
http://technet.microsoft.com/de-de/library/bb125140(v=exchg.150).aspx
Regards,
Martin

Exchange 2013 Mailbox Using 2010 Public Folders

Firstly, we will not be migrating completely to Exchange 2013 public folders for quite a while. Our first Ex2013 server is in a small branch office and won't be appropriate to hose the PF's for the entire company. Our environment consists of
8 Ex2010 servers and now the one Ex2013. I setup a test mailbox on the 2013 server and it access a 2010 PF database on another server just fine. How is that server discovered, and can we specify which one it uses? I understand the way 2013
public folders are moving but is there a downside to leaving our configuration this way for a long period of time?

Yes, the procedure should be followed to move mailbox first. Once you have successfully moved all the mailbox to new exchange server, you can migrate public folder after that.
You can also checekout this thread related to public folder migration from exchange 2010 to 2013 :
http://social.technet.microsoft.com/Forums/exchange/en-US/b7a35a45-9b74-4910-9dc3-c997bc71f03f/migration-form-exchange2010-to-exchange2013?forum=exchangesvrdeploy
Further, for a better convenience, you can also take a look at this application (http://www.exchangemailboxmigration.com/) which would be a good approach while migrating mailboxes and public folders
between two exchange server. It ensures about the data security and email contents during the completion of entire migration process.

User Access to Public Folders Disappearing (Outlook 2013)

I have one particular user who is losing access to public folders in Outlook 2013. I have found that going to
File > Account Settings > Account Settings > Email [TAB] > Repair... and then following through that dialog temporarily restores public folder access after restarting Outlook. However, once Outlook is restarted
for 30-60 seconds, the public folders disappear again. This is only happening for this one user. They receive their public folder permissions via group membership. Other group members report no such issue. I had another user with identical permissions
log into the same workstation and they again had no issue.
What could be causing this? This is a particularly bothersome problem since this user happens to be the office scheduler and the calendar they schedule on is public (which, thanks to reduced functionality in Exchange 2013, is no longer accessible in OWA).
Tech specs: Exchange 2013 CU5 accessed from Outlook 2013 running on Windows 8.1 Update. Outlook did not log any events during the time when public folders were dropped, nor are there any network connectivity issues being logged.
Any ideas for resolving this?

Hi,
Please check the connection status for Outlook.
Press the CTRL key and right-click the Outlook icon in the notification area, then select Connection Status.
Please run the command get-mailbox administrator | fl defaul* to check the default public folder mailbox for this affected user.
Do you have mail-enabled public folders? If you have mail-enabled public folders, you can check if this user can view public folders in OWA.
If possible, please re-add the public folder permissions for this user to check result.
Best regards,
Belinda Ma
TechNet Community Support

Cannot expand public folders in Outlook but can in OWA

Hi All,
I have a problem which I hope some one might be able to shed some light on. Firstly, the environment is Exchange 2010 (v 14.01.0438.000) and all clients use Outlook 2007. We have one user in the organisation who recently noticed that he cannot expand public
folders. He had been able to do so a couple of months back but could not pin point the time it stopped working. The error received reads :-
"Cannot expand the folder. The set of folders cannot be opened. The attempt to log on to Microsoft Exchange has failed."
I thought that this might be a permissions issue but this particular user can access the public folders via OWA. Also, my AD account was a copy of this user's and I can access public folders without issue.
I have tried the following so far :-
Tried running Outlook in safe mode
Tried recreating the Outlook profile.
Tried creating a new Outlook profile on a different client PC.
Tried running Outlook in cached an online modes.
Ran Exchange BPA and found no issues.
Checked ADSIedit for old administrative groups left over from past migrations.
used the test-outlook connectivity cmdlet from powershell which ran it's tests successfully.
This user originally set up all the public folders and was still listed as the owner of all of them.
Tried creating a new public folder.
Checked for an Outlook update that had caused a similar issue.
All the above failed to progress the situation. I have come across posts online that sound very similar, one stated that a Microsoft tech had found a permission that wasn't correct but didn't list which permission and the other related to an update to Outlook
that had triggered it. I can confirm it's not the update and I have checked permissions in the public folder management utility in Exchange. Also, my AD account is a copy of his and I can access the folders without issue.
I have also considered what may have changed on the network recently. The only major change has been a new admin password but I cannot see how that would be relevant.
Any help would be hugely appreciated!
Thanks in advance!

Hello John: We are having the exact same issue. Thank you for the great description, it hits the nail on the head for an issue that is tough to explain. Did rebuilding the mailbox fix the problem? We thought a next step would be to create a new
AD profile for the user all together, although replacing the user herself would be easier for us. She obviously caused this problem and will most likely cause us more problems that might be worse if she keeps clicking and sliding on every thing that
is shiny to see what it does..
I can only surmise that CaRa ChEn has decided to "better understand customer views on social support experience" elsewhere. I think the only logic for the mailbox suggestion would be "grasping for straws" and it is the only thing you have not tried
so far. (Other than replacing the user). Pactera employees get points for being the first to reply to a question and the first to have a suggestion marked as helpful as well as the sheer quantity of replies to the forums that are made. High
value is placed on moving posts to different forums as well so I thought I would ask quick before the thread gets shoveled somewhere else.. If she needs help with the interview project she can find plenty of my thoughts here in the community.
Thanks again, and we will reply back if replacing the user (account) does NOT solve the problem, otherwise one can assume we are happy campers again our new employee and remember just because it is blinking does not mean you should click on it. :)
Best regards,
RickkEE

Calander Sharing Permission is not effective between Exchange 2007 & Exchange 2013 User

When a Exchange 2013 mailbox user share a calander with user in Exchange 2007 with OWNER permission, but Exchange 2007 user cannot modify or view full details of Exchange 2013 user calander.
And same behavior from Exch2007 user sharing calander with Exch2013 user.
In both scnarioes we can view only free/busy information. Cannot see full details of the meetings, cannot edit/modify. But permissions are set correctly.
Getting Yes or No prompt window with message "You dont have permission to view the calander, Do you want to as User A to share his or her calander with you?"
We are in Co exsistance with Exch2007 and Exch2013 CU3.

Hi,
Does the issue happen to all users? What about Exchange 2007 users share calendar with Exch2007 users?
Please double check whether calendar permissions are configured properly. If possible, we can remove the permission in Outlook then re-add it back later to check whether it works.
Thanks,
Winnie Liang
TechNet Community Support

Viewing Public Folders on Android

Is it possible to view public folders on an iPhone or Android device. We are currently on Exchange 2010 and I can't seem to find a way to do this without a third party product. Is it possible in Exchange 2013 without the use of a third part product.
Also if anyone know of a way to do this without a third part product in exchange 2010 that would be great.
My other thoughts were to do away with public folders.
Please advise.
Thanks,

Hi
We could only access Public Folder only via OWA Light version through mobile but it does not support public folders in it and you won't be able to open them.
Unfortunately, Public folders sync is not supported via activesync unless you try them with 3rd party solutions which is not recommended by Microsoft to use because it might cause some other connectivity issues.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
Regards,
Sathish
Sathish

User cannot view dimensions within EPMA Dimension Library in Shared Library

Greetings,
I presume this must be a security issue, but user cannot view his dimensions in the shared library in EPMA. He can, however view view his application, update the local dimensions, and push to Essbase.
If this is a security issue, what assignment should I provision to enable the user to see these shared dims. Many thanks.

Give that user the rights of
Dimension Editor found under Foundation Service --> Shared Service --> EPMA Administrator and then try again.
Thanks.
HyperEPM

Exchange 2013 users cant connect to public folders on Exchange 2010

Hi
I recently migrated all users from exchange 2010 to 2013 and now nobody can connect to public folders.
Ive read several forums with similar issue, but none of the solutions have fixed my problem.
My configuration on exchange 2013:
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
ive also removed negotiation from the rpc site on the IIS.
Is there something else im missing?
Thanks
/Carlos

Are you getting any error message when accessing the Public Folder?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Cannot migrate exchange 2013 user to another database through EMC, only powershell works?

Hi Everyone,
I'm trying to migrate a few mailboxes from a database called "primary" to "archive". I can migrate a single user through powershell, however I cannot migrate users through the GUI. When the "syncing" starts, it reverts the total
from "2" to "0" and makes it appear as though I never added any users to the batch job. The job then completes "successfully"
I can see the users in the job before I hit start. Any idea why my job goes blank?
I'm running exchange 2013 CU6

Hi ,
Thank you for your question.
We could refer to the following steps to troubleshoot:
Restart IIS to check if the issue persist.
End up of the user job to check if the issue persist.
Create a new account to check if the issue persist.
We could check relevant application log, then we could check if EAC and EMS connect to same domain controller, then we could check sync between Exchange server and domain controller.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Exchange 2010 users cannot open Exchange 2013 shared mailbox

Title says it all.
We're in the process of migrating 1000+ mailboxes to Exchange 2013. A number of shared mailboxes have been migrated, but those users still on 2010 cannot open them.
Is this just how it is, or is there a way around it?

Hi,
I tested in my lab, if the shared mailbox is on Exchange 2010, I could open this shared mailbox successfully. Then I moved this shared mailbox to Exchange 2013, after that, I couldn’t open it anymore, I got the following error:
Besides, I tried to open a shared mailbox on Exchange 2013 which was not moved from Exchange 2010, it is the same error message.
Based on the test, it seems that Exchange 2010 users can’t open shared mailbox on Exchange 2013. So I recommend you move those users to Exchange 2013.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2013 user cann't access exchange 2013 public folder

Hi, during the coexistence exchange 2007 and exchange 2013, outlook is unable to access public folder of exchange 2007 from exchange 2013, I've install CU2 for exchange 2013 and also set authentication to Ntlm, but also failed. please help to look into this
problem, thanks.
belows are information about outlook anywhere in our exchange.
exchange 2007：(primary site)shmail04,shmail05,shmail06; (DR site)drpmail05,drpmail06
exchange 2013：(primary site)shcas01,shcas02; (DR site)wxcas01
Identity                         : SHCAS01\Rpc (Default Web Site)
InternalHostname                : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : True
ExternalHostname                : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : SHCAS02\Rpc (Default Web Site)
InternalHostname                : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : True
ExternalHostname                : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : WXCAS01\Rpc (Default Web Site)
InternalHostname                : infor.tdw.com
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : True
ExternalHostname                : infor.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : SHMAIL04\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : SHMAIL05\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : SHMAIL06\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : DRPMAIL05\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}
Identity                         : DRPMAIL06\Rpc (Default Web Site)
InternalHostname                :
InternalClientAuthenticationMethod : Ntlm
InternalClientsRequireSsl       : False
ExternalHostname                : legacy.tdw.com
ExternalClientAuthenticationMethod : Ntlm
ExternalClientsRequireSsl       : True
IISAuthenticationMethods          : {Ntlm}

Hi,
I have found an article said that we need to set the external host name the same. See more details in the following link:
http://blogs.technet.com/b/mspfe/archive/2013/10/21/upgrading-to-on-premises-exchange-server-2013.aspx
To allow your Exchange 2013 Client Access server to redirect connections to your Exchange 2007 servers, you must enable and configure
Outlook Anywhere on all of the Exchange 2007 servers in your organization. If some Exchange 2007 servers in your organization are already configured to use Outlook Anywhere, their configuration must also be updated to support Exchange 2013.
The following configuration is set on each Exchange 2007 server:
The Outlook Anywhere external URL is set to the external hostname of the Exchange 2013 server.
Sent By
Silver

Exchange 2013 User cannot view public folders

Similar Messages

Maybe you are looking for