edb installation failed for pgadmin when username is Chinese under c:\user #106
Comments
sandeep-edb
pushed a commit
that referenced
this issue
May 6, 2024
…mining the user running the installer using whoami utility. The reason for Installation failure with chinese username is probably the encoding the cmd.exe uses to output the text
sandeep-edb
pushed a commit
that referenced
this issue
May 6, 2024
…mining the user running the installer using whoami utility. The reason for Installation failure with chinese username is probably the encoding the cmd.exe uses to output the text
sandeep-edb
pushed a commit
that referenced
this issue
May 7, 2024
…authority\system' user accounts
icacls returns "ERROR: no mapping between account names and security IDs was done"
when the user running the installer is 'nt authority\system' and for the username value the
variable ${system_username} is used.
Similar error is seen for the Chinese user account and the username is determined by
running whoami utility.
Hence, use the conditions for both these scenarios.
Tested in UI and unattended modes
sandeep-edb
pushed a commit
that referenced
this issue
May 7, 2024
…authority\system' user accounts
icacls returns "ERROR: no mapping between account names and security IDs was done"
when the user running the installer is 'nt authority\system' and for the username value the
variable ${system_username} is used.
Similar error is seen for the Chinese user account and the username is determined by
running whoami utility.
Hence, use the conditions for both these scenarios.
Tested in UI and unattended modes
sandeep-edb
pushed a commit
that referenced
this issue
May 7, 2024
…authority\system' user accounts
icacls returns "ERROR: no mapping between account names and security IDs was done"
when the user running the installer is 'nt authority\system' and for the username value the
variable ${system_username} is used.
Similar error is seen for the Chinese user account and the username is determined by
running whoami utility.
Hence, use the conditions for both these scenarios.
Tested in UI and unattended modes
sandeep-edb
pushed a commit
that referenced
this issue
May 7, 2024
…authority\system' user accounts
icacls returns "ERROR: no mapping between account names and security IDs was done"
when the user running the installer is 'nt authority\system' and for the username value the
variable ${system_username} is used.
Similar error is seen for the Chinese user account and the username is determined by
running whoami utility.
Hence, use the conditions for both these scenarios.
Tested in UI and unattended modes
|
committed the fix on all supported branches. the fix will be available in this week's minor updates |
|
Hi Sandeep,
Thanks for your quick feedback and effort.
Best regards,
Joe
***@***.***
From: Sandeep Thakkar
Date: 2024-05-07 13:45
To: EnterpriseDB/edb-installers
CC: rdczhzq; Author
Subject: Re: [EnterpriseDB/edb-installers] edb installation failed for pgadmin when username is Chinese under c:\user (Issue #106)
committed the fix on all supported branches. the fix will be available in this week's minor updates
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I tried to use postgresql-16.2-1-windows-x64 to install on a window laptop. I got the following error message and installation aborted.
After using another not edb installation:pgadmin4-8.5-x64.exe, I successfully installed pgadmin by changing the default install path from c:\user\老王 to all English character path.
The text was updated successfully, but these errors were encountered: