Hello,
> -----Original Message-----
> From: Nicolas Huillard [mailto:nhuillard@ghs.fr]
> Sent: 26 October 1999 16:59
> To: pgsql-interfaces@postgreSQL.org
> Subject: [INTERFACES] pgAdmin connection error on NT and W98
<SNIP>
> The error occurs while opennign the main pgAdmin window :
This is a known bug that has been fixed for the next release! If you go to:
System -> Tracking
you will be asked if you wish to create some required tables.
> I then had the following error while trying to migrate an
> Access database (last button in the migration wizard) :
I can't reproduce this error at all. Does it still occur after the first
problem has been fixed? If so, please switch on logging (File -> Logging),
exit and restart pgAdmin and then re-create the error and send me the
logfile.
> Under NT:
> I cannot connect to Postgres using pgAdmin. I installed MDAC
> 2.1, then pgAdmin. The problem is that this machine is a very
> used server, and I cannot reboot it when I want, if I install
> something.
> The error is stored in VSErr.log, and not in pgAdmin.log :
Any errors that occur before pgAdmin has finished starting up will be logged
to VSErr.log. When a file is installed on a win32 machine, if an older
version is already on the system and is locked open, then the install
program will copy the new file to a temporary filename which will be moved
into place on reboot. This is essential for files such as the Visual C
runtime libraries that windows needs to startup and run.
To cut a long explanation short, you *must* reboot if you want things to
work correctly. I would suggest though that you should avoid running
anything (other than backup/server management software etc.) on a server
that is that critical.
Regards,
Dave.
--
Network & Systems Manager, The Vale Housing Association.
http://www.vale-housing.co.uk (Work)
http://www.pgadmin.freeserve.co.uk (Home of pgAdmin)
Beer can be a permanent solution, but only if you have enough of it!
