This topic is 1631 days old. Please don't post here. Open a new topic instead.
We have a couple of servers running on AWS. As of the middle of last week we suddenly are having connection problems. The server logs mostly lists error 10, sometimes error 51. These customers have poor internet connection, so we have set up a server and a client in the cloud. The users connects to the client through an RDP session. It is a Windows enviroment with one customer using Windows server 12 and FMS 14, the other Windows server 16 and FMS15. We use a seperate AD server to control the RDP access and accounts to the FMP server, clients have no acces to the FMS server.
I have read previous posts on this issue. I do not think there can be any hardware issue, since the server is hosted with Amazon and both server and client are on an internal network. To be sure I have filed a support request with Amazon as well.
The strange thing is that the error message sometimes occurs within a minute and then FMP freezes on the user while they are still working in the FM app. It is my understanding that error 10 occurs if the client does not respond to the server ping for 2 pings, so time out for this error should be 125 seconds.
These servers have been running without this issue for a long time now. Any idea why this has suddenly changed and why the error message errors while tghe users is using the FM app?
I'm looking for both guidance and software to assist in FileMaker Change Control. With over a 100 deployed solutions across multiple servers the process change management from dev > test > production is very labor intensive. BaseElements helps a lot but it is only one part of the puzzle. Porting the data from production > test across these solutions and then doing UAT and QA is again, labor intensive.
How are others handling this? Is there some software or process documents I'm missing? I'd welcome any input to this topic.
I'm wrapping my head around the Standby Server feature, and there's only one aspect that I can't figure out. I use Webdirect, so I'm forwarding port 80 to the internal ip address assigned to my primary server. If that were to go down, my standby server would take over - but it's assigned a different ip address - so my router's port forwarding rules will still be pointing to the ip address of the primary server. Is this accurate? If so, is there a way around this?
For security reasons, my institution is requiring me to migrate my FMS15 solution, currently residing on a MacPro in my office, to the IT data center. Since they do not run MacOS, this includes a migration to a hosted windows server running FMS advanced. I no nothing about windows (eg: what is a hosted win server vs simple win server ???) , so I will be totally dependent on the IT staff knowing what they are doing (and they barely know FM, I narrowly escaped having them try to recreate the solution in Access for $$$$$ ...):
· FileMaker Server Advanced running on local Mac OS12.12 system.
· RAID-0, Solid State Drives
· 8-Core CPU
· 32gb RAM
· FileMaker DB is 100gb with additional storage required for temporary files and local DB backups
· Hosted Windows Server running FileMaker Server Advanced
· 16gb RAM
· 1tb Storage
I have many questions/concerns, but would appreciate feedback on 2 issues:
1. Backups: My understanding is that FM is adamant that no backup system can touch a “live” database file, causing potential corruption. FMS has its own internal backup mechanism, and you point it to some external drive / directory etc, where it creates backups that can then be copied/archived by a system process or third party backup system.
The IT manager I am discussing this with replied the following: "Backups should not be an issue either. We've been using this model on our SQL servers and have not experienced a single issue over many years. They do their backups and we do our own as well."
I don't know what the windows server system is doing for backups, but are the FM warnings about letting other backup systems touch live FM files only for 3rd party SW, and system processes are OK? Any specifics I should communicate to the IT guys? Again, I know nothing about how win or win/server does this.
2. Performance: I am obviously worried performance will take a hit, if only from networking.
I am hosting a dozen related files ranging from 1-50 GB, typically 5-10 concurrent local and remote users.
The proposed environment seems less optimized for DB performance - what are the key parameters I should negotiate on? My current 32gb RAM may well be more than what is needed (I don't use any web or go functions, just straight FM clients), but can I determine from the admin console logs/stats how much is really needed? My request for SSDs was immediately shot down, how much can I get from various RAID configs they may or may not agree to?
Thanks for any feedback - I am so not looking forward to this...
I have a filemaker server 15 advanced running on windows server 2008r2 in a local LAN network. I want to connect to server with client (filemaker 15 pro). Everything work well in the local LAN but I am unable to access to the database outside the office using internet connection and IP. I just have made the port forwarding setup (5003 and 16000) but no results. Maybe the Windows server need to be opened in some service or funcionality?
Before of the server I had a simepl windows XP pc running filemaker server 5.5 and it work well also outside the lan.
Who Viewed the Topic