did you try installing with developer as well?
Maybe some of the scripts to install the pg cluster and repository are in the developer installation…
I would try that if I were you, and you are not obliged to use developer on this machine anyway.
Ok, I just tried full installation of Servoy (including Developer, etc). — after installation the database directory is empty. The problem persists -even with full installation. See the icons in the explorer/database image capture below:
[attachment=1]developerExplorerDBCapture.GIF[/attachment]
I tried disable/enable to enable the server and I got the following error:
[attachment=0]connectionToServoyRepository.GIF[/attachment]
I am not sure if the problem is with the scripts that installs the pg cluster, but it might be. PosrgreSQL installation in Windows has shown some challenges in the past (for what I’ve seen in other Forums, but I really don’t know anything about PostgreSQL in practice).
I’ll try the installation in another XP computer. If the problem persists, I’ll reach out to Servoy Support.
Ok, I now installed Servoy 5.2.1 using the .jar installer on different computer running Windows XP Professional…and what it happened to Rob happened to me: the database cluster was nicely created! My problem is solved!
The problem is on the other computer. However, I has to say that in that computer I had installed and uninstalled 5.2.1. The first installation (which I did a few days ago) worked fine. I uninstalled it later, and when I installed again yesterday, it’s when I started having problems.
I wonder if this problem has something to do with PostgreSQL. I said this because in an stand alone installation of PostgreSQL 9 I experienced that it all works fine until I stop the database server. When I tried to start the Server again I got the following message: could not create file “postmaster.opts”: Permission denied. This is what I did to start the server:
C:\Program Files\PostgreSQL\9.0\bin>pg_ctl start -D "C:\Program Files\PostgreSQL\9.0\data"
server starting
C:\Program Files\PostgreSQL\9.0\bin>2010-09-21 16:33:36 PDT LOG: could not create file "postmaster.opts": Permission denied
It’s most likely that I just don’t know what I am doing with PostgreSQL.
In any case, the problem of an empty database directory after installation is solved. Thank you for helping me!
You can simply start/stop Pg using the Services control panel (like any other services).
When you use the commandline you have to do it using the postgres (system) user, that’s why you had the permission denied error.
ROCLASI:
You can simply start/stop Pg using the Services control panel (like any other services).
When you use the commandline you have to do it using the postgres (system) user, that’s why you had the permission denied error.
I see. I did the installation in my development machine. I’m the administrator. The postgres (system) user is the superuser set during installation. Correct?
I just ran into the same problem on a brand new XP SP3 32-bit, with the latest Windows updates and Java 1.6.0_21
I have built a few Virtual Machines to have every kind of OS at hand, and had no problem in most OS, but when I installed Servoy 5.2 in that one, I ended up with an empty database folder in /application_server/
On Windows 2003/2008 or Vista/Win 7, I would have thought of a permission issue (run the installer as administrator), but on XP it’s never been a problem before.
End of the line: I strongly suspect some of the latest windows security updates to have messed up a few things and the installer is now broken.
Maybe there is an issue with IzPack (the packaged installer that Servoy uses).
I did an install with -DTRACE=true, see the attached result, it is clear in there that the calls to the creation of the database cluster fails…
Possibly the other related installation problem on 2008 R2 is coming from the same issue.
Looking deeper in that issue, it seems that it could be related to a missing Assembly.
I have tons of these errors in the EventViewer at the time of the installation (always coupled, one after the other):
So basically you would need the Visual C++ Runtimes. Which is not there by default on a clean XP install.
I probably had it on other systems coming from some other installation…
Probably the best would be to integrate in the installer and register it on XP.
[EDIT] Actually installing the Visual C++ 2005 Runtimes (and reboot) didn’t fix the issue
Tomorrow I’ll install Visual C++ Runtime and run the installer. I’m sure it will work.
Patrick your suggestion of putting it in the installer is a good one. I have the impresion that when you install PostgreSQL using EnterpriseDB binary, Visual C++ is installed.
Well I got an answer from Dave Page (the maintainer of the EDB installer (among other things within the project)):
The latest for VC++ 2005 should work (ie. 2005 SP1 with ATL fix), if it was built with VC++ 2005, or the latest 2008 version. It really depends how the binaries were built.
If I try to start postgres from command line (pc_ctl start…) all works fine,I’m able to also to start more than one instance of postgres service BUT
if I try to installa postgress as a windows service than the error 1057 occour without a good description,only (the traslation is done by myself,so it can be little different from the real)"pc_ctl : Is not possible to register the service “myservice”:error code: 1057.
I’m using windows xp sp3 and I’m an administrator,I’ve tried also with the “administrator” account but the I obtain the same result.
Actually I’ve tried only Servoy’s bundled version.About third part I’ve downloaded Postgress 8.4.4.1 (At now I’m using pgAdmin III) but I don’t try it for postgres service installation
The third party (EnterpriseDB) installer installs it as window service. But if you had Servoy Developer running when you ran the installer then the new instance will use port 5433 (since Servoy was using the default (5432) port). Else it is using the default port and you will have troubles using the bundled PostgreSQL instance (since it wants to use port 5432).
So if you want to use both at the same time you need to change the port number on one of the instances.