• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Creating physical hosting error

testmogo

New Pleskian
Server operating system version
Windows Server 2022 Standard
Plesk version and microupdate number
Plesk Obsidian Web Admin Se Edition Version 18.0.54 Update #3
Please help

Creating physical hosting
System user update is failed: Unable to create system user: Unable to execute usermng: no such table: ImpersonationUsers
at Unable to execute console command: '--add'(vconsoleapp::start line 95)
at Unable to execute command: '"C:\Program Files (x86)\Plesk\admin\bin\usermng" --add "--name=xdddd.co_mnr10kowt3h" "--password=*" "--home=C:/Inetpub/vhosts/xdddd.com"'(vconsoleapp::run line 117)
(Error code 1)

Thank you advance
 
Hi @testmogo, the issue was known in a much older Plesk version, but was fixed sind 18.0.46. If the above suggestion by @scsa20 does not help, you could try

C:> plesk sbin upgrade --repair
C:> plesk sbin upgrade.exe --deferred

If that does not help either, please open a ticket with Plesk support and mention these internal IDs: PPP-57663, PPS-12933, PPS-14660, PPS-13932. Engineers would like to check the issue directly on your server. https://support.plesk.com
 
Hi @testmogo, the issue was known in a much older Plesk version, but was fixed sind 18.0.46. If the above suggestion by @scsa20 does not help, you could try

C:> plesk sbin upgrade --repair
C:> plesk sbin upgrade.exe --deferred

If that does not help either, please open a ticket with Plesk support and mention these internal IDs: PPP-57663, PPS-12933, PPS-14660, PPS-13932. Engineers would like to check the issue directly on your server. https://support.plesk.com
It helps a lot, thank you!

Just for others, if someone has the same issue:

1. Open CMD like administrator
2. C:> plesk sbin upgrade --repair
3. C:> plesk sbin upgrade.exe --deferred
4. "%plesk_cli%\repair.exe" --synchronize-impersonation-storage

Thanks everybody for the help.
 
Back
Top