Thread: some activex bug

some activex bug

From

Date:

02 January 2003, 11:08:42

hi there,

I've installed CygWin, cygipc 1.13-2 and postgres on a Windows NT workstation
(nt4, service pack 6, ie6, ns7.0 etc). Postgres is running fine (tested with
console psql on an new testdatabase under cygwin), and downloaded and installed
the newest (pgadmin2-1_4_12) pgadmin with msi.

Unfortunately, starting up pgAdmin causes an alert window drop up (by clicking
ok pgadmin quits). The window message is also saved in a "C:\pgAdmin II_XXX.Log"
file, and contains always the same message:

2003-01-02 13:35:17 -
*******************************************************************
2003-01-02 13:35:17 - Error(s)
2003-01-02 13:35:17 -
*******************************************************************
2003-01-02 13:35:17 - Error in pgAdmin II:basMisc.BuildPluginsMenu: 429 -
ActiveX component can't create object

2003-01-02 13:35:17 - Windows Version: Windows NT v4.0 build 1381 Service Pack 6
2003-01-02 13:35:17 - pgSchema Version: 1.4.12

Though I'm not a windows developer, I've tried to debug this issue using various
sysinternals' tools (filemon, etc.) but have found nothing interesting. Closing
other running apps (even cygipc and postgres daemon...) did not help either.
Is this an issue of pgAdmin2, my NT installation, or anything else (dll hell,
etc.)? Do you know a workaround?

Best regards,

trajic
www.demoscene.hu

Re: some activex bug

From

"Dave Page"

Date:

02 January 2003, 11:32:30


> -----Original Message-----
> From: - [mailto:turcsat@dragon.klte.hu]
> Sent: 02 January 2003 13:06
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] some activex bug
>
>
> hi there,
>
> I've installed CygWin, cygipc 1.13-2 and postgres on a
> Windows NT workstation
> (nt4, service pack 6, ie6, ns7.0 etc). Postgres is running
> fine (tested with
> console psql on an new testdatabase under cygwin), and
> downloaded and installed
> the newest (pgadmin2-1_4_12) pgadmin with msi.
>
> Unfortunately, starting up pgAdmin causes an alert window
> drop up (by clicking
> ok pgadmin quits). The window message is also saved in a
> "C:\pgAdmin II_XXX.Log" file, and contains always the same message:
>
> 2003-01-02 13:35:17 -
> *******************************************************************
> 2003-01-02 13:35:17 - Error(s)
> 2003-01-02 13:35:17 -
> *******************************************************************
> 2003-01-02 13:35:17 - Error in pgAdmin
> II:basMisc.BuildPluginsMenu: 429 -
> ActiveX component can't create object

Hi,

This sounds like a plugin is registered on yoour system but doesn't
exist. Have you tried and then removed the Migration wizard for example?
Something else you could try is uninstalling pgAdmin, then re-installing
a *full* installation.

Regards, Dave.

Re: some activex bug

From

Date:

02 January 2003, 14:31:42

   > This sounds like a plugin is registered on yoour system but doesn't
   > exist. Have you tried and then removed the Migration wizard for example?
   > Something else you could try is uninstalling pgAdmin, then re-installing
   > a *full* installation.

Huh, here's the whole story...

I've never used pgAdmin before, that's why I've chosen a custom - full -
installation even for the first time.
After receiving your email, I've tried the following 'tricks' (every '-' means a
unique, single step - after which I've tried re-running pgAdmin):

- MSI Installer's repair option (at the Control panel/Add/remove programs)
- reinstalled pgAdmin (complete install)
- I've tried to add the Migration wizard by copying it into the Plugins
directory.
- uninstalled pgAdmin - restarted NT - reinstalled pgAdmin,
- uninstalled only plugins,
- uninstalled only extensions,
- reinstalled pgAdmin with different user option (only admin user/all users)
- I've taken a look at it with MS WinDebug (windbg)
- and even examined using regmon.exe
    I've found some missing registry keys, that's why I was google-ing a CLSID
    that wasn't found by pgAdmin. They pointed to ADODB, MDAC pages and stuff.
    I've went to microsoft.com/data, and downloaded mdac_typ.exe (redistributable)
    installed - and guess what? It helped! :DDD I'm wondering why an
    updated pc (like this one) needed this, but hey, it's working now :)
    Maybe you should put some verify-routine into pgAdmin that checks for
    an up-to-date MDAC installed, or just drop this info on the troubleshooting
    page!

Have a nice day!
Regards,

trajic
www.demoscene.hu