Re: PostgreSQL 16.3 install fails on Windows with domain user if a local user exists with the same name

Поиск
Список
Период
Сортировка
От Sandeep Thakkar
Тема Re: PostgreSQL 16.3 install fails on Windows with domain user if a local user exists with the same name
Дата
Msg-id CANFyU97471R9bP8wwb+jmqfNuD4KJ-482GTMEyoTZ7NbxuGU5A@mail.gmail.com
обсуждение исходный текст
Ответ на PostgreSQL 16.3 install fails on Windows with domain user if a local user exists with the same name  ("Klaus P." <kpi6288@gmail.com>)
Список pgsql-bugs
Hi Klaus

Thanks for the report. Let me check and get back to you

On Wed, Jun 12, 2024 at 9:21 PM Klaus P. <kpi6288@gmail.com> wrote:
First detected on a production system when trying to update from 16.2 to 16.3.
 
The problem is however reproducable with a fresh installation of version 16.3 and occurs under the following condition:
- A local user exists e.g. MyServer\DomAdmin and has a user profile under C:\Users\DomAdmin
- A domain user exists e.g. MyDomain\DomAdmin and has a user profile under C:\Users\DomAdmin.MyDomain

Shortly after starting an installation of 16.3 under the domain user, the following error occurs:
Error copying file from packed archive C:/Users/DomAdmin.MYDOMAIN/Downloads/postgresql-16.3-2-windows-x64.exe to C:/Users/DomAdmin.MYDOMAIN/AppData/Local/Temp/postgresql_installer_da4fcce335/prerun_checks.vbs:Destination not writable

The destination directory C:/Users/DomAdmin.MYDOMAIN/AppData/Local/Temp/postgresql_installer_da4fcce335 exists in the correct directory but it is owned by the local user MyServer\DomAdmin instead of MyDomain\DomAdmin

Installing 16.3. with the local administrator works without a problem.
In our case, the setup is however part of another application which must run under a domain user.

Thank for your support

Klaus


--
Sandeep Thakkar


В списке pgsql-bugs по дате отправления:

Предыдущее
От: PG Bug reporting form
Дата:
Сообщение: BUG #18511: changing global certificate directory path
Следующее
От: PG Bug reporting form
Дата:
Сообщение: BUG #18512: Backend memory leak when using command parameters after generating notifications