• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 811
  • Last Modified:

Microsoft Exchange initialization failed: logon failure

Hi everyone,

I have a problem with my exchange-server. I can't login to the management console anymore.
I get the following error-message.

I have changed my administrator password, so will try rebooting during the break, but can there be other possibilities?
0
Silencer001
Asked:
Silencer001
  • 10
  • 4
  • 4
1 Solution
 
ckeshavCommented:
Where is the error message?
0
 
Syed_M_UsmanCommented:
if you was using Administartor password and you have change the password in AD and not able to logon EMC, why dont you just logoff and try using Exchange Admin password? till you finish office ?
0
 
Silencer001Author Commented:
I have tried loging off, but it doesn't work. I forget the image, here it is in this post.
mailserver.png
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
ckeshavCommented:
If you disabled IPV6, enable it back and reboot the server.
Then try opening the Console
0
 
Syed_M_UsmanCommented:
then you can try restarting exchange services (if urgent) otherwise you have to restart server.
0
 
Silencer001Author Commented:
I have followed ckeshav recommendation, but now the server is restarting for 30 minutes...

Applying computers settings...

Can someone please tell me what to do?
0
 
Syed_M_UsmanCommented:
i don't no what to say but you can power off server manually and start again. i don't think so IPV 6 has any link when you change admin password for your domain.

if you face problem that logon screen not appearing and system waiting for Network connections to apply for more than 5-10 minutes you can remove network cables and you will have logon screen. logon your server if succeed connect your cable back and start using server if not succeed connect cable and try.

by the way Manually power off server is not recommended but if your system is not working as last resort you can try  

 
0
 
Silencer001Author Commented:
I have disabled services from exchange in safe mode and was able to boot...
0
 
Syed_M_UsmanCommented:
good, a sign of relief :)
0
 
Silencer001Author Commented:
But now the information store wouldn't start, what seems to be the problem here?

I found this link: http://blogs.technet.com/b/sbs/archive/2008/10/24/issues-after-disabling-ipv6-on-your-nic-on-sbs-2008.aspx
0
 
Silencer001Author Commented:
I enabled ipv6 to avoid this being an issue and then did the following:
http://www.howexchangeworks.com/2010/07/exchange-2010-error-process.html

Really don't know the reason why it happened..
0
 
Silencer001Author Commented:
But I am still experiencing the problem.. What could be the resolver?
0
 
ckeshavCommented:
I suggested IPv6 because I had a similar issue and that solved my problem.

I'm not sure if that caused your IS to stop.

What is the status now...is your Information store is in the starting status?
This normally happens if Exchange permissions are lost on the AD side.

You can run setup /adprep once, this would re-add the permissions. Running this command again would not create any issue.
0
 
Silencer001Author Commented:
I have found the solution. The microsoft Exchange was using the previous cached password.

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/A_448-How-to-DELETE-Windows-Local-Domain-Cached-Credentials.html
0
 
Silencer001Author Commented:
@ckeshav: So if you run "setup /adprep" all your default permissions are set-up?
0
 
ckeshavCommented:
Yes..but you seem to be resolved the issue or the issue is still there?
0
 
Silencer001Author Commented:
No the issue is resolved, it had to do with the cached credentials..

But we had to revert to the old password..
When we booted again, exchange services couldn't be started. We had to boot again in safe mode, disable exchange services, boot in regular mode and start services manually.

When we set back the previous password (and change the cached credentials again), everything started working fine and the clients got connected to exchange again.

Everything started to go wrong when we changed the password of the admin account.
Is there an option in exchange where you need to alter the password seperatelly?

I really have no idea and have never heard of an option to do this...
Maybe something else is wrong and it is just coincidence, I have no idea...

I was hoping that some of you could shine a light on this?
0
 
Silencer001Author Commented:
Found the solution myself
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 10
  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now