Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 4642 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

Our client purchased the FMS11 to be installed in their system, the issue is that they only have the one DC, 2003sbs.

This is not a supported OS for the FMS11, has anyone successfully installed and configured FMS11 on Windows 2003 SBS.

The installation completes, but the "deployment assistant" does not open.

I followed the following troubleshooting:

 

Deployment assistant does not start after installation

If the Deployment assistant does not start immediately after you run the FileMaker Server installation program, the most common solutions are:

On Mac OS, check whether your browser is configured to prevent files from opening after downloading. If so, you can start the Deployment assistant by double-clicking admin_console_webstart.jnlp in your download folder, or double-clicking the FMS 11 Start Page shortcut on the desktop.

On Mac OS and Windows, if the Admin Server process does not respond within 60 seconds to the FileMaker Server installation program, the following message appears:

The FileMaker Server Admin Console Start page is not available.

If you see this message, do the following steps in the order shown:

Make sure the Admin Server process is running. On Mac OS, open the Activity Monitor and make sure a Java process owned by FileMaker Server is running.On Windows, open the Task Manager and make sure the fmadsminserver.exe process is running. If necessary, you can restart the Admin Server process by entering the following command in a command prompt (Windows) or the Terminal application (Mac OS):

fmsadmin RESTART ADMINSERVER

On Windows, you can stop and the restart the FileMaker Server service in the Administrative Tools > Services control panel.

If your server computer has a firewall, make sure all required ports are open in the firewall. (See "Before you begin" on page 11.)

If your machine is running slowly, shut down any unnecessary applications.

Restart your machine. Open a web browser on the master machine and enter http://localhost:16000.

The FileMaker Server service was not installed.

Posted

SBS isn't supported as you noted. Also, if I read your post correctly, the current SBS machine is the Domain Controller. If so, that's not a good place at all to install FileMaker Server. You really need a dedicated server for this.

Steven

Posted

It can be done but it is more trouble than it is worth and it does not allow for much expansion. You can not add another DC box to the deployment for instance.

You're better off getting a regular 2003 Server copy. If you must proceed with SBS, you have remove any other role that it has (file/print sharing, exchange, sharepoint,...). If those are already installed, do a complete re-install and do not select any of those roles.

The time you're spending on it is probbly more expensive than getting a copy of regular Server 2003...

This topic is 4642 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.