Over 46,000+ Business Solution Developers Find answers, ask questions, and connect with our community of business solutions developers, business owners and partners.
New! FileMaker Server 11.0v1 and FileMaker Server 11.0v1 Advanced release notes – FileMaker Today
New Known Issues! This document provides additional information about FileMaker Server 11 and FileMaker Server 11 Advanced.
Please register your FileMaker product to be eligible for software updates, new feature notifications and special upgrade prices. You can submit your registration form over the Internet during installation, or send it by fax or mail to the pre-printed address.
1. Installation and Configuration Issues
1.1. FileMaker Server Deployment Assistant does not support using IPv6 addresses for worker machines. In the list of available worker machines, choose either the IPv4 address or the actual machine name.
1.2. Installing FileMaker Server on Windows Server 2008 requires the user Anonymous to be enabled. When installing FileMaker Server on Windows Server 2008, if the user Anonymous is disabled then the Deployment Assistant cannot find IIS 7 (Internet Information Services 7.0). Enable the user Anonymous before installing FileMaker Server.
1.3. When running FileMaker Server in an environment that uses a firewall, configure the firewall to allow network access to ports 5003, 5013, 16000, and 16001.
1.4. If you install FileMaker Server 11 on a system where FileMaker Server 10 had previously been installed, you may see FileMaker Server 10 graphics when you open FileMaker Server 11 Admin Console Start page, Technology Tests page, or Web Publishing Tools page in a web browser. To display the correct FileMaker Server 11 graphics, clear the web browser cache and refresh the web page.
1.5. If you install FileMaker Server 11 on a system where FileMaker Server had previously been installed, you should remove or rename all of the FileMaker Server log files before installing FileMaker Server 11. Otherwise the server deployment may have errors when parsing the log files and may cause the server deployment to be slow.
1.6. You can improve the performance of the FileMaker Server 11 installation or reduce the installation time by minimizing the installer window while files are being installed. Minimize the installer window after clicking “Install” on the page where you enter the license key.
1.7. Due to PHP version changes, if you are currently running FileMaker Server on Mac OS X 10.5 (Leopard) and you want to upgrade to Mac OS X 10.6 (Snow Leopard), you need to use the Deployment Assistant to update the server deployment on the new operating system:
1. After installing Mac OS X 10.6, start FileMaker Server Admin Console.
2. On the FileMaker Server Overview pane, click Edit Server Deployment.
3. Click Next to verify the deployment options.
4. In the Deployment Summary step, click Finish to update FileMaker Server on Mac OS X 10.6.
2. Admin Console Issues
2.1. On Windows Server 2008 and Windows Server 2003, Microsoft security patches may change the Internet Explorer security settings, making it impossible to start Admin Console from the FileMaker Server Start page (http://localhost:16000/). To fix this security issue, you need to change the Internet Explorer security settings in one of the two following ways:
• Open Internet Explorer’s Internet Options, click the Security tab, and add the IP address of the FileMaker Server master machine to the list of “Trusted sites.”
• Open Internet Explorer’s Internet Options, click the Security tab, and change the “Custom level” settings. For Scripting, enable the Active Scripting setting. For “Miscellaneous” enable the Allow META REFRESH setting.
2.2. When you open FileMaker Server Admin Console on a remote machine, if the remote machine goes to sleep, you may lose the connection to FileMaker Server. When you wake up the machine, you may see the error message “The admin console cannot establish a connection to the admin server.” Close Admin Console and restart it to reestablish the connection to the Admin Server.
2.3. Admin Server loads and indexes the log files when it starts. If you have very large log files, Admin Server will take a long time to start and will require large amounts of RAM.
2.4. If you use Log Viewer to view too many entries from the log files, Log Viewer may be slow.
2.5. If your server machine does not have sufficient memory, then you may get an Admin Server connection error message if you attempt to export from the Log Viewer page of Admin Console.
2.6. If you edit a schedule quickly after creating it, you may unintentionally create a duplicate schedule (a second schedule with the same name). However, you may not see the duplicate schedule listed until after you view another part of the user interface and then return to the list of schedules. If you do see a duplicate schedule, it is safe to delete the duplicate schedule.
2.7. For previous releases of FileMaker Server, the external authentication group would default to the fmsadmin group. In this release, FileMaker Server no longer connects to the fmsadmin group on the domain by default. The fmsadmin group is still valid but you must explicitly specify it.
2.8. On some versions of Windows, the desktop version of the Admin Console icon may be appear in a lower resolution.
3. Admin Group Issues
3.1. When you create a new administrative group, if you enter invalid data, the Save button is not enabled. If you change to another pane or dialog, the values you entered are discarded because they were invalid.
3.2. When you configure an administrator group using the Manage Groups tab, if the additional databases folder is assigned as the group folder for the administrator group that you are editing, the “Create subfolder” button will be disabled. To create a subfolder of the additional databases folder, you need to change the group folder setting or open Manage Groups for a different administrator group.
3.3. If you open Admin Console using an account that does not have the “View Statistics and Logs” privilege enabled, you may see hyphens rather than values on the FileMaker Server Overview page.
4. Additional Databases Folder Issue
4.1. On Windows, you may not use the root of a secondary drive as the additional databases folder. For example, filewin:/D:/ is not a valid folder for the additional databases folder. However, you may use a subfolder on a secondary drive as the additional databases folder. For example, filewin:/D:/foldername/ is a valid folder for the additional databases folder.
5. Backup Folder Issue
5.1. On Windows, if the oldest folder in a backup set is locked, FileMaker Server may be unable to delete the oldest backup. As a result, FileMaker Server may create more database backups than the maximum number that you have specified. Make sure that the oldest backup folder is not locked by an application that locks a folder, such as the command line interface on Windows.
6. Send Mail Script Step Running on FileMaker Server
6.1. If you use the Send Mail script step with SMTP to email file attachments from a server-side script, the file attachments should be placed in the same folder that FileMaker Server is allowed to export to.
7. PHP Site Assistant Issues
7.1. When using PHP Site Assistant, experiment with live preview, previewing layouts using various themes. Some themes may be more appropriate depending on the number of columns in a database table and the content of the table.
7.2. If User Access Control is enabled when you run PHP Site Assistant on Windows Server 2008, the live preview may not be able to display page views. Right click on the PHPSA shortcut and select “Run as administrator.”
7.3. When you run PHP Site Assistant on Windows, the live preview may not update the image in the “Home” page when you switch themes. To see the updated image, save the project, then close PHP Site Assistant. Right click on the PHPSA shortcut and select “Run as administrator.”
7.4. In a multiple-machine configuration, if you run PHP Site Assistant from a worker machine rather than the master machine, PHP Site Assistant is not able to open PHP Site Assistant Help pages. Use PHP Site Assistant from the master machine in order to view the PHP Site Assistant Help.
7.5. When you run the PHP Site Assistant on Mac OS, the live preview’s Delete button does nothing. To see how the Delete button works, select “View Site” to view the site in a browser rather than using the live preview.
7.6. The Search page (findrecords.php) generated by PHP Site Assistant returns only records that have data for fields represented by HTML text areas, and does not return records with empty fields represented by HTML text areas. To correct this issue, edit the findrecords.php file, remove all line breaks, indentation, and unnecessary whitespaces between the <textarea> and </textarea> tags, and format the code to fit on a single line. For example:
<textarea class=”fieldinput” type=”text cols=”30″ rows=”5″ name=”<?php echo getFieldFormName($fieldName, 0, $record, true, ‘SCROLLTEXT’, ‘text’);?>”><?php echo $fieldValue;?></textarea>
8. Custom Web Publishing with PHP Issue
8.1. If you have configured your web server to allow communication via the SSL port and are using a self-signed certificate, your solution may not be able to communicate with the Web Publishing Engine. If this issue occurs, open the PHP API located on the server in this folder:
/FileMaker Server/Web Publishing/publishing-engine/php/lib/php/FileMaker/conf
and uncomment this line of code:
$__FM_CONFIG[‘curlOptions’] = array(CURLOPT_SSL_VERIFYPEER => false)
9. External ODBC Driver Issues
9.1. To support authentication with an external ODBC data source in Instant Web Publishing and Custom Web Publishing, the user name and password for the published solution must match the user name and password for the external data source, and you must store the user name and password for the external data source in the FileMaker database.
10. xDBC Issues
10.1. In a solution where a FileMaker database is shared using ODBC, if you attempt to close the FileMaker database while an ODBC or JDBC client is accessing it, the fmxdbc_listener process may issue a crash report, but the fmxdbc_listener process continues working. However, the ODBC or JDBC client may see an error message.
10.2. While an ODBC or JDBC application is connected to a database, if you close the hosted database or if you disable ODBC/JDBC sharing by clearing the Enable ODBC/JDBC setting, an open TCP connection may temporarily prevent the FileMaker xDBC Listener from restarting. You may have to wait up to 10 minutes before enabling ODBC/JDBC or before opening the hosted database.
10.3. For additional information about issues related to ODBC and JDBC, see the FileMaker Pro 11 readme file.
11. Instant Web Publishing/Custom Web Publishing Performance Issue
11.1. On Windows, to improve performance of an Instant Web Publishing or Custom Web Publishing solution, avoid using localhost in the URL by replacing it with the IP address, either 127.0.0.1 or the actual host IP. For example, change http://localhost/fmi/iwp to use http://127.0.0.1/fmi/iwp instead.
11.2. For additional information about issues related to IWP, see the FileMaker Pro 11 readme file.
12. Documentation Issues
12.1. FileMaker Server Help and CLI help documentation for the “fmsadmin restart server” command is not correct. The documentation says that “fmsadmin restart server” stops and then starts the Database Server. As implemented, the “fmsadmin restart server” command performs the same function as the “fmsadmin stop server” command: the Admin Server is stopped, but the Database Server is not restarted.
To learn about the custom actions executed by the FileMaker Server installer, visit the FileMaker Knowledge Base (www.filemaker.com/kb) and enter 6936 in the search field.
To learn about unsigned files used by FileMaker Server, visit the FileMaker Knowledge Base (www.filemaker.com/kb) and enter 6937 in the search field.
To learn about .exe files installed by FileMaker Server that do not have product information, visit the FileMaker Knowledge Base (www.filemaker.com/kb) and enter 6972 in the search field.
To learn about .dll files installed by FileMaker Server that do not have product information, visit the FileMaker Knowledge Base (www.filemaker.com/kb) and enter 7508 in the search field.