Exchange 2013 SP1: Unable to log on to ECP ASP.NET 4.0.30319.0 unhandled exception …..[SOLVED]


HI

Same player shoot again. Today this is the ECP directory who refuse all connections. OWA now work but not the ECP . Why? .. don’t ask me please !

Let enable Logs with these commands on my 2 Exchange servers :

set-eventloglevel -identity « MSExchange Control Panel\General » -level expert
set-eventloglevel -identity « MSExchange Control Panel\Performance » -level expert
set-eventloglevel -identity « MSExchange Control Panel\Redirect » -level expert
set-eventloglevel -identity « MSExchange OWA\Core »-level expert
set-eventloglevel -identity « MSExchange OWA\Configuration » -level expert
set-eventloglevel -identity « MSExchange OWA\Themes » -level expert
set-eventloglevel -identity « MSExchange OWA\SmallIcons » -level expert
set-eventloglevel -identity « MSExchange OWA\Proxy » -level expert
set-eventloglevel -identity « MSExchange OWA\Transcoding » -level expertµ
set-eventloglevel -identity « MSExchange OWA\ADNotifications » -level expert
set-eventloglevel -identity « MSExchange OWA\InstantMessage » -level exp

Resetting all external Url to $null for Ecpvirtualdirectory
My both Ecp virtualdirectory on each cas server look like this

[PS] C:\Windows\system32>Get-EcpVirtualDirectory -Server srvexc02 | fl identity,internalurl,externalurl
Creating a new session for implicit remoting of « Get-EcpVirtualDirectory » command…
Identity : SRVEXC02\ecp (Default Web Site)
InternalUrl : https://srvexc02.company.loc/ecp
ExternalUrl :

Identity : SRVEXC02\ecp (ExchangeBasic)
InternalUrl :
ExternalUrl :

IISreset clearing all the eventviewer log and test again

And now ! A Well know friend of mine! ASP.NET 4.0.30319.0 unhandled exception!


Log Name: Application
Source: ASP.NET 4.0.30319.0
Date: 4/22/2014 10:30:44 AM
Event ID: 1309
Task Category: Web Eventµ
Level: Warning
Keywords: Classic
User: N/A
Computer: SrvExc02.company.loc
Description:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 4/22/2014 10:30:44 AM
Event time (UTC): 4/22/2014 8:30:44 AM
Event ID: 40677d0459d84302974496a0d6feea05
Event sequence: 12
Event occurrence: 11
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/2/ROOT/owa-3-130426287673269311
Trust level: Full
Application Virtual Path: /owa
Application Path: C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\
Machine name: SRVEXC02
Process information:
Process ID: 9504
Process name: w3wp.exe
Account name: NT AUTHORITY\SYSTEM
Exception information:
Exception type: MapiExceptionIllegalCrossServerConnection
Exception message: MapiExceptionIllegalCrossServerConnection: Monitoring mailbox [] with application ID [Client=OWA] is not allowed to make cross-server calls from [SRVEXC02.company.loc] to [SRVEXC01.company.loc] at Microsoft.Mapi.CrossServerDiagnostics.BlockCrossServerCall(ExRpcConnectionInfo connectionInfo, String mailboxDescription)

Let’s go again to delete and recreate the Ecp virtualdiretory on both servers … exchange 2013 SP1 a finished product?

Trying to reopen the case on Microsoft Support but no answer since last week. .. grrr….

Action on the second server

remove-ecpvirtualdirectory -identity « SRVEXC02\ecp (Default Web Site) »
iisreset
new-ecpvirtualdirectory -websitename « Default Web Site »
set-ecpvirtualdirectory -identity « SRVEXC02\ecp (Default Web Site) » -internalurl « https://srvexc02.company.loc/ecp » -externalurl $null

Action on the first server

remove-ecpvirtualdirectory -identity « SRVEXC01\ecp (Default Web Site) »
iisreset
new-ecpvirtualdirectory -websitename « Default Web Site » -server srvexc01
set-ecpvirtualdirectory -identity « SRVEXC01\ecp (Default Web Site) » -internalurl « https://srvexc01.company.loc/ecp » -externalurl $null

And now when you try to log on Srvexc01 you’ve got this! We made some progress no?


Whaou in the second server srvexc02….

I ve got this now; Not real progress. Let’s reboot all these Exchange servers…


Let’s try after reboot…

After the reboot the server srvec02 is well presenting the page but no possibility to log on. Server error in /Ecp is no more present. (in the doubt .. reboot still works )

Reboot the first one./ Same issue enable to log on to ECP/ owa works not ecp . And stil have the fuc…. ASP.NET 4.0.30319.0 unhandled exception!

Let try now to set the FBA authentication on Ecp just in case of…. The Fba is activated by default on ECP … weird. I just compared the Authentication option on OWA and ECP on both servers.. they are the same.

After performing a Get-serverhealth

I can see that as a result but I will not give me more information except the fact that ECP is not working!

RunspaceId : bbc64357-cfb9-42cb-89ab-f6f3138a0674
Server : srvexc01
CurrentHealthSetState : NotApplicable
Name : EacCtpMonitor
TargetResource :
HealthSetName : ECP
HealthGroupName : CustomerTouchPoints
AlertValue : Unhealthy
FirstAlertObservedTime : 4/22/2014 12:01:54 PM
Description : µ
IsHaImpacting : False
RecurranceInterval : 720
DefinitionCreatedTime : 4/22/2014 11:28:11 AM
HealthSetDescription :
ServerComponentName : None
LastTransitionTime : 4/22/2014 11:25:41 AM
LastExecutionTime : 4/22/2014 12:01:54 PM
LastExecutionResult : Succeeded
ResultId : 12375674
WorkItemId : 44
IsStale : False
Error :
Exception :
IsNotified : False
LastFailedProbeId : 379
LastFailedProbeResultId : 7015930
ServicePriority : 2
Identity : ECP\EacCtpMonitor\
IsValid : True
ObjectState : New

I will try to remove the second ecp website using for Basic authentication needed for Kemp

After looking on the website. I saw that on the default website the Ip Addresse has been fixed. I decided to put to set the value like this


After retrying a connection the ECP website invite me to login with basic authentication. And I can access to the ECP Website!.
I decided to put the form authentication on the ecp virtualdirectory and retry.

PS] C:\Windows\system32>Get-EcpVirtualDirectory -Identity « SRVEXC02\ecp (Default Web Site) » | Set-EcpVirtualDirectory FormsAuthentication $true

Running IISRESET after that and ….

It works !!

Regards

Laurent

 

 

 

 

 

 

 

 

 

 

 

Laisser un commentaire