OK, the log starts at
22:09:40 Log opened, server 8.1.0
and ends with
22:23:27 ERROR: The 1-line data file doesn't exist!
22:23:27 Weather Unsafe! data-file acquisition error:
The 1-line data file doesn't exist!
So it only took 14 minutes for the file to become inaccessible. The code that is executing at the time is
Code:
If Not FSO.FileExists(c_sLogFileName) Then ' Catch vaporized data file
c_dtLastPollTime = Now ' Keep poll interval for possible long delay (NetBIOS)
PollFail &H80040407, "The 1-line data file doesn't exist!"
End If
Note that this code has executed 143 times before this, successfully, so the name of the file being sought (which is established when setting up the weather server) is valid and the file was found there 143 times before it disappeared.
I am most concerned, though, with ACP's potential reaction to this condition. The other times you reported it, the weather was declared unsafe as a result of the data file disappearing. But the last time you reported, the Scheduler died as though ACP died. I really need to know what is going on with ACP when you see the scheduler give up like this. Please see (a) is ACP running? (b) if so does it look alive? and (c) are there any popup boxes showing maybe underneath ACP. The file disappearing should definitely not be fatal to the weather server and ACP so I need more info. I'm sorry, I'm flying blind.
Again I plan to make Scheduler's reaction more palatable, but that won't help the basic problem. I should also note that there are plenty of others using the AAG CloudWatcher successfully and reliably.
While I'm thinking about this, are you have it write the file to maybe a network drive or cloud drive where a syncing process may make the file invisible briefly. If there is a non-zero chance the file could be invisible, however briefly, then we will absolutely see this eventually.