When attempting to log into Plesk Control Panel the following error message is received:
DefPackageMng() constructor failed: defpackagemng failed: Access is denied.(Error code 5) at CreateProcess 'C:\\WINDOWS\\system32\\cmd.exe /c ""C:\\Plesk\\admin\\bin\\defpackagemng.exe" --get"' at execUtil C:\\Plesk\\admin\\bin\\defpackagemng.exe --get on C:\\Plesk\\admin(PleskSrvClient::execUtil line 420)at execute console command --get(vconsoleapp::start line 128) at execute C:\\Plesk\\/admin/bin/defpackagemng --get(vconsoleapp::run line 138)
RESOLUTION
Such error occurs when Plesk Control Panel web server service cannot access the C:\Windows\System32\cmd.exe ( C:\Windows\SysWOW64\cmd.exe on 64bit Windows version). This may happen when administrator has manually changes permissions to access the file. User SERVICE should have Read+Execute; Read on the file.
The following permissions should be set on cmd.exe :
- Administrators - Full Control
- System - Full Control
- Service - Read+Execute; Read
- Interactive - Read+Execute; Read
The file owner should also be administrator, otherwise it will not be possible to change these. File owner can be checked in file’s Properties, Security tab, Advanced button, Owner tab.
Getting defpackagemng errors when logging into Plesk Control Panel
Posted by adminix Labels: Knowledgebase, Plesk for windows
Hot on the heels of the CNN Alerts: my custom alert email spam comes a new variant: msnbc.com: BREAKING NEWS spam.
The emails follow the same format as the CNN spam, with the link to the supposed featured story going to an unrelated third-party website which attempts to attack the users PC.
Read more on SecurityWatch.
Website asks for password - Plesk for Windows
Posted by adminix Labels: Knowledgebase, Plesk for windows
SYMPTOMS
It's impossible to access website - authorization prompt appears.
CAUSE
There may be several reasons of this issue. To determine them, the following conditions need to be checked:
1. There should be read + execute permissions for IUSR_
2. Root directory for the domains can be under Plesk protection.
3. Passwords for system user and IIS user can be out of synchronization.
RESOLUTION
1. Go to %plesk_vhosts%\domain.com\httpdocs directory and check permissions for IUSR_
2. It can be checked using Plesk Control Panel. Go to Plesk, domains, domain.com, Protected URLs. If the root directory "/" is present there, it needs to be removed.
3. The password can be synchronized using the following command:
"%plesk_bin%\websrvmng.exe" --update-anon-password --domain-name=
http://kb.parallels.com/en/976
How to install PHP5 with legacy Plesk versions
Posted by adminix Labels: Knowledgebase, PHP, Plesk for windows
Plesk 7.5.5-7.6.1versions support this version of PHP but they are not able to manage PHP4 and PHP5 at the same time only PHP4 or PHP5.
If your Plesk version is 7.5.5 or higher you can follow these steps to install PHP5 at your server:
1. Download PHP5 Windows Binaries:
- PHP 5.x.x zip package
- Collection of PECL modules for PHP 5.x.x
2. Remove current PHP4 extensions from Register Web Service Extensions in IIS:
Open command prompt:
cscript c:\windows\system32\iisext.vbs /RmFile "%plesk_dir%\Additional\php\php.exe"
cscript c:\windows\system32\iisext.vbs /RmFile "%plesk_dir%\Additional\php\sapi\php4isapi.dll"
3. Rename folder "%plesk_dir%Additional\Php" to "%plesk_dir%Additional\Php4"
4. Re-register web service extensions for PHP4.
Open command prompt:
cscript c:\windows\system32\iisext.vbs /AddFile "%plesk_dir%Additional\php4\php.exe" 0 PHP 1 "PHP Extensions"
cscript c:\windows\system32\iisext.vbs /AddFile "%plesk_dir%Additional\php4\sapi\php4isapi.dll" 0 PHP 1 "PHP Extensions"
cscript c:\windows\system32\iisext.vbs /EnFile "%plesk_dir%Additional\php4\php.exe"
cscript c:\windows\system32\iisext.vbs /EnFile "%plesk_dir%Additional\php4\sapi\php4isapi.dll"
5. Unzip PHP 5.x.x package into %plesk_dir%Additional\Php.
6. Unzip Collection of PECL modules into %plesk_dir%Additional\Php\Ext.
7. Register PHP5 extension in IIS manually:
Open command prompt:
cscript c:\windows\system32\iisext.vbs /AddFile "%plesk_dir%Additional\php\php-cgi.exe" 0 PHP 1 "PHP Extensions"
cscript c:\windows\system32\iisext.vbs /AddFile "%plesk_dir%Additional\php\php5isapi.dll" 0 PHP 1 "PHP Extensions"
cscript c:\windows\system32\iisext.vbs /EnFile "%plesk_dir%Additional\php\php-cgi.exe"
cscript c:\windows\system32\iisext.vbs /EnFile "%plesk_dir%Additional\php\php5isapi.dll"
8. Backup or rename C:\Windows\php.ini.
9. Put attached to this article file php.ini to C:\Windows\php.ini.
10. Configure default C:\Windows\php.ini according to Plesk configuration.
Set parameters:
extension_dir = "%plesk_dir%Additional\Php\ext"
Example:
extension_dir ="C:\Program Files\SWsoft\Plesk\Additional\Php\ext"
11. Re-configure webmail in IIS to use PHP4 because HORDE webmail does not work on PHP5.
IIS Management, Web Sites, webmail(default), Properties, Home Directory tab, Configuration button, Application Extensions, edit value for `.php` extension, set to "%plesk_dir%additional\php4\php.exe"
Edit "%plesk_vhosts%webmail\horde\php.ini"
Change parameter:
extension_dir = "%plesk_dir%Additional\Php4\extensions"
Example:
extension_dir ="C:\Program Files\SWsoft\Plesk\Additional\Php4\extensions"
12. Make sure that PHP5 has been detected by Plesk. You can check in Plesk, Server, Components Management, Web Scripting section PHP should be listed there. If not, you need to check whether all the steps were done properly.
13. Reconfigure domains web-sites in IIS to use PHP5.
"%plesk_bin%\websrvmng.exe" --reconfigure-all
Additional information
Please see also Simultaneous PHP 4 and PHP 5 usage
http://kb.parallels.com/en/1048
How to install CDONTS on Windows 2003 Server
Posted by adminix Labels: Knowledgebase, Plesk for windows
Microsoft Windows Server 2003 does not install Collaboration Data Objects (CDO) for NTS (CDONTS). Therefore, applications that use CDONTS do not function on a Windows Server 2003-based computer. Windows Server 2003 provides improved alternatives to CDONTS.
To make CDONTS functioning on a Windows Server 2003-based computer, use one of the following solutions:
1. Download an attached CDONTS.ZIP file. Once you have downloaded it unzip the CDONTS.DLL and put it into %systemroot%\system32 folder (C:\Windows\system32 by default). You can also get CDONTS.DLL from your Windows 2000 CD.
2. Register the CDONTS.DLL component on your server using the following command:
regsvr32 "%systemroot%\system32\cdonts.dll"
For example:
C:\WINDOWS\system32>regsvr32.exe cdonts.dll
3. After you have registered your CDONTS.DLL component you need to check whether your SMTP service is running.
Go to Administrative tools, IIS and expand your local machine. If SMTP service is listed then it is installed, else it's necessary to install this service.
To install SMTP perform the following operation:
Go to Control Panel, Add/Remove Programs, Add/Remove Windows Components, Application Server, IIS, Check on SMTP service, Click OK.
4. Change the port number for SMTP service. Default port is 25. Use 25 only if you don't have another SMTP service running. If another SMTP service is already running on your server you should switch IIS SMTP port to another, for example to 8025.
You can do through IIS management console: Control Panel, IIS, expand `local computer`, SMTP, Properties, General tab, click on Advanced button, Edit.
5. Configure SMTP service. The main things are to set a valid full-qualified domain name for SMTP service: Control Panel, IIS, expand `local computer`, SMTP, Properties, Delivery tab, click on Advanced button and configure Security for SMTP service.
It's necessary to grant permissions to IIS_WPG standard IIS Worker Process Group. Control Panel, IIS , expand `local computer`, SMTP, Properties, Security tab , click on Add button, cick Object types... button, check on Groups item, click OK, type IIS_WPG as object name to add , click OK.
Additional setting: Choose Authentication and tick Anonymous Access and Integrated Windows Authentication. Click OK, and then click CONNECTION. Configure RELAY settings as you wish. Click the DELIVERY tab then click ADVANCED. Set the MAX hop count to whatever you like but we recommend at least 20
Now IIS SMTP service is configured and ready to work.
Additional Notes can be found on Microsoft's website:
http://support.microsoft.com/default.aspx?scid=kb;en-us;324649
http://kb.parallels.com/en/560
You may create Service Container on a Virtuozzo hardware node using 'vzsveinstall' utility:
# vzsveinstall -D DISTRIB_DIR -s SERVICE_CT_IP
where
- DISTRIB_DIR - path to Virtuozzo distribution directory hierarchy on a server. F.e. if you have the Virtuozzo distrib on your server in the folder /root/Rel400 then DISTRIB_DIR should be /root/Rel400/;
- SERVICE_CT_IP - IP address to be assigned to Service Container;
Please refer to man page on 'vzsveinstall' utility for additional information.
Please note - OS template 'redhat-as3-minimal' must be installed on a hardware node and cached before Service Container may be created. If you have no that template on a node please do the following:
- install OS template 'redhat-as3-minimal', corresponding RPM package is located in the folder 'virtuozzo/SVE' inside Virtuozzo distrib (in Virtuozzo 3.x it is the folder 'HW/SVE');
- create OS template cache using 'vzpkgcache' command on a node.
If Virtuozzo server has been updated since the very first release (using 'vzup2date' utility or manually) then you need to apply all needed updates to the Service Container as well. Updates downloaded by 'vzup2date' utility are usually located under /vz/vzup2date/3.0.0/TU-3.0.0-* dirs on a Virtuozzo server. You may apply them to the Service Container using 'vzsveupgrade' utility using this simple script:
# for i in `find /vz/vzup2date/$(awk '{print $NF}'
If you need to re-create Service Container then you may destroy the existing one using 'vzctl destroy 1' utility (container must be stopped first), then create it from the scratches and apply available updates as it is described above.
Iptables NAT module does not work in container
Posted by adminix Labels: Knowledgebase, Linux, Virtuozzo
SYMPTOMS
NAT module does not work in container, you get "can't initialize iptables table 'nat'" error:
# iptables -t nat -L -n
iptables v1.2.11: can't initialize iptables table `nat': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
The following Iptables modules settings are configured on the hardware node:
# cat /proc/net/ip_tables_targets
LOG
TOS
TCPMSS
REJECT
ERROR
# grep con /etc/modprobe.conf
options ip_conntrack ip_conntrack_disable_ve0=1
RESOLUTION
If order to enable NAT you should perform the following actions on the hardware node:
- stop Virtuozzo service and all containers:
# service vz stop
- reconfigure IPtables module "ip_conntrack":
# sed -i '/ip_conntrack/ d' /etc/modprobe.conf
# echo "options ip_conntrack ip_conntrack_disable_ve0=0" >> /etc/modprobe.conf
- restart IPtables service:
# service iptables restart
- start Vituozzo service and all CTs:
# service vz start
--- http://kb.parallels.com/en/5228
Yeah. Why I haven't thought about it. In the following posts, you will be seeing KB entries from Parallel's Knowledgebase. I will just be posting about the most known problems I've encountered. But please, before you touch anything, make sure that you have a backup. Use this kb's at your own risk.
Cheers.
Horde error 502 - Web server received an invalid response while acting as a gateway or proxy server.
Posted by adminix Labels: horde, Plesk for windows
Child 4800: Encountered too many errors on Plesk 8.6 for Windows
Posted by adminix Labels: Apache, IIS, Plesk for windows
If you are using a windows 2003 server, apache, this error pops out from the ssl.log filesAn operation was attempted on something that is not a socket. : Child
4800: Encountered too many errors accepting client connections. Possible causes:
dynamic address renewal, or incompatible VPN or firewall software. Try using the
Win32DisableAcceptEx directive.
Solution:
Switch Plesk Control Panel to IIS.
Run the following from the command prompt:
"%plesk_bin%\reconfigurator.exe" --switch-plesk-web-server --new-provider=iis
