You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have used tedious succesfully in the past to connect to various stanadrd SQL Server instances. I have spent the whole day to try and connect to an database hosted on Azure, to no avail.
At this point I have activated the debug options (available here) and it seems that it fact a connection is established, but is closed right after the login has been sent. The encrypt option is set to true, and I can connect to the database with the same credentials by other means (SSMS).
This might have something to do with the recent Availability Group stuff I put in place. Could you possibly post the debug output so I can take a look?
I've set up a (temporary) test case so that no information contained in the output should be sensitive. This way you could also reproduce the behaviour.
I was unable to connect to that particular server, but I did notice that you had encrypt: true directly on the config object. That flag needs to be on the options object (per the docs). Can you move that over and see if that clears things up?
I don't think inferring configuration is the road we want to go down. What might be a good idea is to include a section in the documentation about connecting to Azure.
Activity
rossipedia commentedon Sep 11, 2014
This might have something to do with the recent Availability Group stuff I put in place. Could you possibly post the debug output so I can take a look?
mcartoixa commentedon Sep 11, 2014
Sorry, my previous post did not make it clear: the output is available at https://gist.github.com/mcartoixa/c32db3279510775c8ce4
rossipedia commentedon Sep 12, 2014
Hmmm.... that's odd. can you set the following debug options and show me the output?
This'll turn on all available debugging output.
mcartoixa commentedon Sep 12, 2014
I've set up a (temporary) test case so that no information contained in the output should be sensitive. This way you could also reproduce the behaviour.
The connection options:
The debug output:
rossipedia commentedon Sep 13, 2014
I was unable to connect to that particular server, but I did notice that you had
encrypt: truedirectly on the config object. That flag needs to be on theoptionsobject (per the docs). Can you move that over and see if that clears things up?mcartoixa commentedon Sep 13, 2014
Indeed, the correct answer was RTFM. Sorry for wasting your time.
Keep up the good work 👍
rossipedia commentedon Sep 13, 2014
No worries! That's what we're here for :)
vvo commentedon Jan 22, 2015
@rossipedia Should we automatically put encrypt:true when windows.net in the hostname?
bretcope commentedon Jan 22, 2015
I don't think inferring configuration is the road we want to go down. What might be a good idea is to include a section in the documentation about connecting to Azure.
arthurschreiber commentedon Jan 23, 2015
Like this?
ccf8573
bretcope commentedon Jan 24, 2015
yes... like that.
TyrionLanister commentedon Aug 3, 2015
Hej @rossipedia @arthurschreiber @vvo
I am connecting to an Azure database. But I am receiving connnection error with code: Elogin
Detailed log is here=>
I am new to tedious. Any help will be greatly appreciated.
@bretcope Is there any updates on documentation for connecting to azure
ReadySoftTeam commentedon Jul 5, 2019
A mi me funciono de esta forma:
const sequelize = new Sequelize('DB Name', 'Username', 'Password', {
host: 'Host',
dialect: 'mssql',
dialectOptions: {
options: {
encrypt: true,
}
}
});