I would think the update did not fail as it's noted by the admin console.
Did you restart the machine after the update?
Also, have you tried recreating the schedules to see if maybe the metadata stored with the schedules did not update?
It seems also that Get(HostApplicationVersion) returns 13v2 after the 13v3 update, even though the admin console lists server version 13.03.300... even after a restart.
I opened the FM_sample.fmp12 hosted on FMS 13, open the data view, evaluate get(hostapplicationversion) and also get the same result as Stephen.
thanx for all the feedback.
so i got Server 13v2 back thru Get ( HostApplicationVersion ) on WIndows Server 2012.
so is this just sloppyness / a flaw or do i have to reinstall the server?
where is QA?
is there anyone out where the get function returns Server 13v3?
Message was edited by: FileKraft
At this point it seems to be an FM issue. I would submit an issue report for it.
I have not performed the update myself yet so I can not confirm it’s an issue for me. If anyone does NOT see the issue after updating, hopefully they will chime in.
my question was and still is if this is a flaw which i can live with or if the upgrade failed and i am still running FMS13v2 and just got
the admin console display changed when applying the update.
since no-one else seams to get the get function to display "server 13v3" it looks that my specific installation didn't fail as an individual instance.
Waiting for FMI now for the answer.
Understand this is confusing and for some frustrating. Let me see if I can explain...
First of all, the update ran fine for those of you who are concerned it might not have.
The "reason" the version is not updating like you would expect it to that the only thing the v3 updater updated was the OpenSSL library. Other components remained the same which we rely on more when it comes to reporting versioning. This is why some of you are seeing "v2" reported back from Get (HostApplicationVersion).
For what it is worth, this has sparked some internal conversations on how we report versioning going forward. All things considered, this update should have somehow magically reported "v3" using Get (HostApplicationVersion) even though only the security libraries were touched but it does not.
Hope this clears things up.
still would be nice if it displayed consistently what's running.
glad don't have to worry about our installation. fms13v2/3 seams to be rock-solid on Windows Server 2012.