Page 1 of 1

Have tried everything imo!!

PostPosted: Sat Apr 18, 2009 2:16 am
by deepsquat
Hi,

Ive tried absolutely everything to get Postgres working.

Whenever i use the isnstaller it always stops and the end "failed to create process to run initdb" or similar.

Ive uninstalled it, deleted in from program files, reinstalled it. Ive gone to the cmd line and "net user postgres /delete" and it will complete that successfully but i still get the same install problems.

I tried vesper's post on installing initdb manually, that still didnt work. It deletes c:/data at the end. A copy is below.

Can anyone help me??? thx

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\WINDOWS\ServicePackFiles\i386>cd "c:\program files\postgresql\8.3\bin"

C:\Program Files\PostgreSQL\8.3\bin>initdb -W -A md5 -D c:/data
The files belonging to this database system will be owned by user "user".
This user must also own the server process.

The database cluster will be initialized with locale English_United States.1252.

The default database encoding has accordingly been set to WIN1252.
The default text search configuration will be set to "english".

creating directory c:/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 10
selecting default shared_buffers/max_fsm_pages ... 400kB/20000
creating configuration files ... ok
creating template1 database in c:/data/base/1 ... initdb: could not execute comm
and ""C:/Program Files/PostgreSQL/8.3/bin/postgres.exe" --boot -x1 -F ": No erro
r
initdb: removing data directory "c:/data"

C:\Program Files\PostgreSQL\8.3\bin>initdb -W -A md5 -D c:/data
The files belonging to this database system will be owned by user "user".
This user must also own the server process.

The database cluster will be initialized with locale English_United States.1252.

The default database encoding has accordingly been set to WIN1252.
The default text search configuration will be set to "english".

creating directory c:/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 10
selecting default shared_buffers/max_fsm_pages ... 400kB/20000
creating configuration files ... ok
creating template1 database in c:/data/base/1 ... initdb: could not execute comm
and ""C:/Program Files/PostgreSQL/8.3/bin/postgres.exe" --boot -x1 -F ": No erro
r
initdb: removing data directory "c:/data"

C:\Program Files\PostgreSQL\8.3\bin>

Re: Have tried everything imo!!

PostPosted: Sat Apr 18, 2009 2:42 am
by deepsquat
Btw my Anti virus is Mc afee Viruscan Enterprise 8.5i

I have no idea how to disable it fwiw. Ive tried through windows security and through the actual program

Re: Have tried everything imo!!

PostPosted: Sat Apr 18, 2009 9:00 am
by kraada

Re: Have tried everything imo!!

PostPosted: Sun Apr 19, 2009 3:29 am
by deepsquat
Thanks, but its def not Mcafee thats causing the problem.

I have the exact same Mcafee version on both computers and ive never had a problem on my home computer with postgresql.
Is there anything else it could be??

Its driving me insane

Re: Have tried everything imo!!

PostPosted: Sun Apr 19, 2009 5:00 am
by deepsquat
Ive completely deleted/uninstalled mcafee and disbaled windows firewall and gone through all the procedures as before and have the same problem.

Not sure what else i can try?

Not sure whether its related, but whenever i try and access "cmd" when i click "Start" then "Run" it comes up with an error message saying "Windows cannot find cmd" This was happening before i removed mcafee anyway.

Thanks

Re: Have tried everything imo!!

PostPosted: Sun Apr 19, 2009 10:58 am
by APerfect10
It sounds like your Windows installation is corrupted. The command line execution is failing and you are not even able to open up a command prompt. :(

If you have your Windows XP CD, insert it and restart your computer then boot-up to the CD. There should be a repair function which will hopefully resolve the issue.

Best regards,

Derek

Re: Have tried everything imo!!

PostPosted: Tue Apr 21, 2009 8:13 am
by deepsquat
Thanks guys. A clean re-install of XP has fixed the problem. Appreciated!!!

highfalutin