FMS10 on Windows Server 2008 64bit

[Tristan77]

Hello FMForum, I'm a beginner at this, so please bare with me.

I am currently running FMS 10 Advanced V.2 on Windows Server 2008 R2 (64bit). (If you need to know, the workstations are running FM 10 Advanced V.3 on windows xp sp3).

The problem is after a install of server it tries to start the admin console but an error messages pops up saying "The database server is not available. To edit the server deployment please start the database server first." I press restart, then nothing really happens for about 30 seconds and then another error pops up saying "Unable to start the database server. Please contact your system administrators for assistance."

This happens every time i try to start the admin console.

The weird thing is that the server is serving files fine, whatever files are in the database folder are showing up and being used fine. The only problem seems to be the admin console.

I have reinstalled multiple times but yield the same problem.

Other info: • Bonjour V.1.0.106

• Java 6 update 7 AND 16 (both are installed)

i do not know if having 2 of those java's installed will effect anything or not.

Also i found out by playing with the admin console shortcut on the desktop that if you make the shortcut compatible with Windows XP SP3 and then try to open it, it comes up with a different error that says "Admin server connection error" "an unknown error has occured"

That could either help a bit or be totally useless.

Please any suggestions would be nice, because i am out of ideas.

Thank you,

Tristan

[Vaughan]

From the FMS Getting Started Guide:

On Windows 64-bit editions, FileMaker Server requires the 32-bit version of Java 6 Update 7.

[Tristan77]

Thank you for pointing that out to me, i checked my java on the server and yes they are 64bit. I am currently downloading the 32bit java 6 update 22. I will get back to you if this solved it. *Fingers Crossed*

[Tristan77]

Sorry, i am still getting the same error.

Here are the programs that are installed on the server.

http://upic.me/show/17242494

I do not understand why its not working. I un-installed everything (java bonjour FMS 10). I then rebooted the server and installed the Java and bonjour then i installed the FMS 10, the admin console failed to open with the same error message, then i installed the updater FMS 10 V.2 and still would not open.

Any other suggestions ?

Thanks

Tristan

[Vaughan]

Have you tried running the admin console on another computer?

[Steven H. Blackwell]

I am currently running FMS 10 Advanced V.2 on Windows Server 2008 R2 (64bit).

FileMaker Server is a 32 bit service. If you're going to run it on this OS, you must run it in 32 bit mode. See http://thefmkb.com/7643 Tech Info.

Steven

[Tristan77]

it seems to be running on 32bit

Screenshot of the process, they are all *32

http://upic.me/show/17268658

Or am i looking at the wrong place ?

Also i tried entering the admin console through another computer (running windows XP sp3 32bit) and it showed the same message.

[color:red]The database server is not available. To edit the server deployment please start the database server first :)

Edited October 15, 2010 by Guest

[Tristan77]

I have resolved the problem. It was a network adapter called IBM USB Remote NDIS Network Device.

It's some sort of software that came with the computer, that seemed to be conflicting with the server.

Thank you both, Old Advance Man and Vaughan very much.

Tristan

[ghettocottage]

Just to add some extra input here...I had the exact same issue. Running FMServer 10 with 2008R2 64 bit. Database Server running, but unable to connect with Server Admin on local machine.

Resolved by disabling one of the two network adapters on the server. Connecting to the Server Admin works fine when second Network Adapter is disabled. Re-enabling second Network Adapter makes it happen again.s

For now, I will simply disable the second Network Adapter when I want to log in to the Admin Interface, which is not that often...and re-enable my second adapter when I am finished, since it does not seem to affect the Database Server itself, just the Admin Interface, which I am guessing gets confused as to what adpater to connect to when it launches.

Edited November 28, 2010 by Guest