FileMaker Server 14 doesn’t allow some connection types to databases with periods in name
Operating system version
Windows Server 2008 R2 SP1
Description of the issue
When the database has a period in the name, like Assets.v2.fmp12 the file will show in the WebDirect and FileMaker Go listing of databases, but will report “Database not found” when you click on it to open. Changing the name to remove the period, such as Assetsv2.fmp12 corrects the behavior. FileMaker Pro 14 has no trouble opening these databases remotely. FileMaker Pro 13 and 12 however can’t open them remotely when they are hosted on FileMaker Server 14.
Everything works as expected in FileMaker Server 13.
Steps to reproduce the problem
Create a database titled Assets.v2.fmp12 using FileMaker Pro 14, enable "Access via FileMaker Network" and "Access via FileMaker WebDirect" on the Full Access privilege set, place the database on a FileMaker Server 14 instance and Open it.
Using a browser, login to WebDirect (via https://(server address)/fmi/webd) as the database's Admin user. You'll see Assets.v2 listed as an available database. Click it and you'll receive "Database Not Found."
Using FileMaker Go 14, connect remotely to the server and login as the database's Admin user. You will see Assets.v2 in the list of Available Files. Tap it and you'll get the "Database Not Found" error.
Using FileMaker Pro 12 or 13, connect remotely to the server and login as the database's Admin user. You will see Assets.v2 in the list of Available Files. Double click it and you'll get the "Database Not Found" error. FileMaker Pro 14 *will* open the file.
Rename the database by removing the period and everything works as expected.
I should be able to open the database in all methods of connecting to it as I currently can using FileMaker Server 13.
I receive "Database Not Found" errors when using FileMaker Go, FileMaker Pro 12 & 13 and WebDirect.
Exact text of any error message(s) that appear
"Database Not Found"
Remove the period from the filename.
We use FileMaker Server to host many databases where the version number of the database is included in the name of the database and often has periods. This is creating a jarring experiencing for the end users.