Solved

OWA website is down after i rebooted server.  How to bring back up and running?

Posted on 2008-10-04
15
288 Views
Last Modified: 2011-10-19
I rebooted our exchange server and after it restarted the OWA site is down. In the exhange server are blackberry BES, our owa hosting server (virtually) .   I am not familiar with Exchange Shell (codes), but how do i get the OWA site running again.  Please help me.  
0
Comment
Question by:dhidalgo
  • 8
  • 7
15 Comments
 
LVL 15

Expert Comment

by:tntmax
ID: 22642347
Is IIS admin running? Web services? OWA will not work without WWW services running. Any errors in the event log?
0
 

Author Comment

by:dhidalgo
ID: 22642356
how do i determine those if they are running? what are the shell codes?
0
 
LVL 15

Expert Comment

by:tntmax
ID: 22642369
start -> run -> services.msc

Look for IIS Admin and World Wide Web Publishing services. They should be set to automatic and started. IIS Admin is needed to administer the website through the IIS MMC, and WWW is required to actually run the page.

Alternatively, you can look for w3wp.exe in the task manager (processes tab).

If they are not running, try starting them from the services console, otherwise check the event viewer to find out why it is not running.
0
Flexible connectivity for any environment

The KE6900 series can extend and deploy computers with high definition displays across multiple stations in a variety of applications that suit any environment. Expand computer use to stations across multiple rooms with dynamic access.

 

Author Comment

by:dhidalgo
ID: 22642398
Under services, ISS admin and WWWpublishing services are running and on auto.

the w3wp.exe in task manager under processes was not found... would that be the problem?
0
 
LVL 15

Expert Comment

by:tntmax
ID: 22642407
Can you go into IIS Admin and see if the default website is running? You can also start and stop the website within IIS, so even if WWW running, you can still stop the website. Once again, any error codes in the event logs?
0
 

Author Comment

by:dhidalgo
ID: 22642435
Microsoft Exchange couldn't find a certificate that contains the domain name ls-ex1.lifestream.local in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Internet Send Connector with a FQDN parameter of ls-ex1.lifestream.local. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.

the certificate that was installed yesterday was for mail.lifestream.com
0
 

Author Comment

by:dhidalgo
ID: 22642442
here is a clip of the error.  
a certificate was issued for mail.lifestream.com website for OWA
error-log.bmp
0
 
LVL 15

Expert Comment

by:tntmax
ID: 22642453
What are the transport warnings? Any errors or warnings in System?

How did you install the cert? What kind of cert? Did you do a single domain cert, or one of the new special multi-domain certs? With Exchange 2007, you need to have a cert that will sign for at least 5 domains, including external and internal names for the server.
0
 
LVL 15

Expert Comment

by:tntmax
ID: 22642461
0
 
LVL 15

Accepted Solution

by:
tntmax earned 500 total points
ID: 22642468
finally, this site was most helpful to me to understand Exchange 2007 certs:

http://msexchangeteam.com/archive/2007/02/19/435472.aspx
0
 

Author Comment

by:dhidalgo
ID: 22642472
it was set up yesterday; and everything was running smoothly until I restarted the server today.  Why do you think restartig the server would initiate something or the owa to not run again.
0
 
LVL 15

Expert Comment

by:tntmax
ID: 22642477
Not sure, I don't know your environment, that's why I'm asking questions :-)
0
 

Author Comment

by:dhidalgo
ID: 22642485
this is the trasport warning:  Microsoft Exchange couldn't find a certificate that contains the domain name ls-ex1.lifestream.local in the personal store on the local computer. Therefore, it is unable to support the STARTTLS SMTP verb for the connector Default LS-EX1 with a FQDN parameter of ls-ex1.lifestream.local. If the connector's FQDN is not specified, the computer's FQDN is used. Verify the connector configuration and the installed certificates to make sure that there is a certificate with a domain name for that FQDN. If this certificate exists, run Enable-ExchangeCertificate -Services SMTP to make sure that the Microsoft Exchange Transport service has access to the certificate key.

An internal transport certificate expired. Thumbprint:664B36....
0
 

Author Comment

by:dhidalgo
ID: 22642496
so it is still refering to the expired certificate.  

Csr was generated on exchange server (the cert was for a domain 2yrs for mail.lifestream.com).  was then imported and enabled.  installed to root and intermediate...

before i left yesterday; everything worked.
0
 
LVL 15

Expert Comment

by:tntmax
ID: 22642507
Once again, how did you install your cert? How did you generate it? Did you read the links that I gave you, and did you follow those instructions? The msexchangeteam article has the commands that you need to run to get this working, so there's no need to type it again.
0

Featured Post

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When converting a physical machine to a virtual machine using VMware vCenter Converter Standalone or vCenter Converter Enterprise, if an adapter type is not selected during the initial customization the resulting virtual machine may contain an IDE d…
This article outlines why you need to choose a backup solution that protects your entire environment – including your VMware ESXi and Microsoft Hyper-V virtualization hosts – not just your virtual machines.
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:
Teach the user how to use vSphere Update Manager to update the VMware Tools and virtual machine hardware version Open vSphere Client: Review manual processes for updating VMware Tools and virtual hardware versions: Create a new baseline group in vSp…

749 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question