Re: Ynt: Ynt: Server Closed the connection unexpectedly

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Mehmet Keleş <mehmetkeles(at)outlook(dot)com>
Cc: pgsql-odbc <pgsql-odbc(at)postgresql(dot)org>
Subject: Re: Ynt: Ynt: Server Closed the connection unexpectedly
Date: 2017-04-20 13:56:25
Message-ID: d705cfee-91c2-5193-ac6c-395ce67a3647@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-odbc

On 04/19/2017 10:54 PM, Mehmet Keleş wrote:

Please reply to list also.
Ccing list.
> Hello,
>
> yes it's name is MongoDB BI Connector,

Which version as it seems MongoDB has changed from Postgres to MySQL
between version 1.x and 2.0?

>
> I followed this webinar,
>
> https://www.mongodb.com/blog/post/analyzing-data-in-microsoft-excel-with-the-mongodb-connector-for-bi

That is for the Postgres(BI Connector version 1.x) version. If you are
using that version then the video applies. The important part would be
the port number. In your original post you used 27017 as the port for
the BI Connector(Postgres). 27017 is the default port for MongDB so I
doubt it is the port for the BI Connector as that is a separate server.
If you are indeed using the Postgres version of Bi Connector then you
need to find what port it is running on and use that as the port number
in the ODBC setup.

If you are running BI Connector 2+ then you will need to use the MySQL
ODBC driver. See here:

https://docs.mongodb.com/bi-connector/master/installation/#connect-to-the-bi

>
>
> and download the ODBC driver from
> here: https://www.postgresql.org/ftp/odbc/versions/msi/ but i didn't
> connect via this driver.
>
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-odbc by date

  From Date Subject
Next Message Adrian Klaver 2017-04-20 14:28:08 Re: Ynt: Ynt: Server Closed the connection unexpectedly
Previous Message Inoue, Hiroshi 2017-04-19 06:35:23 Re: PGAPI_ProcedureColumns and no support for table output arguments