Article ID: 1326, created on Oct 6, 2008, last review on May 11, 2014

  • Applies to:
  • Plesk for Windows

Symptoms

Apache is used as a Parallels Plesk Control Panel web server. When attempting to start Plesk CP using the Services management console, the service fails to start. In Event viewer, System,  the following records can be found regarding this problem:

Event Type: Error
Event Source:     Service Control Manager
Event Category:   None
Event ID:   7024
Date:       9/28/2006
Time:       1:46:54 PM
User:       N/A
Computer:   SWSOFT-4B1I8KAX
Description:The Plesk Control Panel Service service terminated with service-specific error 1 (0x1).For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

If you see this error, you should check the Application events. Here are two possible situations:

1. You see an error similar to:

Event Type: Error
Event Source: Apache Service
Event Category: None
Event ID: 3299
Date: 9/28/2006
Time: 1:46:53 PM
User:  N/A
Computer: SWSOFT-4B1I8KAX
Description: The description for Event ID ( 3299 ) in Source ( Apache Service ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: The Apache service named, , reported the following error: >>>, (20024)The given path misformatted or contained invalid characters: Invalid config file path C:\\Program files\\SWsoft\\Plesk\\admin\\conf\\httpd.conf,,,,,.

2. The error is similar to:

Event Type: Error
Event Source: Apache Service
Event Category: None
Event ID:   3299
Date: 9/28/2006
Time: 1:55:26 PM
User:  N/A
Computer:  SWSOFT-4B1I8KAX
Description:The description for Event ID ( 3299 ) in Source ( Apache Service ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: The Apache service named, , reported the following error:>>>, Unable to open logs,,,,,.

Cause

CAUSE 1

This problem is caused by insufficient privileges to access configuration files of Apache. Configuration files for Plesk Apache are located in %plesk_dir%\admin\conf. Apache service runs on behalf of the psaadm user. This user should have at least permission to `List folder contents` on all directories leaning to %plesk_dir%, including the drive’s root. psaadm should have Read+Read&Execute+ List folder contents privileges to access the  %plesk_dir% folder.

CAUSE2


This problem is caused by  insufficient permissions to access the folder with Apache log files: %plesk_dir%admin\logs. Apache service is running on behalf of the  psaadm user. This user should have at least permission to `List folder contents` on all directories leading to %plesk_dir%, including the  drive’s root. The psaadm user should have Read+Read&Execute+List folder contents permission to access  %plesk_dir% folder. The user must have Modify+Write permissions to access the logfiles in %plesk_dir%admin\logs.

Resolution

RESOLUTION 1

Necessary permissions to access all folders leading to %plesk_dir% need to be granted to the psaadm user.

RESOLUTION 2

You should grant necessary permissions for all folders leading to %plesk_dir% to user psaadm and set the correct permission for  %plesk_dir%admin\logs.

85a92ca67f2200d36506862eaa6ed6b8 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF