Article ID: 127494, created on Nov 19, 2015, last review on Nov 19, 2015

  • Applies to:
  • Plesk Automation 11.5

Symptoms

When trying to create IIS-based webspace the task Add the IP address 203.0.113.2 fails with the error:

The unexpected HTTP code '503' was received on the HTTP request to the agent at 'https://192.168.0.12:8443/agent.cgi'.

The following events are registered in the System journal in the Windows Event viewer:

Warning (id 5921): 
The identity of application pool PleskControlPanel is invalid. The user name or password that is specified for the identity may be incorrect, or the user may not have batch logon rights. If the identity is not corrected, the application pool will be disabled when the application pool receives its first request.  If batch logon rights are causing the problem, the identity in the IIS configuration store must be changed after rights have been granted before Windows Process Activation Service (WAS) can retry the logon. If the identity remains invalid after the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.

Error (id 5059):
Application pool PleskControlPanel has been disabled. Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.

Cause

The passwords for the user of the application pool PleskControlPanel and system user psaadm are not synchronized.

Resolution

  1. Find current password of the user which is used to run application pool:

    cd %windir%\system32\inetsrv
    appcmd list apppool "PleskControlPanel" /text:*
    

    find the following lines:

    [processModel]
      identityType:"SpecificUser"
      userName:"psaadm"
      password:"ChU04"
    
  2. Set password for the system user psaadm:

    2.1. Go to Control Panel\System and Security\Administrative Tools

    2.2. Unfold Local User and Grous anf select Users container

    2.3. Right-click psaadm user and choose Set Password..., click Proceed

    2.4. Enter the password obtained on the step 1 in both fields and click OK

  3. Rerun the failed task - it will fail with the next output:

    Unable to authenticate at the host '192.168.0.12'. To resolve this issue, please follow the instructions at https://kb.parallels.com/116606.
    

    in order to resolve the issue use the KB link from the error or follow steps 4 and 5

  4. SSH to the management node and retrieve access key:

    mysql> select accessKey from ServiceNodes where ipAddress='192.168.0.12';
    +--------------------------------+
    | accessKey                      |
    +--------------------------------+
    | fI16140Px2J6fzx17zQS7X05ecO88L |
    +--------------------------------+
    1 row in set (0.01 sec)
    
  5. Go to the IIS node and update the key:

    run cmd.exe and execute in the command line:

    cd %plesk_bin%
    usermng.exe --set-password-agent-user --password="fI16140Px2J6fzx17zQS7X05ecO88L"
    
  6. In the same command line run reconfigurator.exe and then select in the GUI Repair Plesk Installation > select Plesk Server Accounts and Plesk Services, click Check

  7. Re-run the failed task Add the IP address 203.0.113.2.

Search Words

Add the IP address

Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool

Unable to create IIS web hosting

The identity of application pool PleskControlPanel is invalid

Application pool PleskControlPanel has been disabled

The unexpected HTTP code '503' was received on the HTTP request

Unable to authenticate at the host

33a70544d00d562bbc5b17762c4ed2b3 caea8340e2d186a540518d08602aa065 e0aff7830fa22f92062ee4db78133079

Email subscription for changes to this article
Save as PDF