I will try installing this in server & will let you know how it goes. thanks

I get the following message.

The program can not start because MSVCR120.dll is missing from your computer, try reinstall to fix the problem.

Hi Blaha, regarding the issue you mentioned about the absolute path, I worked around that by creating similar folder structure in the server as well. Now I get a different error message which I believe is not related to the path issue you mentioned above. The recent error message I receive now is below.

2017-04-12T12:56:33.625Z - error: Error when processing render request Error during rendering report: Command failed: C:\JSTest\node_modules\wkhtmltopdf-installer\vendor\wkhtmltopdf.exe --debug-javascript --proxy proxyservername:8080 --margin-top 20mm --header-spacing 2 --header-html file:///C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6header.html toc C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.html C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.pdf
Error: Command failed: C:\JSTest\node_modules\wkhtmltopdf-installer\vendor\wkhtmltopdf.exe --debug-javascript --proxy proxyservername:8080 --margin-top 20mm --header-spacing 2 --header-html file:///C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6header.html toc C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.html C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.pdf

at ChildProcess.exithandler (child_process.js:206:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:877:16)
at Socket.<anonymous> (internal/child_process.js:334:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at Pipe._handle.close [as _onclose] (net.js:498:12) requestId=1

2017-04-12T12:56:33.627Z - error: Error during processing request: http://localhost:5488/api/report details: Error during rendering report: Command failed: C:\JSTest\node_modules\wkhtmltopdf-installer\vendor\wkhtmltopdf.exe --debug-javascript --proxy proxyservername:8080 --margin-top 20mm --header-spacing 2 --header-html file:///C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6header.html toc C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.html C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.pdf
Error: Command failed: C:\JSTest\node_modules\wkhtmltopdf-installer\vendor\wkhtmltopdf.exe --debug-javascript --proxy proxyservername:8080 --margin-top 20mm --header-spacing 2 --header-html file:///C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6header.html toc C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.html C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.pdf

at ChildProcess.exithandler (child_process.js:206:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:877:16)
at Socket.<anonymous> (internal/child_process.js:334:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at Pipe._handle.close [as _onclose] (net.js:498:12)

Sorry, Please ignore the above exception. I actually get the below error, I have replaced actual proxy server name from the error message I actually get. Please advice

2017-04-12T12:56:33.625Z - error: Error when processing render request Error during rendering report: Command failed: C:\JSTest\node_modules\wkhtmltopdf-installer\vendor\wkhtmltopdf.exe --debug-javascript --proxyservername:8080 --margin-top 20mm --header-spacing 2 --header-html file:///C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6header.html toc C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.html C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.pdf
Error: Command failed: C:\JSTest\node_modules\wkhtmltopdf-installer\vendor\wkhtmltopdf.exe --debug-javascript --proxy proxyservername:8080 --margin-top 20mm --header-spacing 2 --header-html file:///C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6header.html toc C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.html C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.pdf

at ChildProcess.exithandler (child_process.js:206:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:877:16)
at Socket.<anonymous> (internal/child_process.js:334:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at Pipe._handle.close [as _onclose] (net.js:498:12) requestId=1

2017-04-12T12:56:33.627Z - error: Error during processing request: http://localhost:5488/api/report details: Error during rendering report: Command failed: C:\JSTest\node_modules\wkhtmltopdf-installer\vendor\wkhtmltopdf.exe --debug-javascript --proxy proxyservername:8080 --margin-top 20mm --header-spacing 2 --header-html file:///C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6header.html toc C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.html C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.pdf
Error: Command failed: C:\JSTest\node_modules\wkhtmltopdf-installer\vendor\wkhtmltopdf.exe --debug-javascript --proxy proxyservername:8080 --margin-top 20mm --header-spacing 2 --header-html file:///C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6header.html toc C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.html C:\Users\pxa0683\AppData\Local\Temp\5\jsreport-temp\74179660-1f7f-11e7-8fe4-d124996c7ce6.pdf

at ChildProcess.exithandler (child_process.js:206:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:877:16)
at Socket.<anonymous> (internal/child_process.js:334:11)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)
at Pipe._handle.close [as _onclose] (net.js:498:12)

Hi Blaha,
Thanks again. I tried copying my local application to server & tried launching hello world template. That worked successfully. I am using wkhtmltopdf extension in my project report which fails with following error. Could you please advise what could be wrong here? The same report works in my local instance.

2017-04-12T12:34:02.653Z - error: Error when processing render request Error during rendering report: spawn C:\JSTest\node_modules\wkhtmltopdf-installer\vendor\wkhtmltopdf.exe ENOENT Error: spawn C:\JSTest\node_modules\wkhtmltopdf-installer\vendor\wkhtmltopdf.exe ENOENT
at exports._errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9) requestId=1
2017-04-12T12:34:02.658Z - error: Error during processing request: http://localhost:5488/api/report details: Error during rendering report: spawn C:\JSTest\node_modules\wkhtmltopdf-installer\vendor\wkhtmltopdf.exe ENOENT Error: spawn C:\JSTest\node_modules\wkhtmltopdf-installer\vendor\wkhtmltopdf.exe ENOENT
at exports._errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)

Hi Blaha,
Thanks for your response.
This app was installed by my colleague using npmbox as the running npm command directly from the server is violating our network security policy.
No I could not find phantomjs.exe in node_modules\phantomjs\lib\phantom\ folder

Please advise how do I overcome this

Hi,
We have installed a fresh instance of jsreport in server yesterday. When we tried to run a test template with just some hello world text we get the following error. We are using handlebars & phantom pdf as the options(the default ones). Can you please advise what could possibly be wrong here? Thanks in advance.

Error message from Log file below:

2017-04-12T10:38:01.904Z - error: uncaughtException: Bad argument date=Wed Apr 12 2017 06:38:01 GMT-0400 (Eastern Daylight Time), pid=10308, uid=null, gid=null, cwd=C:\IIS_dependencies\npmbox, execPath=C:\Program Files\nodejs\node.exe, version=v6.9.2, argv=[C:\Program Files\nodejs\node.exe, C:\IIS_dependencies\npmbox\server.js], rss=83066880, heapTotal=63000576, heapUsed=51406776, loadavg=[0, 0, 0], uptime=1477847.5843038, trace=[column=null, file=null, function=TypeError, line=null, method=null, native=true, column=26, file=internal/child_process.js, function=ChildProcess.spawn, line=289, method=spawn, native=false, column=9, file=child_process.js, function=exports.spawn, line=380, method=spawn, native=false, column=15, file=child_process.js, function=Object.exports.execFile, line=143, method=exports.execFile, native=false, column=34, file=C:\IIS_dependencies\npmbox\node_modules\phantom-html-to-pdf\lib\dedicatedProcessStrategy.js, function=null, line=47, method=null, native=false, column=10, file=C:\IIS_dependencies\npmbox\node_modules\graceful-fs\graceful-fs.js, function=null, line=43, method=null, native=false, column=15, file=fs.js, function=FSReqWrap.oncomplete, line=123, method=oncomplete, native=false], stack=[TypeError: Bad argument, at TypeError (native), at ChildProcess.spawn (internal/child_process.js:289:26), at exports.spawn (child_process.js:380:9), at Object.exports.execFile (child_process.js:143:15), at C:\IIS_dependencies\npmbox\node_modules\phantom-html-to-pdf\lib\dedicatedProcessStrategy.js:47:34, at C:\IIS_dependencies\npmbox\node_modules\graceful-fs\graceful-fs.js:43:10, at FSReqWrap.oncomplete (fs.js:123:15)]

Thanks for the suggestion.
However now I am facing another issue. I am told that, In the server, I can not run npm command at all which means I can not run the "npm install jsreport-wkhtmltopdf" command. Is there any other option available so I can download the server & also enable the wkhtmltopdf extension by not using npm install command mentioned above in the server?

Hi Blaha,

        I am unable to install the server in my client environment due to firewall restrictions. The IT support team are unwilling to let the download due to breach in security policies. Hence I am trying to use Executable option mentioned in 

https://github.com/jsreport/jsreport/releases/latest

I was able to install jsreport in my local machine(not server) using jsreport-configure option mentioned in the documentation. But I am unable to install the wkhtmltopdf extension. I get the following message when I try to install wkhtmlto pdf.

C:\Users\pxa0683\Downloads\jsreport-win>npm install jsreport-wkhtmltopdf
jsreport-server@ C:\Users\pxa0683
`-- jsreport-wkhtmltopdf@1.3.0

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\c
okidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents
1.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"
)
npm WARN jsreport-server@ No description
npm WARN jsreport-server@ No repository field.
npm WARN jsreport-server@ No license field.

I have used a different port number(5489) for the executable server version as I have another instance(full download) at 5488 which is working fine.

Please advice how we can go about resolving this issue. I have used wkhtmltopdf extensively in the only template that I have created.

Regards

Prabu