Knowledgebase
20DNS 40Domains 62DotNetNuke 17Downloads 84eMail 14File Transfer Protocol 126Flash Tutorials 23General 11IIS 4Migrations 30MSSQL Server 9MySQL Server 111Parallels Plesk Panel 6Security and Hack 10SEO 23Server Settings 8SSL Certificates 1Video Tutorials 11Your Account
Knowledgebase : Parallels Plesk Panel
Parallels Plesk 10 (31)
Solving DNS related issues with Plesk Panel Windows
[DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection Error when binding MSSQL database with plesk 10
Parallels Plesk 11 (28)
Solving DNS related issues with Plesk Panel Windows
[DBNETLIB][ConnectionOpen (Invalid Instance()).]Invalid connection Error when binding MSSQL database with plesk 10
Parallels Plesk 9 (38)
Administrators guide to Plesk
Cannot create domain: mailmng failed:
‘www’ prefix not working

If you didn’t add the ‘www’ prefix at the time of setting up the domain, even adding it back in later does not seem to work.

Solution:
To work around this problem, firstly – turn on the ‘www’ prefix again within the Plesk control panel.

Go to Plesk CP > Domains > yourdomain.xxx > 'Domain Administration' drop-down menu > Rename domain. It will force IIS to configure www.yourdomain.com hostheader for your domain.


Also, make sure your www.yourdomain.com resolves to the same IP adress as yourdomain.com.

530 User cannot log in, home directory inaccessible.

You have created a FTP Account through Plesk Control Panel, but when you try to connect your FTP site you get this error "error 530 User cannot log in, home directory inaccessible."

Server Configuration:

  • Windows Server 2008 or 2008 R2
  • Plesk Control Panel
  • IIS 7 or 7.5
  • Microsft SQL Server 2005, 2008, 2008R2

Solution:

  1. Connect to your server using RDP
  2. Connect to SQL Server using Microsft Management Studio Express
  3. Expend Datatbases
  4. Expand Plesk Database
  5. Expend Tables
  6. Right Click on dbo.domains and Click Edit  Top 200 Rows
  7. Check if your domain "Status" has any other status than 0, if the status is already set to 2, 4, 16, 64, 256 set it ot "0".
  8. Close the table and recreate the FTP Account in Plesk Control Panel.
  9. Now try to connect your FTP site. You should be able to login and browse site's Files and Folders.

Feel Free to leave your comments.

Cannot create domain: mailmng failed:

Cannot create domain: mailmng failed: Loaded Postoffice Configuration Provider (MEAIPO.DLL) MEAOPO.PostOffice.AddPostOffice failed

 
APPLIES TO:
  • Parallels Plesk Panel for Windows

Symptoms

Domain cannot be created with following error reported in Parallels Plesk Panel interface:

Error: Unable to update domain data: Failed mail post-configuration: Can't create mail domain servie: mail_Facade->createDomain() failed: mailmng failed: Loaded Postoffice Configuration Provider (MEAIPO.DLL) MEAOPO.PostOffice.AddPostOffice failed for name domain.tld [domain.tld]

Cause

It may be caused by previously failed attempt to add or remove domain with the same name, which resulted in domain being absent from Parallels Plesk Panel, but MailEnable postoffice exists due to unsuccessful rollback of domain creation/removal.

Resolution

Postoffice should be removed from MailEnable manually.

  1. Open MailEnable control panel using Start → All Programs → Mail Enable → MailEnable Administrator or Start → Run... →mailenable.msc on the server.

  2. Go to Messaging manager → Post Offices and remove/rename postoffice of domain that causes error.

Cannot Set SmarterMail as Default MailServer in Plesk Panel
Error: Set default component failed: defpackagemng failed: Loaded Postoffice Configuration Provider (MEAIPO.DLL)
Unable to assign port to IP address. Reason: Unknown IP Address: 169.254.16.152

Follow the below given steps to solve this issue :

  1. Go to Regedit.
  2. Go to the path: Local_Machhine >> Software >> Wow6432Node >> Plesk >> Psa config >> config 
  3. Locate the record MAIL_PROVIDERW_DLL and change it to: C:\Program Files (x86)\Parallels\Plesk\admin\bin\smartermailprovider.dll
  4. Locate the path: Local_Machhine >> Software >> Wow6432Node >> Plesk >> Psa config >> config >> Packages >> Mailserver and set Default regisrty entry to smartermail
  5. Save the registry. 
  6. Open Plesk using admin login, go to  Tool and setting >> Server components >> and click on refresh.
Error code 2- at Unable to connect to pipe Plesk Windows

You cannot connect to my Plesk Control Panel and receive the following error:

get_config_string failed: PRODUCT_DATA_D: The system cannot find the file specified.
(Error code 2) at Unable to connect to pipe \\.\pipe\psapipe

Problem Cause

The Plesk services have lost their connection to the Plesk database.  There are several reasons this might happen, but the quick fix is the same in all cases.

Solution

The quick fix for this problem is to restart the Plesk services and the Plesk database servers.

Follow these steps to perform this action:

  1. Login to your server with Remote Desktop.
  2. Open the Plesk icon in your system tray.
  3. Select the Plesk Run-Time checkboxes so they are checked.
  4. Select the SQL Server boxes so they are checked.
  5. Uncheck everything else.
  6. Click the Restart button.

This will restart the services involved in the Plesk database connection and allow them to communicate.

 

Error: Cannot open user default database. Login failed.

When you try to perform MSSQL Database backup in DNN4Less Control Panel you receive the following error:

Error: Cannot open user default database. Login failed. Login failed for user 'xxxxxxxxxxxxx'.
Source: .Net SqlClient Data Provider

 Solution :

  1. Login to the Control Panel: https://control.DNN4Less.com/cp
  2. Select your Domain
  3. Go to Websites & Domains 
  4. Click Click Databases
  5. Click Click Database Name
  6. Check the database User Name 
  7. Click Make Default for DB Webadmin
failed: Unable to logon user (SERVER_NAME\\username): (1331) Logo...
FileList::init() failed: ls_dir_wrapper() failed: Unable to logon user (SERVER_NAME\\username): (1331) Logon failure: account currently disabled.
---------------------- Debug Info -------------------------------
0: C:\\Program Files\\SWsoft\\Plesk\\admin\\htdocs\\filemanager\\filemanager.php:672 psaerror(string "FileList::init() failed: ls_dir_wrapper() failed: Unable to logon user (SERVER_NAME\\username): (1331) Logon failure: account currently disabled."

Resolution

The user needs to be enabled using the Computer Management console or the command line:

Go to Computer Management, expand Local Users and Groups, Users, find the user that is disabled, right-click, Properties, General tab, uncheck Account is disabled check-box, click OK.
How to create a Plesk domain backup in your DNN4Less Control Pane...

You will need to log into your DNN4Less control panel by doing the following:

  1. Open up a web browser and navigate to the following URL: https://control.DNN4Less.com/cp
  2. Enter in your username and password that were sent to you when your hosting package was created and click “Sign In” (the username will be the primary contact email address of the hosting package administrator).
  3. Once you have logged into your control panel, Click “Subscriptions /Domains”
  4. Select and click a Subscription
  5. Click “Website & Domains”
  6. Click “Backup Manager”
  7. Click “Back Up”
  8. As you cannot specify the file name for the backup, please add a prefix for further searching. You can also write the brief comments for the backup.
  9. Set the volume size of backup and select the location of the backup. By default, the backup will be stored in the same server. If you want to perform a remote backup, please select “Personal FTP repository”.
  10. Enter the email address to receive the notification upon task completion
  11. Select the backup content then click “Back Up”
How to manage log files and avoid usage overages

Log files show a running list of every time the site is accessed with information like the operating system, device type, and
browser accessing it, files loaded, and how they got there (what search engine, etc.) They can be useful if you’re interested 
in drawing statistics on who your customers or visitors are, and for investigating certain types of problems with the site.
However, if not properly managed, excessive log files can cause resource usage overages. 

You will need to log into your DNN4Less control panel by doing the following:

  1. Open up a web browser and navigate to the following URL: https://control.DNN4Less.com/cp
  2. Enter in your username and password that were sent to you when your hosting package was created and click “Sign
    In” (the username will be the primary contact email address of the hosting package administrator).
  3. Once you have logged into your control panel, Under Statistics, click on Log Manager.
  4. Once you’re in the Log Manager, click on Log Rotation.
  5.  In the Log Rotation, you can maintain logs at a certain size, or rotate them out on a time-basis (for example,
    discard anything older than 1 month)
This should allow you to maintain your log files at a potentially useful level, rather than 
keeping them infinitely and using up your available hosting space.

How to retrieve Plesk admin password on Windows
APPLIES TO:
  • Parallels Plesk Panel 11.x for Windows
  • Parallels Plesk Panel 10.x for Windows
  • Parallels Plesk Panel 9.x for Windows
  • Parallels Plesk Panel 8.x for Windows
Resolution
Apart from the password reminder available on the login screen, you can use theplesksrvclient.exe utility located in the %plesk_bin% folder to set up a new password or retrieve the old one.

You can set up a new password by running the following command:

"%plesk_bin%\plesksrvclient" -set <new_password> true

You can also retrieve the current password by running this utility with:

"%plesk_bin%\plesksrvclient" -get


To retrieve the password in the command line, you can use -nogui option:

"%plesk_bin%\plesksrvclient" -get  -nogui > plesk_password.txt


After that, you can find the retrieved Plesk password in the plesk_password.txt file.
Permissions for IWPD user removed

Symptom:

  • You have an ASP.net based site which requires MODIFY permissions for the IWPD user
  • Some feature stopped working on your site, and the Support team corrected the issue, indicating that "permissions for the IWPD user needed to be reapplied".
    Information:

Background:

  • Each site has multiple unique users associated with it:
    • FTP user
    • An IUSR user, used for accessing/executing your site's HTML, PHP, and ASP based files.
    • An IWPD user, used for accessing/executing your site's ASP.net based files.
  • MODIFY permissions for the IWPD user can be removed due to a design flaw in Plesk. Around version 8.x of Plesk, Plesk began tracking permissions settings on each domain's directory structure, so that it could reapply them if/as necessary. Unfortunately, Plesk doesn't allow us to set the necessary permissions with the IWPD_user within plesk itself, so we set them manually outside of plesk. As a result, any subsequent changes in plesk, which cause it to reapply permissions, it removes that permission for the IWPD user we set manually.
  • IWPD permissions may be required for ASP.net applications which need to create or modify files (uploading skins, modules, and/or other files) and for the URL Rewrite ISAPI Filters. If Plesk removes these permissions, ASP.net applications will still function for operations that require READ access to the site files, but if any create/modify/delete operations occur, the ASP.net application will experience an ACCESS DENIED error.
  • What types of changes in plesk trigger it to reapply permissions, thus removing the manually added IWPD user permissions? The most common item is any change within the SETUP options for the domain... i.e., FTP password change, changing version of ASP.net or PHP, enabling/disabling custom error documents, etc). There may be other options within the control panel which also trigger the permissions reset.
  • To date, this has not been resolved in any version of Plesk.
  • This issue has the largest impact because it affects DNN sites, which require the additional MODIFY permissions for the IWPD user when adding files, adding a module, skin, or other extensions.

RESOLUTION:

As of 04/01/2011, DNN4Less Support Staff has identified a method for preventing Plesk from removing the IWPD user permissions, but this modification has to be applied manually on your domain. If you've been affected by this problem, please contact our support team.

From now on, any time DNN4Less Support Staff adds MODIFY permissions to a domain at a customer's request (for an DNN installation or other), we will also put this modification in place to ensure the permissions for the IWPD user are not removed in the future by plesk.

Plesk domain status codes
List all active domains: SELECT name FROM domains WHERE status = '0'

List all suspended domains: SELECT name FROM domains WHERE status = '16'

List all expired (hosting) domains: SELECT name FROM domains WHERE status = '256'

List all domains with backup/restore in progress: SELECT name FROM domains WHERE status = '4'

List all domains suspended by client: SELECT name FROM domains WHERE status = '64'

Unable to call SOAP server: (-2147467259) Unspecified error

When you create a new domain or update an existing one in Plesk you receive the following error:

"Unable to call SOAP server: (-2147467259) Unspecified error"

This error will occur if you have SmarterMail installed on your server and its not properly configured, or (smwebmail) site is stopped in IIS.

SOLUTION:

  1. Check to make sure that Plesk is configured properly to connect with SmarterMail
  2. "smwebmail" site in IIS is not stopped
  3. Be sure you have bind 9998 port with all assigned IPs in the webmail site if using IIS.
WebAdmin: 405 - HTTP verb used to access this page is not allowed...

When you access your MSSQL database through MSSQL Server Eeterprise Manager from Parallels Plesk Control Panel or a web browser you get following error.

"405 - HTTP verb used to access this page is not allowed.
The page you are looking for cannot be displayed because an invalid method (HTTP verb) was used to attempt access."

Solution:

1. Enter into %plesk_bin% directory.
2. Execute the command 'defpackagemng --fix --type=sqladminmssql '

 

If above solution does not work change the application pool for 'mssql' to 'DefaultAppPool' that is set to 'integrated' mode. And then try the above solution again.