Resolved no such table: ImpersonationUsers at Unable to execute console command: '--add'(vconsoleapp::start line 95) at Unable to execute command: ...

[Ebrahim A. Senejani]

Plesk 18.0.40 on Windows Server 2019
While adding new domain get the following error:
no such table: ImpersonationUsers
at Unable to execute console command: '--add'(vconsoleapp::start line 95)
at Unable to execute command: 'D:\Plesk\admin\bin\usermng --add "--name=example.com" "--password=*" "--home=D:/Inetpub/vhosts/example.com"'(vconsoleapp::run line 117)

I have found this but the problem is my license has no support to submit a ticket to Plesk.
Can you please someone help me out?

 

[IgorG]

Please try to fix it with the following steps:

1. Download the empty database scheme.
2. Go to %plesk_dir%admin\db (just paste this path in Windows Explorer to open) and create a copy of the original ImpersonationCache.db file.
3. Replace the original ImpersonationCache.db file with the downloaded.
4. Start a command prompt as an Administrator and run the following command to sync impersonation storage with the Plesk database:
   

   C:\> "%plesk_cli%\\repair.exe" --synchronize-impersonation-storage

 

[Ebrahim A. Senejani]

Thanks a lot, Igor, the issue is solved.

 

[bittu.john08]

Help me , when entering the cmd access is denied. This app can't run on your pc.

 

[soris1989]

Help me , when entering the cmd access is denied. This app can't run on your pc.

try open cmd as an administrator

 

[binu22]

hello man i can pay to teach me how to fix this issue please

 

[AlexLaforge]

Still occurring with Plesk Obsidian 18.0.67 Update 2: Incredible !

 

[Sebahat.hadzhi]

@AlexLaforge , as far as I am aware, this issue could be caused due to ImpersonationCache.db corruption, why the corruption occurred is difficult to say without server access. Were you able to solve the issue following Igor's recommendation?

 

[AlexLaforge]

@Sebahat.hadzhi This ImpersonationCache.db corruption file was simply empty, not "corrupted".
No reason why it would be. And this is a long KNOWN ISSUE.
Igor's recommendaiton solved the issue, but Igor left Plesk a long time ago. This is not acceptable that such a bug persists.
I believe that my 15% price increase each year for the last 5 years would serve another goal that developing SiteJet as a competitor of Joomla or Wordpress.

 

[Sebahat.hadzhi]

Thank you for your update, @AlexLaforge When the issue was initially reported our engineers performed extensive investigation for several months. The trouble is that this behavior is not reproducible at all times. There were hypothesis, such as interruptions during installation, installation performed on a non-clean environment, etc. One of the possible reasons that was proven to be related to the the issue was corrected back then. I understand that from a user-perspective this doesn't matter much especially when encountering the issue, but I don't want you to be under the impression that the issue was not paid the necessary attention and it was handing in the backlog for ~2-3 years while our team was working on other things.

If the same behavior reoccurs and you have the option and you are willing to do so, please provide our engineers with access to the server so they can review and address the issue.