Unable to logon to Exchange Admin Center - bad username/password (Network Steve Forum)

Unable to logon to Exchange Admin Center - bad username/password

Dear Experts,

We are in the middle of testing a migration of an SBS 2011 (running Exchange 2010 SP1) over to Server 2012 R2 with Exchange 2013 installed. The new 2012 R2 has all FSMO roles.

After the successful Installation of Exchange 2013, we are unable to logon to the Exchange Admin Center (https://localhost/ecp). Says bad username or password. My admin is a member of the Organization Management Exchange Security Group, along with "Organisation-Admins" and "Schema-Admins" .

Any ideas? Thanks, Oliver

Edited by Oliver Buckie Friday, April 17, 2015 5:36 PM

April 17th, 2015 5:15pm

Just trying on the server itself. All services are started. No, the accounts don't have mailboxes on the Exchange 2013 - we have just installed the 20123R2 Server with Exchange 2013 and trying to migrate from the SBS 2011 (Exchange 2010). Where / how should I create the account you want me to test?

Create a mailbox for a test account on the 2013 server ( Or move an existing one) and add it to the Org Mgmt group. Also test if you can connect to EAC from a workstation.

Free Windows Admin Tool Kit Click here and download it now

April 18th, 2015 7:38am

How can I go about doing this - I can't access the Exchange Administrative Center on the 2012R2 and on the SBS 2011 in the Exchange Console the new Exchange 2013 is not seen and when I create a new Mailbox I can't select the new Server or DB?

I have also tried via Exchange Powershell on the W2012R2. Here the output when I connect:

AUSFHRLICH: Verbindung mit W2012R2-Hostname.domain.local wird hergestellt.
New-PSSession : [fnk-pdc.fink.local] Beim Verbinden mit dem Remoteserver "W2012R2-Hostname.domain.local" ist folgender Fehler
aufgetreten: Zugriff verweigert Weitere Informationen finden Sie im Hilfethema "about_Remote_Troubleshooting".
In Zeile:1 Zeichen:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
AUSFHRLICH: Verbindung mit W2012R2-Hostname.domain.local wird hergestellt.
New-PSSession : [W2012R2-Hostname.domain.local] Beim Verbinden mit dem Remoteserver "W2012R2-Hostname.domain.local" ist folgender Fehler
aufgetreten: Zugriff verweigert Weitere Informationen finden Sie im Hilfethema "about_Remote_Troubleshooting".
In Zeile:1 Zeichen:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed
AUSFHRLICH: Verbindung mit SBS2011-Hostname.domain.local wird hergestellt.
AUSFHRLICH: Verbunden mit SBS2011-Hostname.domain.local.

I think this could be the Problem???

Edited by Oliver Buckie 15 hours 15 minutes ago

April 18th, 2015 12:01pm

I have also tried via Exchange Powershell on the W2012R2. Here the output when I connect:

I think this could be the Problem???

Edited by Oliver Buckie Saturday, April 18, 2015 4:10 PM

Free Windows Admin Tool Kit Click here and download it now

April 18th, 2015 3:58pm

Hi,

Please make sure you are by using the correct URL to access the EAC. If youre in a coexistence scenario and your administrator mailbox is still housed on the Exchange 2010 Mailbox server, we should access the EAC in Exchange 2013 by using the following URL:

https://localhost/ecp?ExchClientVer=15

If it still doesn't work, please create a test mailbox in Exchange 2013 and confirm if the new mailbox can be accessed with OWA (https://localhost/owa) and ECP (https://localhost/ecp). If the OWA and ECP still doesn't work for new created user, please recreate the OWA and ECP virtual directory to have a try.

Regards,

April 21st, 2015 5:53am

Default installation of 2012R2. Installed the ADDS role and other requirements for Exchange 2013. Default installation of Exchange 2013 and CU9. No changes whatsoever. No relevant logs in the Event Viewer at time of login failures. Which logs in IIS should I check - path/name? Thanks.

I'm kinda thinking a rebuild is in order if you cant get it to work. Or open a ticket with Microsoft.

Free Windows Admin Tool Kit Click here and download it now

April 21st, 2015 7:27am

For testing purposes we created a virtualised copy of the current SBS 2011. In this test environment we tried the migration which then failed when trying to login to EAC. We rollbacked the test SBS 2011, retried the migration again and had the same problem with EAC. We believe it must be something to do with the co-existence of Exchange 2010 with Exchange 2013 in this SBS 2011 environment. Perhaps it's something that we are not doing as part of this migration?

Yes, we would like to open a ticket with Microsoft - how is this best done and any costs involved? Will Microsoft help us plan/perform this test migration so that we can create a project plan for the live migration?

Thanks again for your advise.

April 21st, 2015 8:59am

You can contact them here:

https://support.microsoft.com/en-us/ph/13965

If you want consulting help, they can help at additional cost or you would need to hire someone.

Also consider moving to Office 365.

Cant tell you the cost however.

Free Windows Admin Tool Kit Click here and download it now

April 21st, 2015 5:41pm

This topic is archived. No further replies will be accepted.