MarkusMuellerit
asked on
Exchange 2010 OWA not loading
I have installed a new Exchange 2010 server into a exchange 2003 environment. The install went without issue and everything else seams to work great. The only problem I have is my CAS\HUB server wont load OWA. The domain does have the same external and internal dns space.
ECP and EWS also wont load
It loads nothing at all when I launch https:\localhost\owa
It loads a server error when I launch https:\localhost\exchange
SEE THE ERROR BELOW
from a remote computer it loads when trying owa
https://excas1.domain.domain.com/owa/auth/logon.aspx?
if i try the ip i get the same error
https://172.22.6.135/owa/auth/error.aspx?aspxerrorpath=/owa/
url=https://domain.domain.com/owa/&reason=0
from a remote computer it loads the same error as from the localhost when trying \exchange
I have removed and reset OWA via the ems
Remove-OwaVirtualDirectory
New-OwaVirtualDirectory -owa (default Web site)
when i run Test-OwaConnectivity
WARNING: [01:27:36.269] : The server returned the language selection page. This is the first logon for the test user.
WARNING: [01:28:06.362] : The test timed out while attempting to connect to the external URL for this virtual
directory.
WARNING: [01:28:06.377] : Test failed for URL 'https://excas1.sheriff.pima.gov/owa/'.
ERROR
https://localhost/owa/auth/error.aspx?aspxerrorpath=/owa/
Server Error in '/' Application.
--------------------------
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustomp
</system.web>
</configuration>
ECP and EWS also wont load
It loads nothing at all when I launch https:\localhost\owa
It loads a server error when I launch https:\localhost\exchange
SEE THE ERROR BELOW
from a remote computer it loads when trying owa
https://excas1.domain.domain.com/owa/auth/logon.aspx?
if i try the ip i get the same error
https://172.22.6.135/owa/auth/error.aspx?aspxerrorpath=/owa/
url=https://domain.domain.com/owa/&reason=0
from a remote computer it loads the same error as from the localhost when trying \exchange
I have removed and reset OWA via the ems
Remove-OwaVirtualDirectory
New-OwaVirtualDirectory -owa (default Web site)
when i run Test-OwaConnectivity
WARNING: [01:27:36.269] : The server returned the language selection page. This is the first logon for the test user.
WARNING: [01:28:06.362] : The test timed out while attempting to connect to the external URL for this virtual
directory.
WARNING: [01:28:06.377] : Test failed for URL 'https://excas1.sheriff.pima.gov/owa/'.
ERROR
https://localhost/owa/auth/error.aspx?aspxerrorpath=/owa/
Server Error in '/' Application.
--------------------------
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustomp
</system.web>
</configuration>
Rick Hobbs
"The domain does have the same external and internal dns space." Please explain what you mean and why you would want it that way.
ASKER
The internal domain has the same name as the external name for the exchange. for example the internet domain is ABCcorp.com and the domain on the inside is ABCcorp.com.
Do you have any kind off redirection set, I will recommend it to remove all redirection and check if OWA works, also u can run updatecas.sp1
<Drive Letter>:\Program Files\Microsoft\Exchange Server\V14\Bin\UpdateCas.p
Hope this helps!!
<Drive Letter>:\Program Files\Microsoft\Exchange Server\V14\Bin\UpdateCas.p
Hope this helps!!
What was the last modification\update on this CAS server?
Can you check if the server\update installation completed successfully? without any big issues?
Can you check if the server\update installation completed successfully? without any big issues?
ASKER
E_aravind
This is a fresh install. I didn't see any major errors.
saakar_rao:
I will run the update. I dont have any redirects in place other then the default ones.
This is a fresh install. I didn't see any major errors.
saakar_rao:
I will run the update. I dont have any redirects in place other then the default ones.
how about the basic htm, gif files out of this iis?
Are they working fine?
<%=now%>
>can you save the above file as time.asp and time.aspx on the c:\inetpub\wwwroot and then try to access these files from Browser using
https:\\servername\time.asp and https:\\servername\time.aspx??
> Did you tried using the administrator and other users logon?
Tried @ different machines? Different versions of Browsers?
Are they working fine?
<%=now%>
>can you save the above file as time.asp and time.aspx on the c:\inetpub\wwwroot and then try to access these files from Browser using
https:\\servername\time.asp and https:\\servername\time.aspx??
> Did you tried using the administrator and other users logon?
Tried @ different machines? Different versions of Browsers?
ASKER
saakar_rao:
I ran the updatecas.ps1 without any luck
I still get no page and get redirected to the following URL
https://localhost/owa/auth/logon.aspx?url=https://localhost/owa/&reason=0
I ran the updatecas.ps1 without any luck
I still get no page and get redirected to the following URL
https://localhost/owa/auth/logon.aspx?url=https://localhost/owa/&reason=0
ASKER
e_aravind:
I tried mulitple browsers and I dont get to a login page.
I will try to test IIS in a bit.
I tried mulitple browsers and I dont get to a login page.
I will try to test IIS in a bit.
what is the response,
When you try accessing the OWA usign the Internal-URL and External-URL rather than just the Localhost and IP-addresses?
Can you access the .asp and .aspx pages......or the browser is getting taken-up to any redirection URLs?
When you try accessing the OWA usign the Internal-URL and External-URL rather than just the Localhost and IP-addresses?
Can you access the .asp and .aspx pages......or the browser is getting taken-up to any redirection URLs?
can u try to recreate OWA Virtual Directory? also if u can share the user account that you are testing with along the IIS logs
ASKER
I ended up reloading the bringing up a new cas\hub server.
Sorry I had tried just about everything. It must have just been a bad install. Verything is now working. I did have to go in and create new connectors and redo some other stuff.
I removed the old CAS from the exchange 2010 and then the domain.
The only issue that I have now is that there are a few user that I had moved for testing and they point to the old cas server. I cant get them to connect to the new cas server. I even blow the outlook profile away and start fresh.
Any help would be appreciated.
Sorry I had tried just about everything. It must have just been a bad install. Verything is now working. I did have to go in and create new connectors and redo some other stuff.
I removed the old CAS from the exchange 2010 and then the domain.
The only issue that I have now is that there are a few user that I had moved for testing and they point to the old cas server. I cant get them to connect to the new cas server. I even blow the outlook profile away and start fresh.
Any help would be appreciated.
few user that I had moved for testing and they point to the old cas server. I cant get them to connect to the new cas server
>> how are you checking them?
So after moving these mailbox from E2k3 to the new E2010 servers...Outlook is not connecting correct?
What is the version of Outlook involved?
Did we configured the rpcclientaccess server value on the exchange databases correctly?
>> how are you checking them?
So after moving these mailbox from E2k3 to the new E2010 servers...Outlook is not connecting correct?
What is the version of Outlook involved?
Did we configured the rpcclientaccess server value on the exchange databases correctly?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
please award point to e_aravind:
ASKER
THIS IS NOT THE SOLUTION FOR THE ORIGINAL PROBLEM
I am writing this post because it gave me the idea to solve a similar problem:
problem:
When I try to access via browser on my Exchange server 2010 SP1 Rollup Update 4 (just installed) I get the following error message: https://localhost/owa/auth/error.aspx?aspxerrorpath=/owa/
solution:
Some components were missing in the installation of the IIS server. Try to install all (Excluding WEBDAV and FTP Server)
Thank you all !!!!!!!
problem:
When I try to access via browser on my Exchange server 2010 SP1 Rollup Update 4 (just installed) I get the following error message: https://localhost/owa/auth/error.aspx?aspxerrorpath=/owa/
solution:
Some components were missing in the installation of the IIS server. Try to install all (Excluding WEBDAV and FTP Server)
Thank you all !!!!!!!
problem:
As title, on a Microsoft Exchange Server 2010 SP1 fresh install, when I try to open the web interface (OWA) from the server that I have this error:
"Https://localhost/owa/auth/logon.aspx?url=https://localhost/owa/&reason=0"
solution:
After Ravana on the internet for days and days reading and testing countless "false" solutions, I started to compare the server running an indicted for 1 year and a half point by point. And here I am doing the "macraba" discovered that during the installation of the role "IIS Server" (contemporary to the Exchange) has not been successfully installed all components of the IIS server itself. Then proceed with the addition of "Role Services" missing (as a precaution I installed all except: WebDAV Publishing, Recording Custom, ODBC logging, FTP server and HWC) and magically everything works without even a reboot.
As title, on a Microsoft Exchange Server 2010 SP1 fresh install, when I try to open the web interface (OWA) from the server that I have this error:
"Https://localhost/owa/auth/logon.aspx?url=https://localhost/owa/&reason=0"
solution:
After Ravana on the internet for days and days reading and testing countless "false" solutions, I started to compare the server running an indicted for 1 year and a half point by point. And here I am doing the "macraba" discovered that during the installation of the role "IIS Server" (contemporary to the Exchange) has not been successfully installed all components of the IIS server itself. Then proceed with the addition of "Role Services" missing (as a precaution I installed all except: WebDAV Publishing, Recording Custom, ODBC logging, FTP server and HWC) and magically everything works without even a reboot.