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

SQL Server connector apparently using wrong port #9226

Open
JohnAtFenestra opened this Issue Jan 7, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@JohnAtFenestra
Copy link

JohnAtFenestra commented Jan 7, 2019

Bugs

If you're filing an issue about a bug please include as much information
as you can including the following.

  • Metabase version: 0.31.2

  • Metabase hosting environment: Elasticbeanstalk and local Windows

  • Metabase internal database: SQL Server

  • Repeatable steps to reproduce the issue

We attempted to connect to an SQL Server RDS instance. We received a timeout error. I replicated the issue on a Windows Server box using metabase.jar where I knew the server had access to the RDS.

I noticed that the default port for SQL Server is showing as 1433.

In utter desperation, I hand entered 1433 into the field. The server connected immediately.

Apparently, what is showing in the port field as the placeholder text is not identical to what is being used by Metabase as the connection string for SQL Server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment