Exchange 2013 CU2, Alert for OWA Health set unhealthy from SCOM 2012

I am facing issue in Exchange 2013 CU2, I got this alert from SCOM 2012 atleast 5-6 times a day, OWA health set is unhealthy, I have done all the steps mentioned in this web link. Authentication type for OWA Virtual directory is integrated windows and Basic.
I have 2 CAS servers, and this alert generated from both of them.
http://technet.microsoft.com/en-us/library/ms.exch.scom.OWA(EXCHG.150).aspx?v=15.0.712.24
Alert: Health Set unhealthy
Source: EX-CAS - OWA
Path: EX-CAS;EX-CAS
Last modified by: System
Last modified time: 1/5/2014 8:15:08 PM
Alert description: Outlook Web Access logon is failing on ClientAccess server EX-CAS.
Availability has dropped to 0%. You can find protocol level traces for the failures on C:\Program Files\Microsoft\Exchange Server\V15\Logging\Monitoring\OWA\ClientAccessProbe.
Incident start time: 1/6/2014 4:05:08 AM
Last failed result:
Failing Component - Owa
Failure Reason - CafeFailure
Exception:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException:
Microsoft.Exchange.Net.MonitoringWebClient.ScenarioException:
Failure source: Owa
Failure reason: CafeFailure
Failing component:Owa
Exception hint: CafeErrorPage: CafeFailure Unauthorized Inner exception: Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException
ErrorPageFailureReason: CafeFailure, RequestFailureContext: FailurePoint=FrontEnd, HttpStatusCode=401, Error=Unauthorized, Details=, HttpProxySubErrorCode=, WebExceptionStatus=
Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: An error occurred on the Client Access server while processing the request
WebExceptionStatus: Success
GET https://localhost/owa/ HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; OWACTP)
Accept: */*
Cache-Control: no-cache
X-OWA-ActionName: Monitoring
Cookie:
HTTP/1.1 401 Unauthorized
request-id: 211474d2-a43e-4fab-8038-3aab35353568
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM,Basic realm="localhost"
X-Powered-By: ASP.NET
X-FEServer: EX-CAS
Date: Mon, 06 Jan 2014 04:14:47 GMT
Content-Length: 0
Response time: 0s
 ---> Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException
ErrorPageFailureReason: CafeFailure, RequestFailureContext: FailurePoint=FrontEnd, HttpStatusCode=401, Error=Unauthorized, Details=, HttpProxySubErrorCode=, WebExceptionStatus=
Microsoft.Exchange.Net.MonitoringWebClient.CafeErrorPageException: An error occurred on the Client Access server while processing the request
WebExceptionStatus: Success
GET https://localhost/owa/ HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; MSEXCHMON; ACTIVEMONITORING; OWACTP)
Accept: */*
Cache-Control: no-cache
X-OWA-ActionName: Monitoring
Cookie:
HTTP/1.1 401 Unauthorized
request-id: 211474d2-a43e-4fab-8038-3aab35353568
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM,Basic realm="localhost"
X-Powered-By: ASP.NET
X-FEServer: EX-CAS
Date: Mon, 06 Jan 2014 04:14:47 GMT
Content-Length: 0
Response time: 0s
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Net.MonitoringWebClient.BaseExceptionAnalyzer.Analyze(TestId currentTestStep, HttpWebRequestWrapper request, HttpWebResponseWrapper response, Exception exception, Action`1 trackingDelegate)
   at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.AnalyzeResponse[T](HttpWebRequestWrapper request, HttpWebResponseWrapper response, Exception exception, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse)
   at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.EndSend[T](IAsyncResult result, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse, Boolean fireResponseReceivedEvent)
   at Microsoft.Exchange.Net.MonitoringWebClient.HttpSession.EndGet[T](IAsyncResult result, HttpStatusCode[] expectedStatusCodes, Func`2 processResponse)
   at Microsoft.Exchange.Net.MonitoringWebClient.Authenticate.AuthenticationResponseReceived(IAsyncResult result)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Net.MonitoringWebClient.BaseTestStep.EndExecute(IAsyncResult result)
   at Microsoft.Exchange.Net.MonitoringWebClient.Owa.OwaLogin.AuthenticationCompleted(IAsyncResult result)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Net.MonitoringWebClient.BaseTestStep.EndExecute(IAsyncResult result)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Bool
States of all monitors within the health set:
Note: Data may be stale. To get current data, run: Get-ServerHealth -Identity 'EX-CAS' -HealthSet 'OWA'
State              
Name                                   
TargetResource                     HealthSet                    
AlertValue     ServerComponent    
NotApplicable       OwaCtpMonitor                                                             
OWA                          
Unhealthy      None               
States of all health sets:
Note: Data may be stale. To get current data, run: Get-HealthReport -Identity 'EX-CAS'
State              
HealthSet                    
AlertValue     LastTransitionTime      
MonitorCount       
NotApplicable       ActiveSync                   
Healthy        1/3/2014 5:21:13 AM     
2                  
NotApplicable       AD                           
Healthy        11/24/2013 6:54:18 AM  
 10                 
NotApplicable       ECP                          
Healthy        1/5/2014 3:03:05 AM     
1                  
Online             
Autodiscover.Proxy           
Healthy        11/20/2013 10:06:37 AM  
1                  
NotApplicable       Autodiscover                 
Healthy        1/3/2014 10:18:17 PM    
2                  
Online             
ActiveSync.Proxy             
Healthy        11/20/2013 10:06:37 AM  
1                  
Online             
ECP.Proxy                
    Healthy       
11/21/2013 6:16:08 PM    4                  
Online             
EWS.Proxy                    
Healthy        11/20/2013 10:06:37 AM  
1                  
Online             
OutlookMapi.Proxy            
Healthy        11/24/2013 6:54:28 AM   
4                  
Online             
OAB.Proxy                    
Healthy        11/19/2013 7:14:34 PM   
1                  
Online             
OWA.Proxy                    
Healthy        11/20/2013 10:06:37 AM  
2                  
NotApplicable       EDS                          
Healthy        1/3/2014 5:19:56 AM     
10                 
Online             
RPS.Proxy                    
Healthy        1/3/2014 5:21:27 AM     
13                 
Online             
RWS.Proxy                     Healthy       
1/3/2014 5:20:09 AM      10                 
Online             
Outlook.Proxy                
Healthy        1/3/2014 5:21:12 AM     
4                  
NotApplicable       EWS                          
Healthy        1/3/2014 10:18:17 PM    
2                  
Online             
FrontendTransport            
Healthy        1/5/2014 3:47:09 AM     
11                 
Online             
HubTransport                 
Healthy        1/5/2014 3:47:09 AM     
29            
NotApplicable       Monitoring                   
Unhealthy      1/5/2014 4:05:57 AM     
9                  
NotApplicable       DataProtection               
Healthy        1/3/2014 5:25:42 AM     
1                  
NotApplicable       Network                       Healthy       
1/4/2014 1:51:16 PM      1                  
NotApplicable       OWA                          
Unhealthy      1/5/2014 8:05:08 PM     
1                  
NotApplicable       FIPS                         
Healthy        1/3/2014 5:21:12 AM     
3                  
Online             
Transport                    
Healthy        1/5/2014 4:11:00 AM     
9                  
NotApplicable       RPS                          
Healthy        11/20/2013 10:07:12 AM  
2                   
NotApplicable       Compliance                   
Healthy        11/20/2013 10:08:10 AM  
2                  
NotApplicable       Outlook                      
Healthy        11/21/2013 6:12:54 PM   
2                  
Online             
UM.CallRouter                
Healthy        1/5/2014 3:47:10 AM     
7                  
NotApplicable       UserThrottling               
Healthy        1/5/2014 4:16:42 AM     
7                  
NotApplicable       Search       
                Healthy       
11/24/2013 6:55:06 AM    9                  
NotApplicable       AntiSpam                     
Healthy        1/3/2014 5:16:43 AM     
3                  
NotApplicable       Security                     
Healthy        1/3/2014 5:19:28 AM     
3                  
NotApplicable       IMAP.Protocol                
Healthy        1/3/2014 5:21:14 AM     
3                  
NotApplicable       Datamining                   
Healthy        1/3/2014 5:18:34 AM     
3          
NotApplicable       Provisioning                 
Healthy        1/3/2014 5:19:56 AM     
3                  
NotApplicable       POP.Protocol                 
Healthy        1/3/2014 5:20:44 AM     
3                  
NotApplicable       Outlook.Protocol             
Healthy        1/3/2014 5:19:46 AM     
3                  
NotApplicable       ProcessIsolation             
Healthy        1/3/2014 5:19:26 AM     
9                  
NotApplicable       Store                        
Healthy        1/3/2014 5:20:38 AM     
6                  
NotApplicable       TransportSync                
Healthy        11/24/2013 6:53:09 AM   
3                  
NotApplicable       MailboxTransport             
Healthy        1/3/2014 5:21:11 AM     
6                   
NotApplicable       EventAssistants              
Healthy        11/21/2013 6:22:01 PM   
2                  
NotApplicable       MRS                          
Healthy        1/3/2014 5:20:29 AM     
3                  
NotApplicable       MessageTracing               
Healthy        1/3/2014 5:18:15 AM     
3                  
NotApplicable       CentralAdmin                 
Healthy        1/3/2014 5:17:25 AM     
3                  
NotApplicable       UM.Protocol                  
Healthy        1/3/2014 5:17:08 AM     
3                  
NotApplicable       Autodiscover.Protocol        
Healthy        1/3/2014 5:17:13 AM     
3                  
NotApplicable       OAB                          
Healthy        1/3/2014 5:20:51 AM     
3                  
NotApplicable       OWA.Protocol                 
Healthy        1/3/2014 5:20:52 AM     
3                  
NotApplicable       Calendaring                  
Healthy        11/24/2013 6:56:59 AM   
3                  
NotApplicable       PushNotifications.Protocol   
Healthy        11/21/2013 6:16:05 PM   
3                  
NotApplicable       EWS.Protocol                 
Healthy        1/3/2014 5:19:07 AM     
3                  
NotApplicable       ActiveSync.Protocol 
         Healthy       
1/3/2014 5:20:16 AM      3                  
NotApplicable       RemoteMonitoring             
Healthy        1/5/2014 3:47:09 AM     
3
Any solution for this alert, how to rectify it, but OWA is running perfect for all users.           

Hi,
Sorry for the late reply.
Do we have Exchange 2010 coexistence?
If it is the case, I know the following known issue:
Release Notes for Exchange 2013
http://technet.microsoft.com/en-us/library/jj150489%28v=exchg.150%29.aspx
Please note the "Exchange 2010 coexistence" session.
If it is not related to our problem, please check the IIS log.
If there is any detailed error code, like 401.1, 401.2, please let me know.
Hope it is helpful
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Similar Messages

  • Exchange 2013 CU2 to CU3 OWA now redirects to IIS page

    so i did the the update from Exchange 2013 CU2 to CU3 last night and i am unable to access OWA. when i go to the site i initially received a 403 forbidden error but i cleared out the require SSL, which somehow got re-enabled, and now it redirects to the
    IIS 8 page. 
    In IIS it seems like the redirect values for default web site got cleared away. I put in the address that was previously there and then e-mail for the whole company goes down after an IIS reset. In the default web site i entered to redirect to https://mail.contoso.com/owa
    like how it was before but that doesn't work. 
    any ideas/feedback would be great!
    Thanks!

    I guess you are running a multirole server.
    Did you try removing the OWA virtual directories -  for both Default Website and Exchange Back End site with:
    #Replace ServerName
    Remove-OwaVirtualDirectory "ServerName\owa (Default Web Site)"
    Remove-OwaVirtualDirectory "ServerName\owa (exchange back end)"
    and re-creating them again with:
    #Replace ServerName & mail.domain.com
    New-OwaVirtualDirectory -InternalUrl "https://ServerName/owa" -ExternalUrl "https://mail. domain.com/owa"
    New-OwaVirtualDirectory -InternalUrl "https://ServerName/owa" -ExternalUrl "https://mail. domain.com/owa" -WebSiteName "Exchange Back End"

  • Alert: Health Set unhealthy - Clustering

    We have SCOM 2012 R2 setup to monitor our Exchange 2013 CU5 enviroment and we have gotten this error message about our Clustering going in to an unhealthy state a couple of times.  We have checked the FSW and everything seems OK on its end.  I
    cannot find much out there on this message, so any help would be greatly appreciated:
    Alert: Health Set unhealthy
    Source: EXCHANGE04 - Clustering
    Path: EXCHANGE04.company.com;EXCHANGE04.company.com
    Last modified by: System
    Last modified time: 8/24/2014 1:36:35 PM Alert description: The Cluster Group has not been healthy for 7200 minutes. The most recent probe failure message is: Check 'Microsoft.Exchange.Monitoring.QuorumGroupCheck' thrown an Exception!
    Exception - Microsoft.Exchange.Monitoring.ReplicationCheckFailedException: QuorumGroup has failed. Specific error is: Quorum resource 'Cluster Group' is not online on server 'exchange06'. Database availability group 'exchDAG' might not be reachable or may have
    lost redundancy. Error:
      File Share Witness (\\FSW01.company.com\exchDAG.company.com): Offline  is offline. Please verify that the Cluster service is running on the server.
       at Microsoft.Exchange.Monitoring.ReplicationCheck.Fail(LocalizedString error)
       at Microsoft.Exchange.Monitoring.QuorumGroupCheck.RunCheck()
       at Microsoft.Exchange.Monitoring.DagMemberCheck.InternalRun()
       at Microsoft.Exchange.Monitoring.ReplicationCheck.Run()
       at Microsoft.Exchange.Monitoring.ActiveMonitoring.HighAvailability.Probes.ReplicationHealthChecksProbeBase.RunReplicationCheck(Type checkType) Check 'Microsoft.Exchange.Monitoring.QuorumGroupCheck' did not Pass!
    Detail Message - Quorum resource 'Cluster Group' is not online on server 'exchange06'. Database availability group 'exchDAG' might not be reachable or may have lost redundancy. Error:
      File Share Witness (\\FSW01.company.com\exchDAG.company.com): Offline  is offline. Please verify that the Cluster service is running on the server.
    To add some additional information, when I look in Failover cluster manager this is what I see.  I know when we setup the servers the correct FSW information was being displayed.

    Hi,
    According to the error message, "Offline  is offline. Please verify that the Cluster service is running on the server.",
    I suggest double check whether the Cluster service is running as well. If not, please restart the service manually to verify whether this issue exists.
    Please also refer the blog below to double check whether the FSW online:
    Verifying the file share witness server / directory in use for Exchange 2010
    http://blogs.technet.com/b/timmcmic/archive/2012/03/12/verifying-the-file-share-witness-server-directory-in-use-for-exchange-2010.aspx
    If there is nothing abnormal on the Exchange server, it seems an issue on the SCOM side. Please contact SCOM Forum for help so that you can get more professional suggestions. For your convenience:
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/home?category=systemcenteroperationsmanager
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Outlook 2010 SP2 - Error when editing shared calendar: Post Exchange 2013 CU2 Migration

    Hi there,
    I have a strange comportment with Outlook 2010 SP2 and Exchange 2013 CU2 and i really need your help.
    Frequently, when an user (who has the good permissions for) want to edit a shared calendar (edit a meeting or add one), he has this error message: 
    " Cannot display the folder. Your server administrator has limited the number of items you can open simultaneously. Try closing message you have opened or removing attachments and images from unsent messages you are composing "
    I see anything in the Exchange server event log but i have each time, an error message in the client event log:
    " Microsoft Office14 Alerts ID 300"
    Everything work very well with Outlook 2013.
    Many thanks in advance for your assistance, and I am looking forward to reading from you.

    Hi,
    According to your description, the issue is related to your Office 2010 client.
    And the issue can be resolved by installing the Microsoft Office 2010 Deployment Kit.
    Here are the steps you can refer to :
    1. Open a command prompt with administrative permissions.
    2. Browse to the directory that contains the Offvirt.msi.
    3. At the command prompt, run the following command:
    msiexec /i OffVirt.msi [licensing flags]
    You must enter a correct licensing flag in the following list to correctly configure the Deployment Kit. Otherwise, functionality may be incorrect.
    For more information, you can refer to the following article:
    http://blogs.technet.com/b/virtualworld/archive/2010/07/07/microsoft-has-encountered-an-error-with-licensing-and-will-need-to-close.aspx
    If you have any question, please feel free to let me know.
    Thanks,
    Angela
    Angela Shi
    TechNet Community Support

  • Exchange 2013 CU2 to CU3 upgrade error

    I'm getting this error when running an Exchange 2013 CU2 to CU3 upgrade. Please help!
    Error:
    The following error was generated when "$error.Clear(); 
              $keyPath = "HKLM:\Software\Microsoft\WebManagement\Server";
              if (!(Get-Item $keyPath -ErrorAction SilentlyContinue))
                New-Item $keyPath -Force
              Set-ItemProperty -path $keyPath -name "EnableRemoteManagement" -value 0x1 -Type DWORD -Force;
              if (Get-Service WMSVC* | ?{$_.Name -eq 'WMSVC'})
                Set-Service WMSVC -StartupType Automatic
                Stop-SetupService -ServiceName WMSVC;
                Start-SetupService -ServiceName WMSVC
            " was run: "Service 'WMSVC' failed to reach status 'Running' on this server.".

              if (Get-Service WMSVC* | ?{$_.Name -eq 'WMSVC'})
                Set-Service WMSVC -StartupType Automatic
                Stop-SetupService -ServiceName WMSVC;
                Start-SetupService -ServiceName WMSVC
            " was run: "Service 'WMSVC' failed to reach status 'Running' on this server.".
    Is the certificate for Web Management Service (WMSvc) missing?
    If so, then you need to create a new one and assign it to the feature "Management Service" in IIS.
    Martina Miskovic

  • Exchange 2013 CU2 will not install, Exchange is now in an unuseable state.

    I have downloaded Exchange 2013 CU2 and attempted to install it from a local drive.  Exchange 2013 is installed on a Server 2012 Standard VM in Hyper-V.  I ran the two following commands before trying to install
    setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
    setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
    Upon trying to run the installer, I recieve the following error.
    Error:
    The following error was generated when "$error.Clear();
                        & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                    " was run: "AuthorizationManager check failed.".
    During my first install attept, the error was on step 4 of 15. I have tried to rerun the setup with no luck.  I noticed the installer leaves all the Exchange services disabled, as well as winmgmt, remoteregistry, w3svc, iisadmin.  These four services
    are the critical services the errors refer to.  I have verified my execution policy is correct
    PS C:\Windows\system32> Get-ExecutionPolicy -list
    Scope                                            
    ExecutionPolicy
    MachinePolicy                                               
    Unrestricted
    UserPolicy                                                  
    Undefined
    Process                                                  
    Undefined
    CurrentUser                                                  
    Undefined
    LocalMachine                                               
    RemoteSigned
    Upon trying to rerun the setup, I have ran the following commands in order to start the critical services manually
    Get-Service-name
    winmgmt,
    remoteregistry,
    w3svc,
    iisadmin
    |
    set-service -startuptype
    automatic
    Get-Service-name
    winmgmt,
    remoteregistry,
    w3svc,
    iisadmin
    |
    Start-Service
    No matter what I do, the Exchange 2013 CU2 installer seems to fail.  I'd appreciate any possible help with this.
    Thanks,
    Chris
    To add to what I posted, I also have the following error in the event log.
    [07/22/2013 13:57:01.0279] [1] Executing:
                        & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
    [07/22/2013 13:57:01.0373] [1] The following 1 error(s) occurred during task execution:
    [07/22/2013 13:57:01.0373] [1] 0.  ErrorRecord: AuthorizationManager check failed.
    [07/22/2013
    13:57:01.0373] [1] 0.  ErrorRecord:
    System.Management.Automation.PSSecurityException: AuthorizationManager
    check failed. ---> System.Runtime.InteropServices.COMException: The
    service cannot be started, either because it is disabled or because it
    has no enabled devices associated with it. (Exception from HRESULT:
    0x80070422)
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at System.Management.ManagementScope.InitializeGuts(Object o)
       at System.Management.ManagementScope.Initialize()
       at System.Management.ManagementObject.Initialize(Boolean getObject)
       at System.Management.ManagementObject.Get()
       at System.Management.Automation.PsUtils.GetParentProcess(Process current)
       at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId, ExecutionPolicyScope scope)
       at System.Management.Automation.SecuritySupport.GetExecutionPolicy(String shellId)
       at Microsoft.PowerShell.PSAuthorizationManager.CheckPolicy(ExternalScriptInfo script, PSHost host, Exception& reason)
    at Microsoft.PowerShell.PSAuthorizationManager.ShouldRun(CommandInfo
    commandInfo, CommandOrigin origin, PSHost host, Exception& reason)
    at
    System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo
    commandInfo, CommandOrigin origin, PSHost host)
       --- End of inner exception stack trace ---
    at
    System.Management.Automation.AuthorizationManager.ShouldRunInternal(CommandInfo
    commandInfo, CommandOrigin origin, PSHost host)
       at
    System.Management.Automation.CommandDiscovery.ShouldRun(ExecutionContext
    context, PSHost host, CommandInfo commandInfo, CommandOrigin
    commandOrigin)
       at
    System.Management.Automation.CommandDiscovery.LookupCommandProcessor(CommandInfo
    commandInfo, CommandOrigin commandOrigin, Nullable`1 useLocalScope,
    SessionStateInternal sessionState)
       at
    System.Management.Automation.CommandDiscovery.LookupCommandProcessor(String
    commandName, CommandOrigin commandOrigin, Nullable`1 useLocalScope)
       at System.Management.Automation.ExecutionContext.CreateCommand(String command, Boolean dotSource)
    at
    System.Management.Automation.PipelineOps.AddCommand(PipelineProcessor
    pipe, CommandParameterInternal[] commandElements, CommandBaseAst
    commandBaseAst, CommandRedirection[] redirections, ExecutionContext
    context)
       at
    System.Management.Automation.PipelineOps.InvokePipeline(Object input,
    Boolean ignoreInput, CommandParameterInternal[][] pipeElements,
    CommandBaseAst[] pipeElementAsts, CommandRedirection[][]
    commandRedirections, FunctionContext funcContext)
       at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)
       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
    [07/22/2013 13:57:01.0373] [1] [ERROR] The following error was generated when "$error.Clear();
                        & $RoleBinPath\ServiceControl.ps1 EnableServices Critical
                    " was run: "AuthorizationManager check failed.".
    [07/22/2013 13:57:01.0373] [1] [ERROR] AuthorizationManager check failed.
    [07/22/2013
    13:57:01.0373] [1] [ERROR] The service cannot be started, either
    because it is disabled or because it has no enabled devices associated
    with it. (Exception from HRESULT: 0x80070422)
    [07/22/2013
    13:57:01.0388] [1] [ERROR-REFERENCE]
    Id=AllRolesMidFileCopyComponent___af0f15afe35c4e7cba121e546f405214
    Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [07/22/2013 13:57:01.0388] [1] Setup is stopping now because of one or more critical errors.
    [07/22/2013 13:57:01.0388] [1] Finished executing component tasks.
    [07/22/2013 13:57:01.0435] [1] Ending processing Start-MidFileCopy
    [07/22/2013 13:58:09.0121] [0] End of Setup
    [07/22/2013 13:58:09.0121] [0] **********************************************
    I also have these two errors in event viewer that keep occuring. 
    Event 2280, IIS-W3SVC-WP
    The Module DLL C:\Program Files\Microsoft\Exchange Server\V15\Bin\kerbauth.dll failed to load.  The data is the error.
    Event 2300, IIS-W3SVC-WP
    The
    worker process cannot access the CLR configuration file at 'C:\Program
    Files\Microsoft\Exchange
    Server\V15\bin\GenericAppPoolConfigWithGCServerEnabledFalse.config'. 
    Verify that the file exists and that the worker process has read access
    to the file.

    I kept quickly running the following two commands while the install was happening
    Get-Service-name
    winmgmt,
    remoteregistry,
    w3svc,
    iisadmin
    |
    set-service -startuptype
    automatic
    Get-Service-name
    winmgmt,
    remoteregistry,
    w3svc,
    iisadmin
    |
    Start-Service
    This caused the install to succeed. 

  • Mails were deleted automatically from inbox and sent items, even in deleted items in Exchange 2013 CU2

    Dear all:
    I encountered a problem and needs to be solved.
    We runs Exchange 2013 CU2, and some users told me that their mails in sent items and inbox were automatically delivered into "deleted items", especially in last two weeks or yesterday.
    The users said they cannot delete so many mails at one time. And now I found one user's mails in "deleted items" were also deleted this morning.
    I don't know whether it was bug or not in exchange 2013 cu2, and how to solve this problem? Thanks for any help.
    koiso 
    Technet Microsoft

    Hi koiso,
    Are there any commons among problematic users or deleted emails? For example,
    they are on the same database
    they have delegate settings
    they are using mobile phone to sync emails
    At the same time, I'd recommend you enable Mailbox Audit Log for the problematic users. For your reference:
    http://technet.microsoft.com/en-us/library/ff459237(v=exchg.150).aspx
    Regards,
    Rebecca Tu
    TechNet Community Support

  • FrontendTransport health set unhealthy (OnPremisesSmtpClientSubmissionMonitor)

    FrontendTransport health set unhealthy (OnPremisesSmtpClientSubmissionMonitor) - The client submission probe failed 3 times over 15 minutes. 
    Seems like these alerts have started comming for some of the servers, where mailbox and CAS role is installed together. when i cehcked the queue, all seems to be fine. Performed the below mentioned steps, but the issue didn't fixed:
    1. invoke-monitoringprobe" command doesn't work.
    2. Have restarted "health manager service" didn't work.
    Still the alert value is in uhealthy state, have anyone come across the same issue, if so, can you share what are the steps that we have take? 
    Your answers are much appreciated!

    Hi,
    Please check the Monitor Result and Probe Result in the following path and see if there is any related message.
    Event Viewer\Applications and Services Logs\Microsoft\Exchange\ActiveMonitoring\ProbeResult( or MonitorResult).
    Based on your description, everthing works well except this alert. However, there is a way to hide the alert by overriding the monitor using the command below:
    Add-GlobalMonitoringOverride -Identity "FrontendTransport\OnPremisesSmtpClientSubmissionMonitor" -PropertyName Enabled -PropertyValue 0 -ItemType Monitor -ApplyVersion "version"
    Hope this is helpful to you.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • How is called the Services "OpsMgr Health Service" in the SCOM 2012 and Client machine?

    Hi,
    Can anybody tell me how is called the Services of OpsMgr Health Service in the SCOM 2012?
    I have installed the agent of scom2012 on my client computer. But I dont find any agent called "OpsMgr Health Service" on the Client machine?
    Regards

    Hi
    If you look in the services.msc window then it is listed as the System Center Management Service. This is the display name.
    The actual service name is HealthService
    Cheers
    Graham
    Regards Graham New System Center 2012 Blog! -
    http://www.systemcentersolutions.co.uk
    View OpsMgr tips and tricks at
    http://systemcentersolutions.wordpress.com/
    The Ayman answer is god, It is called "Microsoft Monitoring Agent"

  • Exchange 2013 CU2 OWA Redirection not working

    Hi,
    I installed Exchange 2013 RTM in existing environment with Exchange 2010 Sp3 in our test environment.  After installing Exchange 2013 RTM I checked when I access OWA using Internal URl it redirected to Exchange 2010 CAS server's Internal URL and I was
    able to access Exchange 2010 mailbox.
    I upgraded to CU2 and now Exchange 2013 internal URl not re-directing it to Exchange 2010 mailbox anymore. I checked all the settings on virtual directories and made sure that FBA authentication is selected.  It is a test environment and I just wanted
    to test the re-direction in co-existence environment using Internal URL. It should work out of the box but not sure what happened.  There was no issue in CU2 instllation.
    Exchange 2013 CAS and mailbox roles are on separate servers.  Same with Exchange 2010.  There is no certificate 3rd party certificate install on CAS servers since it is a test environment.
    Not sure what else can I check.
    I appreciate if any help I can get.
    Thanks,
    Regards
    Raman
    Raman

    I have been seeing issue where 2013 OWA was not re-directing to Exchange 2013, as mentioned on top of this thread.  After spending days over it.
    Finally it resolved for me after doing the following: -
    Go to CAS 2010 IIS
    OWA directory -> Authentication -> Windows Authentication -> Add provider
    Negotiate and NTLM.
    Although, now when I click on "Options" once OWA is redirected to 2010.  ECP does
    not work.  It just open up ECP page but no link works not even sign out.  I had to click back on the browser's back button go get back to main OWA mail page.
    OWA and ECP directory settings are same.  I have checked several times.
    Thanks,
    Raman

  • Out of office replies in Exchange 2013 not working for external recipients

    Hi,
    Few days ago a couple of company workers went to vacation. They set up OOF automatic replies in OWA 2013. However automatic replies are not working for external recipients (outside of company). Internal users (company users) receive OOF notification.
    I'm using smart host in sender connector configuration (SMTP server of internet provider) to deliver emails. Any clues about this problem ? Please find below part of the transaction log. For testing purposes i set up administrator account
    to be on vacation.
    HARED... SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    RECEIVE  SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    DROP     ROUTING 
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    AGENT... AGENT    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    HARED... SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    RECEIVE  SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    AGENT... AGENT    [email protected]           
    {[email protected]}             Automatic reply: vacation test
    TRANSFER ROUTING  [email protected]           
    {[email protected]}             Automatic reply: vacation test
    FAIL     SMTP    
    [email protected]           
    {[email protected]}             Automatic reply: vacation test

    Hi Informus,
    Please check if it is allowed in AllowedOOFType of the Remote Domain *
    In Exchange 2013, the only way to see or change the current configuration for automatic replying and forwarding to the Internet is via the Exchange Management Shell (EMS) with PowerShell commands.
    To get the currently configured Remote Domains, use:
    Get-RemoteDomain
    Name                           DomainName                                  
    AllowedOOFType
    Default                        *                                           
    External
    Get-RemoteDomain Default | fl AllowedOOFType, AutoReplyEnabled, AutoForwardEnabled
    AllowedOOFType     : External
    AutoReplyEnabled   : False
    AutoForwardEnabled : False
    To change the settings, use the Set-RemoteDomain command.
    Enable automatic replies
    Set-RemoteDomain -AutoReplyEnabled $true
    Enable automatic forwards
    Set-RemoteDomain –AutoForwardEnabled $true
    Enable OOF for Outlook 2003 and previous (for Exchange 2007 and 2010 support)
    Set-RemoteDomain –AllowedOOFType $ExternalLegacy
    To change all these properties at once, you can use:
    Set-RemoteDomain Default -AutoReplyEnabled $true –AutoForwardEnabled $true –AllowedOOFType $ExternalLegacy
    Note:
    Valid settings for the AllowedOOFType property are:
    External
    This is the default and only allows for the new style OOF messages as introduced in Outlook 2007.
    ExternalLegacy
    This settings allows for both the new style and old style OOF messages and needs to be set if you want to enable external OOF support for Outlook 2003 as well.
    None
    This setting doesn’t allow for the use of OOF messages at all (both internal and external).
    InternalLegacy
    This setting only allows for internal OOF messages to be sent for all Outlook versions.
    Regards,
    Satyajit
    Please “Vote As Helpful”
    if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Exchange 2013 ECP redirects to OWA

    Dear Collegues,
    after that I ve installed Exchange 2k13 on my win server 2012 std, I am not able to reach the EAC, when I tried to enter this URL: https://servername/ecp or https://servername/ecp?ExchClientVer=15 it redirects me always to OWA. I ve also tried this solution
    http://www.telnetport25.com/2012/11/quick-tipcreating-an-icon-on-the-desktop-for-the-exchange-2013-eac/ with no effect, also this http://lyncdude.com/2013/02/07/cannot-access-exchange-contorl-panel-ecp-in-exchange-server-2013/, but what really strange is,
    that my powershell cant recognize for ex. this syntax -  Get-owavirtualdirectory | fl or Set-owavirtualdirectory -identity “owa <Default Web site>” -FormAuthentication:$true at all.
    I am really confused with all of that Exchange 2k13 installation and configuration, from the beginning there are so many problems.
    Please can anyone help me?

    Hi,
    To enable the system mailboxes, I’d like to confirm how you disable them: delete the mailboxes from the Exchange management tool or delete the account from the ADUC.
    For more detailed steps to enable the system mailbox, you can refer to the following article:
    http://social.technet.microsoft.com/wiki/contents/articles/6874.how-to-recreate-system-mailbox-federatedemail-discoverysearchmailbox-in-exchange-2010.aspx
    For the redirection issue, I recommend you check the result if you login with a admin account: check it’ OWA or EAC.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Error Installing Step 10 of 12 Mailbox roles: Mailbox service on Exchange 2013 CU2

    Step 10 of 12 Mailbox roles: Mailbox service
    Error:
    The following error was generated when "$error.Clear();
              if (!$RoleIsDatacenter -and !$RoleIsDatacenterDedicated)
                $createNewOab = $false;
                $oabName = $null;
                $oabAddressList = $null;
                $oabVdirs = $null;
                $oabGlobalWebDistribution = $false;
                $oabConfiguredAttributes = $null;
                Write-ExchangeSetupLog -Info ("Looking for an existing default OAB");
                $defaultOab = Get-OfflineAddressBook -DomainController:$RoleDomainController | where {$_.IsDefault};
                if ($defaultOab -ne $null)
                  Write-ExchangeSetupLog -Info ("Found a default OAB: " + $defaultOab.Name + ";
    checking its version");
                  if ($defaultOab.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012)
    -lt 0)
                    $e15Oab = Get-OfflineAddressBook -DomainController:$RoleDomainController | where {$_.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012)
    -eq 0};
                    if ($e15Oab -eq $null)
                      Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2010 or older;
    will create a new OAB");
                      $createNewOab = $true;
                      $oabName = $defaultOab.Name + " (Ex2013)";
                      $oabAddressList = $defaultOab.AddressLists;
                      $oabGlobalWebDistribution = $defaultOab.GlobalWebDistributionEnabled;
                      $oabConfiguredAttributes = $defaultOab.ConfiguredAttributes;
                    else
                      Write-ExchangeSetupLog -Info ("Already has an existing Exchange 2013
    OAB:" + $e15Oab.Name + "; will not create a new OAB");
                  else
                    Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2013 or newer; will not
    create a new OAB");
                else
                  Write-ExchangeSetupLog -Info ("Did not find a default OAB; will create one");
                  $createNewOab = $true;
                  $oabName = [Microsoft.Exchange.Data.Directory.SystemConfiguration.OfflineAddressBook]::DefaultName;
                  $nonDefaultOabWithDefaultName = Get-OfflineAddressBook $oabName -DomainController:$RoleDomainController
    -ErrorAction SilentlyContinue | where {$_.IsDefault -eq $false};
                  if ($nonDefaultOabWithDefaultName -ne $null)
                    $createNewOab = $false;
                    Write-ExchangeSetupLog -Warning `
                      ("Offline address book " + `
                      $nonDefaultOabWithDefaultName.Name + `
                      " already exists: " + `
                      $nonDefaultOabWithDefaultName.DistinguishedName + `
                      ". Use administrative tools to change it to default OAB.");
                  $allGals = @(Get-GlobalAddressList -DomainController:$RoleDomainController | where {$_.IsDefaultGlobalAddressList});
                  if ($allGals -eq $null -or $allGals.Count -eq 0)
                    $createNewOab = $false;
                    Write-ExchangeSetupLog -Warning `
                      ("Couldn't find the default global address list. The default offline
    address book can't be created.");
                  elseif ($allGals.Count -gt 1)
                    $createNewOab = $false;
                    Write-ExchangeSetupLog -Warning `
                      ("Found " + $allGals.Count + " default global address
    lists. You can have only one default global address list in your organization. The default offline address book will not be created.");
                  else
                    $oabAddressList = $allGals[0];
                    Write-ExchangeSetupLog -Info ("OAB will be based on default GAL: " + $oabAddressList.Name);
                if ($createNewOab)
                  if ($oabGlobalWebDistribution -eq $false)
                    $currentAdSiteDn = (Get-ExchangeServer $RoleFqdnOrName -DomainController:$RoleDomainController).Site.DistinguishedName;
                    $allOabVdirs = @(Get-OabVirtualDirectory -DomainController:$RoleDomainController);
                    $e15MinimumServerVersion = New-Object Microsoft.Exchange.Data.ServerVersion([Microsoft.Exchange.Data.Directory.SystemConfiguration.Server]::E15MinVersion);
                    if ($allOabVdirs -ne $null -and $allOabVdirs.Count -gt 0)
                      foreach ($oabVdir in $allOabVdirs)
                        if ([Microsoft.Exchange.Data.ServerVersion]::Compare($oabVdir.AdminDisplayVersion,
    $e15MinimumServerVersion) -gt 0)
                          $oabVdirSiteDn = (Get-ExchangeServer $oabVdir.Server
    -DomainController:$RoleDomainController).Site.DistinguishedName;
                          if ($oabVdirSiteDn -eq $currentAdSiteDn)
                            $oabVdirs = $oabVdir;
                            break;
                          elseif ($oabVdirs -eq $null)
                            $oabVdirs = $oabVdir;
                    if ($oabVdirs -ne $null)
                      Write-ExchangeSetupLog -Info ("OAB will be distributed to OAB virtual
    directory " + $oabVdirs.Name);
                    else
                      Write-ExchangeSetupLog -Info ("Could not find any OAB virtual directories;
    OAB will be configured without distribution.");
                  try
                    Write-ExchangeSetupLog -Info ("Creating new default OAB.");
                    $newOab = New-OfflineAddressBook `
                      -Name $oabName `
                      -AddressLists $oabAddressList `
                      -VirtualDirectories $oabVdirs `
                      -GlobalWebDistributionEnabled $oabGlobalWebDistribution `
                      -IsDefault $true `
                      -DomainController:$RoleDomainController;
                  catch [Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException]
                    Write-ExchangeSetupLog -Warning ("Tried to create new default OAB but the object
    already exists; it may have been created by another instance of setup.");
                  if ($oabConfiguredAttributes -ne $null)
                    Write-ExchangeSetupLog -Info ("Setting OAB ConfiguredAttributes to: " +
    $oabConfiguredAttributes);
                    Set-OfflineAddressBook $newOab -ConfiguredAttributes $oabConfiguredAttributes -DomainController:$RoleDomainController;
            " was run: "Cannot find an overload for "CompareTo" and the argument count: "1".".

    so we're having the same issue. Installing Exchange 2013 across 2 sites in a coexistence 2007/2010 environment. Everything on one site (3x Exchange servers) installed perfectly, but only 1x Exchange servers on other site installed. Remaining 2x Exchange
    servers gave the same error that Harry had. Any ideas? I checked OAB and all mailboxes had a default OAB assigned already. looked through the logs and found this in case it helps:
    [02/13/2015 22:37:31.0105] [2] Found a default OAB: Default Offline Address List (Ex2013) Default Offline Address List (Ex2013)
    CNF:608015af-50a4-450a-0000-91fada1a9af9; checking its version
    [02/13/2015 22:37:31.0120] [2] Ending processing Write-ExchangeSetupLog
    [02/13/2015 22:37:31.0151] [1] The following 1 error(s) occurred during task execution:
    [02/13/2015 22:37:31.0151] [1] 0.  ErrorRecord: Cannot find an overload for "CompareTo" and the argument count: "1".
    [02/13/2015 22:37:31.0151] [1] 0.  ErrorRecord: System.Management.Automation.MethodException: Cannot find an overload for "CompareTo" and the argument count: "1".
       at CallSite.Target(Closure , CallSite , Object , Object )
       at System.Dynamic.UpdateDelegates.UpdateAndExecute2[T0,T1,TRet](CallSite site, T0 arg0, T1 arg1)
       at System.Management.Automation.Interpreter.DynamicInstruction`3.Run(InterpretedFrame frame)
       at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)
    [02/13/2015 22:37:31.0151] [1] [ERROR] The following error was generated when "$error.Clear(); 
              if (!$RoleIsDatacenter -and !$RoleIsDatacenterDedicated)
                $createNewOab = $false;
                $oabName = $null;
                $oabAddressList = $null;
                $oabVdirs = $null;
                $oabGlobalWebDistribution = $false;
                $oabConfiguredAttributes = $null;
                Write-ExchangeSetupLog -Info ("Looking for an existing default OAB");
                $defaultOab = Get-OfflineAddressBook -DomainController:$RoleDomainController | where {$_.IsDefault};
                if ($defaultOab -ne $null)
                  Write-ExchangeSetupLog -Info ("Found a default OAB: " + $defaultOab.Name + "; checking its version");
                  if ($defaultOab.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012) -lt 0)
                    $e15Oab = Get-OfflineAddressBook -DomainController:$RoleDomainController | where {$_.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012) -eq 0};
                    if ($e15Oab -eq $null)
                      Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2010 or older; will create a new OAB");
                      $createNewOab = $true;
                      $oabName = $defaultOab.Name + " (Ex2013)";
                      $oabAddressList = $defaultOab.AddressLists;
                      $oabGlobalWebDistribution = $defaultOab.GlobalWebDistributionEnabled;
                      $oabConfiguredAttributes = $defaultOab.ConfiguredAttributes;
                    else
                      Write-ExchangeSetupLog -Info ("Already has an existing Exchange 2013 OAB:" + $e15Oab.Name + "; will not create a new OAB");
                  else
                    Write-ExchangeSetupLog -Info ("Existing OAB is Exchange 2013 or newer; will not create a new OAB");
                else
                  Write-ExchangeSetupLog -Info ("Did not find a default OAB; will create one");
                  $createNewOab = $true;
                  $oabName = [Microsoft.Exchange.Data.Directory.SystemConfiguration.OfflineAddressBook]::DefaultName;
                  $nonDefaultOabWithDefaultName = Get-OfflineAddressBook $oabName -DomainController:$RoleDomainController -ErrorAction SilentlyContinue | where {$_.IsDefault -eq $false};
                  if ($nonDefaultOabWithDefaultName -ne $null)
                    $createNewOab = $false;
                    Write-ExchangeSetupLog -Warning `
                      ("Offline address book " + `
                      $nonDefaultOabWithDefaultName.Name + `
                      " already exists: " + `
                      $nonDefaultOabWithDefaultName.DistinguishedName + `
                      ". Use administrative tools to change it to default OAB.");
                  $allGals = @(Get-GlobalAddressList -DomainController:$RoleDomainController | where {$_.IsDefaultGlobalAddressList});
                  if ($allGals -eq $null -or $allGals.Count -eq 0)
                    $createNewOab = $false;
                    Write-ExchangeSetupLog -Warning `
                      ("Couldn't find the default global address list. The default offline address book can't be created.");
                  elseif ($allGals.Count -gt 1)
                    $createNewOab = $false;
                    Write-ExchangeSetupLog -Warning `
                      ("Found " + $allGals.Count + " default global address lists. You can have only one default global address list in your organization. The default offline address book will
    not be created.");
                  else
                    $oabAddressList = $allGals[0];
                    Write-ExchangeSetupLog -Info ("OAB will be based on default GAL: " + $oabAddressList.Name);
                if ($createNewOab)
                  if ($oabGlobalWebDistribution -eq $false)
                    $currentAdSiteDn = (Get-ExchangeServer $RoleFqdnOrName -DomainController:$RoleDomainController).Site.DistinguishedName;
                    $allOabVdirs = @(Get-OabVirtualDirectory -ADPropertiesOnly -DomainController:$RoleDomainController);
                    $e15MinimumServerVersion = New-Object Microsoft.Exchange.Data.ServerVersion([Microsoft.Exchange.Data.Directory.SystemConfiguration.Server]::E15MinVersion);
                    if ($allOabVdirs -ne $null -and $allOabVdirs.Count -gt 0)
                      foreach ($oabVdir in $allOabVdirs)
                        if ([Microsoft.Exchange.Data.ServerVersion]::Compare($oabVdir.AdminDisplayVersion, $e15MinimumServerVersion) -gt 0)
                          $oabVdirSiteDn = (Get-ExchangeServer $oabVdir.Server -DomainController:$RoleDomainController).Site.DistinguishedName;
                          if ($oabVdirSiteDn -eq $currentAdSiteDn)
                            $oabVdirs = $oabVdir;
                            break;
                          elseif ($oabVdirs -eq $null)
                            $oabVdirs = $oabVdir;
                    if ($oabVdirs -ne $null)
                      Write-ExchangeSetupLog -Info ("OAB will be distributed to OAB virtual directory " + $oabVdirs.Name);
                    else
                      Write-ExchangeSetupLog -Info ("Could not find any OAB virtual directories; OAB will be configured without distribution.");
                  try
                    Write-ExchangeSetupLog -Info ("Creating new default OAB.");
                    $newOab = New-OfflineAddressBook `
                      -Name $oabName `
                      -AddressLists $oabAddressList `
                      -VirtualDirectories $oabVdirs `
                      -GlobalWebDistributionEnabled $oabGlobalWebDistribution `
                      -IsDefault $true `
                      -DomainController:$RoleDomainController;
                  catch [Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException]
                    Write-ExchangeSetupLog -Warning ("Tried to create new default OAB but the object already exists; it may have been created by another instance of setup.");
                  if ($oabConfiguredAttributes -ne $null)
                    Write-ExchangeSetupLog -Info ("Setting OAB ConfiguredAttributes to: " + $oabConfiguredAttributes);
                    Set-OfflineAddressBook $newOab -ConfiguredAttributes $oabConfiguredAttributes -DomainController:$RoleDomainController;
            " was run: "Cannot find an overload for "CompareTo" and the argument count: "1".".
    [02/13/2015 22:37:31.0151] [1] [ERROR] Cannot find an overload for "CompareTo" and the argument count: "1".
    [02/13/2015 22:37:31.0167] [1] [ERROR-REFERENCE] Id=SystemAttendantDependent___b06ea38070354e2c9f0000c2b971306a Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [02/13/2015 22:37:31.0167] [1] Setup is stopping now because of one or more critical errors.
    [02/13/2015 22:37:31.0167] [1] Finished executing component tasks.
    [02/13/2015 22:37:31.0214] [1] Ending processing Install-MailboxRole

  • Exchange 2013 "Server Error in '/owa' Application" - System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 1

    Out of nowhere...literally this started happening to our standalone Exchange server / Domain Controller
    Operating System: Microsoft Windows Server 2012 Standard
    Problem Child: Microsoft Exchange Server 2013
    Error: When i try to login to the OWA or ECP i receive the listed errors above.
    OS and Exchange installed on C:\
    Mailbox Databases installed on D:\
    Mailbox Logs on E:\
    Outlook is still working for the end-user, but Outlook Web Access, ECP and all other features required to make this server manageable are failing. I can access the login screen, though at:
    https://<servername>/owa
    or
    https://<servername>/ecp
    I have tried reset of virtual directories. Tried IISRESET /NOFORCE after this, but no success.

    Hi MRXennix,
    Base on my research, the issue is caused by corrupted Killbit.xml file on "ClientAccess\owa\15.0.xxx.x\owa2\ext\killbit".
    I recommend you refer to the following method to solved the issue:
    1. Remove the Killbit.xml file and restart IIS
    2. Install the latest CU builds of the exchange 2013.
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Migrating from 2010 windows nlb cas array to exchange 2013 using netscaler for HLB

    i currently have exchange 2010 sp3 setup as follows
    2 cas/ht using windows nlb for array.internal.com as the nlb name
    2 mailbox servers using 1 dag for replication between them.
    I would like to stand up 2 new CAS 2013 sp1 servers(2012 r2) and use our netscaler hlb to load balance and do ssl offloading.
    id like to use the hlb to load balance and ssl offload all possible traffic not just owa, i.e. activesync etc.
    the netscaler is running version 10.5.
    does anyone have any thoughts on how to perform such a migration?
    id like to make this as seamless as possible for the user, so no owa name change or anything like that.
    thx in advance for any help.

    Exchange 2013 CAS cannot be managed effectively without an Exchange 2013 mailbox server since the CAS won't run the Exchange 2013 management tools without it.  Your Exchange 2013 servers should simply have both roles.  There are few cases where
    splitting the roles has any business value.
    If what you're planning to do is within the same forest and organization, then it's a "transition", not a "migration".  What you are asking to do is easy.  Build the Exchange 2013 servers, configure load balancing, test
    access, and then switch the DNS records to point to them.
    Personally, I would skip the SSL offloading.  It's my opinion that it makes the solution more difficult to troubleshoot without providing any real benefit.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Maybe you are looking for

  • Field Catalog in Free Goods Setup

    Hi Gurus, We are trying to set up Free Goods in CRM standalone. No condition type is replicated from R/3 and we have to set up everything from scratch in CRM. Under the IMG, Free goods, the first menu option is 'Field Catalog'. Could you please advis

  • Default Selection in Combo Box

    Hi, I have a query regarding combo box. I have populated combo box using UserDataSources. Is it possible to make a default selection of an Item in combo box. Regards Ronald

  • Removing Install Files

    Hello Arch forums. I've recently just reinstalled Arch because it was going to *bleep*, and after I installed and uninstalled some packages (namely the Eclipse and Eric IDEs) I noticed that when I reinstall them, the total download size is 0.00 MB, a

  • Combine two tables without common field

    Hi Experts, I have two database tables, DBSTATORA(stores inform about all the tables involved in infoproviders), and RSDODSO ( stores information about ODS Objects. I have to list the ods objects and its associated tables as the output, but there is

  • Hurry! Call for Proposals to India's Annual Summit for Business Technologies Closes 30 June 2010!

    To join Business Technology Summit 2010 as a speaker is a great opportunity to build brand equity for both you as an individual and for your organization. By presenting your experiences, technical & market knowledge, and innovations, through keynotes