mhdcommunications
asked on
Cannot get Exchange 2007 OWA working - "Service Unavailable" after installing Symantec Endpoint Protection 11.0.4014.26 + SMSFME
Server 2003 Std. x64 w/ SP2 - Single Server Environment (DC, DNS, DHCP, E-mail, File Server, etc.)
Everything worked prior to installing SEP. I have tried everything to get OWA to work, but continue to get "Service unavailable".
I have tried:
Reinstalling IIS (numerous times)
Followed - http://support.microsoft.com/kb/894435 and any other post regarding this method.
Followed other EE posts with the same issue, to no avail.
Symantec is offering no support since this is not a problem with THEIR product. Although the installation of their product has damaged my system, they are assuming no responsibility.
Most (80-90%) of my users use OWA, so i need this up NOW. I will remove SEP + SMSFME is needed, but i dont think this will fix the issue.
Below are the events from the App log after trying to get to the OWA page:
Event Type: Error
Event Source: W3SVC-WP
Event Category: None
Event ID: 2214
Date: 5/21/2009
Time: 10:36:42 AM
User: N/A
Computer: FLC-EHX
Description:
The HTTP Filter DLL C:\WINDOWS\System32\RpcPro
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7e 00 00 00 ~...
Event Type: Error
Event Source: W3SVC-WP
Event Category: None
Event ID: 2268
Date: 5/21/2009
Time: 10:36:43 AM
User: N/A
Computer: FLC-EHX
Description:
Could not load all ISAPI filters for site/service. Therefore startup aborted.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7e 00 00 00 ~...
Event Type: Error
Event Source: MSExchange RPC Over HTTP Autoconfig
Event Category: General
Event ID: 2002
Date: 5/21/2009
Time: 10:47:05 AM
User: N/A
Computer: FLC-EHX
Description:
An unexpected failure has occurred. The problem will require administrator intervention. The service will retry the operation in 15 minutes. Diagnostic information:
at Microsoft.Exchange.Managem
at Microsoft.Exchange.Managem
at Microsoft.Exchange.Managem
at Microsoft.Exchange.Service
at Microsoft.Exchange.Service
An error occurred while trying to access IIS (Internet Information Service) metabase. Make sure the Internet Information Service Manager component is installed and configured properly.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
__________________________
Below are the events from the System log after attempting to open OWA:
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1039
Date: 5/21/2009
Time: 9:34:25 AM
User: N/A
Computer: FLC-EHX
Description:
A process serving application pool 'MSExchangeOWAAppPool' reported a failure. The process id was '7268'. The data field contains the error number.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7e 00 07 80 ~..€
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1039
Date: 5/21/2009
Time: 9:46:26 AM
User: N/A
Computer: FLC-EHX
Description:
A process serving application pool 'MSExchangeAutodiscoverApp
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7e 00 07 80 ~..€
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1002
Date: 5/21/2009
Time: 9:46:27 AM
User: N/A
Computer: FLC-EHX
Description:
Application pool 'MSExchangeAutodiscoverApp
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1002
Date: 5/21/2009
Time: 9:46:27 AM
User: N/A
Computer: FLC-EHX
Description:
Application pool 'MSExchangeAutodiscoverApp
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
__________________________
Thanks in advance.
Everything worked prior to installing SEP. I have tried everything to get OWA to work, but continue to get "Service unavailable".
I have tried:
Reinstalling IIS (numerous times)
Followed - http://support.microsoft.com/kb/894435 and any other post regarding this method.
Followed other EE posts with the same issue, to no avail.
Symantec is offering no support since this is not a problem with THEIR product. Although the installation of their product has damaged my system, they are assuming no responsibility.
Most (80-90%) of my users use OWA, so i need this up NOW. I will remove SEP + SMSFME is needed, but i dont think this will fix the issue.
Below are the events from the App log after trying to get to the OWA page:
Event Type: Error
Event Source: W3SVC-WP
Event Category: None
Event ID: 2214
Date: 5/21/2009
Time: 10:36:42 AM
User: N/A
Computer: FLC-EHX
Description:
The HTTP Filter DLL C:\WINDOWS\System32\RpcPro
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7e 00 00 00 ~...
Event Type: Error
Event Source: W3SVC-WP
Event Category: None
Event ID: 2268
Date: 5/21/2009
Time: 10:36:43 AM
User: N/A
Computer: FLC-EHX
Description:
Could not load all ISAPI filters for site/service. Therefore startup aborted.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7e 00 00 00 ~...
Event Type: Error
Event Source: MSExchange RPC Over HTTP Autoconfig
Event Category: General
Event ID: 2002
Date: 5/21/2009
Time: 10:47:05 AM
User: N/A
Computer: FLC-EHX
Description:
An unexpected failure has occurred. The problem will require administrator intervention. The service will retry the operation in 15 minutes. Diagnostic information:
at Microsoft.Exchange.Managem
at Microsoft.Exchange.Managem
at Microsoft.Exchange.Managem
at Microsoft.Exchange.Service
at Microsoft.Exchange.Service
An error occurred while trying to access IIS (Internet Information Service) metabase. Make sure the Internet Information Service Manager component is installed and configured properly.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
__________________________
Below are the events from the System log after attempting to open OWA:
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1039
Date: 5/21/2009
Time: 9:34:25 AM
User: N/A
Computer: FLC-EHX
Description:
A process serving application pool 'MSExchangeOWAAppPool' reported a failure. The process id was '7268'. The data field contains the error number.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7e 00 07 80 ~..€
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1039
Date: 5/21/2009
Time: 9:46:26 AM
User: N/A
Computer: FLC-EHX
Description:
A process serving application pool 'MSExchangeAutodiscoverApp
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7e 00 07 80 ~..€
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1002
Date: 5/21/2009
Time: 9:46:27 AM
User: N/A
Computer: FLC-EHX
Description:
Application pool 'MSExchangeAutodiscoverApp
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Error
Event Source: W3SVC
Event Category: None
Event ID: 1002
Date: 5/21/2009
Time: 9:46:27 AM
User: N/A
Computer: FLC-EHX
Description:
Application pool 'MSExchangeAutodiscoverApp
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
__________________________
Thanks in advance.
Rajith Enchiparambil
Try taking Symantec off. That software gives a hell lot of issues with exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Raghuv-
I did that already, and it did nothing.
Rajith_Enchiparambil-
This wasn't an option since it's a single server environment, and there are no other servers to put it on. I have Deployed SEP SMB Ed. on four (4) other networks, ALL on the Exchange server (Exchange 2003) and everything was seamless, and had no problems. This is the first Exchange 2007 server (and 64-bit OS) i have deployed this product to, and it has done nothing but cause problems.
I actually just had to remove the SMSFME because it was conflicting with Exchange, and puting ALL e-mail (internal->internal, internal->external,externa
I have a feeling SEP SMB Ed. is not compatible with a 64-bit OS and/or Exchange 2007. Just as a note to anyone looking at this post, i had to call Symantec because i could not install the software originally (SEPM would get to "Configuring IIS..." then would roll back and fail, and SMSFME would fail immediately with some sort of ASP.net error). They fixed it by having me re-install IIS.
I will be getting Symantec on the phone tomorrow, and will post their response/fix.
I did that already, and it did nothing.
Rajith_Enchiparambil-
This wasn't an option since it's a single server environment, and there are no other servers to put it on. I have Deployed SEP SMB Ed. on four (4) other networks, ALL on the Exchange server (Exchange 2003) and everything was seamless, and had no problems. This is the first Exchange 2007 server (and 64-bit OS) i have deployed this product to, and it has done nothing but cause problems.
I actually just had to remove the SMSFME because it was conflicting with Exchange, and puting ALL e-mail (internal->internal, internal->external,externa
I have a feeling SEP SMB Ed. is not compatible with a 64-bit OS and/or Exchange 2007. Just as a note to anyone looking at this post, i had to call Symantec because i could not install the software originally (SEPM would get to "Configuring IIS..." then would roll back and fail, and SMSFME would fail immediately with some sort of ASP.net error). They fixed it by having me re-install IIS.
I will be getting Symantec on the phone tomorrow, and will post their response/fix.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Tons of people are apparently having problems with my specific setup:
Server 2003 64-bit w/ Exchange 2007
The problem is with IIS. After installing SEPM 11, it screwed up (i mean TOTAL HOSED) IIS, and all associated permissions, which is why i was having problems. Symantec told me it was out of their hands, and i needed to call MS to get IIS working properly. Tried returning the software since they sold me an 'incompatible' product that their 'software advisors' said would work, but once the product is registered (which must be done prior to install) it cannot be returned. Lesson learned.
Anyone running Exchange 2007 (or a 64-bit OS) install SEP on a seperate server. In my case, it's a single server environment, so it's not an option. Case closed.
I would, and still recommend SEP for anyone that wants a cheap, effective Business AV, just be cautios about what server you install it on. Or, if you have an extra XP Pro PC, you can turn it into the SEP server (since you can install IIS).
Thank you all for your help, but this problem will not be resolved, because i refuse to call MS due to Symantec's ignorance.
Server 2003 64-bit w/ Exchange 2007
The problem is with IIS. After installing SEPM 11, it screwed up (i mean TOTAL HOSED) IIS, and all associated permissions, which is why i was having problems. Symantec told me it was out of their hands, and i needed to call MS to get IIS working properly. Tried returning the software since they sold me an 'incompatible' product that their 'software advisors' said would work, but once the product is registered (which must be done prior to install) it cannot be returned. Lesson learned.
Anyone running Exchange 2007 (or a 64-bit OS) install SEP on a seperate server. In my case, it's a single server environment, so it's not an option. Case closed.
I would, and still recommend SEP for anyone that wants a cheap, effective Business AV, just be cautios about what server you install it on. Or, if you have an extra XP Pro PC, you can turn it into the SEP server (since you can install IIS).
Thank you all for your help, but this problem will not be resolved, because i refuse to call MS due to Symantec's ignorance.
ASKER
I would agree with Rajith - incompatible. You would figure a Small Business product would work on a Small Business Server OS.... figures.
We have Symantec Endpoint Protection installed on Exchange 2003 and 2007 servers. Policies have to be in place and assigned to servers different than your regular computers. You DO NOT install the Firewall module on this (that is the Network Threat Protection) if you did, then you shoot yourself on the foot.
Proactive Threat Protection and Network Threat Protection are to be left alone. By default, SEP knows if a system is a server and it you hvae SQL, Exchange, IIS, it will create its own rules to avoid issues with these apps, but if you installed the Firewall and application and device control, then you are on your own doing specific policies that, one way or another, might interfere with the native rules.
Have not had any problems with any systems with over 300 servers.
Proactive Threat Protection and Network Threat Protection are to be left alone. By default, SEP knows if a system is a server and it you hvae SQL, Exchange, IIS, it will create its own rules to avoid issues with these apps, but if you installed the Firewall and application and device control, then you are on your own doing specific policies that, one way or another, might interfere with the native rules.
Have not had any problems with any systems with over 300 servers.