I have filemaker server 10 running on a Winserver 2008 box and haven't seen that one even though I have three different back up schedules.
Don't know if it's a factor, but there was an update for FMS 10 released and the version info your report suggests you haven't downloaded and installed it. You might go to Filemaker's download screen and download it to see if it makes any difference.
I experience the exact same problem. I've tried several different locations for the backup folder but nothing validates. The path is still marked as Not Valid, or "Ogiltig sökväg" in swedish. In my case the backups doesn't seem to run either. I'm looking forward to any input on this. TIA.
I'm using FileMaker Server 188.8.131.52 (latest as of today) on Windows Server 2003 SP2.
What's the exact path you're using? This folder is local to the machine, correct?
If the backupfolder is located on a share (samba, NFS, NAS etc), the account running FM must have full write access to that share. I dont know what account the FM services run under by default on Win.X since i only have FM experience running under OSX. Its however very common that such services by default would not run under any account with network sharing access (eg local system). This problem should not appear if the backups folder path is local to the machine *in most cases*, however do make sure that the account running the process has read, write and list permissions under NTFS security tab. This is a common "error" i see many MS SQL users ask about, the most common error in this case is that the service runs under a local account with no network priviledge and the folder path is on a network path and not locally.
Am running FM Server under Windows now, the Filemaker Server Service by default runs under the local system account. Meaning you cant schedule backups if they are pointed to a share or unc path unless you change the account the service runs under. Hope this helps.
Just had this issue on FMS12. I can't reboot the server now. But the backups are working, but I deleted one because of the invalid path. So I need to restore it once I reboot the server.