Lists: | pgsql-ports |
---|
From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Kent Morrison" <kmorrison(at)metrostudy(dot)com>, <pgsql-ports(at)postgresql(dot)org> |
Subject: | Re: Problem Installing on Windows 2000 Server |
Date: | 2005-12-21 19:06:41 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE6C7DC4@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-ports |
>
> With each version 8.0.4 and 8.1.1, I have tried at different times to
> install:
>
> * on a clean machine with no folders or users previously created.
> * on a machine with E:/Program Files/PostgreSQL created and
> the service user created with permissions set to full control
>
> I got the following message:
>
> Failed to run initdb: 1!
> Please see the logfile in "E:\Program
> Files\PostgreSQL\8.1\tmp\initdb.log
>
> The log file:
>
> creating directory E:/ProgramFiles/PostgreSQL/8.1/data/global
> ... initdb:
> could not create directory "E:/Program Files": File exists
> initdb: removing contents of data directory "E:/Program
> Files/PostgreSQL/8.1/data"
>
> The odd thing is that this log entry happens even when the
> PostgresSQL folder was not present before the install program
> ran. What would cause the install program to be able to
> create the PostgresSQL directory during one step and then not
> be able to create other directories later?
The first steps are run as your account, the step that fails runs as the
service user.
> Searching the archives, it appears that others have had this
> problem in the past and it was a permissions problem, but as
> I stated before, I tried creating the service account before
> the install and granting it full control of the install dir
> and it still did not work.
>
> Anyone have any ideas?
I've seen similar issues when there was a directory or file on the
system called C:\Program, causing windows to get confused abotu the
path. Any chance that's your case?
//Magnus
From: | "Kent Morrison" <kmorrison(at)metrostudy(dot)com> |
---|---|
To: | "Magnus Hagander" <mha(at)sollentuna(dot)net>, <pgsql-ports(at)postgresql(dot)org> |
Subject: | Re: Problem Installing on Windows 2000 Server |
Date: | 2005-12-21 19:23:27 |
Message-ID: | JMEOICPKFKLLGODKMNGOMELICLAA.kmorrison@metrostudy.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-ports |
Yes there is a c:\Program Files directory.
I tried to install to e:\PostgreSQL and still got the same error.
-----Original Message-----
From: pgsql-ports-owner(at)postgresql(dot)org
[mailto:pgsql-ports-owner(at)postgresql(dot)org]On Behalf Of Magnus Hagander
Sent: Wednesday, December 21, 2005 1:07 PM
To: Kent Morrison; pgsql-ports(at)postgresql(dot)org
Subject: Re: [PORTS] Problem Installing on Windows 2000 Server
>
> With each version 8.0.4 and 8.1.1, I have tried at different times to
> install:
>
> * on a clean machine with no folders or users previously created.
> * on a machine with E:/Program Files/PostgreSQL created and
> the service user created with permissions set to full control
>
> I got the following message:
>
> Failed to run initdb: 1!
> Please see the logfile in "E:\Program
> Files\PostgreSQL\8.1\tmp\initdb.log
>
> The log file:
>
> creating directory E:/ProgramFiles/PostgreSQL/8.1/data/global
> ... initdb:
> could not create directory "E:/Program Files": File exists
> initdb: removing contents of data directory "E:/Program
> Files/PostgreSQL/8.1/data"
>
> The odd thing is that this log entry happens even when the
> PostgresSQL folder was not present before the install program
> ran. What would cause the install program to be able to
> create the PostgresSQL directory during one step and then not
> be able to create other directories later?
The first steps are run as your account, the step that fails runs as the
service user.
> Searching the archives, it appears that others have had this
> problem in the past and it was a permissions problem, but as
> I stated before, I tried creating the service account before
> the install and granting it full control of the install dir
> and it still did not work.
>
> Anyone have any ideas?
I've seen similar issues when there was a directory or file on the
system called C:\Program, causing windows to get confused abotu the
path. Any chance that's your case?
//Magnus
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.3/209 - Release Date: 12/21/2005
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.3/209 - Release Date: 12/21/2005