[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2669
  • Last Modified:

Exchange 2010 console not working after failed SP1 Upgrade

We tried to install SP1 on our Exchange 2010 server yesterday, and it hung on the Hub Transport upgrade. We rebooted, tried again and the same. We thought Groupshield might be the issue, so removed it and tried again. Still the same. As it stands, The Exchange Management Console is inaccessible, stating initialization failed. Powershell also cannot connect to the server.

We can still send and receive email fine, but OWA is not functioning, so we also don't have activesync.

The event log is full of ASP.Net errors, event ID 1310 stating

Exception message: Could not load file or assembly 'Microsoft.Exchange.Security, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Autodiscover\web.config line 855)

Replacing this file with one from a working system has no effect.

Any ideas would be very much appreciated!

Leanne
0
tisl
Asked:
tisl
  • 9
  • 6
  • 3
  • +3
3 Solutions
 
AkhaterCommented:
Honestly at this point I would do one of 2 things

1. since you said it is still working fine I would create a new server and move everything to it

2. give PSS a call

I'm afraid that attempting to manipulate the server more would break what is (still) running

good luck
0
 
boxerenterprisesCommented:
My advice would be to disable all exchange services and restore all exchange program files and the system state from backup
0
 
sagiamarCommented:
try to run the installation by right click and "run as administrator"
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
tislAuthor Commented:
Thanks Akhater, I'm actually in the process of setting up a server to do just that, as I was thinking along the same lines. We have also 5 calls to Micosoft which we haven't used, so I think I'll give them a call.

I hadn't actually considered doing a restore, so I may give that a try if all else fails.

I'll post the solution on here, if it turns out there is one, in case anyone else has this issue.
0
 
Mkris9Commented:
Pls check if IIS server stopped listening on port 80 for internal websites. If yes, add the server name and the server FQDN to the bindings for port 80. EMC & OWA should start working.

Also exchange 2010 SP1 has been creating a lot of issues. please go through http://msexchangeteam.com/archive/2010/09/01/456094.aspx and comments where a few and its solutions have been listed.
0
 
tislAuthor Commented:
Thanks for the link, I'll take a look. I checked IIS and it was still listening on port 80.
0
 
sunnyc7Commented:
Will second the IIS check for port 80
and check these too

a) www.testexchangeconnectivity.com/
Test for Outlook autodiscover

b) Go here
C:\Program Files\Microsoft\Exchange Server\V14\bin
open
exBPA.exe

Run a health scan on your exchange installation.
Export the report as HTML
Copy paste the errors here.

thanks
0
 
tislAuthor Commented:
These are critical issues
Critical Issues 10/09/2010 13:08:35
Page 1
(7 items)
 
The Offline Address Book Site Public Folder Store Was DeletedOrganization: First Organization The public folder store where offline address book 'OAB' is hosted has been deleted. Current public folder store: 'domainname.net/Configuration/Deleted Objects/Public Folder Database DEL:05c68d26-0bca-408f-a77e-13fe980e8f64'.
 
Site folder server deleted Admin Group: Exchange Administrative Group (FYDIBOHF23SPDLT) The site-wide public folder database for administrative group 'Exchange Administrative Group (FYDIBOHF23SPDLT)' has been deleted. Current public folder store: 'CN=Public Folder Database\0ADEL:05c68d26-0bca-408f-a77e-13fe980e8f64,CN=Deleted Objects,CN=Configuration,DC=domainname,DC=net'.
 
'ClientAccessRole' not configuredServer: MAILSERVER 'ClientAccessRole' is not configured on server 'servername' Please run setup again.
'HubTransportRole' configured partiallyServer: MAILSERVER 'HubTransportRole' is partially configured on server 'servername'. Either setup is configuring it right now or setup failed while configuring it. Please rerun the setup if isn't being run.
'HubTransportRole' not configuredServer: MAILSERVER 'HubTransportRole' is not configured on server 'servername'. Please run setup again.
'MailboxRole' not configuredServer: MAILSERVER 'MailboxRole' is not configured on server 'servername'. Please run setup again.
A NTFS.sys update is available to prevent the Exchange server from hangingServer: MAILSERVER An updated version of the NTFS.sys driver is available for server servername. Updating to the new version will prevent the Exchange server from experiencing a known deadlock issue. For more information, see Microsoft Knowledge Base Article 974646 (http://go.microsoft.com/fwlink/?linkid=3052&kbid=974646). Current installed version: 6.0.6002.18005.
0
 
sunnyc7Commented:
your exchange 2010 SP1 didnt install properly and that explains

c:\exchangesetup\exchangesetup.log

Please upload it.
0
 
tislAuthor Commented:
Yes, the upgrade to SP1 kept crashing out. I've attached the log. It's pretty long!
ExchangeSetup.zip
0
 
sunnyc7Commented:
tisl
lot of these things are starting to make sense after going through the log.
the set-up installed some of the roles / services partially.

Can you run these cmdlets from exchange shell.

get-organizationconfig
test-setuphealth

Also to be clear:
a) Windows install 4.5 is installed
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5a58b56f-60b6-4412-95b9-54d056d6f9f4&displaylang=en

b) Any of the services disabled ?

c) when was the last time you did a restart.

Calling PSS is a good idea, as you are in the middle of a SP1 upgrade and some parts got installed and others didnt.
The log will help you in figuring this out.

tisle2010.txt
0
 
tislAuthor Commented:
Microsoft are currently dialled in to our server taking a look, so I'll report back...
0
 
sunnyc7Commented:
keep the extracted log file for reference.

I am not sure if these 2 cmdlets are working / giving appropriate responses.

get-organizationconfig
test-setuphealth

Please update when you are free


thanks
0
 
tislAuthor Commented:
Been on the phone with Microsoft all this time, but still no further forward. They're calling me back again on Monday.
0
 
tislAuthor Commented:
Just thought I'd post an update before I close this question. We spent several days on the phone to Microsoft, and didn't really get anywhere, so we are reinstalling our domain today. Microsoft told us that removing and re-adding Exchange from our existing server, would not resolve the issue, and when we installed Exchange on a different server, it wouldn't talk to our existing server, so re-doing our domain was the only option open to us really. Despite all the hours on the phone, and all the diagnostics, it was never determined why our Service Pack failed half way through, and there didn't seem to be any way of getting it to complete. One of those things I guess!
0
 
AkhaterCommented:
wow... bad luck sorry to hear that
0
 
sunnyc7Commented:
that's a really hairy mess @
Surprising @ MSFT didnt help you on this.
0
 
sunnyc7Commented:
akhater @ have you faced something like this earlier @ failure to install service pack leads to domain reinstall ?
 
I haven't
0
 
tislAuthor Commented:
We spent hours on the phone to them, with them dialled in, but they were unable to resolve it. They did offer us more help, but we just didn't feel they would ever be able to resolve it, so we took the decision to wipe our servers. We're an IT company, so don't really have any non-techie end users to worry about, so it's not too much of a problem.
0
 
AkhaterCommented:
no never and I don't see why another server wouldn't "talk" to the current one since email flow is still working
0
 
tislAuthor Commented:
The reason they wouldn't talk is because Powershell wasn't working properly. The whole thing was a mess, and it was VERY satisfying to wipe the whole thing!
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 9
  • 6
  • 3
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now