Failed to load collection Issue



  • Hi, we faced problem that we can't access js report server. We saw reporter.log and found the below error. Could you teach us workaround or what we can investigate this problem?

    reporter.log
    2019-03-12T08:02:44.560Z - info: Initializing jsreport@1.5.1 in development mode using configuration file dev.config.json
    2019-03-12T08:02:45.138Z - info: Searching for available extensions in [JSReport Folder]
    2019-03-12T08:02:45.153Z - info: Extensions location cache contains up to date information, skipping crawling in [JSReport Folder]\node_modules
    2019-03-12T08:02:45.435Z - info: Found 29 extensions
    2019-03-12T08:02:45.481Z - debug: Writing extension locations cache to C:\Windows\TEMP\jsreport-temp\extensions\locations.json
    2019-03-12T08:02:45.497Z - debug: Discovered 29 extensions
    2019-03-12T08:02:45.497Z - info: Using extension import-export
    2019-03-12T08:02:46.075Z - info: Using extension tags
    2019-03-12T08:02:46.091Z - info: Using extension templates
    2019-03-12T08:02:46.091Z - info: Using extension jsrender
    2019-03-12T08:02:46.091Z - info: Using extension cli
    2019-03-12T08:02:46.106Z - debug: Extension authentication is disabled, skipping
    2019-03-12T08:02:46.106Z - info: Using extension debug
    2019-03-12T08:02:46.106Z - info: Using extension express
    2019-03-12T08:02:46.325Z - info: Using extension fop-pdf
    2019-03-12T08:02:46.325Z - info: Using extension handlebars
    2019-03-12T08:02:46.325Z - info: Using extension phantom-pdf
    2019-03-12T08:02:46.450Z - info: Using extension fs-store
    2019-03-12T08:02:46.966Z - info: Using extension images
    2019-03-12T08:02:46.997Z - info: Using extension data
    2019-03-12T08:02:46.997Z - info: Using extension child-templates
    2019-03-12T08:02:47.013Z - info: Using extension licensing
    2019-03-12T08:02:47.169Z - info: Using extension authorization
    2019-03-12T08:02:47.169Z - debug: Extension authorization was disabled
    2019-03-12T08:02:47.169Z - info: Using extension text
    2019-03-12T08:02:47.169Z - info: Using extension reports
    2019-03-12T08:02:47.247Z - info: Using extension resources
    2019-03-12T08:02:47.263Z - info: Using extension browser-client
    2019-03-12T08:02:47.278Z - info: Using extension studio
    2019-03-12T08:02:47.403Z - info: Using extension html-to-xlsx
    2019-03-12T08:02:47.575Z - info: Using extension scripts
    2019-03-12T08:02:47.638Z - info: Using extension assets
    2019-03-12T08:02:47.653Z - info: Using extension scheduling
    2019-03-12T08:02:47.700Z - info: Using extension xlsx
    2019-03-12T08:02:47.982Z - info: Using extension sample-template
    2019-03-12T08:02:48.044Z - info: Using extension public-templates
    2019-03-12T08:02:48.060Z - debug: Extension public-templates was disabled
    2019-03-12T08:02:48.075Z - info: Initializing fs storage at [JSReport Folder]\data
    2019-03-12T08:02:49.419Z - error: Failed to load collection reports Error: ENOENT: no such file or directory, open '[JSReport Folder]\data\reports~'
    at Error (native)
    2019-03-12T08:02:49.419Z - error: Failed to load collection schedules Error: ENOENT: no such file or directory, open '[JSReport Folder]\data\schedules~'
    at Error (native)
    2019-03-12T08:02:49.435Z - error: Failed to load collection tasks Error: ENOENT: no such file or directory, open '[JSReport Folder]\data\tasks~'
    at Error (native)
    2019-03-12T08:02:49.435Z - error: Error occured during reporter init Error: ENOENT: no such file or directory, open '[JSReport Folder]\data\reports~'
    at Error (native)
    2019-03-12T08:25:12.509Z - info: Initializing jsreport@1.5.1 in development mode using configuration file dev.config.json



  • This is a quite old version, not sure if this was fixed in some of the newer versions, but we don't have such bug reported now.

    I would recommend jsreport version update If you can't update and don't use extensions reports and scheduling, just disable them.

    {
      "scheduling": {
        "enabled": false
      }
    }
    

Log in to reply
 

Looks like your connection to jsreport forum was lost, please wait while we try to reconnect.