![]() ![]() It’s been over a year, and it’s not been tested by FileMaker. FileMaker 13 was released shortly thereafter. Why not? R2 was released in October of 2013. Why couldn’t we install on the Windows machine? FileMaker has not tested Server 13 on Windows Server 2012 R2. This will resolve the issue temporarily until the computer is restarted.įortunately, that did work, and now we are on track to complete the upgrade to V 13.īut the questions these two problems raise are disturbing: The temporary workaround is to use the Change License Key option (General Settings > Change License Key…) in the FileMaker Server Admin Console and reenter the same credentials. Fortunately, there is a simple work-around (quoted from the thread in the forum): And FileMaker is aware of this problem and turned if over to Testing and Development for further review on 11/25/14, the day after FileMaker released the v5 patch for Yosemite. And the symptom? Files would not open for sharing. There is a bug in FileMaker 13 v5, and it may not register the license properly on Mac running Yosemite. This copy of FileMaker Server will not open any databases, but will allow updating the license key in the Admin Console. Forums were browsed, advice followed.įinally, after about three hours, I found the answer in a forum by searching for this error I found in the Status area log in the console:Īnother copy of FileMaker Server (FMPserver ) is already running with this license. The files were uploaded via FileMaker Pro Advanced, and still no luck. Not even the FileMaker_Sample file–installed during the installation process by the installer–would open.įile permissions, the usual suspect in these types of cases, were checked and found to be OK. And a new set of problems were encountered: Everything installed flawlessly, but the files would not open on the console. In desperation, and with a deadline looming, we switched gears and bought a Mac Mini. We called FileMaker support and followed their advice (lots of small tips, most already tried before). We uninstalled and reinstalled IIS and FileMaker Server, configured options, followed advice from people who suffered from the same problem with both V13 and earlier versions, much more. The basic problem: When step 2 of the deployment process was invoked (Single or Multiple Machines, and we tried both), the installation software would return the error that the connection was refused by the web server. We both spent hours browsing the web and trying different fixes. The server side would install and run without problem, but the web publishing engine would install but not deploy. The IT consultant firm working on this machine is quite experienced and also has installed, configured and supported FileMaker Server on both Macs and Windows.Īnd we could not make it work. The first attempt was made on a new Dell server running Windows Server Standard 2012 R2. Out biggest problem came with upgrading to FileMaker Server 13.0 V5. In preparation, we have upgraded the databases from 11 to 13 on test machines and laid the groundwork for a successful switch over by testing functionality of the various functions and processes. If you notice a connection or speed issue with your server, we invite you to contact us.A client is upgrading to FileMaker 13 this weekend, both clients and server. Our staff is always willing to help via phone or email. When restarts are needed, we schedule it with an email announcement to each customer. Restarts are typically done after hours when most customers are not impacted. When necessary and appropriate, we will restart the servers for necessary OS updates or FileMaker Server updates. We've crafted these specialized plans to fit the niche needs of a FileMaker hosting customer. When you host with us, you know your files are on a world-class infrastructure and managed by AWS certified experts. ![]() We fully control everything on them, which is the main reason they are so stable and speedy.įor our dedicated hosting plans, we capitalize on the security, stability and strength of the Amazon Web Services (AWS) technology. With our shared hosting plans, we own all our own servers, they are not shared by any third-party and there is no virtualization. Our job at PCI is to keep your FileMaker server up and running to ensure your data is backed up daily and secured with the highest level of encryption technologies and state-of-the-art remote connection mechanisms. Our alert system pings a dedicated FileMaker test file on each of our servers every 5 minutes ensuring that FileMaker Server and everything needed to support it is up and running. In most cases, we catch the issue before our customers notice a problem. We have a robust alert system in place and, in the event that service is interrupted, we are automatically alerted. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |