You have a few options, but I would start with looking at your old server and see what version of Java it was running. Java updates frequently break the FMS Admin Console and related functions like deployment. When I googled this version, folks were running it on 2003RĪlmost all issues related to installation of FileMaker Server have to do with the version of Java installed. Its only supported on Windows Server 2003 They stated that this version was not supported on Windows Server 2003 R2. The only error I saw in the “Application Log” referenced something about a ?ssl.exe not able to start (? References – I can’t recall the first 3 letters)
We manually attempted to start the database server in “Services”. “The database server is not available to edit the deployment. When it comes to starting the Admin Console, it fails and the Deployment dialog box pops up. When we run the “fms_90v2.1_full_ESD.exe”, it goes thru the normal installation Installed all the latest Microsoft Server updates We have a newly Windows Server 2003 R2 32bit with Service Pack 2 Since this product is older, we are not going to run it on Windows Server 2008 R2 but Server 2003 instead
Doing so, we are setting up a newer server before retiring the older failing server. We have a failing server that we want to replace. We use it to run a database for the printing industry and version 9 has been working fine We realize this version of FileMaker Pro Server 9 is outdated and no longer supported by FileMaker Pro but it works perfectly fine for many folks FileMaker Pro Server 9 fails starting database server during new build install
0 kommentar(er)
