Export script executes from command line but not scheduler

RouterOS Scripting
1

The following simple export script runs fine from the command line, but fails after printing “Beginning” to the log when run from either the scheduler or by clicking the “Run Script” button in WebFig:

:log info "Beginning"
/export compact file=test.rsc
:log info "Done."

Full properties:

name="test" owner="admin" policy=reboot,read,write,policy,test,password,sniff,sensitive last-started=sep/08/2014 15:09:35 run-count=6 
     source=
       :log info "Beginning"
       /export compact file=test.rsc
       :log info "Done."

Version (MikroTik RB1100AHx2):

> /system package print
Flags: X - disabled 
 #   NAME                                                  VERSION                                                  SCHEDULED              
 0   system                                                6.12                                                                            
 1   ntp                                                   6.12                                                                            
 2   ppp                                                   6.12                                                                            
 3   dhcp                                                  6.12                                                                            
 4   security                                              6.12                                                                            
 5   advanced-tools

Unfortunately, no error code or message is returned (as captured by ) and wrapping the command in a try/catch block triggers the catch in all but the command line. I wish to schedule this as part of a bigger backup operation, but I have been unsuccessful in getting over this hurdle. For whatever reason, “/system backup” works fine, but “/backup file” consistently fails from the scheduler.

2

Any ideas on why “/export file=” might not run from the Scheduler?

Stepping back a bit, do I even need the export AND backup files? Would “/system backup” suffice in case of emergency?

3

I am also having this issue and I just wanted to bump this thread for visibility. I can use the backup command from scheduler, but not the export command.

4

FWIW, I was able to circumvent this bug by pasting the code directly into the scheduler. Whereas the old “On Event” value referenced my script by name (which wasn’t clear in my original post), the new “On Event” value is the script itself; i.e. the code is entered directly into the scheduler. For reasons unknown, the export seems to fail only when the script is called directly from the scheduler.