FM Server Admin Console not Refreshing DB List

[Quartekoen]

As the subject explains, our DB Server is not showing the correct files in the Database section of the Admin Console.

I had a large number of 'old' versions of databases that I wanted to remove. At the same time, I have another new database that I want to open. The new database was added to the folder containing all other working DBs. The file did not appear on the list, but I realized that the server was already hosting it's maximum number of databases. In the server Configuration, I increased the maximum number of files to host (at this point, it's at the maximum, and still not working). When this didn't work, I went to delete the 'old' databases. I deleted them from the folder of other working DBs, but even still, they appear on the list.

After deleting these files, they are obviously inaccessible, since the Admin Console is unable to do anything to the files (Open, remove, pause, etc...), yet they refuse to leave the list, even after clicking "Refresh List". The new DB also refuses to show on the list, even though I've very carefully checked the file. It is accessible via the fmapp, and sharing is turned on for all users. What am I missing here?

Thanks.

[Steven H. Blackwell]

OS of server and OS of machine running the Admin Console if that is different?

There are some prior reports of similar behavior to what you describe.

Steven

[Quartekoen]

The server is running Mac OS 10.5.6, but this shouldn't make a difference, since it was on the server that I was running the Admin Console. I also tried using the admin console on a client machine running Windows XP, but this had the same result.

We recently had to download an update to the server. This didn't relate to FileMaker itself (just a security update), but a restart was required for it to take affect. After the restart, the Admin Console listed the databases correctly.

Could this just be a FileMaker Server bug?

[Steven H. Blackwell]

Could this just be a FileMaker Server bug?

Yes. Or an OS bug. Or a Java bug. Or just some conflict amongst all three. Hope you closed files and then stopped FMS daemon before rebooting.

Steven