• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Failure after installation of Plesk for Windows

S

steffan

Guest
After installation i get this message, after login with (admin, setup):
Unable to fetch IP adresses list: ifmng failed: Can't create user (mydomain\Administrator) token: Anmeldung fehlgeschlagen: unbekannter Benutzername oder falsches Kennwort.
at execute D:\PROGRA~1\Plesk/admin/bin/ifmng "--reread"(RunTime::RunAsUser::run line 280)

OK, can somebody help? It is a Windows 2003 Server Basic. I installed the newest release of Plesk 6.5.2.

What i have done:
Installed Plesk
Restart
Installed the latest Hotfix
Restart
Logged in to the admin site.


Thanks
 
OK, one more time.......

After Installation of Ples 6.5.2 on a Windows 2003 Server Basic, i get this message when i login to Plesk:

Unable to fetch IP adresses list: ifmng failed: Can't create user (mydomain\Administrator) token: Anmeldung fehlgeschlagen: unbekannter Benutzername oder falsches Kennwort.
at execute D:\PROGRA~1\Plesk/admin/bin/ifmng "--reread"(RunTime::RunAsUser::run line 280)

Anmeldung Fehlgeschlagen means Login fail
unbekannter Benutzername means unknown username
falsches Kennwort means wrong password
 
Are you on a dynamic IP?

Also, under %pleskdir%\admin\bin\ is a file called "plesksrvclient".

This file will allow you to reset the Plesk password, but you will have to make sure it matches the MySQL Password.
 
IP

It´s on Static IP.

What else could it be?

Thanks.
 
If you are running a localized version of windows this is probably the problem.

You will need to email SW-Soft for the patch.

I should have caught this earlier.
 
Back
Top