So I know there are a lot of these threads, so I'll list what I've done and what I've tried so far.
The setup is a pair of multirole servers with a DAG. We have a root domain and sub domain.
I've created 4 databases associated with the DAG, I successfully removed the default database on the 2nd mail server, then migrated the arbitration/system/discovery etc... mailboxes to one of the DAG databases. I then removed the 1st mail server's default database after killing it's healthmailbox. Rebooted the pair of servers and after that the ECP/OWA were inaccessible.
To run tests I installed .NET 3.5 SP1 so I could run the ExBPA which really didn't get me anywhere.
I can access the logon screen for both, but when I enter my username and password, I get the http 500 internal server error.
I have used: Get-OwaVirtualDirectory -Server <server name> | fl *auth*
To verify that basic and forms based auth are enabled, and they are.
I've verified all services have started.
I've tried to remove and re-add the app pools and the ecp virtual directories.
http://social.technet.microsoft.com/Forums/ie/en-US/bb148ccb-a75e-4571-bfc7-76950f8e638e/exchange-2013-cu2-cant-access-ecp-unexpected-error-500?forum=exchangesvrgeneral
I've tried to use ADSI Edit to purge the Canary Data.
http://social.technet.microsoft.com/Forums/exchange/en-US/777b51ee-330d-43cc-a56e-4614d44aed7b/unable-to-access-owa-or-ecp-something-went-wrong-or-500-unexpected-error?forum=exchangesvrclients
I've tried to run test-ecpconnectivity but stated that the test user wasn't available.
So I tried to use the powershell script to create a new test user, but it doesn't seem to work either I think it's related to the exchange machine not being a member of the root domain, but not sure on that one.
I seem to be able to manage everything with command-line still. Create and remove mailboxes etc.
As far as errors/warnings go exchange wise I get an ASP.NET 4.0 warning Event ID 1309 stating that an unhandled exception occurred, which seems to coincide with the logon attempt. I'm sure this has something to do with it, but not real sure what yet. Nothing I can see within the logon attempt from IIS or anything else really.
I think that's about all I have.
The setup is a pair of multirole servers with a DAG. We have a root domain and sub domain.
I've created 4 databases associated with the DAG, I successfully removed the default database on the 2nd mail server, then migrated the arbitration/system/discovery etc... mailboxes to one of the DAG databases. I then removed the 1st mail server's default database after killing it's healthmailbox. Rebooted the pair of servers and after that the ECP/OWA were inaccessible.
To run tests I installed .NET 3.5 SP1 so I could run the ExBPA which really didn't get me anywhere.
I can access the logon screen for both, but when I enter my username and password, I get the http 500 internal server error.
I have used: Get-OwaVirtualDirectory -Server <server name> | fl *auth*
To verify that basic and forms based auth are enabled, and they are.
I've verified all services have started.
I've tried to remove and re-add the app pools and the ecp virtual directories.
http://social.technet.microsoft.com/Forums/ie/en-US/bb148ccb-a75e-4571-bfc7-76950f8e638e/exchange-2013-cu2-cant-access-ecp-unexpected-error-500?forum=exchangesvrgeneral
I've tried to use ADSI Edit to purge the Canary Data.
http://social.technet.microsoft.com/Forums/exchange/en-US/777b51ee-330d-43cc-a56e-4614d44aed7b/unable-to-access-owa-or-ecp-something-went-wrong-or-500-unexpected-error?forum=exchangesvrclients
I've tried to run test-ecpconnectivity but stated that the test user wasn't available.
So I tried to use the powershell script to create a new test user, but it doesn't seem to work either I think it's related to the exchange machine not being a member of the root domain, but not sure on that one.
I seem to be able to manage everything with command-line still. Create and remove mailboxes etc.
As far as errors/warnings go exchange wise I get an ASP.NET 4.0 warning Event ID 1309 stating that an unhandled exception occurred, which seems to coincide with the logon attempt. I'm sure this has something to do with it, but not real sure what yet. Nothing I can see within the logon attempt from IIS or anything else really.
I think that's about all I have.