-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error connecting to SQL2014 -> ConnectionError: Connection is closed. #1
Comments
Please let me know which version of jsreport you have |
Also please make sure your TCP/IP protocol is enabled in the SQL Server Configuration Manager |
Maybe you can also change I tried it on my windows and I'm able to connect, however I see some issues with the latest version UI which I'll quickly fix |
And I'm in Europe, so another timezone delay :)
|
Hi Jan, Yeah, it's a good excuse isn't it :-) :-) Good news, its working now. It was the combination of:
I did try both, but not at the same time until now. Awesome work, As a token of my appreciation, I'm happy to send you a draft for updating the help pages to include these tips. I can also take the hint if you decide to thankfully decline or not to add them :-) :-) Cheers! |
On Win2012 R2 Server
Using this config:
I'm getting this error
2016-07-19T11:51:41.953Z - error: Error occured during reporter init ConnectionE
rror: Connection is closed.
at D:\Deploy\dev\NodeJS\node_modules\mssql\lib\main.js:1519:17
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
From previous event:
at Array.reduce (native)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
ConnectionError: Connection is closed.
at D:\Deploy\dev\NodeJS\node_modules\mssql\lib\main.js:1519:17
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
From previous event:
at Array.reduce (native)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
Any ideas?
The text was updated successfully, but these errors were encountered: