Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
SBS 2011 OWA Not working, ASP 2 errors, no access to Exchange console or powershell

Answered SBS 2011 OWA Not working, ASP 2 errors, no access to Exchange console or powershell

  • Tuesday, September 27, 2011 2:10 AM
     
     
    Sign In to Vote
    0

    OK, I have a problem that I'm pretty sure is related to IIS but is causing me a whole heap of issues.

     

    Server was rebooted to install a new tape drive.  Following reboot OWA stopped working as well as ActiveSync.  Believed it to be a faulty install of Exchange 2010 rollup 4v2 so followed advice and installed it with elevated administrative priveledges.

     

    This didn't fix the issue but now means I can't get into Exchange management AT ALL.  Exchange itself is working. Event Viewer is littered with ASP errors  Error messages at bottom – I’ll detail what I’ve tried to fix it first (as I’ve tried a LOT)

    1)      Tried uninstalling the rollup

    2)      Registered ASP 2.0, allowed .NET Framework 1.1 in IIS. Confirmed all AppPools are started

    3)      Tried everything in http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx including running EMTShooter which gave me a supremely unhelpful output

    4)      Renamed security.config

    5)      Installed WinRM for IIS and also confirmed WinRM is correctly configured

    6)      Checked that Kerbauth is native and just in powershell (not also def website)

    7)      Checked WSMan module is in ApplicationHost.config

    8)      Confirmed port 80 is bound to the default website

    9)      Confirmed the location of Exchange install and powershell is correct

    10)   Ran ExBPA.exe directly from its location – no issues

    So I’m basically at my wits end and any help would be appreciated J

    ASP Errors in Event Viewer:

    Event 1334 ASP>NET 2…

     

    Failed to initialize the AppDomain:/LM/W3SVC/1/ROOT/Microsoft-Server-ActiveSync

     

    Exception: System.SystemException

     

    Message: Failed to create AppDomain.

    Plus

    IIS-W3SVC-SP 2299

    An application has reported as being unhealthy. The worker process will now request a recycle. Reason given: ASP.NET application initialization failed.. The data is the error.

    When I try to connect to Exchange Console I get:

    Attempt to connect using Kerberos failed. ..WinRM client received an HTTP server status (500)

    Connecting to powershell gives:

     VERBOSE: Connecting to SBS2011.Blah.local

    [sbs2011.blah.local] Connecting to remote server failed with the following error message : The WinRM client rece

    ived an HTTP server error status (500), but the remote service did not include any other information about the cause of

     the failure. For more information, see the about_Remote_Troubleshooting Help topic.

        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc

       eption

        + FullyQualifiedErrorId : PSSessionOpenFailed

    VERBOSE: Connecting to SBS2011.blah.local

    [sbs2011.blah.local] Connecting to remote server failed with the following error message : The WinRM client rece

    ived an HTTP server error status (500), but the remote service did not include any other information about the cause of

     the failure. For more information, see the about_Remote_Troubleshooting Help topic.

        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc

       eption

        + FullyQualifiedErrorId : PSSessionOpenFailed

    VERBOSE: Connecting to SBS2011.Blah.local

    [sbs2011.blah.local] Connecting to remote server failed with the following error message : The WinRM client cann

    ot process the request. It cannot determine the content type of the HTTP response from the destination computer. The co

    ntent type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.

        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc

       eption

        + FullyQualifiedErrorId : PSSessionOpenFailed

     

All Replies

  • Tuesday, September 27, 2011 2:17 AM
     
     
    Sign In to Vote
    0
    ping and reverse lookup all working.
     
  • Tuesday, September 27, 2011 3:21 AM
     
     
    Sign In to Vote
    0

    EMT result

    Welcome to the Exchange Management Troubleshooter!

    We recommend that you run the troubleshooter after making changes to
    IIS to ensure that connectivity to Exchange Powershell is unaffected.

    Checking IIS Service...

    Checking the Exchange Install Path variable...

    Checking the Powershell Virtual Directory...

    Checking the Powershell vdir SSL setting...

    Checking the Powershell vdir path setting...

    Checking HTTP Port 80...

    Checking HTTP Port 80 Host Name...

    Testing for errors...

    VERBOSE: Connecting to SBS2011.blah.local


    [sbs2011.bell-booth1.local] Connecting to remote server failed with the following error message : The WinRM client recei
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExcep
        + FullyQualifiedErrorId : PSSessionOpenFailed
    The Exchange Management Troubleshooter successfully completed connecting to:

    SBS2011.blah.local

    Failed to connect to any Exchange Server in the current site.

    Problem found:

    Looking for error...

    After each error is resolved, close this window and re-run the tool to check for additional problems.

     
  • Tuesday, September 27, 2011 7:00 PM
     
     
    Sign In to Vote
    0
    I am having this exact same issue - am on my second day of an SBS 2003 to SBS 2011 migration.  Are you migrating or did you simply apply updates?  I made the mistake of installing updates on a reboot and ended up in your camp.  I had started going down the same road you detailed (rereg asp, install WinRM, etc) before I saw your post.  I'm currently peeling back updates on at a time...
    I can connect to the login page for OWA, the login page will tell me if/when my password is incorrect but once I login successfully I am bounced to a 500 error.  Exchange clients are offline as well - keeps asking for their username/password.
     
  • Tuesday, September 27, 2011 7:11 PM
     
     
    Sign In to Vote
    0
    I was able to restore client Exchange access by removing KB2555251 - Update Rollup 1 for Windows Small Business Server 2011 Standard (KB2555251).  My OWA remains broken despite removing the update and rebooting, but at least client PCs are back in Exchange.  
     
  • Tuesday, September 27, 2011 7:47 PM
     
     
    Sign In to Vote
    0

    Server has been in for a while.  Not passing the buck but this was put in by another team so I have no idea how it all went.  I do know they had issues from the off, especially with backups and sharepoint.  Sharepoint has been switched off.


    However Sharepoint SP1 has been applied.  I'm wondering if, because SP was switched off, that this didn't apply correctly and has caused ASP issue (honestly I'm clutching at straws here)

     

    Clients can connect to Exchange OK.  OWA not working and consle not working (which means you can't set contacts/forwards etc etc)

    Current plan is to image it up, bring it back to the lab and start ripping things out.

     
  • Tuesday, September 27, 2011 10:51 PM
     
     
    Sign In to Vote
    0

    Try recreating powershell VD:

    Go to a normal powershell and type:

    add-pssnapinMicrosoft.Exchange.Management.PowerShell.E2010

     

    Then type Get-PowershellVirtualDirectory | Remove-PowershellVirtualDirectory

     

    Then type New-PowershellVirtualDirectory->Hit Reutrn->type "powershell"->iisreset and try again

     
  • Wednesday, September 28, 2011 12:06 AM
    Moderator
     
     
    Sign In to Vote
    0
    When I've seen this someone has ran the SharePoint config wziard and set
    up a new SharePoint-80 web site.
     
    Nuke the site, restart the default web site.
     
    Bottom line compare the IIS settings in this non working to a working
    SBS 2011 (virtualize one in vmware or virtualbox as a guide)
     
     
  • Wednesday, September 28, 2011 1:52 AM
     
     
    Sign In to Vote
    0

    thanks for the responses.  Recreating the Powershell vd did not resolve the issue.


    Setup of IIS is exactly the same as two other boxes.

    Anything that uses .NET 4 as an app pool base (e.g. localhost\remote) works.  Anything that uses .NET2 fails.

    I've tried to repair .net2 (sfc /scannow and asp_iisreg) but this has made no difference.  I think its an issue with .NET2 but I can't uninstall or repair it in the slightest (very frustrating).

    If I change OWA to use .NET 4 it asks for credentials but then bombs me out. Does the same on powershell vd if I browse it as well.

    So, how can I repair my .NET 2?

     
  • Wednesday, September 28, 2011 2:56 AM
    Moderator
     
     
    Sign In to Vote
    0

    I'd post in the partner forum as well on this issue.  www.sbspartnerforum.info

    Did you install any line of business app that took over the .net -ism?

     
  • Wednesday, September 28, 2011 4:11 AM
     
     
    Sign In to Vote
    0

    Can you post a screenshot of IIS please?

    Inside the following folder C:\Program Files\Windows Small Business Server\Bin\CMPNENTS you'll find a .net 4.0 and a .ASP Ajax setup file. Run both of those (asp first and .net4 second)

    Also you can always modify the exchange server install to remove the Client Access Role, and then after a reboot, modify it again to re-install it. Make sure you have good backups now before you do anything as you're in better shape now than you will be if something goes wrong.

     
  • Wednesday, September 28, 2011 4:18 AM
     
     
    Sign In to Vote
    0

    I'll collate all my findings and post there tomorrow cheers.

    Forgot to say in my earlier post that running psconfig and finishing the Sharepoint 2010 SP1 install had no effect.

    I've now restored (to the lab) a C drive image taken before this issue.  Everything works.  However all the Windows updates that I had suspected, were already installed so it's definately NOT a Windows update that's caused this.

    Checking with the tech who escalated this to me highlighted that Symantec Backup Exec 2010 R3 was installed.  This is currently now my culprit as I suspect it may have installed .NET2 over the top of the old one, or just snaffled it.

    Once I've got the live site up and running again I'm going to try and break the lab server one by installing BE2010R3 just to see.

     
  • Wednesday, September 28, 2011 4:24 AM
     
     
    Sign In to Vote
    0

    what would we do without backups? lol. , a http 500 error says there's something wrong with the code of the website, uninstalling the client access role and re-installing it should default your iis exchange directories and re-install .NET2 over the existing one resolving the issue. If you can break it on the lab one, see if what I suggested works, it'll be nice to know for sure for next time.

    Thanks

     
  • Wednesday, September 28, 2011 4:33 AM
    Moderator
     
     
    Sign In to Vote
    0

    http://msmvps.com/blogs/bradley/archive/2011/04/16/promise-me-you-won-t-try-to-do-this.aspx

     

    See if that a/v installed .net like that?

     
  • Wednesday, September 28, 2011 8:09 AM
     
     
    Sign In to Vote
    0
    If exchange is forced on .net 4 it will bust it out.Check event viewer....are you getting any crash events [1000] or any other error for MSExchangeRPCClientAccess ?
     
  • Wednesday, September 28, 2011 2:05 PM
     
     
    Sign In to Vote
    0

    Can you check if you have

    HKEY_LOCAL_COMPUTER\SOFTWARE\Microsoft\.NETFramework

    OnlyUseLatestCLR set to 1

    Sumesh P - Microsoft Online Community Support
     
  • Wednesday, September 28, 2011 7:33 PM
     
     
    Sign In to Vote
    0

    http://msmvps.com/blogs/bradley/archive/2011/04/16/promise-me-you-won-t-try-to-do-this.aspx

     

    See if that a/v installed .net like that?


    That was one of the first things I tried thanks Susan (straight from your blog)
    • Edited by AndyB-NZ Wednesday, September 28, 2011 7:33 PM
    •  
     
  • Wednesday, September 28, 2011 7:34 PM
     
     
    Sign In to Vote
    0
    Exchange itself is fine.  Mail flow and client access (non OWA or Active-Sync) is fine.
     
  • Wednesday, September 28, 2011 7:36 PM
     
     
    Sign In to Vote
    0
    I don;t appear to have that Sumesh - should it appear under a specific Key under .NET framework?
     
  • Wednesday, September 28, 2011 7:38 PM
     
     
    Sign In to Vote
    0

    Can you post a screenshot of IIS please?

     


    Any particular part? :)
     
  • Wednesday, September 28, 2011 10:21 PM
     
     
    Sign In to Vote
    0

    OK, current thinking is that it was the Visual Studio C++ 2010 part of the BE2010R3 update install that broke ASP 2

    Reasoning being that it was all working with BE2010R3 on and only went south when the update and C++ were installed.

     
  • Wednesday, September 28, 2011 11:33 PM
     
     
    Sign In to Vote
    0

    lol i'd like to say the entire thing, with all your settings but that'd probably take you a while...

    It't doesn't matter now anyways, I still think doing the uninstall and re-install of just the client access role will resolve it.

     
  • Thursday, September 29, 2011 1:26 AM
     
     
    Sign In to Vote
    0

    site is back up with the restore of the C drive so that's a relief.


    Now some replication attempts on the one in the lab

     
  • Thursday, September 29, 2011 8:54 PM
     
     Answered
    Sign In to Vote
    0

    lol i'd like to say the entire thing, with all your settings but that'd probably take you a while...

    It't doesn't matter now anyways, I still think doing the uninstall and re-install of just the client access role will resolve it.


    except you can't uninstall the CAS role in SBS 2011.  If you try and do it through Programs and Features it's greyed out.  You may be able to do it from the Exchange powershell but since that was my issue I couldn't do that either.  I firmly believe it was a .NET corruptuion.

    I have been unable to repo this (although I have managed to break Exchange in new and exciting ways on my test environment) at all.

    However, like seemingly most things in SBS 2011, I believe the only fix for this was roll back to a previous image.  Everything seems to be so embedded in this version that there is no 'fix' for core components as such (IIS, Exchange, ASP).

    So my resolution is rollback the OS to a time before the issue occurred.  Thsi caused no issues on the domain, no issues with the secondary DC on the branch site, no replication issues either despite going back a week.

    Highlights the imporatnace of good imaging technology (I haven't used the built in Windows backup as a major yet so can't comment on it's effectiveness in this regard).

    • Marked As Answer by AndyB-NZ Thursday, September 29, 2011 8:54 PM
    •  
     
  • Sunday, March 18, 2012 9:44 PM
     
     
    Sign In to Vote
    0

    I am having this problem now on one production server.

    What was the resolution?

    OWA and Company Web are down.

    Remote Web Workplace is up, but no one can connect remotely anymore to any workstations "Gateway temporarily unavailbale" message.

    Application log Errors 2299 and 1334

    An application has reported as being unhealthy.  The worker process will now request a recycle.  Reason given: ASP.NET application initialization failed.. The data is the error.

    and

    An error occurred while trying to start an integrated application instance.  Exception: System.SystemException Message: Failed to create AppDomain. blah blah blah...

    Just started happening, server has been running fine for a year.  I have been googling all weekend and this is the closest thread I found to the problem.

    I agree it looks like ASP.NET 2.0 problems, how to fix?

     
  • Friday, April 13, 2012 8:00 PM
     
     
    Sign In to Vote
    0

    Jason, please start a new post.

    Since this one has already been answered, its unlikely people will check this post.

    In addition every situation is different, even if the symptoms look the same, so It would be wise to start troubleshooting from scratch to make sure we get all the accurate facts.

    Thanks

    -GT

     
  • Tuesday, September 11, 2012 12:43 AM
     
     
    Sign In to Vote
    0
    I'm in the same boat as AndyB was in. Restoring server from image is not an option as I've gone several days since the issue started...please help