Solved

Problems installing Filemaker Server 12 with instant web publishing component on Windows SBS 2008 - OWA broken

Posted on 2014-10-20
8
244 Views
Last Modified: 2014-12-01
Hello
I broke OWA of my SBS 2008 server when I setup Filemaker Server 12 with instant web publishing component.
I uninstalled Filemaker Server, but it didn't restore the OWA on SBS.
When accessing https://127.0.0.1/owa/ the error is :
Erreur HTTP 500.19 - Internal Server Error
Here is a screenshot :
Screenshot of errorCould you help me to restore OWA functionnality back
I will install Filemaker Server Web Publishing component on another server
Tanks for help
0
Comment
Question by:mdmmp
  • 3
  • 3
  • 2
8 Comments
 
LVL 24

Expert Comment

by:Will Loving
ID: 40393005
I don't know about how to reestablish OWA other than by performing a re-install, but I do know that FileMaker Server has never been qualified for running on SBS and there are known issues - which is appears you may have run into - especially with Web Publishing. Bottom line, don't install FMS Server on SBS or upgrade to a full version of Windows Server.
0
 
LVL 6

Expert Comment

by:slinkygn
ID: 40401160
As a rule, Will's right: SBS is officially not a supported platform for FM Server.  In particular, installing FM Server Web Publishing on an SBS machine will clobber a lot of SBS's web services (as you've learned); unofficially speaking, I know of a few people running FM Server on SBS 2008 without Web Publishing who say it works okay -- but of course, you're well into "your mileage may vary" mode!

If you've already tried uninstalling FM Server from your SBS machine, you probably have also found that that doesn't actually fix your problem -- FM Server doesn't know how to roll back properly from an SBS machine, and often won't properly fix what it broke when removed.

My most likely guess for what specifically broke is that installing FMS threw FMS's self-signed HTTPS certificate onto your Default Site in IIS, which breaks OWA's HTTPS functionality.  If that's the case, swapping to the right certificate is covered in this link:
http://oliverslay.blogspot.com/2010/05/exchange-2007-sp2-on-sbs-2008-owa-not.html
Basically you're removing HTTPS (port 443) access from FM and giving it back to OWA.  Naturally, this will break Web Publishing access in FM -- you'll only be able to use one or the other without some serious messing around -- so make sure you've uninstalled Web Publishing *first*.

The other possibility I can think of is that you clobbered some of your OWA virtual directories in the install; http://www.techexams.net/forums/exchange-server-office-communications-server-exams/50190-rebuild-owa-virtual-directories-sbs2008.html covers how to restore those.

Beyond that, your only hope is to see if SBS can heal itself.  (May want to try this first, I suppose.)  In SBS 2008, you have a Fix My Network Wizard that can fix a number of issues, including a few with OWA.  http://technet.microsoft.com/en-us/library/cc546095(v=ws.10).aspx will get you there.

Hope one of these helps!  Let us know how it goes.
0
 

Author Comment

by:mdmmp
ID: 40412649
Hello tanks you for your answer
I had Filemaker Server running on sbs without web publishing very well.
But with the update, I check web publishing component by mistake and it broke my OWA.
I tried the cetificate
I also tried to remove OWA virtual directories and reinstal it by CLI interface on exchange 2007.
Finally I run the fix my network wizard, but problem is still there.
Actually I'm looking on how to reinstall the web access component without braking mailbox access in Outlook client.
0
 
LVL 6

Expert Comment

by:slinkygn
ID: 40412661
What we're trying to say is:  That basically isn't possible.  That's why SBS is not a supported platform for FileMaker Server.
0
What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

 

Accepted Solution

by:
mdmmp earned 0 total points
ID: 40468512
Tanks for your answers, I close the subject because I have no solution for this problem
0
 
LVL 24

Expert Comment

by:Will Loving
ID: 40468521
There is a solution that will most likely fix your problem but it's not what you're hoping for:

You need to get rid of the SBS version and and install/upgrade to a version of Windows Professional or Windows Server that FileMaker Server is officially qualified for. These include:

Windows 7 Professional Edition SP1 * (32-bit)
Windows Server 2008 Standard Edition SP2 * (32-bit)
Windows Server 2008 R2 SP1 * (64-bit)
Windows 7 Professional Edition SP1 * (64-bit)
Windows Server 2008 Standard Edition SP2 * (64-bit)
Windows Server 2003 R2 SP2 * (32 Bit)

See: http://help.filemaker.com/app/answers/detail/a_id/10072/
0
 
LVL 6

Expert Comment

by:slinkygn
ID: 40472966
Will's right that your "solution" is to switch OS's.  Of course, that will still not allow you to run OWA on the same server.

Your fundamental question is that you want SBS (and OWA) to run on the same server with FMS Web Publishing.  While we've given some workarounds, the fundamental answer is, "you can't do that."  For information on how to proceed when that is the answer, please see:
http://support.experts-exchange.com/customer/portal/articles/755964
0
 

Author Closing Comment

by:mdmmp
ID: 40473338
no solution
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
Scam emails are a huge burden for many businesses. Spotting one is not always easy. Follow our tips to identify if an email you receive is a scam.
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
how to add IIS SMTP to handle application/Scanner relays into office 365.

706 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

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now