Link to home
Create AccountLog in
Avatar of tisl
tislFlag for Afghanistan

asked on

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
SOLUTION
Avatar of Akhater
Akhater
Flag of Lebanon image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of boxerenterprises
boxerenterprises

My advice would be to disable all exchange services and restore all exchange program files and the system state from backup
try to run the installation by right click and "run as administrator"
Avatar of tisl

ASKER

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.
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.
Avatar of tisl

ASKER

Thanks for the link, I'll take a look. I checked IIS and it was still listening on port 80.
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
Avatar of tisl

ASKER

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.
your exchange 2010 SP1 didnt install properly and that explains

c:\exchangesetup\exchangesetup.log

Please upload it.
Avatar of tisl

ASKER

Yes, the upgrade to SP1 kept crashing out. I've attached the log. It's pretty long!
ExchangeSetup.zip
SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of tisl

ASKER

Microsoft are currently dialled in to our server taking a look, so I'll report back...
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
Avatar of tisl

ASKER

Been on the phone with Microsoft all this time, but still no further forward. They're calling me back again on Monday.
ASKER CERTIFIED SOLUTION
Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
wow... bad luck sorry to hear that
that's a really hairy mess @
Surprising @ MSFT didnt help you on this.
akhater @ have you faced something like this earlier @ failure to install service pack leads to domain reinstall ?
 
I haven't
Avatar of tisl

ASKER

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.
no never and I don't see why another server wouldn't "talk" to the current one since email flow is still working
Avatar of tisl

ASKER

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!