Jump to content

FileMaker v13 Admin Console


This topic is 1835 days old. Please don't post here. Open a new topic instead.

Recommended Posts

I've just upgraded my FMS (Windows 2008R2) from v13.0.1 to v13.0.5 (or whatever the latest is). I'm now finding the Web Console to be extremely slow, to a point where it'll easily take a few minutes to click on a tab to actually see a page beig displayed.

Upgrade has been done in two steps (to v13.0.3 and then to v13.0.5 as indicated by FM) and I've also rebooted the box just to be sure. During installation no errors appeared.

Before the console worked fine.

Anybody else see this? Anything I can do to fix it?

Link to post
Share on other sites

No, not seen this.  Ask your FMI rep to give you the url for the full v5 FMS installer, uninstall FMS from the windows control panel, delete any remaining folders that are left behind, reboot and reinstall the full v5.  Perhaps that will clear it up.

Link to post
Share on other sites

Thanks Wim, I'll keep that as a last resort. We've got an annual site license so getting the full version shouldn't be a problem. Might check with support first to see if there's an easier solution. (only reason I haven't checked with support yet is because its weekend, and making changes like reboots is easier on the weekend as there's noone using the system).

Link to post
Share on other sites

I've just upgraded my FMS (Windows 2008R2) from v13.0.1 to v13.0.5 (or whatever the latest is). I'm now finding the Web Console to be extremely slow, to a point where it'll easily take a few minutes to click on a tab to actually see a page beig displayed.

Upgrade has been done in two steps (to v13.0.3 and then to v13.0.5 as indicated by FM) and I've also rebooted the box just to be sure. During installation no errors appeared.

Before the console worked fine.

Anybody else see this? Anything I can do to fix it?

 

I've had this exact problem several times with FMS 13 running in Windows 2008 R2 (spinning loading icon and minutes to load any page in the admin console).  Other than that issue the entire installation was performing fine.  After multiple calls to Filemaker Support, their only suggested fix was to completely reinstall a fresh version of Filemaker Server after performing a complete uninstall.

 

To be fair, I haven't seen this issue crop up since upgrading to FMS 13 v4 but it's pretty sad when your best practice is to simply flatten and reinstall.

Link to post
Share on other sites

Thanks James,

Good to know uninstalling FMS and reinstalling will likely fix the issue. I've been talking to support about this as well, and they suggested the same, though couldn't confirm it was a sure fix. 

Upgrading from v12 to v13 also requires a complete uninstall/re-install. So I'm not completely surprised by this solution.

Annoyed for sure, in this day and age, you'd expect to be able to run an upgrade executable and simply upgrade your older version. 

And if the upgrade fails for some reason, support should have an acceptable fix (ie, delete this setting file and reboot the box).

Anyway, I'll have to schedule this out of hours sometime.

I'm currently in the process of creating another scheduled script, and every step on the console is taking about 5 minutes.

Link to post
Share on other sites
  • 1 month later...
  • 4 months later...

Aurgg!

I waited long enough to upgrade my client all the way to FMS14.  But still have this issue.

I don't think it is the hardware, 2.2G Xeon/24G Ram/1T Drive

or the Software Server 2008R2E SP1, JRE 1.8v40 installed

Link to post
Share on other sites

If it is not the hardware then it has to be something in the OS configuration.  I've installed a dozen FMS14 by now and none of them have the issue...  I also never had it happen on FMS13 on my deployments so since it happens for you on both FMS13 and FMS14 on the same box, with the same OS then those are the places I'd suspect.

Any chance you can do a clean install of the OS at some point to get rid of any gremlins?

Link to post
Share on other sites

Agreed, I too have done dozens of 13/14 installs and never saw this issue.  Except for this one client.

I don't administer this particular server it is another consultant.  reinstalling the OS is not my call.  But I will float that.  This server worked fine with FMS11 and 12.  This issue didn't appear till FMS13.

Thanks.

Link to post
Share on other sites

I can't recall a specific article, but memory tells me reading an article at some point stating you might have to clear the cache/settings for Java. Maybe uninstall java completely, clean temp files/folders, cache for java etc, and reinstall java. Check with support what the recommended java version is for you v14.

Also, disable AV or any other (security) software temporarily to see if that has an impact. I use Sophos Cloud and the webfiltering component impacted the Admin Console. 

Link to post
Share on other sites

This topic is 1835 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Similar Content

    • By Philip Sommers
      I currently administer a Filemaker 16 Server and only use Oracle Java for the admin console (web publishing is turned off). We want to get rid of Java rather than start paying for it. Rather than upgrade to FMS18, is it possible to use OpenJDK instead of Java for the FMS16 admin console? If so, is there anyone that can provide some guidance on how to do that?
    • By jjjjp
      After upgrading to FM Server 16, I am seeing that the automatic daily script executed from the server side is no longer doing so without error. The script sends email reminders to workshop presenters scheduled within 4 days. The error code, which I record in a log, is 119. However, that code isn't listed among the error codes listed in the online help:
      https://fmhelp.filemaker.com/help/16/fmp/en/#page/FMP_Help%2Ferror-codes.html%23
      Knowing the meaning of the error may provide useful information that will help me reconfigure the email account settings for the command Send Via SMTP Server.
      Thanks.
       
    • By "... you mean these fans?"
      Mr. Ignoramus
      We have a solution in Canada where we moved the db from a hosting company to a LAN ( customers building ) They are using a Mac OS machine running FileMaker 16 server.
      We access the FM 16 server via apple's remote access, having trouble locating where we would put the index.html and php files for our web form that we used when we were hosting on an outside hosting company.  The hosting company put the html/php file in the folder that designated our account number. 
      My question is this ... where would we put the two web files; index.html (form) and the .php (create record in FM) file on the FM 16 server.  I can not seem to locate the instruction via the documentation FM is providing.  Have done several internet search ...
      I am gathering information to pass to the individual helping us with the FM server at location.
      Anybody able to provide a link or guidance I would be grateful.
      Thank you.
       
    • By jduncan
      Hello,
      We recently upgraded from FMS 14 to FMS16 and one of our databases won't open via WebDirect due to the way it's named:  the database title has an ampersand ("&") in it.  This worked just fine for FMS14, but not for FMS16.  The easiest solution seems to be to change the database title.  I'm a little hesitant to jump into this because of a large number of externally held containers.  How would one safely go about changing the database name (I'd like to change the "&" to "and") without losing the linked containers? 
      In case anyone's wondering, I didn't name the database; I inherited it.
    • By ShelCOYS
      Hi, I have fm 14 server running on a mac mini. I have recently upgraded to FM16 running Mojave on 2 x local macs. We started with one license, where only one of us could use FM at a time (as we knew), I have since bought another copy and and reinstalled FM16 on the local mac with the new serial number but the server still seems to think we are using the same copy?? and we are getting the attached error. I have completely uninstalled FM locally but still does not work. I have asked my FM guy, as well as 2 or 3 other people but everyone seems to be stumped?? Is there any way of clearer the cache which may be holding this old information? Any help would be much appreciated.

  • Who Viewed the Topic

    3 members have viewed this topic:
    Ankit Tandon  Mark Smith  Robert William 

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.