Hi all,

I have tried uploading a database file to FMSA v10. The admin tool reports that the file uploaded successfully, but on finishing with the upload wizard the file is not listed in the databases pane. I have refreshed this view several times and tried uploading the file into its own folder as well as not opening the file on successful upload.

Server is Windows 2003 Server, and on checking the file structure the new database is indeed moved to the appropriate folder and its permissions are the same as other files in that folder.

Any ideas?

Thanks.

Check that FMS is patched to the latest version.

Try uploading the Sample file and see if it works with that.

I think I have finally found the reason for this behaviour - the daily and weekly backup schedules are showing as still running. Why _that_ would be the case I don't know, but I suspect that explains why the file upload is failing that one final step.

Any known issues from trying to stop the FM service in the middle of a running backup schedule? :)

Just updating the saga here - the FMAdmin tool was still registering the backup scripts (Daily and Weekly) as running; attempts to force-quit the task failed to resolve the issue and now the admin tool cannot connect to the server. The server is still running and allowing clients to connect, but I suspect a restart of the OS will be required (logout and login also attempted but resulted in no change).

This is one of those times where the ability to save a copy of the file from the host would come in really handy. :

You can use the command line to control FMS. It's in the docs.

It turns out that the command line tools did not work either.

However, a restart of the machine (once all the customers agreed to the outage, a process that took around three months) resolved the issue. We were able to restore from backups after a lot of futzing around pulling data from the live files and importing into the last known good files.

For anyone who is researching similar behaviour, I found other posts indicating that leaving the FM Admin Tool running on the VM seems to be the culprit.

Leaving the admin tool running in any situation is not a good idea with FMS10. At some point the underlying admin server will stop responding.

FMS11 added a new command line command to restart the admin server to solve this (the admin server is separate from the database engine so you can do this without disconnecting the clients). In FMS 10 there is no way out of it except stopping FMS and starting it again.