- Plesk 11.x for Windows
- Plesk 12.0 for Windows
- Plesk 12.5 for Windows
MailEnable webmail shows an error:
CONFIG_TEXT: HTTP Error 503 Service Unavailable.
The following error can be found in Event Viewer:
CONFIG_TEXT: Application pool MailEnableAppPool has been disabled. Windows Process Activation Service (WAS) encountered a failure when it started a worker process to serve the application pool.
The following detailed error can be found:
CONFIG_TEXT: HTTP Error 401.2 - Unauthorized
IIS Web Core
C:\Program Files (x86)\Parallels\Plesk\Mail Servers\Mail Enable\Bin\NETWebMail
The following error can be found in Event Viewer > Application log:
CONFIG_TEXT: The identity of application pool MailEnableAppPool 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
The issue is caused by all the system user credentials/profiles being removed after running
, including the IIS user and the application pool user of MailEnable webmail.
- Log in to Plesk via RDP
MailEnable WebMailwebsite is running in IIS > Sites. Start it if it is stopped.
Run Mail Enable installer:
C:\> "%plesk_dir%\Mail Servers\Mail Enable\Bin\MEInstaller.exe"
C:\> "%plesk_dir%\Mail Servers\Mail Enable\Bin\NETInstaller.exe"
Select the second option - "WebMail Installation / Reconfiguration (...)"
Give a random password for the MailEnable service accounts.
Select the fourth option ''Re-Register Administration (MCC) Components''
Select the thirteenth option ''Set .NET Framework version for web applications''
If the issue persists, check the article below: