Internal server error accessing Pengines Admin area

#1

I have PEngines running on my Win 8.1 box. However, when I try to access the Admin area, after I log in (successfully) I get the error dump below.

# Internal server error

source_sink `'www/admin/server.html'' does not exist
In:
[23] throw(error(existence_error(source_sink,'www/admin/server.html'),_2692))
[19] http_dispatch:http_reply_file('www/admin/server.html',[],[protocol(http),...|...]) at c:/program files/swipl/library/http/http_dispatch.pl:988
[18] http_dispatch:call_action(pengines_server:http_reply_file('www/admin/server.html',[]),[protocol(http),...|...]) at c:/program files/swipl/library/http/http_dispatch.pl:935
[16] time:run_alarm_goal('$alarm'(20801924),http_dispatch:call_action(...,...,...)) at c:/program files/swipl/library/time.pl:145
[15] setup_call_catcher_cleanup(time:alarm(300,...,...,...),time:run_alarm_goal(...,...),_2886,time:remove_alarm_notrace(...)) at c:/program files/swipl/boot/init.pl:468
[8] httpd_wrapper:call_handler(pengines_server:http_dispatch,21,[protocol(http),...|...]) at c:/program files/swipl/library/http/http_wrapper.pl:320
[7] catch(httpd_wrapper:call_handler(...,21,...),error(existence_error(source_sink,'www/admin/server.html'),context(_3040,_3042)),httpd_wrapper:true) at c:/program files/swipl/boot/init.pl:386
[6] httpd_wrapper:handler_with_output_to(pengines_server:http_dispatch,21,[protocol(http),...|...],current_output,error(existence_error(source_sink,'www/admin/server.html'),context(_3124,_3126))) at c:/program files/swipl/library/http/http_wrapper.pl:297
[5] httpd_wrapper:handler_with_output_to(pengines_server:http_dispatch,21,[protocol(http),...|...],<stream>(000000C20C1FC530),error(existence_error(source_sink,'www/admin/server.html'),context(_3202,_3204))) at c:/program files/swipl/library/http/http_wrapper.pl:309

Note: some frames are missing due to last-call optimization.
Re-run your program in debug mode (:- debug.) to get more detail.

Is there a way that I can trigger the same code path from the SWI-Prolog REPL (i.e. - from within the main console program, not via a web page) so I can use the graphical debugger to hunt down the problem and fix it?