Exchange 2013 - Out of office unavailable when shared mailboxes added in

Good Morning all,
I have a strange issue with our MS Exchange 2013 environment concerning out of office.
When certain users try and access the OOO it gives them the below error message:
"Out
Of Office cannot be display because the server is currently unavailable"
As I mentioned, this is not affecting all users, here comes the strange part(I think so anyway)
The users in question have a shared mailbox added, if I remove the mailbox VIA ECP / Outlook client, out of office begins to work, once I add the mailbox back in, everything works, until the next day or some sort of refresh takes place and then OOO becomes
unavailable again.
Any help would be greatly appreciated.
Thanks,
San.

Did you recently installed windows update?
If yes, then check this, see if it applies by uninstalling the update.
http://windowsitpro.com/blog/update-causes-outlook-2013-fail-open-archive-mailboxes
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.

Similar Messages

Exchange 2010 Out of Office Assistant not working?

New server with a new Exchange 2010 install into an existing domain...
When users on both the internal network and external network try to access the Out of Office Assistant they get an error message of: " Your Out of Office settings cannot be displayed, because the server is currently unavailable".
I have done tons of research on WebServicesVirtualDirectory and AutodiscoverVirtualDirectory and set both internal and external URL's that work if you go to them in IE )internally and externally offsite).
Here are the settings of Autodiscover and Webservices:
[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory | Format-List
RunspaceId : 86aaf7fc-ca19-45b2-87d1-45ec432a670d
CertificateAuthentication :
InternalNLBBypassUrl : https://MAILSERVER.domain_name.local/ews/exchange.asmx
GzipLevel : High
Name : EWS (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : True
DigestAuthentication : False
WindowsAuthentication : True
MetabasePath : IIS://MAILSERVER.domain_name.local/W3SVC/1/ROOT/EWS
Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS
Server : MAILSERVER
InternalUrl : https://MAILSERVER.domain_name.local/EWS/Exchange.asmx
ExternalUrl : https://mail.domain_name.com/owa
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=EWS (Default Web Site),CN=HTTP,CN=Protocols,CN=MAILSERVER,CN=Servers,CN=Exchange Adm
inistrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=M
icrosoft Exchange,CN=Services,CN=Configuration,DC=domain_name,DC=local
Identity : MAILSERVER\EWS (Default Web Site)
Guid : 4639e4b9-9cf3-4f92-8940-f7c31e07cd47
ObjectCategory : domain_name.local/Configuration/Schema/ms-Exch-Web-Services-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchWebServicesVirtualDirectory}
WhenChanged : 4/1/2010 2:47:37 PM
WhenCreated : 3/11/2010 11:02:22 AM
WhenChangedUTC : 4/1/2010 8:47:37 PM
WhenCreatedUTC : 3/11/2010 6:02:22 PM
OrganizationId :
OriginatingServer : DOMAINCONTROLLER.domain_name.local
IsValid : True
[PS] C:\Windows\system32>AutodiscoverVirtualDirectory | Format-List
RunspaceId : 86aaf7fc-ca19-45b2-87d1-45ec432a670d
Name : Autodiscover (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated, WSSecurity}
LiveIdSpNegoAuthentication : False
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : True
DigestAuthentication : False
WindowsAuthentication : True
MetabasePath : IIS://MAILSERVER.domain_name.local/W3SVC/1/ROOT/Autodiscover
Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Autodiscover
Server : MAILSERVER
InternalUrl : https://MAILSERVER.domain_name.local/autodiscover/autodiscover.xml
ExternalUrl : https://mail.domain_name.com/autodiscover/autodiscover.xml
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=Autodiscover (Default Web Site),CN=HTTP,CN=Protocols,CN=MAILSERVER,CN=Servers,CN=Exc
hange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organiza
tion,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain_name,DC=loca
l
Identity : MAILSERVER\Autodiscover (Default Web Site)
Guid : 7a234ea2-20fc-412b-bbf0-3ea5f965d8da
ObjectCategory : domain_name.local/Configuration/Schema/ms-Exch-Auto-Discover-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchAutoDiscoverVirtualDirectory}
WhenChanged : 4/1/2010 3:00:49 PM
WhenCreated : 3/11/2010 11:02:07 AM
WhenChangedUTC : 4/1/2010 9:00:49 PM
WhenCreatedUTC : 3/11/2010 6:02:07 PM
OrganizationId :
OriginatingServer : DOMAINCONTROLLER.domain_name.local
IsValid : True
Test-OutlookWebServices comes up with errors. The Test E-mail AutoConfiguration within Outlook still appears to be looking for Autodiscover at different URLs...
OOF within Outlook Web App functions.
Any suggestions would be helpful!

From your previous post, I understand that OOF doesn't work for both internal and external clients. Error message "Your Out of Office settings cannot be displayed, because the server is currently unavailable" was received from Outlook client side. Please correct me if I have any misunderstanding.
Before we go any further, I would appreciate your help in clarifying the following questions:
1. When did this issue begin to occur, since the installation of Exchange 2010?
2. Can we access and configure OOF from OWA?
As internal & external clients are using different methods/URL to access Autodiscover and EWS, which provided OOF service, I recommend we focus on the internal users first.
To troubleshoot this issue, please install the hotfix mentioned in the following KB on the Exchange Client Access Server first:
Outlook 2007 crashes or you cannot access OOF settings after you install a package that contains the .NET Framework 3.5 with SP1 and the .NET Framework 2.0 with SP2 on an Exchange 2007 Client Access server or on an Exchange 2010 Client Access server
http://support.microsoft.com/kb/958934
After that, check if the issue remains. If there is still problem, please help me collect:
1. Test E-mail AutoConfiguration from Outlook client
1. Launch Outlook 2007 using a correct configured profile.
2. Hold down the CTRL key on your keyboard and click the Outlook icon in the notification area of the Windows taskbar, also known as the notification area.
3. In the menu that appears, click Test E-mail AutoConfiguration.
4. Enter your E-mail Address and Password (if not logged into the domain) in the respective edit boxes.
5. Choose the desired auto configuration methods with Use Autodiscover, clear other selection.
6. Click Test.
7. Please send me the screenshot of the result tab and log tab.
2. Result files after running the following command on the Exchange 2007 server
Get-ExchangeCertificate | FL >C:\cert.txt
Get-WebServicesVirtualDirectory –Server ServerName | FL >C:\EWS.txt
Get-AutodiscoverVirtualDirectory –Server ServerName | FL >C:\Audis.txt
Get-ClientAccessServer | FL >C:\cas.txt
Email them to me at [email protected]
With the title as
"Exchange 2010 Out of Office Assistant not working?"
Regards
Fazal M khan

Out of office message when sending mail to Lotus Notes from SAP

Hi,
Is it possible to have an 'out of office' message when sending mail to Lotus Notes from SAP?
I'm sending account statements by mail via a modified version of function FI_OPT_ARCHIVE_CORRESPONDENCE. The SAP username is send as a parameter, and later converted to the e-mail saved in the user profile. This works, - but I would like to have an out of office reply if the user I send to is out of office.
Hope someone can help...
Regards,
Lene

As Thomas pointed out, you can use regular SMTP mail to send the contents to Lotus Notes. You can use the function module SO_OBJECT_SEND or any of the SAP Office function modules to do this.
Only thing to remember is that the SMTP may have been disabled by your basis team due to security risks involved. An alternative could be a lotus notes connector available from IBM.
Srinivas

First exchange 2013 server install in coexistence: Recreating arbitration mailboxes first

Hi
We have exchange 2010 servers and I want to introduce the first exchange 2013 server.
Some of our arbitration mailboxes currently in 2010 have become corrupt and my initial exchange 2013 installation failed.
Question: Can I remove existing exchange 2010 arbitration mailboxes and recreate them using EXCHANGE 2013 "SETUP /PrepareAD"???????? Afterall there are no 2013 servers in the environment yet
I wonder if it will fail due to version incompatibilities
Thanks

Hi,
Agree with DJ Grijalva. Exchange 2013 /prepareAD will create the arbitration mailboxes for Exchange 2013. And the arbitration mailboxes between Exchange 2010 and Exchange 2013 are different. So I recommend you use the 2010 /prepareAD to recreate the arbitration
mailboxes for 2010.
Hope my clarification is helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Outlook 2013 with Exchange 2007 - out of office problem

We are using outlook 2013 with Exchange 2007. When users select their out of office it will work fine for the first day, however there after the Out of Office replies stop working. Out of Office is set correctly within Outlook, but what we have found
is that if the user opens Outlook the Out of Office starts to work again. Also when the user opens Outlook it takes around two minutes before it registers that Out of Office is on.
Any Ideas?

Hi,
How do you configure your OOF? From standard OOF wizard or define an automatic reply template from Rule wizard?
If you are using a template, Outlook must be running for the Rules Wizard to automatically reply. Please refer to the Note in the following KB:
http://support.microsoft.com/kb/311107
If it is configured by using standard Out of Office assistance in File > Automatic Replies, please remove OOF settings in Outlook and set it from OWA 2007, then check whether the issue can be reproduced.
Regards,
Winnie Liang
TechNet Community Support

Outlook 2007 & Exchange 2007 - Out of office assistant not working

Hi,
when using outlook 2007 and the users mailbox is on an Exchange 2007 server the out of office assistant doesn't work. When you start the out of office assistant the following message is displayed:
'Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later.'
Using Outlook 2003 and connect to the same mailbox, the assistant works fine, however you don't have the additional features new to the Assistant.
Also, when using outlook 2007 and connect to an Exchange 2003 mailbox the out of office assistant is also functioning fine.
Using Outlook Web Access on Exchange 2007 to set the out of office assistant works also fine, so the error message is not correct.
Any idea how to fix this ?
Franc.

Whilst I agree that auto-discover and other comment's could be upheld, I know that even when EWS and auto-discover are setup correctly that this problem will still occur.
I manage an Exchange 2007 environment with 300 users and and Exchange 2010 environment with 700 user's all using Outlook 2007. We are in the progress of deploying Outlook 2010 but I know with the new authentication process of the Outlook
client with Exchange 2007 or older and Outlook 2007 or older, this problem will still occur.
I know that their are just a few out of a 1,000 user base that experience this problem, so I don't see how global settings and configurations and settings are the culprit.
Just like the problem caused by a badly designed update in November or December of last year that meant auto-discover does not auto-configure a new Outlook profile because it would not detect the user's e-mail address but somehow create some random e-mail
address with the AD account name before the @ and the FQDN for the domain name, which involved a further release of another update several month's later to fix that.
Plus the other problem with the daily and frequent prompt's throughout the day for OWA domain login credential's despite being authenticated and Outlook contacting Exchange fine signified by the bottom-right hand corner status stating so. I press escape
and Outlook carries performing as normal for it do the same a few hours later, however I find that after about half a dozen prompt's over several days, it will disconnect the Outlook client saying 'Need Password' in the bottom-right, which despite left and
right-mouse clicking does not load a login prompt to re-enter credentials that I should not need to be doing in the first place considering that I am logged in with the correct domain account on my computer and using the destined mailbox for that AD account.
Exiting Outlook gracefully and re-launching Outlook a few seconds later allowing time for the background application handles and sub-handles amongst probably other things from the previous Outlook session to close (although, I do find every so often this
process is hampered every so often by having to end the Outlook.exe process directly through Task Manager before being able to re-attempt launching the Outlook client) and Outlook will just reconnect without the need or receiving a prompt to enter the login
details but I will no doubt receive another login prompt that I can likely just press cancel to or the escape button or perhaps, have to follow the above process again.
Just like releasing SP1 for Exchange 2010 to add more problems that worked without it but fixing those problems that existing in 2010.
I find that deleting a database result's in a failure error that in fact does successfully remove the database but since SP1, I know have to run a shell command to remove the database in the registry to delete an entry from a 'state' and 'lockstate' folder
before I am rid of the Exchange configuration, to then have to suspend all database copies on that server and re-start all of the Exchange services before I can actually delete the edb file. Just absurd.
It's all just a backwards and forwards exercise with Microsoft but would love permanent solutions to all of the above. Please advise on the above because it is a major irritation.

Project Server 2013 - Out of Office Sync - Only two months in future?!?

Hello there guys,
after Long Long search for the problem, I've found out that our Project Server 2013 only syncs the out of Office time from our Exchange Calendar for the next two months.
But for our Project planning we Need of course a more longtime synchronization, at least 6 or better 12 months.
I didnt find any Option where I could set it to sync more then 2 months of the out of Office times in the calendars.
I've spent already so much time on this Problem... When I set the Project Server time 2 weeks(!) in the future, then the sync will also sync two more weeks in the future, but not more.
The timesheet periods are also set for the next 12 month.
Does anybody have an Information/help regarding this Problem for me?
How can I set the Out of Office sync to synchronize more then just 2 months?
THANK YOU VERY MUCh!!
Regards
Lukas Meyer
PS: Using the current October 2013 CU.

I've searched the Verbose Log and found the following:
12/17/2013 14:38:16.32 Microsoft.Office.Project.Server (0x0928) 0x1A6C Project Server Exchange Sync aaubf Verbose PWA:https://servername/PWA, ServiceApp:Project Server-Dienstanwendung, User:PROJECTSERVER\system,
PSI: Calling service.GetUserAvailability() for user:2c3909bc-d6fb-e211-b239-000c296be823 for period:12/17/2013 00:00:00-02/17/2014 00:00:00, LogLevelManager Warning-ulsID:0x00014045 has no entities explicitly specified. 3a2f619c-f4a0-f018-b62b-b2d1299a489f
So the Project Server is only asking for two months of User Availability on the Exchange. Where can I Change this Setting so that the Project Server syncs more then 2 months?
Otherwise this functionality is quite useless in my view as we are planning our Projects longer then only 2 months...
Thank you!

Exchange 2013 OWA HTTP 500 error when opening another mailbox

We have an Windows Server 2012 Exchange 2013 server with OWA.
All users can login fine, but when I open another mailbox with my Admin account, having enabled access to that user's mailbox, the URL redirects to /owa/auth/errorfe.aspx?httpCode=500 and shows:
something went wrong
Sorry, we can't get that information right now. Please try again later. If the problem continues, contact your helpdesk
Google won't help me in this instance. Where in the eventlog are OWA events logged?

Hello,
I am joining to the thread opener, however, we do not use exchange server. we are using the Cloud services through Microsoft and as far as I know, the version is 2013 wave 15 (again, through Microsoft's cloud).
when I open the outlook, I can see the shared mailbox just fine.
when I open the office web access, and I search the mailbox through the 'add another mailbox..' It finds it however when I press the add button I get the HTTP 500 error.
when I tried to open a different mailbox (another shared mailbox I gave myself permissions for), it opens just fine.
it seems (from what I can tell) it is this specific shared mailbox that I cannot open through OWA while others I can.
when I try to open the mailbox in question through a different internet browser (Chrome) I get this Error:
NegotiateSecurityContext failed with for host 'db3pr04mb138.eurprd04.prod.outlook.com' with status'LogonDenied'
the error seems to be persistent on this specific mailbox only regardless to what browser I am trying to access with.
I can only assume that the solutions you (Winnie) offered isn't relevant in my case.
thanks in advance for any attempt to help me with this issue.

Exchange 2007 Out of Office Certificate Error

Hello,
I have an Exchange 2007 Server and for some odd reason this week, we have been having issues enabling Out of Office in Outlook. It is some sort of issue with the Autodiscover service, but despite reading forum post after forum post, nothing has worked for
me. At first when we would go into Outlook and click on Out of Office, it would freeze and then say the server is unavailable. I realized that it was trying to resolve a URL so I added a manual A record in the DNS server pointing to the local IP of the server
and it fixed the issue, kind of. Now when we click on Out of Office Assistant, we get a security certificate error and it is driving my users crazy. I have updated the SRV record and many things, still unable to get it to work.
Any help would be super!!
Thanks!

Hi,
1.First of all please check the name what you are using for autodiscover service is available on SAN certificate.
2.Please check the name resolution is happening for autodiscover namespace.
I.e if you try to resolve autodisccover.mydomain.com (or) mail.mydomain.com in your problematic PC it should have to resolved in to cas server ip address or in some scenarios it will get resolved in to LB
3.Then please check whether you have properly set the autodiscover internal URL in all the cas servers.
It might be like below
https:\\autodiscover.mydomain.com\autodiscover\autodiscover.xml
(or)
https:\\mail.mydomain.com\autodiscover\autodiscover.xml
4.Then please check for the web services url in all the cas servers and that is the major thing which will make the availability services (i.e OOF,free busy lookup) to work perfectly .
5.In the problematic please uncheck the internet proxy exceptions.
6.You cane use test email configuration to check whether the outlook client is fetching up the proper url for autodisocver and ews .
7.test-outlookwebservices (we can use this command to check the fuctionality of autodiscover for an problematic user account)
8.Please check the root certificates in the problematic client to check whether it is a expired or not .Root certificates is nothing but the one which will come by default with OS .
9.If all the above is set as perfect but still you are facing the issue.Please follow the below one and this may be not required.
Please export the san certificate from exchnage to pfx file which should have to include the certificate key by using MMC.Then import the pfx file in to problematic client .Let us see what happens .
Same on my side i am having few questions about your environment .
1.Are you facing any certificate errors in OWA .Because why i am asking please check the installed SAN certificate in exchange is valid and or it is not expired ?
2.what is the problematic client operating system veriosn?
Please reply me if you have any issues .
Regards
S.Nithyanandham

Exchange 2013 Outlook Anywhere connection issues when using F5 VIP

Hello,
We are in the process of deploying Exchange 2013 into our Exchange 2010 Org. We are using an F5 to load balance all services. We are doing some initial testing and have not cut over autodiscover or other URLs yet to 2013. We are using host files
on the local testing machines to point the URLs to 2013. OWA, Activesync, ecp work with no issue through the F5 VIP. However, we are having issues with Outlook. If our host file entries point to a single server, Outlook functions
normally. If the host file entries point to the F5 VIP, it keeps prompting for creds and will never connect.
Just wondering if anybody has run into this or has any guidance as far as OA and F5 deployment.
Thanks

Hi,
Please check your Load Balance configuration and make sure the namespace used for Load Balance has been included in the Exchange certificate. For example: mail.domain.com and autodiscover.domain.com.
If possible, please share your load balance configuration with us for further analysis. Here are some references about the Load Balance Scenario:
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx
Regards,
Winnie Liang
TechNet Community Support

Sent items not saved in personal sent items when shared mailbox is open in outlook

hi,
user is using exchange 2010 and the shared mailboxes are in exchange 2003. when user send an email as send as to the shared mailbox the sent items is not saved in her personal sent items. she can look up the sent items on her shared mailboxes sent items.
I tried recreating her profile when the shared mailboxes are not added in the outlook, personal sent items is okay but when the shared mailboxes is added , sent items doesn't go to her personal sent items. Please help. Is it by design?

Hi,
Since Exchange 2003 server is out of support, I still suggest migrating to Exchange 2010 server.
How about this behavior on OWA, if everything going well as expected, it should be an issue on the Outlook client side.
Please try to run Outlook under safe mode to avoid some AVs and add-ins.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013 CU3 Databases only activate on one mailbox server

Hi, guys
I have two Exchange 2013 CU3 Mailbox servers installed, one DAG, 5 databases, each has one copy. I found that if I activated three databases on Mailboxserver1 or Mailboxserver2, then after a few hours, all databases will be activated on the mailbox
server which has three databases activated. All the databases can be activated on Mailboxserver1 or Mailboxserver2, and they work well. I disabled DAC mode for preventing Event 4133 and 4376. And it has the same problem if I enable DAC mode.
From the event log, I found the log when activate one database on another mailbox server, it is Event 3169:
Managed availability system failover initiated by Responder=OutlookMapiHttpDeepTestFailover Component=Outlook.
This caused the database activated on another server.
And I got the message from SCOM, like this:
Alert: Health Set unhealthy
Source: test-mbx - Outlook.Protocol
Path: test-mbx.contoso.local;test-mbx.contoso.local
Last modified by: System
Last modified time: 11/12/2013 5:15:46 AM Alert description: EMSMDB.DoRpc(Logon) step of OutlookRpcDeepTestProbe/DB-01 has failed against test-mbx.contoso.local proxying to test-mbx.contoso.local for [email protected].
Latency: 00:00:00.0320000
ActivityContext:
Outline: [30] EMSMDB.Connect(); [1][FAILED!] EMSMDB.DoRpc(Logon); Likely root cause: Momt
Details:
Error: Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
Log:     Mailbox logon verification
        EMSMDB.Connect()
        Task produced output:
        - TaskStarted = 11/12/2013
5:15:25 AM
        - TaskFinished = 11/12/2013
5:15:25 AM
        - ErrorDetails =
        - RespondingRpcClientAccessServerVersion
= 15.0.712.4012
Latency = 00:00:00.0303884
        - ActivityContext =
    EMSMDB.Connect() completed successfully.
        EMSMDB.DoRpc(Logon)
        Task produced output:
        - TaskStarted = 11/12/2013
5:15:25 AM
        - TaskFinished = 11/12/2013
5:15:25 AM
        - Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
Error returned in LogonCallResult. Error code = WrongServer (0x00000478)
        - ErrorDetails =
        - Latency = 00:00:00.0018801
        - ActivityContext =
    EMSMDB.DoRpc(Logon) failed.
    Task produced output:
    - TaskStarted = 11/12/2013 5:15:25 AM
    - TaskFinished = 11/12/2013 5:15:25 AM
    - Exception = Microsoft.Exchange.RpcClientAccess.RopExecutionException:
Error
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'test-mbx' -HealthSet 'Outlook.Protocol'
State               Name
TargetResource                     HealthSet
AlertValue     ServerComponent
NotApplicable       OutlookMapiHttpDeepTestMonitor
Outlook.Protocol              Unhealthy      None
NotApplicable       OutlookRpcDeepTestMonitor
Outlook.Protocol              Healthy        None
NotApplicable       OutlookRpcSelfTestMonitor
Outlook.Protocol              Healthy        None
NotApplicable       OutlookMapiHttpSelfTestMonitor                                             Outlook.Protocol
Healthy        None
NotApplicable       PrivateWorkingSetWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       PrivateWorkingSetError....rpcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ProcessProcessorTimeWarning....ienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ProcessProcessorTimeError....clienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       ExchangeCrashEventError....pcclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       LongRunningWatsonWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
NotApplicable       LongRunningWerMgrWarning....cclienta... microsoft.exchange.rpcclientacc... Outlook.Protocol              Healthy
None
This test is a cause that mailbox databases in DAG is doing failover to another server
Log Name:      Application
Source:        MSExchangeRepl
Date:          12.11.2013 4:49:46
Event ID:      3169
Task Category: Service
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      test-mbx-2
Description:
(Active Manager) Database DB-01 was successfully moved from test-mbx.contoso.local to test-mbx-1.contoso.local. Move comment: Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchangeRepl" />
    <EventID Qualifiers="16388">3169</EventID>
    <Level>4</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-11-12T00:49:46.000000000Z" />
    <EventRecordID>1606248</EventRecordID>
    <Channel>Application</Channel>
    <Computer>test-mbx-2.contoso.local</Computer>
    <Security />
</System>
<EventData>
    <Data>DB-01</Data>
    <Data>test-mbx.contoso.local</Data>
    <Data>test-mbx-1.contoso.local</Data>
    <Data>Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.</Data>
</EventData>
</Event>
I don't know why, anyone know what's the problem?
Thank you.
Nile Jiang- Please mark the post as answer if it answers your question.
http://www.usefulshare.com

Hi,
After deleting all the health mailboxes and restart
the Exchange Health Manager service, the health mailboxes are recreated successfullly, but when I check the outlook.protocol health, the OutlookRpcDeepTestMonitor or the OutlookMapiHttpDeepTestMonitor is still unhealthy. How can I fix it?
[PS] C:\Windows\system32> Get-ServerHealth -Identity 'MAILBOX1' -HealthSet 'Outlook.Protocol' | ft server,state,name,ale
rtvalue -AutoSize
Server state Name AlertValue
MAILBOX1 OutlookRpcDeepTestMonitor Healthy
MAILBOX1 OutlookMapiHttpDeepTestMonitor Unhealthy
MAILBOX1 OutlookRpcSelfTestMonitor Healthy
MAILBOX1 OutlookMapiHttpSelfTestMonitor Healthy
MAILBOX1 PrivateWorkingSetWarning....cclientaccess.service Healthy
MAILBOX1 PrivateWorkingSetError....rpcclientaccess.service Healthy
MAILBOX1 ProcessProcessorTimeWarning....ientaccess.service Healthy
MAILBOX1 ProcessProcessorTimeError....clientaccess.service Healthy
MAILBOX1 ExchangeCrashEventError....pcclientaccess.service Healthy
MAILBOX1 LongRunningWatsonWarning....cclientaccess.service Healthy
MAILBOX1 LongRunningWerMgrWarning....cclientaccess.service Healthy
Nile Jiang- Please mark the post as answer if it answers your question.
http://www.usefulshare.com

Exchange 2013 - Cannot remove DataBase due to Arbitration Mailboxes

Dear Experts,
I'm running MS Exchange 2013 on Server 2012 R2. I am cleaning/merging databases and have ran into a problem due to the arbitration mailboxes. I am unable to delete a database because of the arbitration mailboxes.
First, I identified all the mailboxes in the DB I wanted to move (DB01)
Get-Mailbox -Database "DB01" -Arbitration
I did the below to move the arbitration and user mailboxes to a different DB
Get-Mailbox -Database "DB01" | New-MoveRequest -TargetDatabase "DB02"
Get-Mailbox -Database "DB01" - Arbitration | New-MoveRequest -TargetDatabase "DB02"
The move was successful, but I was unable to delete DB01 because of an error related to the arbitration mailboxes when I attempted to delete it.
After researching this problem I used
Get-Mailbox -Arbitration | Set-Mailbox -Arbitration -Database "DB02"
I have verified the active arbitration mailboxes are on DB02 by using
Get-Mailbox -Arbitration | Ft Name, Database
Currently DB01 is dismounted and from what I can tell not doing anything except eating up a license. Arbitration mailboxes still reside on DB01, but they are not active. If anyone has any experience on how I can force the deletion of this database
or remove the arbitration mailboxes for good it would make my boss and I so happy. Thanks to everyone in advance.

Dear Experts,
I'm running MS Exchange 2013 on Server 2012 R2. I am cleaning/merging databases and have ran into a problem due to the arbitration mailboxes. I am unable to delete a database because of the arbitration mailboxes.
First, I identified all the mailboxes in the DB I wanted to move (DB01)
Get-Mailbox -Database "DB01" -Arbitration
I did the below to move the arbitration and user mailboxes to a different DB
Get-Mailbox -Database "DB01" | New-MoveRequest -TargetDatabase "DB02"
Get-Mailbox -Database "DB01" - Arbitration | New-MoveRequest -TargetDatabase "DB02"
The move was successful, but I was unable to delete DB01 because of an error related to the arbitration mailboxes when I attempted to delete it.
After researching this problem I used
Get-Mailbox -Arbitration | Set-Mailbox -Arbitration -Database "DB02"
I have verified the active arbitration mailboxes are on DB02 by using
Get-Mailbox -Arbitration | Ft Name, Database
Currently DB01 is dismounted and from what I can tell not doing anything except eating up a license. Arbitration mailboxes still reside on DB01, but they are not active. If anyone has any experience on how I can force the deletion of this database
or remove the arbitration mailboxes for good it would make my boss and I so happy. Thanks to everyone in advance.
Please post the exact error when the database is mounted and you try to remove it.
Is this a multi domain forest? Set: set-adserversettings -viewentireforest $true
then check where the arbitration mailboxes are again:
get-mailbox -arbitration
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange Online - Set FOLDER permissions recursively in shared mailbox

I posted this in the 365 forums. Reposting here see if it gets any traction. Thanks
I have a shared mailbox that is being used instead of public folders. Having trouble with the folders within the shared mailbox syncing to the various users. Want to move folders out of the shared
mailbox but continually run into errors regarding permissions and I must manually find the offending subfolder and set permissions.<o:p></o:p>
So, I have two questions:<o:p></o:p>
1. How can I configure the shared mailbox so that all folders that are created, regardless of which user creates them, will inherit permissions. Any folder created should automatically have permissions
set to owner for a specific security group.<o:p></o:p>
2. How can I set the permissions on these exisiting shared mailbox folders, recursively (all sub folders) ? I have tried the following:<o:p></o:p>
Get-MailboxFolder –Identity user1:\Folder -Recurse | Add-MailboxFolderPermission -User user2 -AccessRights Owner<o:p></o:p>
But I get an error that the mailbox is not found. I believe that the command above does not work on shared mailboxes.<o:p></o:p>
I also found the following, but can not seem to get it to run. I have tried to run as a ps1 file and directly in powershell - I dont get any errors.<o:p></o:p>
ForEach($f in (Get-MailboxFolderStatistics
[email protected] | Where { $_.FolderPath.Contains("/") -eq $True } ) )
$fname = "[email protected]:" + $f.FolderPath.Replace("/","\"); Add-MailboxFolderPermission $fname -User
[email protected] -AccessRights Owner
Write-Host $fname
Start-Sleep -Milliseconds 1000
}<o:p></o:p>
Any help is appreciated. Thanks<o:p></o:p>

First of all, why don't you just give permissions on the mailbox level instead?
If Office 365, the
Get-MailboxFolder cmdlet only works for you own mailbox. So you have to use the Get-MailboxFolderStatistics as shown in the example. You will need to adjust this to give permissions to the Root folder and its best to actually exclude some of the
folders.
The example below should work, note that there is practically no error handling there, so test it first. Also, if the access entry already exists, you will get error messages.
$mailbox = "[email protected]"
$folders = Get-MailboxFolderStatistics $mailbox | ? {$_.FolderType -ne “Root” -and $_.FolderType -ne “Recoverableitemsroot” -and $_.FolderType -ne “Audits” -and $_.FolderType -ne “CalendarLogging” -and $_.FolderType -ne “RecoverableItemsDeletions” -and $_.FolderType -ne “RecoverableItemspurges” -and $_.FolderType -ne “RecoverableItemsversions”}
Add-MailboxFolderPermission $mailbox -User [email protected] -AccessRights Reviewer #root permissions
foreach ($folder in $folders) {
$FolderPath = $folder.FolderPath.Replace("/","\").Replace([char]63743,"/") #with PowerShell v3 'fix'
$MailboxFolder = "$mailbox`:$FolderPath"
Add-MailboxFolderPermission "$MailboxFolder" -User [email protected] -AccessRights Reviewer

Exchange 2013 database unplaned to active on another mailbox server

we have to four mailbox servers, two in primary site, two in dr site. it happens an unplaned failover issue, all of database are actived on mailbox server1, but some hours later, these database are unplaned to active on another mailbox server2, it also happens
in mailbox server2. that's why? after check eventlog, I found below:
AppLogEventID: 3169
AppLogEventMessage:
(Active Manager) Database MDB00 was successfully moved from shmbx01.ebaotech.com to SHMBX02.ebaotech.com. Move comment: Managed availability system failover initiated by Responder=OutlookRpcDeepTestFailover Component=Outlook.
also check server health, found OutlookRpcDeepTestMonitor is degraded, OutlookRpcSelfTestMonitor  is unhealty
Server State         Name
TargetResource                             HealthSetName    AlertValue ServerComponent
shmbx01 NotApplicable OutlookRpcSelfTestMonitor
Outlook.Protocol Unhealthy None
shmbx01 NotApplicable OutlookRpcDeepTestMonitor
Outlook.Protocol Degraded   None
shmbx01 NotApplicable PrivateWorkingSetWarningThresholdExceeded.m.e.rpcclientaccess.service microsoft.exchange.rpcclientaccess.service Outlook.Protocol Healthy    None
shmbx01 NotApplicable ProcessProcessorTimeErrorThresholdExceeded.m.e.rpcclientaccess.service microsoft.exchange.rpcclientaccess.service Outlook.Protocol Healthy    None
shmbx01 NotApplicable ExchangeCrashEventErrorThresholdExceeded.m.e.rpcclientaccess.service   microsoft.exchange.rpcclientaccess.service Outlook.Protocol Healthy    None
shmbx01 NotApplicable OutlookMapiHttpSelfTestMonitor
Outlook.Protocol Healthy    None
shmbx01 NotApplicable OutlookMapiHttpDeepTestMonitor
Outlook.Protocol Healthy    None
I don't know what causes this issue, and how can I resovle it to prevent the database unplaned failover, please help to look into it. thanks.

Hi,
Based on my knowledge, this issue can be caused by the following reasons:
1. Antivirus software. Please disable the Antivirus software to see if it works.
2. LmCompatibilityLevel. For Windows server 2008 R2 or Windows server 2012, this value should be 3. I suggest you modify the value to 3 on all of your Exchange 2013 servers to check the result.
2. Outlook responders. Please try to disable the Outlook responders to check the result.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 - Out of office unavailable when shared mailboxes added in

Similar Messages

Maybe you are looking for