Deleting database from Exchange 2016 – error

exchange-2016

Failed to remove monitoring mailbox object of database "abc" Exception: Active Directory operation failed on "server.def.com" This error is not retriable. Additional information: Access is denied. Active directory response: 00000005: SecErr: DSID-0315274A, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0 .

So this was the error I got after I thought I had deleted all the mailboxes on an old test database (no longer needed) in Exchange 2016, and removed it from ECP. The database has disappeared though, so all looks OK. Just wondering if this will come back to bite me one day or I can safely move on and ignore?

thanks

Best Answer

Health mailboxes CAN be deleted and actually they should if orphaned. The link provided in BastianW answer does involve System mailboxes management and does not help in managing health mailboxes. Basically, Health mailboxes creation logic has been changed in CU6 E2013 so it's ok to remove old health mailboxes.

Health mailbox will be, anyway, recreated upon MsEchangeHM service restart.
A detailed explanation on why it may be necessary to delete monitoring mailboxes can be found here: https://blogs.technet.microsoft.com/admoore/2015/03/11/exchange-2013-health-mailboxes/

Related Solutions

Exchange 2016 Co-Existence – OWA Won’t login when behind a load balancer

I ended up reasonably working around this issue. Several posts had mentioned for similar issues that adding Cookie-based persistence on their load balancer had solved the issue for them.

I had resisted this "because I shouldn't have to", all the technical articles from Microsoft say this is no longer needed, and indeed not recommended.

But I caved, and ended up adding persistence for both OWA and ECP. The result was the issue was not completely resolved, but it became barely noticeable. The only time I experience issues is if I log out of OWA on one mailbox, and then immediately log into another. Even then, it kicks you out once, but if you try to login again it works fine.

There is no ongoing issue after this. Furthermore, I noticed the remaining issue only when moving from a 2013 to 2016 mailbox.

This isn't something our end users are likely to do, and we're nearly finished moving all our mailboxes to 2016. So I'm considering this work around "good enough".

Since we're using HA Proxy, it wasn't a big deal to add some layer 7 cookie-based persistence in the config. In fact, it only took about 5 minutes all up to figure out:

# HTTPS Outlook Web App (OWA)
backend bk_EXCHANGE_https_owa
  cookie LB01 insert indirect nocache # <-- Added this
  balance roundrobin
  mode http

  ...

  # Added the "cookie <name>" at the end of each CAS node definition
  # These names must be unique to each node.
  server n1_exch16_syd_01 172.16.10.2:80 maxconn 1000 weight 10 check cookie EXCH16-SYD-01
  server n1_exch16_syd_02 172.16.10.3:80 maxconn 1000 weight 10 check cookie EXCH16-SYD-02
  server n1_exch13 172.16.10.1:80 maxconn 1000 weight 10 check cookie EXCH13-SYD

Error when trying to install Exchange 2016 on Windows Server 2016

Fixed the problem with using the cumulative update 8. Found it coincidentally: https://www.microsoft.com/de-de/download/details.aspx?id=56363

Best Answer

Related Solutions

Exchange 2016 Co-Existence – OWA Won’t login when behind a load balancer

Error when trying to install Exchange 2016 on Windows Server 2016

Related Topic