Link to home
Start Free TrialLog in
Avatar of Andreas Gieryic
Andreas GieryicFlag for United States of America

asked on

FileMaker Pro Server 9 fails starting database server during new build

FileMaker Pro Server 9 fails starting database server during new build install
-      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
-      We use it to run a database for the printing industry and version 9 has been working fine
We have a failing server that we want to replace. Doing so, we are setting up a newer server before retiring the older failing server. Since this product is older, we are not going to run it on Windows Server 2008 R2 but Server 2003 instead

We have a newly Windows Server 2003 R2 32bit with Service Pack 2
-      Server is an HP ProLiant DL 380 G4
-      Installed all the latest Microsoft Server updates
-      This is a brand new install. Nothing else is running on this server. Basically a “vanilla build”

When we run the “fms_90v2.1_full_ESD.exe”, it goes thru the normal installation
-      When it comes to starting the Admin Console, it fails and the Deployment dialog box pops up. The error is

“The database server is not available to edit the deployment. Please start the database server first.”

We manually attempted to start the database server in “Services”. Restarted the server. And even totally rebuilt the server
-      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)

I contacted FileMaker. They stated that this version was not supported on Windows Server 2003 R2. Its only supported on Windows Server 2003
When I googled this version, folks were running it on 2003R2 and 2008
Avatar of Andreas Gieryic
Andreas Gieryic
Flag of United States of America image

ASKER

I ended up rebuilding the server with "Windows Server 2003" and installing SP2.
I still get the same “The database server is not available to edit the deployment. Please start the database server first.” error.

I also retrieved the same "Application Log" error message
Source: Application Error
Event ID: 1000

Faulting Application openssl.exe, version 0.0.0.0 faulting module openssl.exe, version 0.0.0.0 fault address 0x0005853c
Avatar of Will Loving
Almost all issues related to installation of FileMaker Server have to do with the version of Java installed. Java updates frequently break the FMS Admin Console and related functions like deployment. You have a few options, but I would start with looking at your old server and see what version of Java it was running.

Remove any existing version of Java on the new server, restart, install any updates to FMS 9 so you have the most current version, download the installer for the version of Java that was running on the old server, and restart. Turn off automatic Java updates.

Alternately, you can un-install Java AND FileMaker Server, including deleting all components and the FileMaker Server application folder. Restart. Then install FMS which should install a version of Java that will work with it. Install all FMS updates available on the FileMaker website.  Turn off automatic Java updates.

If you are unsure of what version of Java to install, start with Java 6 Update 7 which I think is compatible. Check the Java website at: http://www.oracle.com/technetwork/java/archive-139210.html   The J2SE Runtime Environment (JRE) is what is required.
I read a little about newer versions of  Java could cause problems. The new build had no Java running. the install prompted that it found no Java version 5 or 6 and prompted to install version 6.

Now I'm told that the latest version 7 is not recommended. I'll try your recommendation downloading the newer version of Java 6 Update 7

I'll disable the Java updates and see what happens - before I try to uninstall any FMS components

The original server that is still up and is only running "Java standard Edition 6", which appears to be the version installed by FMS
Go to the Java Control Panel on the old server and determine the update version. Java 7, any update version, is not compatible with FMS 9. Java 6 Update 7 is an older version that should work for you with FMS 9. The FMS Admin Console is built in Java, so an appropriate version of Java 6 must be installed.
I have already determined that we are running Java version 6 with no updates (as it comes with the install of FMS 9) since this still failed, I'll download and install Java 6 update 7
I'll provide feedback ASAP
Be sure you've updated FMS to the latest possible version 9.0v3

http://www.filemaker.com/support/downloads/downloads_prev_versions.html

some updates install Java updates as well, so install those first if you need any.
Installed the 9.0v3 - still getting the error

Here's what I found on the Java link
Java SE Runtime Environment 6u7  13.07 MB    jre-6u7-windows-x64.exe
 Windows Offline Installation  15.24 MB    jre-6u7-windows-i586-p.exe
 Windows Online Installation  373.40 KB    jre-6u7-windows-i586-p-iftw.exe

I have the 32bit version of Windows Server 2003. do I install the i586-p.exe
that sounds right to me.
I uninstalled the old version.
- Successfully installed Java 6u7
- prompted for a server reboot
- still getting the same error

The older server is running Internet Explorer 8
- this server wont let me upgrade to 8. I'm assuming I need to install all the prereq's first.

Please see the attached screen shot. I'm consistently getting this internet Explorer message. Not sure if this is causing an issue. Still getting "openssl.exe cant load" as well
IMG-0383-1-.JPG
Not sure if this is the ultimate cause, but yes, the IE security may be blocking the Admin Console Java app from launching. Try turning off the Windows Firewall, IE Security, virus protection and anything else that might interrupting or blocking the launch.
Iran all the Windows Server updates including I.E 8
I lowered all the security settings in I.E 8
When I initiate the FMS Console, I get a notification to download. I accept it (I'll provide the exact wording if needed)

Another thing I'm told is that FMS does not like "dual nics". I disabled the 2nd embedded NIC on the server. Failed with same error

I then uninstalled completely, rebooted and reinstalled. Something about how the FMS binds with the NICS. Failed

 I disabled the "Internet Explorer Enhanced Security Configuration" that kept popping up. Restarted IE. failed. IE 8 prompted to "enable intranet settings" tried it with and without. Failed with same error

Rebooted server again: I still get the openssl.exe error every time I reboot the server when FMS is on the server

Started the FMS Admin again. IE again warned that its blocking the site. I looked at the "original sourced" code of the link and it shows something about www.filemaker.com/xmlproperties. Still fails

What concerns me every time I start the FMS admin console, IE8 displays "To help protect your security, Internet Explorer blocked this site from downloading files to your computer. Click here for options" I click and chose download. another box appears as if it tries to download something to a temp folder but it does not show any progress. then I get the same failing error
In my experience, what FMS is trying to download is what's know as the Java Web Start application which helps launch the Java-based Admin Console when you start from the "Start Page" in a web browser. Because of security issues around Java-based applications, Java apps are, I think, blocked by default in IE 8. (I know for certain that that is now the default setting for Mac OS X).

Here is a FileMaker Knowledgebase article on troubleshooting installing FMS 9 Server. http://help.filemaker.com/app/answers/detail/a_id/6454/  It has both Windows and Mac tips mixed together but here is something of possible interest:
On Windows, Start menu > Control panel > Java- General tab-on Temporary Internet Files > click on settings and click on Delete Files. Also clear browser cache: open a browser, Internet Options > General tab- click on Delete Files.
You might also try Firefox or Chrome instead of IE. Sometimes that has helped in my experience.

The following is also a very complete rundown of best practices when installing: http://fmwebschool.com/frm/index.php?topic=1443.0;wap2
I did not have time to do anything the last few days. However I need to make this work ASAP. the original server finally died.

I'm going to uninstall the FMS again, then uninstall the Java 6u7
then install Firefox and then the FMS again

We are not running or need IIS
Attempted using Firefox to no avail. It consistently prompts to install Java.

I further found a recommendation to set the clock back to 1/1/2009. This allowed me to install FMS and begin setting up the deployment. It prompted me to fill out the Admin Console credentials. I configured the basic settings fine

I then installed Internet Explorer 7 - the console configuration still worked and it let me open the Server Admin Console.
- I then updated to Internet Explorer 8. I could still open the Server Admin Console
- I set the clock back to the correct current time and all worked fine

- I am still on the original Java 6.0 from the install.
- I am still running just the one NIC with the 2nd NIC disabled.

So far I'm finding the only difference with the original install and the last install is the time stamp I used to rebuild the server. I'm not sure what FMS was looking for
- should I update the java to 6u7 ? If I do will it take the new update? I's rather not uninstall the original version 6 at this time.
ASKER CERTIFIED SOLUTION
Avatar of Will Loving
Will Loving
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks for all your help. I may try the Java 6up7. If I do, I'll post. For now I'm going to complete the build and get the server onsite
I did update Java to 6up7
NOTE: another tidbit of information
- If you build the server at a different location with a different IP address and then you install the server at its final destination and pull in or hard code a different IP address, the Admin console will still open but the database wont start.  I had to totally uninstall and reinstall FMS (with the time stamp set back during installation) and it worked