From: | Dale Seaburg <kg5lt(at)verizon(dot)net> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Strange error in Windows 10 Pro |
Date: | 2018-04-24 02:09:31 |
Message-ID: | b8898288-f6c6-0ed3-33aa-178766daafed@verizon.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks to Moreno and Igor for the Event Viewer suggestions. Here are a
few lines of log file where they differ between a good install and a bad
incomplete install. The good install was from my Shop PC with Windows
10 Pro.
BTW, I had success with another Dell PC with Win 10 Pro about 4 months
ago. This problem appears to be a one-off.
Good Install:
/Called AclCheck(C:\Program Files\PostgreSQL\9.6\data)//
//Called IsVistaOrNewer()...//
// 'winmgmts' object initialized...//
// Version:10.//
// MajorVersion:10//
//Executing icacls to ensure the SHOP-PC\Dale account can read the path
C:\Program Files\PostgreSQL\9.6\data//
// Executing batch file 'rad0510A.bat'...//
// processed file: C:\Program Files\PostgreSQL\9.6\data//
//Successfully processed 1 files; Failed processing 0 files/
Bad Install:
/Called AclCheck(D:\PostgreSQL\9.6\data)//
//Called IsVistaOrNewer()...//
// 'winmgmts' object initialized...//
// Version:10.//
// MajorVersion:10//
//Executing icacls to ensure the WINDOWS-6BEGVO1\don king account can
read the path D:\PostgreSQL\9.6\data//
// Executing batch file 'rad6DBC7.bat'...//
//
/Notice the last four lines of the *Good Install* vs the last two lines
of the *Bad Install*. There is no indication of processing, or whether
it was successful or not in the bad install.
As you can see, I even took Igor's suggestion to install in a non-system
(Program Files) path, to no success.
Again, not sure what to do. Open for suggestions... I'm almost ready
to call Dell and complain about a "bad" Win 10 Pro install.
Dale
//
On 4/23/2018 9:54 AM, Moreno Andreo wrote:
> Il 21/04/2018 22:35, Adrian Klaver ha scritto:
>> On 04/21/2018 01:08 PM, Dale Seaburg wrote:
>>> Thanks Adrian for the suggestion of running the installer with Admin
>>> rights. Unfortunately, I get the same results. It appears that all
>>> of the folders within C:\Program Files\PostgreSQL\9.6 path are
>>> created, and populated, BUT, when the items in the *data* folder are
>>> to be created, or copied into, it leaves an error message as noted
>>> previously. The *data* folder is empty.
>>>
>>> It's almost as if the PC is missing a critical .dll needed in the
>>> *data* folder filling function (my guess).
>>>
>>> Again, I am at a loss as to what to do.
>>
>> Have you looked at the system logs e.g. Event Viewer?
>
> If you look in %temp%", there should be one or more files named
> "bitrock_installer" or something similar (search for "bitrock"),
> that's the setup log with what's went good and what not.
> Another hint I had since 9.1 times (it was 2012, I guess) was to avoid
> installing Postgres under system folders (c:\program files, c:\users,
> and so on) because in some cases there could be some nasty
> behaviors... try installing on something like c:\PG96...
>
> HTH
> Cheers,
> Moreno.-
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Dale Seaburg | 2018-04-24 02:49:04 | Re: Strange error in Windows 10 Pro |
Previous Message | Tim Cross | 2018-04-23 22:05:04 | Re: Postgres and fsync |