OWA/ECP Monitoring 401 after CU2

We are running mixed Exchange 2010 SP3 and Exchange 2013 CU2. Was previously on CU1. After installing CU2, the monitors for OWA and ECP failing with 401. Both are working fine for users, and monitoring was working fine on CU1. Looking
at the log its just a 401 for every test on OWA and ECP. From the log:
2013-07-17T00:02:05.315Z,---------------------------------------------------------------------------------------------
2013-07-17T00:02:05.299Z,"Starting Owa probe with Target:
https://localhost/owa/, Username:
[email protected] "
2013-07-17T00:02:05.299Z,Test step started: OwaLoginScenario
2013-07-17T00:02:05.299Z,Test step started: Authentication
2013-07-17T00:02:05.299Z,"Request being sent:
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
2013-07-17T00:02:05.299Z,"OWA logon scenario failed: 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: ba2812e2-659b-4b21-895e-ab49ffc6bcf9
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/8.0
WWW-Authenticate: Negotiate,NTLM,Basic realm=""localhost""
X-Powered-By: ASP.NET
X-FEServer: S1EX2013-01
Date: Wed, 17 Jul 2013 00:02:05 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: ba2812e2-659b-4b21-895e-ab49ffc6bcf9
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/8.0
WWW-Authenticate: Negotiate,NTLM,Basic realm=""localhost""
X-Powered-By: ASP.NET
X-FEServer: S1EX2013-01
Date: Wed, 17 Jul 2013 00:02:05 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, Boolean requiresSynchronization)
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: ba2812e2-659b-4b21-895e-ab49ffc6bcf9
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/8.0
WWW-Authenticate: Negotiate,NTLM,Basic realm=""localhost""
X-Powered-By: ASP.NET
X-FEServer: S1EX2013-01
Date: Wed, 17 Jul 2013 00:02:05 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: ba2812e2-659b-4b21-895e-ab49ffc6bcf9
X-FailureContext: FrontEnd;401;VW5hdXRob3JpemVk;;;
Server: Microsoft-IIS/8.0
WWW-Authenticate: Negotiate,NTLM,Basic realm=""localhost""
X-Powered-By: ASP.NET
X-FEServer: S1EX2013-01
Date: Wed, 17 Jul 2013 00:02:05 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)"
2013-07-17T00:02:05.315Z,---------------------------------------------------------------------------------------------

Hi,
I am only aware of the the following known issue:
See the "Exchange Control Panel might not work when requests are proxied through Exchange 2013" section in the following article:
http://technet.microsoft.com/en-us/library/jj150489%28v=exchg.150%29.aspx
If it is not related to your problem, please refer to the IIS log and let me know the detailed error code, like 401.1, 401.2.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Similar Messages

After upgrade exchange owa, ecp and outlook stop working

Yesterday I installed the updates that Microsoft had released. Unfortunate as it looks like OWA, ECP and Outlook stopped working after this installation. See picture for the updates were made.
What you are greeted by when besker OWA and ECP is a blank page. Is anyone had the same problem and knows how to fix this?
Or is there a way to back these updates?
Jesper B

Hi Jesper,
Is there any update? Have the issue been resolved?
The updates are all for Windows server 2012 R2. What's your Exchange server version? Additionally, please check the following in IIS Manager:
a. In IIS manager > Default Web Site, make sure Anonymous Authentication is Enabled in Authentication.
b. Double-click SSL Settings, confirm that "Require SSL" is checked on the root of the default website.
c. Restart IIS service by running iisreset /noforce from a command prompt window.
If possible, please collect more event logs in Event Viewer for further analysis.
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support

Exchange Server 2010 - OWA, ECP, EWS not working

Hello,
I am evaluating exchange server 2010. I was able to install it, but now the admin websites will not render in IIS. OWA, ECP, etc. I especially want Outlook Anywhere to work. I can admin through the windows admin interface so that's not a concern.
I want users to access their email through the web as well. I checked permissions but could have them wrong. Any help is appreciated.
Thanks
John Grace

There are about twenty different types of 403 error. To see which one is happening here, you'd need to look at the IIS log files, and get the status subcode, which is the number after the 403 in the logged line.
The most common, though, is 403.4, which means 'SSL Required'. What happens if you go to
https://servername (i.e. https instead of http).
Another one is 403.6, which means that IIS has been configured to only allow access to a certain range of IP address, and the one you're trying to access it from isn't one of them.
OWA For SmartPhone

Popup for credentials when connecting to OWA/ECP when using HLB DNS name

Hi,
We're experiencing a strange problem when connecting to OWA/ECP.
Since a week or two, we get a popup for credentials when logging onto
https://mail.customer.com/owa.
When the credentials are filled in the first time, we keep receiving the popup, and can't get through.
We're using integrated authentication internally.
When connecting externally, we get a popup from a non domain-joined pc, but get passed correctly to owa and ECP.
We're using a load balancer that uses mail.customer.com, and distributes it over the 3 exchange servers.
When connecting directly to each exchange server, we get a certificate warning (which is logic), but after confirming we get passed to ecp or owa correctly.
Works :
https://exchangeserver1.customer.com/owa (after receiving certificate warning)
https://exchangeserver2.customer.com/owa (after receiving certificate warning)
https://exchangeserver3.customer.com/owa (after receiving certificate warning)
https://10.10.10.30/owa (after receiving certificate warning) > 10.10.10.30 is the VIP ip address used for loadbalancing
Doesn't work :
https://mail.customer.com/owa
When changing the hosts file, and set mail.customer.com to point directly to one of the exchange servers, it doesn't work either.
PS :
So mail.customer.com gets forwarded to the VIP ip address.
We don't experience any problems with outlook.

Hi
Chek if VIP FQDN is added to DNS
Check if RpcClientAccessServer parameter using Set-MailboxDatabase for each mailbox database in the appropriate site
Set-MailboxDatabase -RPCClientAccessServer "CASArrayFQDN"
Change AutoDiscoverServiceInternalUrl on each CAS using Set-ClientAccessServer
Change InternalUrl parameter on each CAS using Set-WebServicesVirtualDirectory Identity EWS*in the appropriate site
Change the InternalURI in the Exchange Control Panel, offline address book, and Microsoft Exchange ActiveSync (through management console under server management for each appropriate CAS)
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
Regards,
Sathish

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

Exchange 2013 cros site blank page OWA/ECP

Hello,
I have an issue with a fresh installation of Exchange 2013 SP1.
The are two AD site in different cities, connected by WAN link (site-to site VPN organized by Cisco ASA).
I installed two Exchange servers in Site A (MBX1 and MBX2, both with MBX+CAS roles), and one Exchange server MBX3 in Site B (also both with MBX+CAS roles).
Each Exchange hosts its own mailbox database (DB1, DB2, DB3 respectively), there are no DAG.
Users spread over all databases. For example, user1 has mailbox in DB1, user2 - in DB2, user3 in DB3.
When user1 opens OWA/ECP on CAS server MBX1 or MBX2, he successfully get into his mailbox.
But, if user1 opens OWA/ECP on CAS server MBX3, he get blank page (no error at all).
And vise versa:
When user3 opens OWA/ECP on CAS server MBX3, he successfully get into his mailbox.
But, if user3 opens OWA/ECP on CAS server MBX1 or MBX2, he get blank page (no error at all).
I know, that Exchange 2013 is able to proxy request cross site.
Where are no custom redirects set on IIS.
Also I check IIS (Back End Site) for right certificate.
There are no error in Windows Event log and IIS event Log.
All ports are allowed between sites.
Everything looks good.
What I did wrong? May be I need to enable cross-site OWA proxy in Exchange somewhere?
Or it is a CISCO ASA misconfiguration?
Any help would be appreciated!
Thank You!
Pavel

Hi,
Firstly, I’d like to confirm if all your Exchange server are internet facing servers.
We can try to clear the Forms based authentication on the non-internet facing server.
And here is a similar thread you can refer to:
http://social.technet.microsoft.com/Forums/exchange/en-US/85983a21-3922-46f4-b64a-d53c0a2271a7/issues-with-crosssite-cas-redirect-of-owa-users?forum=exchange2010
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Win 8.1 not remembering dual monitor setup after reboot

Hello,
I am running Windows 8.1 64-bit Enterprise N with the following hardware:
HP ENVY TouchSmart 4-1245tu Sleekbook with Intel HD 4000 Graphics
Dell Monitor
HDMI Out from laptop to VBGA In on monitor (HDMI to VGA Convertor used to connect with second monitor).
I have setup multiple monitors and it works fine. However once I do a reboot on the laptop the machine, after reboot only laptop screen is detected and second monitor/external monitor not detected ( it is blank with the External monitor having its backlight on (so its not in standby) but nothing is being sent to it.)
It looks as if Windows 8.1 is not remembering the extend monitor setup after a reboot.
I am running the latest drivers from Intel for Windows 8.1 64 bit and Intel 4000 graphics:
Release Version: Production Version
Driver Version: 15.33.5.64.3316
Package: 209756
Intel(R) Graphics Driver: 10.18.10.3316
Intel(R) Display Audio Driver: 6.16.0.3123
Operating System(s):
Microsoft Windows* 8.1 64-bit
Release Date: October 04, 2013
Downloaded from intel site - https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=23405&lang=eng
Any ideas?

I have the same problem with HP8300 Elite CMT
Dual monitor works fine after reinstalling the video drivers.
When I restart the PC the second monitor is not found and the drivers have to be reinstalled.
I have opened a support case
Case ID <4648891774>
Waiting for feedback - if the problem is resolved - I will post an update

Unable to see views Active Alerts, Discovered Inventory, Distributed Applicatios, Task Status, Unix/Linux Computers, Windows Computer under Monitoring workspace after upgrading to UR6

Hi All,
Recently I upgraded SCOM 2012 SP1 CU5 to CU6 and facing following issue:
1. New menu item got grayed out that appears upon the right click on Monitoring node(root) under monitoring workspace.
2. When we click Monitoring in the navigation pane, the Monitoring Overview opens, which displays a summary of health states and alerts. if we click any of the numbers in the overview, it is supposed to open a state view of the selected category but
this function does not work now.
3. Views like Active Alerts, Discovered Inventory, Distributed Applications, Task Status, Unix/Linux Computers and Windows Computer do not appear under Monitoring workspace after upgrading to UR6.
Has anyone out there facing such kind of issue? Any help on fixing these issues would be appreciating. Thanks in advance.

Hi,
Have you re-opened the operation manager console?
There are some known issues when intalling UR6, please go through it:
http://support.microsoft.com/kb/2929885
In addition, there is CU7 for SCOM sp1, why not installing the newest one:
http://support.microsoft.com/kb/2965420
Regards,
Yan Li
Regards, Yan Li

OWA/ecp internally redirects to externalURL value!!

Hi
We have 3 CAS servers. 2 are in main site and One of these CAS servers is on the remote site. I am having a really weird issue with the CAS server in remote site called CAS3.
InternalURL and ExternalURL values are the same and available in both internal & external DNS.
If we go to https://cas3 it redirects over to https://owa.domain.com address!!!!!!!!
I did the following and no difference :-(
1. Did an IISreset
2. Made sure there are NO IIS redirections on / /owa & /ecp
3. I changed InternalURL and ExternalURL value of CAS3 server to internal FQDN
None of the above worked. I don't have such issues with CAS1 and CAS2. What gives???????
Note: All mailboxes are on the production site mailbox servers.

Hi Kman2K,
One of all circumstances that CAS will only perform a redirection action as below:
For Outlook Web App requests, if the mailbox’s location is determined to be in another Active Directory site and there are CAS2013 members in that site that have the ExternalURL populated, then the originating CAS will redirect the request unless the
ExternalURLin the target site is the same as in the originating site – in which case CAS will proxy (this is the multiple site single namespace scenario).
More details to see:
Exchange 2013 Client Access Server Role
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Thanks
Mavis Huang
TechNet Community Support

Multiple OWA & ECP Virtual Directories on Exchange 2010 - 500 internal server error

hello folks,
I've been using below link to create multiple owa & ecp virtual directories on exchange 2010, but I have similar error -500 internal server error
during auth.owa from my 2nd owa url login.
exactly steps follow as below:-
http://johnyassa.wordpress.com/2012/06/07/publish-multiple-owa-ecp-virtual-directories-on-one-exchange-2010-cas-server/
did anyone has come across on this issue and do mind share to me?
thanks
regards
Jimmy

hi Ed Crowley,
thanks for responding to me...
yes, I'm exactly follow blog below to configure my 2nd OWA URL with form based authentication method. upon login to my 2nd OWA URL, the owa authentication failed with return 500 - internal server error.
http://johnyassa.wordpress.com/2012/06/07/publish-multiple-owa-ecp-virtual-directories-on-one-exchange-2010-cas-server/

[SOLVED] Monitor blanking after 10 minutes

I've got to the end of PART II of the excellent Beginners Guide but before I embark on the next part, I need to solve the issue of my monitor blanking after 10 minutes of inactivity. Please note that, at this stage, I do not have "X" installed. Any help would be greatly appreciated, thanks.
Last edited by tenlegger (2010-08-01 06:36:58)

karol wrote:
tenlegger wrote:I've got to the end of PART II of the excellent Beginners Guide but before I embark on the next part, I need to solve the issue of my monitor blanking after 10 minutes of inactivity. Please note that, at this stage, I do not have "X" installed. Any help would be greatly appreciated, thanks.
That's the default behavior. If you don't like it (and want to install X), add
xset s off -dpms &
to your .xinitrc.
'man setterm' will guide you if you need it for the terminal. Check the '-blank' switch.
I've always used
setterm -blank 0
in my .bashrc.
*Don't* try to use and of the acpi=off stuff until you're sure that my advice didn't work.
As I don't yet have "X" installed, I've tried your .bashrc tweak and it's had the desired effect.
When I get around to installing "X", will I need your .xinitrc tweak in addition to the .bashrc tweak.
Many thanks to you and everybody else for your suggestions and help
Regards .....

Adding additional url for owa/ecp

Dear friends,
My requirement is to add additional domain name url for OWA for my exchange 2013. Let me explain:
Currently my public url for OWA is mail.domain.com and now i want to add additional name like mail.domain2.com . I have added additional suffix and create users for this, now the remaining part is the url for OWA. I have created dns entries in godaddy and
i have the ssl certificate for both the domain names. I can access the owa using the another url domain but hitting certificate error.
Please help.

Hi,
From your description, the issue is related to the certificate. I would like to verify if you have one CAS server. If yes, you can create these two names in one certificate and check the result.
What's more, here is a helpful blog for your reference:
Configuring Multiple OWA/ECP Virtual Directories on the Exchange 2013 Client Access Server Role
http://blogs.technet.com/b/exchange/archive/2015/02/11/configuring-multiple-owa-ecp-virtual-directories-on-the-exchange-2013-client-access-server-role.aspx
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support

404 Error After Successfully Logging in to OWA/ECP in Exchange 2013

Hello,
My apologies first if this would be better asked in another forum but this one seems to fit best. I am running Exchange 2013 on Windows Server 2008 R2 Standard and am experiencing an issue after logging in to ECP and OWA. After entering my credentials
(all credentials experience the same issue) I am redirected to a 404 error for both \ecp and \owa. The odd thing is that Re-entering the url completes the login. How do I fix the appearent lack of the login.aspx? If my description isn't
sufficient please let me know.
Thanks.

What if you want to use FBA? We are using FBA and on first logon on any computer the 404 page is displayed. You can click the "Refresh the page" button and it takes you into OWA. When you log out and close IE, the next time you logon on
that same computer it takes you right in. If you clear your temp files (cookies etc. included), you get the same 404 page. I've attached an image below-

Exchange 2013 OWA/ECP HTTP 500 Internal Server Error

So I know there are a lot of these threads, so I'll list what I've done and what I've tried so far.
The setup is a pair of multirole servers with a DAG. We have a root domain and sub domain.
I've created 4 databases associated with the DAG, I successfully removed the default database on the 2nd mail server, then migrated the arbitration/system/discovery etc... mailboxes to one of the DAG databases. I then removed the 1st mail server's default
database after killing it's healthmailbox. Rebooted the pair of servers and after that the ECP/OWA were inaccessible.
To run tests I installed .NET 3.5 SP1 so I could run the ExBPA which really didn't get me anywhere.
I can access the logon screen for both, but when I enter my username and password, I get the http 500 internal server error.
I have used: Get-OwaVirtualDirectory -Server <server name> | fl *auth*
To verify that basic and forms based auth are enabled, and they are.
I've verified all services have started.
I've tried to remove and re-add the app pools and the ecp virtual directories.
http://social.technet.microsoft.com/Forums/ie/en-US/bb148ccb-a75e-4571-bfc7-76950f8e638e/exchange-2013-cu2-cant-access-ecp-unexpected-error-500?forum=exchangesvrgeneral
I've tried to use ADSI Edit to purge the Canary Data.
http://social.technet.microsoft.com/Forums/exchange/en-US/777b51ee-330d-43cc-a56e-4614d44aed7b/unable-to-access-owa-or-ecp-something-went-wrong-or-500-unexpected-error?forum=exchangesvrclients
I've tried to run test-ecpconnectivity but stated that the test user wasn't available.
So I tried to use the powershell script to create a new test user, but it doesn't seem to work either I think it's related to the exchange machine not being a member of the root domain, but not sure on that one.
I seem to be able to manage everything with command-line still. Create and remove mailboxes etc.
As far as errors/warnings go exchange wise I get an ASP.NET 4.0 warning Event ID 1309 stating that an unhandled exception occurred, which seems to coincide with the logon attempt. I'm sure this has something to do with it, but not real sure what yet.
Nothing I can see within the logon attempt from IIS or anything else really.
I think that's about all I have.

Hi,
Please check on the Application Pools to view whether OWA and ECP Application Pool is running on .NET Framework v4.0. It maybe the incompletely installation of Framework that causes this error.
If so, We can try to run the following command as Administrator:
%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i
Or change the MSExchangeECPAppPool from .NET Framework from v4.0 to v2.0. Then restart IIS to have a try.
Regards,
Winnie Liang
TechNet Community Support

Problem with windows and my monitor in after effects

HI . before any thing excuse me for speeking english.
i have a problem with windows in after effect in my monitor
my monitor is 15.6 and resolution is 1366*768
for example when i open interpret footage window i can't see that complete and amount of size window dont visible.
Thanks.

Your system doesn't meet the requirements and that is that. AE has required 900 pixel height ever since CS4. Other than changing your screen res or shuffling around windows there is nothing you can do.
Mylenium

OWA/ECP Monitoring 401 after CU2

Similar Messages

Maybe you are looking for