We have installed FileMaker Server 18. We have added a custom SSL certificate to FileMaker Server 18. On FileMaker Pro, we can view the green encrypted symbol and can able to access the Server DB. But on FileMaker WebDirect, we can't open the Server DB using the Domain name. We have received the error "No such file or directory" on connecting externally. On the internal network, we have received the error "Rejected request from RFC1918 IP to public server address" when we opening the WebDirect using Domain name.
Can anyone help us to solve this issue?
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 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
net stop http /y
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...
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?
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!
Who Viewed the Topic