Hi Jan,

many thanks for your help.
I think i found a solution now. The method i described as 2. works. I had to install an IIS feature to make it work.
In case someone else is having this problem, i found the solution here:
https://forums.iis.net/t/1237168.aspx?What+is+the+Application+Initialization+module+to+download+for+IIS+8+5+in+windows+server+2012+R2+

About using IISNode at all: Yes i could run a service too. But i need the IIS anyway for other things and i am used to it.
So no it is working and i will leave it this way for now.

Thanks again for help, your support is really great!

The reason for this problem is that the node.exe process is not running after the IIS application pool is restartet. It gets startet when the first HTTP request arrives.

I can see 3 possible solutions

1. retry on error as you suggested. Disadvantage is, it has to be implemented everywhere the jsreport api is called.
2. somehow modify the IIS configuration so the node.exe process gets startet automatically without an external request
   this is described here: https://tomasz.janczuk.org/2013/07/application-initialization-of-nodejs.html
   but so far i can't get it to work as it should.
3. I hoped it would be possible to modify the jsreport startup so it would start rendering after init complete.
   Somehow like this (pseudo solution).

var startoptions = {autostart:false}
var jsreport = require('jsreport')(startoptions) // require without starting immediately

jsreport.init().then(function () 
{
	// running
	console.log ("jsreport initialized")
        jsreport.start() // then start after init complete
}).catch(function (e) 
{
	// error during startup
	console.error(e.stack)
	process.exit(1)
})

Hi,

i have the problem that the first Request to the Reportserver after the website is started always fails with this Error:
Not initialized, you need to call jsreport.init().then before rendering

This is my server.js:

var jsreport = require('jsreport')()

jsreport.init().then(function () 
{
	// running
	console.log ("jsreport initialized")
}).catch(function (e) 
{
	// error during startup
	console.error(e.stack)
	process.exit(1)
})

All following requests are ok.
So the problem seems to be, that after Applikation start the jsreport starts rendering before the initialisation is complete.

How can i fix this problem?

Yes, that was the problem.
It is working now.
Many thanks for your support!!!

Here are the logs after one Request over IISNode.
I only made my license key unreadable.

iisnode - WEBSERVICES-7176-stderr-1530007798682.txt
2018-06-26T10:09:59.244Z - debug: Writing extension locations cache to C:\Windows\TEMP\jsreport\core\locations.json

2018-06-26T10:09:59.244Z - debug: Discovered 31 extensions

2018-06-26T10:09:59.510Z - debug: Extension authentication was disabled

2018-06-26T10:09:59.853Z - debug: Extension authorization was disabled

2018-06-26T10:10:00.322Z - debug: Creating samples is disabled

2018-06-26T10:10:00.322Z - debug: Extension public-templates was disabled

IISNode - WEBSERVICES-7176-stdout-1530007798682.txt

2018-06-26T10:09:59.213Z - info: Initializing jsreport@2.1.0 in C:\nvm\v8.11.1\ mode using configuration file: jsreport.config.json

2018-06-26T10:09:59.213Z - info: Searching for available extensions in C:\www\jsreport Version 2.1.0\

2018-06-26T10:09:59.228Z - info: Extensions location cache contains up to date information, skipping crawling in C:\www\jsreport Version 2.1.0\node_modules\

2018-06-26T10:09:59.244Z - info: Found 31 extensions

2018-06-26T10:09:59.291Z - info: Setting process based strategy for rendering. Please visit http://jsreport.net/learn/configuration for information how to get more performance.

2018-06-26T10:09:59.306Z - info: Using extension handlebars

2018-06-26T10:09:59.306Z - info: Using extension import-export

2018-06-26T10:09:59.463Z - info: Using extension templates

2018-06-26T10:09:59.463Z - info: Using extension jsrender

2018-06-26T10:09:59.463Z - info: Using extension authentication

2018-06-26T10:09:59.510Z - info: Using extension freeze

2018-06-26T10:09:59.510Z - info: Using extension cli

2018-06-26T10:09:59.510Z - info: Using extension express

2018-06-26T10:09:59.635Z - info: Using extension debug

2018-06-26T10:09:59.650Z - info: Using extension tags

2018-06-26T10:09:59.650Z - info: Using extension data

2018-06-26T10:09:59.650Z - info: Using extension fs-store

2018-06-26T10:09:59.853Z - info: fs store underlying changes synchronization with studio is disabled

2018-06-26T10:09:59.853Z - info: Using extension authorization

2018-06-26T10:09:59.853Z - info: Using extension html-to-xlsx

2018-06-26T10:09:59.994Z - info: html-to-xlsx detected chrome as available html engine

2018-06-26T10:09:59.994Z - info: Using extension child-templates

2018-06-26T10:09:59.994Z - info: Using extension browser-client

2018-06-26T10:09:59.994Z - info: Using extension chrome-pdf

2018-06-26T10:09:59.994Z - info: Using extension pdf-utils

2018-06-26T10:10:00.119Z - info: Using extension version-control

2018-06-26T10:10:00.150Z - info: Using extension reports

2018-06-26T10:10:00.150Z - info: Using extension text

2018-06-26T10:10:00.150Z - info: Using extension base

2018-06-26T10:10:00.166Z - info: Using extension studio

2018-06-26T10:10:00.213Z - info: Using extension licensing

2018-06-26T10:10:00.228Z - info: Using extension scripts

2018-06-26T10:10:00.244Z - info: Using extension assets

2018-06-26T10:10:00.244Z - info: Using extension scheduling

2018-06-26T10:10:00.291Z - info: Using extension xlsx

2018-06-26T10:10:00.322Z - info: Using extension sample-template

2018-06-26T10:10:00.322Z - info: Using extension resources

2018-06-26T10:10:00.322Z - info: Using extension public-templates

2018-06-26T10:10:00.338Z - info: fs store is persisting using fs

2018-06-26T10:10:00.338Z - info: fs store is synchronizing using fs

2018-06-26T10:10:00.369Z - info: fs store is loading data

2018-06-26T10:10:00.463Z - info: fs store is initialized successfully

2018-06-26T10:10:00.478Z - info: Creating default express app.

2018-06-26T10:10:00.494Z - info: jsreport server successfully started on http port: 5488

2018-06-26T10:10:00.494Z - info: Verifying license key xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

2018-06-26T10:10:00.510Z - info: License key for perpetual license verified against jsreport.license.json file

2018-06-26T10:10:00.510Z - info: reporter initialized

jsreport - reporter.log
2018-06-26T10:09:59.213Z - info: Initializing jsreport@2.1.0 in C:\nvm\v8.11.1\ mode using configuration file: jsreport.config.json
2018-06-26T10:09:59.213Z - info: Searching for available extensions in C:\www\jsreport Version 2.1.0
2018-06-26T10:09:59.228Z - info: Extensions location cache contains up to date information, skipping crawling in C:\www\jsreport Version 2.1.0\node_modules
2018-06-26T10:09:59.244Z - info: Found 31 extensions
2018-06-26T10:09:59.291Z - info: Setting process based strategy for rendering. Please visit http://jsreport.net/learn/configuration for information how to get more performance.
2018-06-26T10:09:59.306Z - info: Using extension handlebars
2018-06-26T10:09:59.306Z - info: Using extension import-export
2018-06-26T10:09:59.463Z - info: Using extension templates
2018-06-26T10:09:59.463Z - info: Using extension jsrender
2018-06-26T10:09:59.463Z - info: Using extension authentication
2018-06-26T10:09:59.510Z - info: Using extension freeze
2018-06-26T10:09:59.510Z - info: Using extension cli
2018-06-26T10:09:59.510Z - info: Using extension express
2018-06-26T10:09:59.635Z - info: Using extension debug
2018-06-26T10:09:59.650Z - info: Using extension tags
2018-06-26T10:09:59.650Z - info: Using extension data
2018-06-26T10:09:59.650Z - info: Using extension fs-store
2018-06-26T10:09:59.853Z - info: fs store underlying changes synchronization with studio is disabled
2018-06-26T10:09:59.853Z - info: Using extension authorization
2018-06-26T10:09:59.853Z - info: Using extension html-to-xlsx
2018-06-26T10:09:59.994Z - info: html-to-xlsx detected chrome as available html engine
2018-06-26T10:09:59.994Z - info: Using extension child-templates
2018-06-26T10:09:59.994Z - info: Using extension browser-client
2018-06-26T10:09:59.994Z - info: Using extension chrome-pdf
2018-06-26T10:09:59.994Z - info: Using extension pdf-utils
2018-06-26T10:10:00.119Z - info: Using extension version-control
2018-06-26T10:10:00.150Z - info: Using extension reports
2018-06-26T10:10:00.150Z - info: Using extension text
2018-06-26T10:10:00.150Z - info: Using extension base
2018-06-26T10:10:00.166Z - info: Using extension studio
2018-06-26T10:10:00.213Z - info: Using extension licensing
2018-06-26T10:10:00.228Z - info: Using extension scripts
2018-06-26T10:10:00.244Z - info: Using extension assets
2018-06-26T10:10:00.244Z - info: Using extension scheduling
2018-06-26T10:10:00.291Z - info: Using extension xlsx
2018-06-26T10:10:00.322Z - info: Using extension sample-template
2018-06-26T10:10:00.322Z - info: Using extension resources
2018-06-26T10:10:00.322Z - info: Using extension public-templates
2018-06-26T10:10:00.338Z - info: fs store is persisting using fs
2018-06-26T10:10:00.338Z - info: fs store is synchronizing using fs
2018-06-26T10:10:00.369Z - info: fs store is loading data
2018-06-26T10:10:00.463Z - info: fs store is initialized successfully
2018-06-26T10:10:00.478Z - info: Creating default express app.
2018-06-26T10:10:00.494Z - info: jsreport server successfully started on http port: 5488
2018-06-26T10:10:00.494Z - info: Verifying license key xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2018-06-26T10:10:00.510Z - info: License key for perpetual license verified against jsreport.license.json file
2018-06-26T10:10:00.510Z - info: reporter initialized

Hello,

i have IISNode 1.10.0 working with IISNode. I wanted to upgrade to V2, this is what i have done:

• copied V1 directory to new V2 directory
• ran migration commands
• gave permissions to new directory to ApplicationPool User
• created new Website in IIS
• copied web.config from V1 installation
• copied server.js from V1 installation

Current Status:
When i start jsreport V2 from command line with npm start it is working. I can access it under localhost:5488.
When i call the IIS Website i get this error

Any ideas what the problem is?
When i change the IIS Website Path to that of V1 installation it shows the V1 website, so IIS settings should be ok.