Jump to content
Sign in to follow this  
carlsson

WebDirect Disabled after update!?

Recommended Posts

Today I updated FM Server from 17.02 to 17.05. After this update WebDirect refuses to start. 

When I click on the slider, it says "Enabled",  but when I go back again it's Disabled.

I have looked for Java updates, but I already have the latest update applied. 

 

I'm on macOS 10.13.6 with all security patches applied.

I haven't installed SSL yet, but it worked before this update so....

Where should I look more?

 

Please help! 😩

Skärmavbild 2019-07-08 kl. 15.25.15.png

Skärmavbild 2019-07-08 kl. 15.25.02.png

Share this post


Link to post
Share on other sites

Solved!

I updated the privileges on the Filemaker server > Web Publishing folder, and now it works.

 

*phew*

Share this post


Link to post
Share on other sites
Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Similar Content

    • By fluffy
      Hi Group  is it possible to have a memo field on a form or in a portal so that when you click on it the memo field pops up in a window as a bigger field so it can be edited and read easier?
    • By JMW
      We have a Filemaker 17 Server set up and running on a mac mini (sorry, I can't get on right now to find out which OS it is running).  We have set up everything so Web Direct can be used to access a web page for making appointments and filling out forms.  We have several different versions running on several different servers (eye doctor's offices) but this one won't work.
      We have ... 
      Set up web direct on the server, installed the certificate, gotten an external ip address, forwarded the ports, turned off all firewalls and it still doesn't seem to work.
      I have used fmsadmin to see if web direct is running.  When I try to start it, fmsadmin says it's running.
      Yesterday when I was comparing the processes running on the mac mini FM Server is running on to a different mac mini running FM Server I noticed there are a lot fewer processes related to web direct running on the computer that the web page won't open on.

      Does anyone have any ideas that can help me figure out what is causing this?  And, if you need more information, let me know
    • By DR. ALI BAHAR
      I have been having some installation difficulty with getting my FMS 17 onto our Windows 2012 R2 box.  
      When it installs, it gives me the well known dialog about ports 80 & 443 being required.  It says port 80 is in use.
      When I called Filemaker Developer, my friend in Usa, they walked me through a netstat -ab | more command.  
       
      Ran Windows PowerShell as an administrator
      typed:
      net stop http /y
      hit enter
      wait for all services to finish/close down
      Tried installing again. and it was successful.
       
       
      I suggest through this Forum to please the Installation ports be manual if possible.
      because previously i have been trying for few days and fresh installations of windows server also have issued if restarted once...
      Thanks.
    • By naio
      I have FMS17 running a system shell script that does the following:
      Tar the latest backup folder and leave it into a specific 'tar' folder Mount an external volume share rsync external share and tar folder The script was running twice a day without any problem until last week when I upgraded the server OS from High Sierra to Catalina.
      FMS event log just shows the following:
      Schedule "schedule-name" aborted; aborted by user. Possibly it's a problem with permissions but how to fix it?
    • By gczychi
      Browsing through my event logs, I am finding weird scripting errors, like:
      ... Information 645 ...local Schedule "Import Main (every minute 8-20)" scripting error (401) at "Import : Import Main : 36 : Perform Find". How can a simple «Perform Find» script step (which works just fine in the server scheduled script, btw.) generate a scripting error? Occasions where the FoundSet = 0 should be considered «normal».
      I also have found other errors, that shouldn't be errors, like «Go to Record/Request/Page [ Next ; Exit after last ]», when there is no next Record.
      What is the best way to prevent this? It’s clogging the log files.
      Thanks a lot for any insight!
      Gary
       
  • Who Viewed the Topic

×
×
  • Create New...

Important Information

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