5 Replies Latest reply on Mar 11, 2009 9:37 PM by smower

    FMSA10 FileMaker Server Advanced 10 and SBS (Small Business Server) 2008 - HTTP Error 503



      FMSA10 FileMaker Server Advanced 10 and SBS (Small Business Server) 2008 - HTTP Error 503

      Your post



      Has anyone got FileMaker Server Advanced 10 with Web Publishing to work on an Small Business Server 2008 64 Bit?  We can get the databases to publish and be viewed by FMP, but when we try to view instant web publishing, PHP or XML/XSLT we just get http 503 errors even though ISAPI filters and ISAPI extensions are turned on and application pooling compatability is enabled for 32 bit.


      Thanks in advance for any assistance.

        • 1. Re: FMSA10 FileMaker Server Advanced 10 and SBS (Small Business Server) 2008 - HTTP Error 503

          Hi smower,

          Thanks for posting.


          Is Sharepoint installed?  If so, Sharepoint uses resources that the Web Publishing Engine uses which can create conflicts.  You will need to uninstall FMS/reboot/un-install Sharepoint/reboot/reinstall FMS.


          Also as a note, FMS should be installed if possible on a W2k8 32 bit as this is the tested and certified OS.


          Hope this helps.



          FileMaker, Inc. 

          • 2. Re: FMSA10 FileMaker Server Advanced 10 and SBS (Small Business Server) 2008 - HTTP Error 503

            Thank you for responding tsturtle.


            Sharepoint is apparently installed by default on the SBS 2008 Server.  I can't seem to figure out how to uninstall it.  Do you have any instructions that show how to remove it from the SBS 2008 server?




            • 3. Re: FMSA10 FileMaker Server Advanced 10 and SBS (Small Business Server) 2008 - HTTP Error 503

              Hey smower,


              For the most accurate steps for uninstalling, I would suggest visiting Microsoft's website.  It may also be beneficial to do a search on the web; I did a quick 'how do i uninstall sharepoint' search on the web and found some good hits. 


              Hope this helps!


              FileMaker, inc. 

              • 4. Re: FMSA10 FileMaker Server Advanced 10 and SBS (Small Business Server) 2008 - HTTP Error 503
                Thanks, we uninstalled sharepoint, rebooted, uninstalled FMSA 10, rebooted, set default app pool to 32 bit and it failer the web server connect test - we changed back to 64 bit and it passed the web server test, and then we changed back to 32 bit and ran the tests and we are now getting this error on web publishing:
                Server Error in Application "DEFAULT WEB SITE"

                Internet Information Services 7.0

                Error Summary HTTP Error 500.0 - Internal Server Error Calling LoadLibraryEx on ISAPI filter "C:\Program Files (x86)\FileMaker\FileMaker Server\Web Publishing\publishing-engine\web-server-support\iis\isapi_redirect.dll" failed
                Detailed Error Information
                Module IIS Web Core Notification Unknown Handler StaticFile Error Code 0x800700c1
                Requested URL http://cepserver.cep08.local:80/fmi/iwp/cgi?-db=FMServer_Sample&-startsession Physical Path C:\inetpub\wwwroot\fmi\iwp\cgi Logon Method Not yet determined Logon User Not yet determined
                Most likely causes:
                • IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred.
                • IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly.
                • IIS was not able to process configuration for the Web site or application.
                • The authenticated user does not have permission to use this DLL.
                • The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.
                Things you can try:
                • Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account.
                • Check the event logs to see if any additional information was logged.
                • Verify the permissions for the DLL.
                • Install the .NET Extensibility feature if the request is mapped to a managed handler.
                • Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.
                Links and More InformationThis error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.

                View more information »

                Microsoft Knowledge Base Articles:

                • 294807

                From: FileMaker Customer Assistance [mailto:customer_assistance@filemaker.com]
                Sent: Thursday, February 12, 2009 2:00 PM
                To: Competitive Edge Products Sales
                Subject: Callback (2) - Unable to deploy IWP [Case: 090209-000153]

                <!--  RNTStart  -->Recently you requested personal assistance from FileMaker Customer Support.

                 Subject Callback (2) - Unable to deploy IWP    Discussion Thread  Response (Dana Medley) 02/12/2009 12:59 PM Hello Shawn,

                Previously, I've tried to call you to advise you that I have consulted with our product specialist regarding the issue and from the information that was given to me I've been given the steps to take for the next troubleshooting step. According to our product specialist, the types of errors that are happening sound like what would happen if the sharepoint service is installed on the machine in the server role.

                So, just as a precaution to ensure that sharepoint is not installed on the machine, the troubleshooting steps that we would like for you to take are as follows:

                1. Uninstall FileMaker Server 10 and IIS from the machine
                2. Reboot
                3. Install IIS without sharepoint - for help with this, I would advise contacting Microsoft for assistance with installing Windows Components
                4. Turn on the 32-bit app pooling in IIS and make the changes that you need to within the documentation
                5. Reboot the machine
                6. Reinstall FileMaker Server 10

                Also, another advisory that our product specialist gave me is that we have only tested & certified on Standard Edition of Server 2008.

                Once these steps are completed, you may contact us back through e-mail or contact us back at 1-800-325-2747 and reference your case number.

                Thank you,

                Dana Medley
                Technical Support Engineer  <!--  RNTEnd60591  -->

                • 5. Re: FMSA10 FileMaker Server Advanced 10 and SBS (Small Business Server) 2008 - HTTP Error 503

                  I think we have found a solution from some IIS 7 server groups and Michael Petrov.


                  In the event viewer was the following error -
                  "The Module DLL C:\Windows\system32\RpcProxy\RpcProxy.dll failed to load. The data is the error."
                  "Application pool 'xxxxxxxxx' is being automatically disabled due to a series of failures in the process(es) serving that

                  application pool."

                  Essentially the rpcpoxy is trying to load into the 32bit pool. 


                  Anyway to fix this issue:

                  Edit  c:\windows\system32\inetsrv\config\applicationhost.config

                  In the section which has <globalmodules> add -  precondition="bitness64" to the rpcproxy line so that you have the following

                  <add name="PasswordExpiryModule" image="C:\Windows\system32\RpcProxy\RpcProxy.dll" preCondition="bitness64" />


                  That should stop the defaultapppool from crashing.

                  Also, you can disable the static and dynamic compression errors with this command at the command prompt:
                  %windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']

                  The following command will re-enable them if you don't need to do FM web publishing.
                  %windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /+



                  Also, the FileMaker ISAPI filters might get added to the global server and other non FileMaker websites outside of the default website so you can remove them from those areas since they can conflict if not.  Just make sure to add the FMI filter into the default website ISAPI filters, this is critical to do, the path for it is Program

                  Files/FileMaker/FileMaker Server/Web Publishing/publishing-engine/web-server-support/iis/isapi_redirect.dll if it is not there already.