Обсуждение: PostgreSQL 16.3 install fails on Windows with domain user if a local user exists with the same name
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
Hi Klaus
Thanks for the report. Let me check and get back to you
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.MyDomainShortly 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 writableThe 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\DomAdminInstalling 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 supportKlaus
Sandeep Thakkar
Hi Klaus,
I've sent you the link to download the test installer with the fix in another thread. Is it possible for you to confirm the fix so the upcoming minor release can include this change?
Thanks
I've sent you the link to download the test installer with the fix in another thread. Is it possible for you to confirm the fix so the upcoming minor release can include this change?
Thanks
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.MyDomainShortly 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 writableThe 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\DomAdminInstalling 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 supportKlaus
Sandeep Thakkar