pgAdmin III v 1.20.0 and Slony-I v2.2.4 and Postgresql v9.4.4

Team

This seems like a recurring problem, "Slony-I creation scripts not available; only joining possible".

My setup consist of a fresh install,
Windows 2012 R2
Using the Win x86-64 download of postgresql-9.4.4-1-windows-x64 from http://www.enterprisedb.com/products-services-training/pgdownload
Installed
Postgresql 9.4.4
And using Stackbuilder downloaded edb_slony_i_pg94 and installed Slony-I v2,2,4

In pgAdmin III, I point my "Sony-I path" to C:\Program Files\PostgreSQL\9.4\share which is where the .sql files live.

When I select "New Sony-I cluster" I get the pop-up window but at the bottom it says "Slony-I creation scripts not available; only joining possible".
Hence I can't start my configuration.

Below id the output of pg_config on my Windows 2012 R2 machine.

The issue seems to be related to the naming of the .sql files in the share directory and the name of the slony1_funcs.dll file in the lib directory and what it expects to see.
Is there a simple fix to this?

Thanks

Aurelio
(M) +44 (0)7714 215454
(T) +44 (0)207 607 4224

C:\Users\Administrator>pg_config
BINDIR = C:/PROGRA~1/POSTGR~1/9.4/bin
DOCDIR = C:/PROGRA~1/POSTGR~1/9.4/doc
HTMLDIR = C:/PROGRA~1/POSTGR~1/9.4/doc
INCLUDEDIR = C:/PROGRA~1/POSTGR~1/9.4/include
PKGINCLUDEDIR = C:/PROGRA~1/POSTGR~1/9.4/include
INCLUDEDIR-SERVER = C:/PROGRA~1/POSTGR~1/9.4/include/server
LIBDIR = C:/PROGRA~1/POSTGR~1/9.4/lib
PKGLIBDIR = C:/PROGRA~1/POSTGR~1/9.4/lib
LOCALEDIR = C:/PROGRA~1/POSTGR~1/9.4/share/locale
MANDIR = C:/Program Files/PostgreSQL/9.4/man
SHAREDIR = C:/PROGRA~1/POSTGR~1/9.4/share
SYSCONFDIR = C:/Program Files/PostgreSQL/9.4/etc
PGXS = C:/Program Files/PostgreSQL/9.4/lib/pgxs/src/makefiles/pgxs.mk
CONFIGURE = --enable-thread-safety --enable-integer-datetimes --enable-nls --wit
h-ldap --with-ossp-uuid --with-libxml --with-libxslt --with-tcl --with-perl --wi
th-python
VERSION = PostgreSQL 9.4.4

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________