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\RpcProxy\RpcProxy.dll failed to load.  The data is the error.

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.Management.Metabase.IisUtility.CreateIISDirectoryEntry(String iisDirectoryEntryPath, TaskErrorLoggingDelegate writeError, Object identity)
   at Microsoft.Exchange.Management.Metabase.IisUtility.FindWebObject(String parent, String name, String type)
   at Microsoft.Exchange.Management.Metabase.IisUtility.FindWebDirObject(String parent, String name)
   at Microsoft.Exchange.Servicelets.RPCHTTP.Servicelet.FindIISVDir()
   at Microsoft.Exchange.Servicelets.RPCHTTP.Servicelet.Work()
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 'MSExchangeAutodiscoverAppPool' reported a failure. The process id was '7908'.  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:      1002
Date:            5/21/2009
Time:            9:46:27 AM
User:            N/A
Computer:      FLC-EHX
Description:
Application pool 'MSExchangeAutodiscoverAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

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 'MSExchangeAutodiscoverAppPool' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
_____________________________________________________________________________




Thanks in advance.
LVL 1
mhdcommunicationsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
Try taking Symantec off. That software gives a hell lot of issues with exchange.
0
RaghuvCommented:
Hi,

Service Unavailable normally occurs due to failure of the Application pool. I also see events related with the application pool crashing (Event ID 1002).

And the App pool can crash due to many reasons,

- Check the ISAPI filter (IIS Manager -> Right click on Websites -> Check the ISAPI filter tab) and check if there's any filter marked in red.

- Check the ISAPI filter (IIS Manager -> Expand Websites -> Right click on Default web sites -> Check the ISAPI filter tab) and check if there's any filter marked in red.

You can also try converting ASP to 64bit and then re-installing ASP by running the below commands,

1) Open a command prompt and type -> cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0

2) Once the above command has ran sucessfully, run the below command,

%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i

3) Make sure that the status of ASP.NET version 2.0.50727 is set to Allowed in the Web service extension list in IIS Manager.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mhdcommunicationsAuthor Commented:
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,external->internal) in the Poison Message queue. After removing SMSFME e-mail started flowing as normal, with no other changes needed. *It was NOT a configuration problem within SMSFME*


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.

0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
I would suspect that the product is not compatible with Exchange 2007. I am not at all a fan of Symantec on an exchange box anyway. Troublesome!
0
mhdcommunicationsAuthor Commented:
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.
0
mhdcommunicationsAuthor Commented:
I would agree with Rajith - incompatible. You would figure a Small Business product would work on a Small Business Server OS.... figures.
0
itsecalertCommented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft IIS Web Server

From novice to tech pro — start learning today.