Get(HostApplicationVersion) on FileMaker Server 13.0.4 returns Server 13.0v2

     Fred Marker:

     Thank you for your post.

     Our Testing and Development departments are already aware of this issue.  The current design takes the information from the database server, which has not been updated since 13.0v2.  The two subsequent updates (13.0v3 and 13.0v4) have been security related (SSL).

     TSGal
     FileMaker, Inc.

     An entry in the Known Bugs List has been linked to this Issue Report. Any Comments/Questions/Suggested Corrections should be posted here or in a new thread. Please do not post such comments to the Known Bugs List thread.

Hello TSGal + Phil,

Testing and development may be aware of the issue - but they are obviously not aware of the impact of this issue!

It is FAR MORE than a "nuisance" as it is categorized in the bugs DB!

It depends, of course, if/how the function is used, and we use it for a very important function:

In Advanter we have a blacklist for FileMaker Clients and Servers. Should a particular Version not work with Advanter we add the Versionnumber to the blacklist, and Advanter does not start with any of the black versions. In this way we can ensure that our code runs as we expect with an acceptable Servert-Client combination.

This bug however makes it impossible to distinguish between VERY IMPORTANT versions.

While 13.0V3 may have been security-related, it also fixed a bug, making server-side-scripts over multiple files possible.

It is extremely important to confirm that the server can successfully run a server-side-script before embarking upon it - due to this BUG it is not possible to tell if the server can do this or not.

Please bump this bug!

Thanking yous

MrWatson, Günther Business Solutions GmbH

P.S. I notice that there was exactly the same problem with FMS 12.0v3 and 12.0v4!!!!! Can I expect the bug with FMS 14.0v3? Please do an HACCP-analysis of your development process, so that the cause of this bug goes away for future releases!

MrWatson:

Thank you for your posts.

I have attached your comments to the original issue.  When more information becomes available, I will post again.

TSGal
FileMaker, Inc.

It is FAR MORE than a "nuisance" as it is categorized in the bugs DB!

Please read the info at the start of either the KBL Thread or the first layout of the database on how a "risk level" is determined. This does not attempt to assign a level of "importance" as any bug can be totally trivial to one developer and a complete showstopper for another. It only provides my best guess as to how dangerous this bug is to your database file and the data contained within it. A bug that results in a crash is always labeled High Risk as a crash can damage your file as well as lose uncommitted data. Bugs that affect the values of large numbers of data are much higher risk than one that more typically would affect the data in just one record. And many bugs are simply very unlikely to affect data or database integrity at all.

I have judged that this bug to be one of those that is very unlikely to have a negative affect on the integrity of your file and the data it contains. But also note that this is just my personal opinion. I don't work for FileMaker and as far as I know, the inclusion of an issue in the KBL, let alone how it is rated has no influence on any kind of priority FileMaker Inc. might assign to fixing it. The purpose of the KBL is to help developers such as yourself to research issues that might pop up during the use of your database without having to go to the trouble of filing an issue report if one has already been posted and confirmed by a TS person.

All:

This issue has been corrected in FileMaker Server 13.0v5.

TSFalcon
FileMaker, Inc.

THANK YOU!