Re: ODBC driver crashing both Enterprise manager and pgAdminII?

I believe I've narrowed it down some.  I moved the postgresql server
Instance to another machine and the ODBC connection and subsequent
Import ran flawlessly.  The versions were similar but not identical,
And I don't currently have cycles to do an exact version to version
Comparison.  That being said, my working assumption is that there is
A network level difference.  That could either be in the driver or
The card.

My best guess is that the odbc driver code expects some level of
Reliability in the connection and the port is either jabbering or
Colliding.  Not much else would make sense.

-----Original Message-----
From: Jeff Eckermann [mailto:jeff_eckermann@yahoo.com]
Sent: Friday, May 16, 2003 12:53 PM
To: greg.maples@linkify.com; pgsql-odbc@postgresql.org
Subject: Re: [ODBC] ODBC driver crashing both Enterprise manager and
pgAdminII?

Are you able to make an ODBC connection from any other
application, e.g. MS Access, MS Excel?
If you continue to have trouble, please post your
driver settings, which may provide a clue.

--- Greg Maples <greg.maples@linkify.com> wrote:
>
> Hi.  I've taken a look at the archives and not seen
> this error
> documented.  I also installed on a second machine to
> verify the
> behavior and it repeated itself.
>
> MS Windows 2000, SP3, v 5.00.2915
> postgres odbc driver file version 7.2.5.0,
> Enterprise manager console v. 1.2
> pgAdminII v. 1.4.12
>
> Behavior 1:
>     Launch pgAdminII
>     Select connect from file
>     Enter connection data
>         <IP Addr>, port 5432, login name postgres
>
>     Result is:
>         "Program Error"
>         pgAdmin2.exe has generated errors and will be
> closed
>         by windows.  You will need to restart the program.
>         An error log is being created.
>
> Behavior 2:
>     Run Enterprise manager
>     Create System DSN
>     Connect to server group,
>     Connect to server,
>     Select DTS,
>     Select Local Packages
>     New package, Connection
>     Other connection, PostgreSQL,
>     System DSN, etc.
>
>     Result is:
>         "Program Error"
>         mmc.exe has generated errors and will be closed
>         by windows.  You will need to restart the program.
>         An error log is being created.
>
> Error/Etc Logs:
>
> mylog:
>     [1348]globals.extra_systable_prefixes = 'dd_;'
> pgAdminII log:
>     2003-05-12 14:56:35 - SQL (template1): SELECT
> version()
>     2003-05-12 14:56:35 - SQL (template1): SELECT
> datlastsysoid FROM
> pg_database WHERE datname = 'template1'
>
>     2003-05-12 14:56:35 -
>
*******************************************************************
>     2003-05-12 14:56:35 - Error(s)
>     2003-05-12 14:56:35 -
>
*******************************************************************
>     2003-05-12 14:56:35 - Error in pgAdmin
> II:frmConnect.cmdConnect_Click: -2147417848 -
> Automation error
>     The object invoked has disconnected from its
> clients.
>
>     2003-05-12 14:56:35 - Windows Version: Windows 2000
> v5.0 build 2195 Service
> Pack 3
>     2003-05-12 14:56:35 - pgSchema Version: 1.4.12
>     2003
>
>
============================================================
>
> Any help would be appreciated.  I'd *really* like to
> be able to
> evaluate transitioning from mssql2000 to postgresql,
> but I'm stopped
> at the moment by this odbc problem.
>
> Thanks in advance.  Please reply directly to greg at
> linkify.com
> and I'll post any interesting results to the list.
>
> Greg
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org


__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com