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

Similar Messages

Exchange 2013 + 2007 OWA coexistance not redirecting properly (HTTP 400)

Hello. I am using this document to funnel our new Exchange 2013 external traffic through an IIS ARR reverse proxy, much like we already do for MIcrosoft
Lync 2013 on this machine.
http://blogs.technet.com/b/exchange/archive/2013/08/02/part-2-reverse-proxy-for-exchange-server-2013-using-iis-arr.aspx
I followed this guide to a T. especially the part on the page 2 that I linked above about creating the legacy.domain.com server farm and URL rewrite rule. This
IIS ARR proxy seems to work fine for Outlook Anywhere, ActiveSync, OWA if the user's mailbox is on the Exchange 2013 server, but it does not work if an OWA user logs in with a mailbox on 2007.
When the user has a mailbox on 2007, after logging into OWA they get HTTP 400 error. The URL bar in the browser is changed to https://legacy.domain.com/owa/auth/owaauth.dll
The Exchange 2007 server IIS logs show this:
70.x.x.x, -, 11/1/2014, 9:45:48, W3SVC1, MAIL, 10.1.1.3, 0, 523, 132, 400, 0, POST, /owa/auth/owaauth.dll, -,
I can't figure out why this is happening. DNS is correct. legacy.domain.com points to the 2007 Exchange server. webm.domain.com points to the
Exchange 2013 server.
Any ideas?

Doing more testing, I almost think the Exchange 2007 server keeps redirecting. So the HTTP 400 is because when you hit legacy.domain.com, it redirects
to webm.domain.com which redirects back to legacy.domain.com and vice versa.
I put a test.txt file in the Exchange 2007 owa virtual directory and I cannot access it in any browser. I tried https://legacy.domain.com/owa/test.txt and
It redirects me to https://webm.domain.com(Exchange 2013). I can however go
one level (or more) deep on the legacy server and get a file such as https://legacy.doamin.com/owa/8.3.342.1/themes/base/logon.css and
in the browser I see the code (both externally AND internally, so I know DNS and firewall is working).
I can't find anywhere on IIS 6.0 on the Exchange 2007 server where any kind of redirection is taking place though. Virtual Directory properies for owa say
"A directory located on this computer: "C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa" Enable default content page is checked with default.aspx but I looked at default.aspx in notepad and I don't see ANY code telling it to
redirect.
In Exchange 2007 management console OWA internal URL and External URL both sayhttps://legacy.domain.com/owa .
I have no idea what is causing this redirection. I did an iisreset and also recycled the OwaAppPool and no change.

Exchange 2010/2013 coexistence: OWA proxy not working properly ":-( Something went wrong"

Hi
Exchange 2010 users are NOT able to connect to their mailboxes when they go through exchange 2013 OWA address. We get a message that says following ---> "Something went wrong"
Following is our URL. The address is pointing to 2013 CAS loadbalancer VIP. Outlook anywhere is working fine. What is going on?
Important: All my exchange 2010 / 2013 URIs are the same as suggested by Microsoft (Owa, ecp, activesync, ews, autodiscover): --> mail.domain.com/XXX

Hello Rawa,
Can you log on Exchange 2010 OWA using its localhost address?
Please make sure the intenralurl value is set to Exchange 2010’s local host name and set the Externalurl to Null.
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2013 Autodiscover Android IOS not working

Hello,
I configured exchange 2013 in my organization. Android, thunderbird and IOS not working with autodiscover.
Windows Phone example Lumia worked with autodiscover correctly.
All needed DNS entry and certificate are uploaded to Exchange.
Test on https://testconnectivity.microsoft.com/ ended successfuly.
Can Android and IOS supported autodiscover.
BR/Lukas

Yes i try https://fqdn/Microsoft-Server-ActiveSync instead
I have White page nothing else.
IOS, Android work after manualy configured. Windows Phone work with autodiscover wonderfully
Ok we added public IP address to our CAS Server. Now from Internet i can login to /OWA or /ECP.
What next to do? Change autodiscover.domain.com Record A to point NAT IP address CAS server?
BR/Lukas

Exchange 2013 / Eudora POP-account not working

I have a MAC (version 9) user who has Eudora (6.2.4). User tries to connect to Exchange 2013 server with POP-account but is unable to get this to work.
I tried to search the web for this answer but couldn't.
I would be happy to know if this is even possible to set up before I spend my time and customer's money on this.
I got Eudora 7.1 working with IMAP on my XP Virtual machine, but I have no way of testing it with MAC-computer.
Edit: I also got POP account working on my XP Virtual machine.

Thanks for your reply. I do not know the specific error message as this happens to one of our end-customer and he has not provided detailed information about this.
User can't update Eudora, because he is using older version of MAC.
I would just like to know if it is even possible to connect Eudora 6.2.4 to Microsoft Exchange 2013.

Exchange 2013 - Public folder search not working

Hi There,
We have Exchange 2013 install on server 2012 and clients using Outlook 2010 on Windows 7.
Since we have installed the system a search of the public folders always returns no results even if we know the email is there. Any suggestions?
Thank you
Dave

Hi Triumphtech,
Yes, if our Exchange 2003 environment is healthy, it will work.
Please forgive me for the silly clarification. If we used Exchange 2003 and wanted to migrate to Exchange 2013. We must migrate to Exchange 2007/2010 first, then to Exchange 2013.
So please make sure we have moved the public folder successfully first.
And great information from Tarique Noorain.
According to the article, I found some points for your reference:
1. Although a full text search of public folder content is available, public folder content isn't searchable across public folders and the content isn't indexed by Exchange Search.
2. You must use Outlook 2007 or later to access public folders on Exchange 2013 servers.
Feel free to contact me if there is any problem.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013 CU3 Retention Policy Not working for Calendar & Tasks

We are currently on Exchange 2013 CU3 with Online Archiving Enabled for the user
Default policy is set to move all the items in mailbox which are older than 30 days to online archive mailbox.
Calendar and Tasks Items are also getting archived alongwith other Outlook items from Inbox,Deleted Items etc
Followed Technet website and created RPT for Calendar and Tasks with retention disabled
Still DPT takes precedence and move all the items under Calendar and Task to Online Archive Mailbox

Hi Sam,
I recommend you refer to the following article, despite this for Exchange 2010, however the same applies to exhcnage 2013:
Prevent archiving of items in a default folder in Exchange 2010
To prevent the <acronym title="Default Policy Tag">DPT</acronym> from being applied to a default folder, you can create a disabled <acronym title="Retention Policy Tag">RPT</acronym> for that folder (or disable
any existing RPT for that folder). The Managed Folder Assistant, a mailbox assistant that processes mailbox items and applies retention policies, does not apply the
retention action of a disabled tag. Since the item/folder still has a tag, it's not considered untagged and the DPT isn't applied to it.
Why are items in the Notes folder still archived?
If you create a disabled <acronym title="Retention Policy Tag">RPT</acronym> for the
Notes folder, you'll see items in that folder are not deleted, but they do continue to be moved to the archive! Why does this happen? How do you prevent it?
It's important to understand that:
A retention policy can have a <acronym title="Default Policy Tag">DPT</acronym> to
archive items (using the Move to Archive retention action) and a DPT to
delete items (using the Delete and Allow Recovery or
Permanently Delete retention actions). Both apply to untagged items.
The move and delete actions are exclusive of each other. Mailbox folders and messages can have both types of tags applied - an archive tag and a delete tag. It's not an either/or proposition.
If you create a disabled RPT for the Notes folder to not delete items, the archive DPT for the mailbox would still apply and move items.
When it comes to archiving, there's only one archive policy that administrators can enforce – the <acronym title="Default Policy Tag">DPT</acronym> with 'Move to archive' action.
You can't create a <acronym title="Retention Policy Tag">RPT</acronym> with the 'Move to archive' action. This rules out using the disabled RPT approach to prevent items from being moved.
Best regards,
Niko Cheng
TechNet Community Support

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"

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

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.

Exchange 2013 CU7 OWA 400 Bad Request after successful login

Scenario:
Exchange 2007/2013 Migration
One
Exchange 2007 Server [removed]
One
Exchange 2013 Server Std, Windows 2012
All mailboxes moved to 2013
- November 27-30 2014
All public folders moved to
2013 - December 2, 2014
Exchange
2007 is still running and has not been removed from the domain, yet. [update]
Exchange
2007 removed from domain - 12-13-14
SSL
Certs are current for: Autodiscover.ExtDom.com, ex13.ExtDom.com, ex13.IntDom.com
Applied
CU6 (Dec 3, 2014) to fix Mobile access issues. Since applying CU6, OWA does not work with the exception of mobile browsers (Chrome - Nexus 7) or Safari 5.1.7 on Windows 7. These browsers get the OWA 2010 theme (Yellow).
User
logs into OWA with Domain\UserName and PWD(IE). After clicking Sign In, page returns Bad Request. No errors logged in w3scv logs.
[update]
CU7 applied 12-11-2014
All
users can connect using Outlook 2013 or Mobile (iPhone & Android)
Exchange
Admin Center (ECP) still works!
Browsers
tested: IE10 (windows 7 x64),Chrome 39.0.2171.71m, Opera 26.0, FireFox 34.0.5, Safari 5.1.7
Attempted:
https://ex13.ExtDom.com/owa
https://ex13.IntDom.com/owa
https://ex13.ExtDom.com/owa?ExchClientVer=15
https://ex13.IntDom.com/owa?ExchClientVer=15
https://localhost/owa
(on Ex 2013 server)
https://localhost/owa?ExchClientVer=15
(on Ex 2013 Server)
Fixes
attempted:
remove
| create Virtual Directories for OWA
Change
authentication through Exchange PowerShell - Integrated/Basic from FBA/Basic
reverted
since change didn’t work.
Run
UpdateCas.ps1
Run
UpdateConfigFiles.ps1
IISReset
(iisReset /NoForce fails)
OWA
(Default Web Site) displays as Version 15.0 (Build 995.29) in EAC. [update] Build 1044.25 (CU7)
Links
used for troubleshooting:
http://community.spiceworks.com/topic/514617-exchange-2013-unable-to-login-to-owa-ecp
https://social.technet.microsoft.com/Forums/ie/en-US/f8aa95d4-19e4-483c-8c4b-b039ab0d0127/400-bad-request-when-logging-in-to-owa-exchange-2013?forum=exchangesvrclients
http://tecfused.com/2013/09/23/exchange-2013-ecp-double-login-error-400/
https://social.technet.microsoft.com/Forums/lync/en-US/c25ce81c-76ea-471a-93ae-eeaf9e5015ac/exchange-2013-owa-error-400-bad-request?forum=exchangesvradmin
http://support.microsoft.com/kb/2871485/en-gb

Hi,
Does it work if you disable the FBA and only use the basic authentication?
Please also let us know the authentication settings on the Default Web site.
Thanks,
Simon Wu
TechNet Community Support

Added barracuda LB. owa 2010 not working on virtual IP - works using host IP. IIS home page works on virtual IP

Hi,
I have 2 exchange servers in a DAG. (exc1 and exc2) (DAG is called: outlook.domain.com)
I added 2 load balancers in front of them to distribute the load + ensure uptime for the users.
the load balancers have a virtual IP - 192.168.1.33
there is an A record in DNS pointing to this IP called: outlook.domain.com
SSL offloading is enabled and certificate has been imported to the LBs
Outlook clients work just fine using outlook.domain.com - everything OK
OWA works using https://exc1/owa and https://exc2/owa
but OWA does NOT work using Https://outlook.domain.com/owa
I get "connection reset"
IIS front page works just fine (https://outlook.domain.com gives iis7 welcome page) - its only when I add /owa to it, that the error appears.
any ideas?
thanks in advance
/chris

Do both sets not say to
set Client certificates, select Ignore?
I'm skimming so may be missing something.
You can have session persistence using IP affinity, but depending on what you want to publish and achieve you may need to inspect the traffic on the LB. I was curious as it adds a bit more complexity.
And is Outlook 2010 upto date? What is the exact build string on a client that is getting the prompt please? This is a person bugbear of mine:
http://blogs.technet.com/b/rmilne/archive/2013/07/18/patching-exchange-don-t-overlook-outlook.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

OWA apps not working

Issue: OWA apps not working
Not sure why APPS are not working only in OWA, tested with IE, Google chrome & Firefox.
Note: APPS are working in outlook 2013
Exchange Version: Exchange 2013 SP1 CU5
OS: Microsoft Windows Server 2012 Datacenter
Regards
Rajesh

Hi,
Please check the following link to solve this issue.
http://support.microsoft.com/kb/2938292
If this issue persists, please take the following steps for workaround.
Locate to %ExchangeInstallPath%FrontEnd\HttpProxy\owa\web.config, open this file in notepad.
Added the key <add key="aspnet:UseLegacyRequestUrlGeneration" value="true" /> to the
<appSettings>
Close this window to apply the change and take a test.
Best Regards.

Windows 7 (Ent) Sp1 on server 2012 R2 HyperV, RFX USB redirection not working

Hello,
I currently have windows server 2012 R2 with HyperV installed. I have built two virtual machines. A windows 8.1 and Windows 7 sp1. Both are enterprise editions
For RemoteFX the hypervisor is using a Zotec GTX 760 GPU. It recognizes it and uses it to apply remoteFX adapter on my Windows 7 Sp1 VM.
As you are aware I do not need to use a GPU to enable RFX on my Windows 8.1 it can do this without the need of a GPU.
Using an RDP client( v8.1) I can connect to my Windows 8.1 VM with a USB headset,memory Key or a printer and they all enumerate on the Virtual machine. The driver for each device installs
and I can use the device without any issues.
However this issue lies with the Windows 7 SP1 VM. I can connect to it via RDP( Same client) but I cannot redirect any devices to it. I have installed the latest integration services available on the VM. I have ran all updates available.
Because I have ran all updates the rdp version on the VM is running v8.1.
Previous to installing the updates USBr still was not working
I have enabled the following group polices under remote desktop services on the Windows 7 SP1 VM :
RDP 8.0 -- Enabled
Configure RFX -- Enabled
Is there a known issue with USB redirection not working on a Windows 7sp1 virtual machine hosted on server 2012 Hypervisor ??
Many Thanks
Brian

Hi,
According to the log above, I found that we run the script on both Server6 and Server7. Errors as below:
Server6: Conversion is not supported in restricted language mode or a Data section.
Server7: Couldn't figure out valid servers from the specified destination scope. Check your parameters and try again.
Since we can only run the RollAlternateserviceAccountPassword.ps1 Script on CAS server, the script not works well if Server6 is MBX server.
For Server7, based on the error message, it seems you still have no right to run the script/cmdlet.
Please add your account to Organization Management Role group(ADUC->domain.com->Microsoft Exchange Security Groups) to test if possible.
By the way, from Technet:
You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Client Access Security" entry in the Client Access Permissions topic.
Client Access Permissions
http://technet.microsoft.com/en-us/library/dd638131.aspx
Feel free to contact me if there is any problem.
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
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 OWA Redirection not working

Similar Messages

Maybe you are looking for