July 26, 200817 yr Okay, pulling my hair out here... I have setup the AutoUpdate feature of FMS 9. I followed a tutorial by Geoff Coffee which carefully explained how configure the server and plugins for deployment. I created the scripts necessary and I keep getting a "-5" error which means that the file cannot be downloaded into the local extensions folder. Oh yeah, this is an all Windows environment. The FM server is on a Windows 2003 box. I have tested from multiple clients with the same result. I have searched FMI's KB resource and poured through the server documentation, but am coming up dry. Any help would be greatly appreciated. Edited July 27, 200817 yr by Guest
July 26, 200817 yr Check to be sure the auto-update plug-in on the client side is enabled as well. Steven
July 26, 200817 yr Author Ah, if only it were that easy. Alas, this is not the case. I have checked and rechecked the setup config on the client and server and they are correct. My scripts also check for a running instance of the local plugin and provide an error if it is not installed or working properly. I am wondering if there is a larger permissions issue. FileMaker Server is running on a Windows2003 Server and I was checking the processes form a second Windows2003 Server (which had a copy of FMA9). I was also controlling the servers with a VNC app (Chicken of the VNC). I am wondering if the VNC app or server to server control were areas that could introduce an issue. I was logged into all servers with an administrator account and had RW access to the directories where the plugins should have been installed. I understood that FileMaker v9 would have installed the plugins to one of two locations. I recieved the error about the extentions folder, but the plugins were never installed to the Local SettingsApplication DataFileMaker location either. I also made sure that the plugins I was trying to get AutoUpdate to install were not in either location. Still searching and thanks for the comment. Aaron Edited July 27, 200817 yr by Guest
Create an account or sign in to comment