Solved

Exchange Management Console unable to connect - Initilization failed

Posted on 2011-09-07
19
4,272 Views
Last Modified: 2012-05-12
The following error occurred while attempting to connect to the specified Exchange Server 'servername.domain.local":

The attempt to connect to http://srvername.domain.local/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message: Logon failure: unknown username or bad password.    
Capture.JPG
0
Comment
Question by:GlenHarvey
19 Comments
 
LVL 12

Accepted Solution

by:
DarinTCH earned 500 total points
ID: 36495590
double chk the user name and password
is active directory up and fully functional

where you logging on with this same account
what changed since then
check AD event viewer
0
 
LVL 12

Expert Comment

by:Nenadic
ID: 36495591
Have a look here:
http://social.technet.microsoft.com/Forums/en-CA/exchange2010/thread/c268a1e7-684a-479c-996e-fa4cb11e4950

Steps:
1.    Apply the latest RU;
2.    Remove the Kerbauth module from the Default Web Site. To do this, follow these steps:
1)    Open IIS Manager.
2)    Click Default Web Site.
3)    Double-click the Modules component.
4)    Click Kerbauth.
5)    Click Remove.
6)    Then, check the PowerShell Virtual Directory, and make sure that the Kerbauth module is listed.  If the module is not listed, follow these steps:
7)    Under Actions, click Configure Native Modules.
8)    Click to select the Kerbauth check box.
9)    Click OK.
0
 

Author Comment

by:GlenHarvey
ID: 36495815
Also I noticed that our backup failed with the following

Click an error below to locate it in the job log
Backup- \\EXCHANGE_SERVER_NAME.DOMAIN.local\Microsoft Information Store\Mailbox Database 0794349792V-79-57344-65298 - The Exchange Store service is not responding. Backup set canceled.

V-79-57344-65072 - An error occurred while connecting to the Backup Exec Remote Agent on the media server. Ensure that the job options are correct, and then submit the job again. The backup set was not created.

Backup- EXCHANGE_SERVER_NAMERemote Agent not detected on EXCHANGE_SERVER_NAME.DOMAIN.local.

Backup- EXCHANGE_SERVER_NAME.DOMAIN.localRemote Agent not detected on EXCHANGE_SERVER_NAME.DOMAIN.local.

Unable to attach to \\EXCHANGE_SERVER_NAME.DOMAIN.local\D:.

V-79-57344-33899 - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent.


Note: Click 'Edit Selection List...' to display the View Selection Details tab of the job's selection list. Select the entry with the server that no longer exists and click Delete to remove it.Edit Selection List...
Make sure that the correct version of the Remote Agent is installed and running on the target computer.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.

Unable to attach to \\EXCHANGE_SERVER_NAME.DOMAIN.local\Shadow?Copy?Components.

V-79-57344-33899 - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent.


Note: Click 'Edit Selection List...' to display the View Selection Details tab of the job's selection list. Select the entry with the server that no longer exists and click Delete to remove it.Edit Selection List...
Make sure that the correct version of the Remote Agent is installed and running on the target computer.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.

Unable to attach to \\EXCHANGE_SERVER_NAME.DOMAIN.local\System?State.

V-79-57344-33899 - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent.


Note: Click 'Edit Selection List...' to display the View Selection Details tab of the job's selection list. Select the entry with the server that no longer exists and click Delete to remove it.Edit Selection List...
Make sure that the correct version of the Remote Agent is installed and running on the target computer.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.

Verify- EXCHANGE_SERVER_NAME.DOMAIN.localUnable to attach to \\EXCHANGE_SERVER_NAME.DOMAIN.local\System?State.

V-79-57344-33899 - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent.


Note: Click 'Edit Selection List...' to display the View Selection Details tab of the job's selection list. Select the entry with the server that no longer exists and click Delete to remove it.Edit Selection List...
Make sure that the correct version of the Remote Agent is installed and running on the target computer.  If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource.


0
 

Author Comment

by:GlenHarvey
ID: 36495901
Hi "DarinTCH" - I am still logging on to the Exchange Server using the Administrator account of our domain. Nothing has changed to the account.

Hi "Nenadic" - The KB article reference does not appear to be the same issue, and I am not convinced this is related. Removing the Kerbauth module from the Default Web Site in IIS seams like a stab in the dark...

Any other thoughts?
0
 
LVL 12

Expert Comment

by:Nenadic
ID: 36495962
Your Kerberos authentication is failing. My suggestion is to switch to NTLM. Not a stab in the dark, but I don't really intend to try and convince you. :-)
0
 

Author Comment

by:GlenHarvey
ID: 36496103
Thanks Nenadic :@)

In IIS Manager, under Default Web Site,  Modules, I dont see Kerbauth listed

As for installing the latest RU, I have yet to deploy Update Rollup 4 for Exchange Server 2010 Service Pack 1, which will have to be done during a service window after hours
0
 
LVL 12

Expert Comment

by:Nenadic
ID: 36496406
You can safely ignore the RU bit. OK, here is the full version from the Exchange Product Group.
http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx

It's a longer read, but much more comprehensive.
0
 

Author Comment

by:GlenHarvey
ID: 36496741
The EMTshooter Troubleshooter described in this article does not include nor cover the error I have: Logon failure: unknown username or bad password.    
0
 
LVL 12

Expert Comment

by:Nenadic
ID: 36496968
You probably need to provide a bit more information:
- Have you ever been able to connect to your Exchange using EMC?
- Have you made any changes recently?
- What errors do you see in default event logs?
- Anything else that is pertinent.
0
Do email signature updates give you a headache?

Do you feel like you are constantly making changes to email signatures? Are the images not formatting how you want them to? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today.

 

Author Comment

by:GlenHarvey
ID: 36497113
Have you ever been able to connect to your Exchange using EMC - Yes, always up until a week or so ago

Have you made any changes recently? - yes, we were recently having problems with Outlook Certificate Warnings popping up following upgrading Outlook 2003 to Outlook 2010 - I followed this article to resolve the issue: http://shift-command-3.blogspot.com/2011/01/outlook-certificate-warning-with.html

What errors do you see in default event logs? - Here is a possibly related error that I have to also tacle: Microsoft Exchange could not load the certificate with thumbprint of 4F05F434CFC888B3F8C5B0FBF2F1C34182EF6AF8 from the personal store on the local computer. This certificate was configured for authentication with other Exchange servers. Mail flow to other Exchange servers could be affected by this error. If the certificate with this thumbprint still exists in the personal store, run Enable-ExchangeCertificate 4F05F434CFC888B3F8C5B0FBF2F1C34182EF6AF8 -Services SMTP to resolve the issue. If the certificate does not exist in the personal store, restore it from backup by using the Import-ExchangeCertificate cmdlet, or create a new certificate for the FQDN or the server enabled for SMTP by running the following command: New-ExchangeCertificate -DomainName serverfqdn -Services SMTP. Meanwhile, the certificate with thumbprint C58D5F7C8FDB8EEC88A37250687AA425974C4C09 is being used.
0
 
LVL 12

Expert Comment

by:Nenadic
ID: 36497173
Have you checked if the Certificate still exists in the Computer store Personal Certificates? That could provide a solution. You could run the command safely even without checking. If the Certificate is not available - it will just produce the error.
0
 

Author Comment

by:GlenHarvey
ID: 36497184
This was the problem!
Credential-Manager.jpg
1
 

Author Comment

by:GlenHarvey
ID: 36497209
I've requested that this question be closed as follows:

Accepted answer: 0 points for GlenHarvey's comment http:/Q_27295214.html#36497184

for the following reason:

I found the solution myself/
0
 
LVL 12

Expert Comment

by:Nenadic
ID: 36497210
DarinTCH did suggest you should check your credentials.
0
 

Author Comment

by:GlenHarvey
ID: 36497273
Yes, you are right. I just didnt know to check the Credential Manager in Control Panel, as the only account that has ever been logged onto this server was the Administrator account of the domain. The Credential Manager must have stored this other account when I connected to OWA via IIS perhaps/.

My appologies gents - Thank you both for all you help!
0
 

Author Closing Comment

by:GlenHarvey
ID: 36497290
Did not know to check the Credential Manager in Control Panel, as the only account that has ever been logged onto this server was the Administrator account of the domain.
0
 
LVL 3

Expert Comment

by:boat_anker
ID: 37073902
Unreal, The credential Manager was the problem for my client also. Spent hours trying to resolve this. Previous IT provider couldn't spell administrator
0
 

Expert Comment

by:tmorr16
ID: 37340649
That was my problem too. Now I am getting the following message:

VERBOSE: Connecting to mtzionserv03.mtzionchurch.org


[xxxxx.xxxxx.com] Connecting to remote server failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
    + FullyQualifiedErrorId : PSSessionOpenFailed
The Exchange Management Troubleshooter successfully completed connecting to:

xxxxx.xxxxx.com

0
 

Expert Comment

by:laginnwt
ID: 37723468
Great Job Glen.  Just helped me out!!!
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

Local Continuous Replication is a cost effective and quick way of backing up Exchange server data. The following article describes the steps required to configure Local Continuous Replication. Also, the article tells you how to restore from a backup…
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
how to add IIS SMTP to handle application/Scanner relays into office 365.

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now