Quantcast
Channel: Exchange Server 2010 forum
Viewing all articles
Browse latest Browse all 15005

Exchange 2010 SP2 Update failed , a lot of problems now.

$
0
0

Hi all,

Since yesterday I have a serious problem with Exchange 2010. I installed Update-rollup 4-V2 from SP1 which was available to me, the installation failed, so I tried to stop the Windows Update and in the end rebooted the server. After it rebooted I had a ton of problems with OWA. So I start reading a million threads on different forums about the same issues I had. Someone adviced me to install SP2 over the current installation. I wish I never would have done that. The SP2 failed at the Hub Transport role and then canceled the rest of the update. All my services were disabled after that , so I enabled them manually and started my Exchange script which start all my services automatically (the ones I need). Still OWA not working, so I tried recreating it following a ton of links of people who had the same problem. This didn't help, then I read that someone removed Default Web Site. At that point I could have just jump of a cliff, deleting that made things even worse.

In the end i'm now stuck with a server where mail flow only works, no OWA, no mobile syncing, no EMC/EMS, I can't do nothing. My mailbox keeps popping up with username and pass (some other users experiencing the same problem).

What can I do, I'm already building a new server and I hope someone can point me in the right direction . Is it possible to export the Default Web Site from a new Exchange server in the old one? Can I move my mailboxes to the other server , then shutdown the old one, rebuild it (cause of the name) and then push back all my mailboxes to that server.

I never experienced this kind of a problem before and I work with Exchange for a long long time now. I'm just stuck and I can't find the answer on this World Wide Web.


Viewing all articles
Browse latest Browse all 15005

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>