3 Replies Latest reply on Jul 8, 2011 7:31 AM by kgreen

    Schedules which were working now say "“not a valid path”

    kgreen

      Title

      Schedules which were working now say "“not a valid path”

      Your post

      I've been using a Daily Schedule to back up my databases to a folder on the local C: drive, and it's been working flawlessly for months.

      I haven't touched or changed anything on server in all that time, but noticed today (7/7/2011) that the Schedules List says that the schedule was Last Completed was on 7/4/2011, and the Next Run is scheduled for 7/5/2011.

      Editing the existing schedule, or attempting to create a new one results in "not a valid path" for any folder I choose, including the default folder by clicking Restore, such as:

      filewin:/C:/Backups/Daily/

      filewin:/C:/Filemaker/

      filewin:/C:/Program Files (x86)/FileMaker/FileMaker Server/Data/Backups/

      Curiously though, the Schedule is apparently still being run daily, as my backup files are being updated as expected. The Log Viewer also shows the Schedule as being started and completed without errors.

      The only problem is I can no longer set a filepath in a new or existing schedule, and the Schedules List shows incorrect Last Completed and Next Run dates.

      I'm probably going to restart the server at some point to see if that fixes things, but it makes me nervous to not know what may have happened?

      Server version 11.0.3.309

      fm3.jpg

        • 1. Re: Schedules which were working now say "“not a valid path”
          TSDuck

          Hi kgreen:

          Thanks for posting.

          What version of Windows are you currently running FileMaker Server 11 on, and were any updates made on your server recently?

          Have you checked the permissions on the both your default folder and the alternate folder path you are using? 

          To check the permissions, navigate to filewin:/C:/Program Files (x86)/FileMaker/FileMaker Server/Data/Backups/.  Right click the backups folder and go to properties.  Click on the security tab, which will list the groups and usernames.  Make sure the administrator group has full control enabled.  Next, make sure the folder has the “everyone” user group.  If the “everyone” group is missing, it can cause a folder path not validate in the admin console.

          TSDuck

          FileMaker, Inc.

          • 2. Re: Schedules which were working now say "“not a valid path”
            kgreen

            Thanks TSDuck,

            We're using Windows 7 Professional. No updates were done to the server, not even to Java. I intentionally leave it as untouched as possible ;)

            I peeked at the permissions mentioned, and all seems well. Administrators and Everyone have full control of the folders.

            The odd thing is FileMaker Server apparently does have access to the filepaths it says are invalid, as the backup files are still being updated as expected, even though the Admin Console says the path is invalid and that the last backup was 7/4/2011. The Schedules are apparently running correctly, it's just that the Admin Console thinks the last successful backup was on 7/4/2011, and that every filepath is invalid ;)

            Here's a clue though: I see in the Event Log entry for 7/4/2011 a Warning saying:

            Administrator "fmsadmin" no longer responding; connection closed. (192.168.0.192)
            Event ID: 628
            7/4/2011 2:31pm

            Could be coincidence, but it looks like after this event, the Admin Console stopped reporting the status of the Schedules correctly (it still thinks 7/4/2011 was the last good run), and it thinks any and every filepath is invalid, lol.

            I'm sure a reboot would fix it, I was just hoping to find an easier fix without needing to kick everyone out of the system.

            • 3. Re: Schedules which were working now say "“not a valid path”
              kgreen
              Aha, using "fmsadmin restart adminserver" from the command prompt fixed it! The console now displays the correct schedule information, and pathnames are marked Valid once again :) Still no idea what happened to make the Admin Console report incorrectly, but at least there was no downtime for the users to fix things...