Hello,

Has anybody successfully installed FileMaker Server Advanced 10 on Windows Small Business Server 2008 with Web Publishing? We have successfully gotten it to host databases to FileMaker clients however we cannot get the web publishing, XML, XSLT or PHP to work. We try to navigate to the test pages with the test database we just get HT to be 503 errors. We uninstalled SharePoint and uninstalled FileMaker server and rebooted and reinstalled and still have the same problem.

Thank you in advance,

Shawn

SBS is [color:red]not a certified OS. Use the Standard Edition SP 2 32 bit instead. The WPE runs just fine on it. IIRC, this is a known issue and FMI does not support running FMSA on SBS.

Steven

Thanks for responding Steven. The FileMaker Server 10 Advanced installation guide says that FileMaker Server 10 advanced will work on Windows 2008 server 64-bit. I thought business server 2008 was about the same thing as this product except for that it has Exchange and some other programs bundled with it. Sharepoint is uninstalled also. The problem we have is that we have invested about five grand on this super powerful computer to do all this will FM stuff so if I can't get this working I am in a world of hurt.

Also, FileMaker didn't list business server 2003 as a supported platform for FileMaker server eight, however it ran FileMaker server eight with Web publishing beautifully even while running exchange and SharePoint at the same time. I just am really hopeful get this new sbs 2008 working as I haven't budgeted for a whole additional server to do this. Is there any hope?

It will run on 64 bit, but if you're doing web publishing you have to enable the SAPI filters, extensions, and application pooling (32 bit). See pp. 57-59 of the Admin Guide.

FMS 10 Advanced is not certified for Windows Server 2008 Small Business Edition. It is certified for Standard Edition only. There is a 100 percent guaranteed conflict between FileMaker Server and Share Points.

It sounds as if you are planning on running multiple services on the FMS machine. That conflicts with best practices that recommend a dedicated machine for FMS especially for web publishing. OTOH, you have several possible configurations for heavy web publishing including the all-in-one, the 1:2, the 2:1, and the each on own (3 machine).

Steven

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:Windowssystem32RpcProxyRpcProxy.dll failed to load. The data is the error."

and

"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:windowssystem32inetsrvconfigapplicationhost.config

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

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%system32inetsrvappcmd.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%system32inetsrvappcmd.exe set config -section:system.webServer/httpCompression /+

[name='xpress',doStaticCompression='false',dll='%windir%system32inetsrvsuscomp.dll']

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.

I think you likely would not have had this issue had you stayed with an approved OS. We have Server 10 Advanced deployed on Windows Server without issue.

Steven

Very nice set of fixes - thank you very much for sharing them

There are now at least two Windows 2008 SBS x64 servers with FMPro10 Advanced Server running on them.

Mines a development box, running inside a VMWare instance with Windows Sharepoint Services 3.0 SP1 on it, and so not mission critical and working fine now!

I've impletented this fix but now I'm presented with an HTTP 500.19 error, which I understand may be related to permissions.

Have you encountered this?