Cumulus Support

I have a few files that are set up to be processed and then output the result to a folder inside the CumulusMX folder on one of my computers. I have 2 files listed in the "Extra Web Files" under settings. One uploads to my webserver and the other is NOT saving locally. I can send both to my server and then get them back via HTTP File Settings, but would obviously like to skip the upload and immediate download. Not sure if the format of the Destination Filename is incorrect. Log states:

2024-12-16 13:15:53.581 FTP[160]: Error uploading \\WXPC\CumulusMX\Tony\bit1.txt : Error while uploading the file to the server. See InnerException for more info.
2024-12-16 13:15:53.581 FTP[160]: Inner Exception: Code: 553 Message: Can't open that file: No such file or directory

The bolded/underlined text is the Destination Filename. Changing it to C:\CumulusMX.... doesn't change anything. Again, works fine if the destination is a web server.

Any help would be greatly appreciated!

Hi,

Not sure if the format of the Destination Filename is incorrect.

I had a couple extra web files working and these are set as relative to the \CumulusMX folder i.e. \CumulusMX\interface/ and \CumulusMX\web/
Enjoy,
Paul

golfgod56 wrote: ↑Mon 16 Dec 2024 7:46 pm The bolded/underlined text is the Destination Filename. Changing it to C:\CumulusMX.... doesn't change anything. Again, works fine if the destination is a web server.

Any help would be greatly appreciated!

Your local computer is not running an ftp server, so you cannot upload to it. Instead you should use ”local copy” feature, that is also defined under internet settings before uploads. I haven’t used it myself, so I can’t give exact instructions.

As stated above you are not running a local FTP server so you cannot FTP to do this.

If you want a copy of any of the files that MX produces in Internet Settings > Web/Upload Site there is a setting called Local copy destination folder path:, set this to the local path on your PC. Then any files you are telling it to copy in Standard File Settings, Graph File Settings and Daily Graph File Settings will be copied there.

In your case as you are using extra web files to do this copy you will have to set up a network Disk i.e. Z:\ that points to \\WXPC\CumulusMX\Tony\ ( I have assumed that \\XWPC is the network computer name) and then tell CumulusMX to copy it to Z:\ in the destination folder i.e. Z:\bit1.txt.

@SamiS, @water01,
What @golfgod56 wants to do will work fine in current CMX that was implemented some time ago, process a template file and uploadsave it (send/save to the local C:\CumulusMX\subfolder) to whatever subfolder he wishes, rather than to a remote site - see the settings snippet in my earlier post. He just needs to have the correct name and path of the Local Filename, and also in the Destination Filename, and Enable. On the Destination Filename side, tick: Process if it is a template with webtags, Realtime if needed, I don't believe you have to tick Upload, UTF8 and Binary, and not sure on End of Day or Incremental as my extra files didn't need that.

Maybe I haven't explained it well.

Enjoy,
Paul

Thanks all of you for the ideas. Was able to find a solution:

Almost too easy....UNCHECK Upload on the Extra Web Files page.

MXDiags now is showing:

2024-12-16 16:14:40.607 Realtime[30]: Copying extra file \\WXPC\CumulusMX\web\bit1.tmp to C:\CumulusMX\web\temp.txt
2024-12-16 16:14:40.607 Realtime[30]: Processing extra file \\WXPC\CumulusMX\web\bit1.tmp
2024-12-16 16:14:40.620 Realtime[30]: Real time upload files starting
2024-12-16 16:14:40.620 Realtime[30]: Real time files complete

Again, thanks for the input and a starting point

PaulMy wrote: ↑Mon 16 Dec 2024 9:53 pm Maybe I haven't explained it well.

We speak the same language but not.

You were right on saying that the destination filename and path must be correct. But the actual error seen on the log was caused by the upload being ticked, and thus cmx trying to use ftp instead of file copy. And that bit of information was missing from your original answer.

Anyway, glad to see that the problem was resolved.