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

HELP! SBS 2008 Exchange 2007 SP2 install failed and now IIS and TS gateway not working

Help!

Last night I attempted to install Exchange 2007 Service Pack 2 on a SBS2008 machine.  I used the MS tool specifically for this here:

http://support.microsoft.com/kb/982423

During service pack install the installer crashed.  I have attached the log file from the install.  the error mentions something about memory.

the upshot of this is I was able to successfully start the Exchange services, and mail is flowing.  I tried to re-apply the service pack via the SBS2008 tool in the link above but it now thinks it has SP2 installed.  Exchagne Management console reports Exchange version is now 8.1 build 240.6.  Is that SP2?

However, my main issues which need urgent resolution are these:

the Terminal Server Gateway that runs on the SBS208 box no longer works.  It is started, but connection attempts to any PC say that the gateway is temporarily unavailable.

IIS sites seem to be corrupt.  I get a Runtime Error error trying to browse to https://sbsserver/owa.   this is preventing users outside the office using Outlook over HTTP from accessing their email.  Perhaps this is also related to the TS Gateway issue as well?

Can anyone help urgently?

I vaguely recall a support article about errors in SBS websites after Exchange SP2 install which i think is what the install help tool above is meant to fix so I'm going to go hunting for that now too.

thanks
nathan
ExchangeSetup.log
0
natrat22
Asked:
natrat22
  • 8
  • 2
  • 2
  • +1
1 Solution
 
natrat22Author Commented:
As a followup:

I have looked at the issues here:

http://support.microsoft.com/kb/973862#issues

which are exactly what I have.  I have applied the suggested fixes and restarted IIS Admin Service and the TS Gateway Service but the same issues remain.  runtime error accesing /owa internally, and the TS gateway server temporarily unavailable error.
0
 
natrat22Author Commented:
Further to this:

When I add the third party SSL certificate to the TS Gateway Manager, it applies successfully.  When I restart TS Gateway service, the SSL settings have gone.  I still can't connect before or after restarting the TS Gateway service though.

When i first tried re-adding the SSL certificate to the TS gateway manager as per the troubleshooting page above, it prompted me about an IIS config error.  I clicked the prompt and ity said it had now configured IIS for TS gateway.  However, it still doesnt work.
0
 
natrat22Author Commented:
This is the error when browsing to OWA:

Server Error in '/owa' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.

Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly"/>
    </system.web>
</configuration>
 

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="On" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>
0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 
natrat22Author Commented:
I've changed the mode so i can see the actual error message.  it is below.

I imagine its definitely due to the crash of the Exchange SP2 install.    So - where to now?  

Server Error in '/owa' Application.
--------------------------------------------------------------------------------

Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly 'Microsoft.Exchange.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

Source Error:


Line 49:                         the compiler.  All assemblies in the GAC and owa\bin are referenced automatically.
Line 50:                         -->
Line 51:                         <add assembly="Microsoft.Exchange.Data,
Line 52:                               Version=8.0.0.0,
Line 53:                               Culture=neutral,
 

Source File: C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\web.config    Line: 51

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Exchange.Data, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' could not be loaded.


WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
0
 
natrat22Author Commented:
Geez I am really stuck.  I was just trying to see if the client Access Role was installed by going to "change" under Exchange Server 2007 in Programs and Features, and i get the error:

Setup previously failed while performing the action "BuildToBuildUpgrade".  you cannot resume setup by performing the action "install".

I am looking at this now:

http://support.microsoft.com/kb/947281

But don't now how to figure out where the install was up to in order to manually continue it?
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
TO check SP you always should check the version of Store.exe or Mad.exe ... this will exactly tell you what is your Exchange version :)

to check the install you need to check through Registry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v8.0
There would be keys like "Client Access\mailbox\Hub" .... what keys do you see under that ?

Let me know if there is Watermark on any of them or see if you expand them an djust share a screenshot of those registries and the error with location :)

- Rancy
0
 
NetfloCommented:
Hi,

In answer to your questions, your version number indicates you are still on SP1. Reference: http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollups-build-numbers-en-us.aspx

First and foremost I would recommend taking a full system backup and then proceeding to install Exchange 2007 SP3 - it is a cumulative update, so you don't need to do SP2 first. SP3 is also much more seamless, you don't need to run an extra tool. I would also recommend disabling your antivirus and third party backup solutions - i.e. Backup Exec to ensure the upgrade process is not interrupted.

Exchange 2007 SP3 on SBS: http://support.microsoft.com/kb/982423

Let me know how you get along.
0
 
Exchange_GeekCommented:
You're memory issue was cause of .NET - possible re-install might help you, however as @Netflo mentioned it would be wise to upgrade to SP3 and allow it to fix you're issue.

Ref: http://forums.msexchange.org/m_1800534462/mpage_1/key_/tm.htm#1800534482

Regards,
Exchange_Geek
0
 
natrat22Author Commented:
After spending half a day on it I ended up paying MS to look at it.  the SP2 install is half corrupt.  they've got OWA and TS gateway working again, just mobile phone connectivity still down, then they will re-run the service pack install.  Will update final resolution when done.
0
 
Exchange_GeekCommented:
@natrat22: you should have worked with SP3 upgrade, fair enough - please post you're solution here.

Regards,
Exchange_Geek
0
 
natrat22Author Commented:
As the SP2 install itself is only half applied i thought it might make things worse going to SP3.  The issue started 1.5 days ago and i didn't get any advice and had all external users (outlook and TS gateway) screaming at me so I rang MS :)
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Yeah we can understand how bad it is to be stuck in such a situation ...... please keep us updated so that if anything required we can assist you.

- Rancy
0
 
natrat22Author Commented:
No solution provided in the time frame before I had to get MS support to fix it.
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 8
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now