Windows versions with the Start menu: Click Start menu > All apps or All Programs > FileMaker Server > FileMaker Server Admin Console. Windows: Double-click the FileMaker Server Admin Console shortcut on the desktop. To start Admin Console using a desktop shortcut: Optionally, you can stop now and open Admin Console later. If necessary, see Admin Console doesn't start after installation on the primary. Windows: In the last step of the installer, enable Start Admin Console, then click Finish. This process may take several minutes.Īfter the software has been successfully installed, open Admin Console. See Installation notes.įileMaker Server begins to install. If Bonjour is not running, you are prompted to run it. The only way to change the PIN value is to reinstall FileMaker Server.Įnter your macOS user name and password, then click Install Software. Important The PIN value can be set during installation only. Passwords are case sensitive.Įnter a PIN value that can be used to reset the password using the command line interface (CLI). The server administrator is responsible for installing and configuring FileMaker Server as well as managing the FileMaker Pro databases hosted on FileMaker Server. See Installation notes.Īssign the user name and password to use whenever you sign in to Admin Console as the server administrator. If the existing user account you specified does not have sufficient privileges for FileMaker Server to run, the installer displays an error message. You may want to choose this option if you already have an account that has privileges set as you want-for example, to access network-attached storage. To use an existing account on this machine, choose User Name, enter the account's user name and password. To use the default account, choose Local System (Windows) or fmserver (macOS). See Installation notes.Ĭhoose an option for the FileMaker Server user account (the account under which you want to run FileMaker Server): Note In Windows, you can specify a non-default location. Review and accept the end user license agreement. If there is a task you did not do, quit the installer and do the task. Read the important information displayed. To continue with installation, click Next (Windows) or Continue (macOS). If you do not have Bonjour for Windows installed, you are prompted to allow the FileMaker Server installer to install it. If you do not have IIS and Microsoft Application Request Routing (ARR) extension for IIS installed, you are prompted to allow the FileMaker Server installer to install them. If a security message appears, click Continue. MacOS: Double-click the installation icon. If a User Account Control alert appears, click Yes. Windows: If you have Bonjour for Windows installed, make sure it is running before you run the FileMaker Server installer. MacOS: /Library/FileMaker Server/CStore/LicenseFile on the machine where FileMaker Server is being installed Windows: :\Program Files\FileMaker\FileMaker Server\CStore\LicenseFile, where is the drive on which FileMaker Server is being installed The installer folder (the folder where the installer is located) Place the license certificate in one of the following locations: All that has happened since it was provisioned is filemaker has been downloaded direct from our account with Claris.Installing FileMaker Server on a single machine (FileMaker Server only, Windows and macOS)įollow your electronic download instructions to download the installation disk image and license certificate file. To clarify, the server has 32gb ram and is a fresh install. I created a new administrator account locally in the machine, the error still appears. I have since run the install as administrator (even though my account is administrator). This leads me to believe that this is not the source of the problem.īased on the first error code I wondered if it was a permissions problem. To add no that, the error appears immediately after trying to start the service, it does not reach the end of the time limit before there’s and error. However, despite increasing the time frame given to the services to start before timing out, it still fails. My understanding from the second error code is that the service did not start in time and therefore timed out. I’m not totally inadequate at light problem solving, but have been unable to resolve this. I provisioned another new server with windows server 2016 and had exactly the same problem. Unless the service is started the installation cannot finish, so I then went into services and tried to start manually and got error 1920. I proceeded to turn off firewalls and windows defender just in case. I have provisioned a new dedicated server today with the intention of installing FileMaker server 19.Īs a fresh install I did not expect to run into any problems.īefore the installation finished it tried to start the service and subsequently failed with an error 1053.
0 Comments
Leave a Reply. |