Knowledgebase : Parallels Plesk Panel > Parallels Plesk 11

Issue with one domain not resolving when you are running BIND server.

Suspend and quickly un-suspend the domain works around 20% of situations and if that also fails, we may need to work in the Plesk PSA database.  

NOTE: Before you work on this, please make sure that the plesk psa database is backed up.

cd %plesk_bin%
cd ..\..\MySQL\bin
mysql -u admin -pPASSWORD -P 8306
 

In most cases, Plesk MySQL server’s admin PASSWORD will be the Plesk password itself. If it isn’t reset the plesk password again, but with “%plesk_bin%\plesksrvclient.exe” -set NEW_PASSWORD_HERE true (true parameter will reset the MySQL admin password as well)

Assuming you are now in the plesk mysql server prompt, follow the below steps in mysql prompt.

mysql> use psa;
mysql> select * from dns_zone where name like 'domain_name.com';
 

In the output shown similar to below, check the status of the zone. I have seen only the values 0 and 2. Not sure whether there is a status value of 1 even.

If DNS for some domain is managed in Plesk Control Panel, the status for this domain in dns_zone table is temporary setting to value 2 (to lock it for any changes) and sets it to 0 value when the transaction is over. If for some reason the transaction is interrupted during DNS managing (Plesk restarts for example) the status field value is not changed to 0 and stays as 2. Domains with that status value are not recorded in named.conf file during any DNS management.

Now check to see whether there is only one such record for the ID shown for the above sql query. Chances are there could be two and if there are two, you should delete the record which is orphan or has no reference back to dns_zone.

mysql> select * from dns_recs where dns_zone_id=`the_id_you_got_from_the_above_mysql_query`;

The results you get should be matching with the DNS_Zone_ID and the domainname in question. If you see anything else, i.e orphans or else if you don’t see any entries in dns_recs corresponding to the dns_zone_id, delete it.

mysql> delete from dns_zone where id=[wrong_record_id];
 

And finally update the status from 2 to 0;

mysql> update dns_zone set status=0 where id=[the_dns_zone_id_you_got]
 

When it’s done update DNS records using dnsmng.exe utility:

cd %plesk_bin%
dnsmng.exe update domain.com
 

Finally there could be a few situations where the entire DNS service is down. Usually the monitoring should detect such situations. However I usually noticed that this happens only when it is the BIND server which is being used as the DNS server software. A switch of the DNS server to Microsoft DNS should fix the issue. You may need to check the versions supported at the release notes available at http://www.parallels.com/products/plesk/docs/ . On my investigation disabling the zone of an internationalized domain name solved the issue with one server though and let us continue using BIND server.

 

References : http://kb.parallels.com/en/5242

Connection to a named instance of SQL server 2005/2008 should be made using the format ‘VirtualServer\Instancename’. if the IP address of a machine running a named SQL server instance (ONE)is 192.141.128.140, you can connect to the named instance using  192.141.128.140\ONE for the servername.

To avoid a client app from using the above convention for a servername, a client  alias can be created using the client network utility. Client network utility  can be initiated by

Start->Programs ->Microsoft SQL Server->Client Network Utility

and you can create a Named Pipes or TCP/IP alias for your server and try connecting again.

This guide is intended for server administrators who are going to manage Parallels Panel 11 and Customer and Business Manager. This document also includes instructions about offering Web Presence Builder in the Try and Buy (or trial) mode.
The guide provides information about Panel abilities beyond that available in the standard GUI. System administrators can use this guide to access fine-grained Panel configuration and improve the system performance, security, and other options. Among the other topics, the document also explains how to:

  • Customize Web Presence Builder topics
  • Integrate additional services into Plesk service plans

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.

Applies to Paralle's Plesk 10.x.x & 11.x.x

If you have a production website and want to improve it, it is advised to clone it and let your designers and programmers work on the copy of the site without interrupting the operations of your production site. Cloning is done by creating a copy of your site files and databases attached to it.

1. Prepare development environment.
You are advised to decide where you will host your development copy before copying site files and databases. Depending on your security and production isolation policy, you may choose to create a development copy of your site under the same hosting account, under a different hosting account on the same server if you have FTP access to its files, or on another server. If you decide to go with development site under the same account, add a site (domain or subdomain), or designate one that already exists. If you want to use another server or another account, make sure FTP access to your development site is correctly configured. In all cases, you may follow regular site creation procedures to prepare your development instance.

2. (Optional) Install APS applications

Install the desired site applications in your development environment in the same subdirectory as you have on your production site.

This step is needed if you set up your development environment under your account in the Panel and your production site has APS applications installed via the Panel (at the Applications tab). The reason is that copying site files will not register a new instance of APS application on your site copy. The application copy will still work, but it won't be listed among Installed Applications on the Panel Aplications tab, so you will not be able to change its settings from the Panel. In such a case, you will have to change all database connection settings manually in the application scripts. So perform this step to avoid such manual operations and take advantage of the APS management on your development instance.

3. Copy site files.
To copy your site content, go to the production subscription and select the "Website Copying" operation. You are advised to decide where you will host your development copy before going to that page and preparing the destination for the site content (see Step 1).

4. Copy databases.
In the production subscription, go to Websites & Domains tab > Databases. Click the name of the database with which your site works and select the "Make a Copy" operation. If your site works with more than one database, repeat the procedure for each database. If your production site produces a substantial load on the database server, it is advised to install a separate database instance for development purposes. Create and register the new databases with your development workspace. Then copy your production databases to the development server.

5. Change database connection settings in the scripts.
Be sure to change the database connection settings in the scripts in your development version. Remember that after the files are copied, they are still pointing at the production database. Make sure that your developers will work with the cloned instance instead.

6. (Optional) Complete APS applications setup.
Go to the Applications tab for your development site, locate the application in the list of installed applications, open its Settings screen and re-save the parameters. With this operation, the APS scripts should stop pointing at the production database and reconnect the application to the database copy.

This step is needed if your production site has APS apps installed via the Panel and you performed Step 2 of the current instruction.

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.

 

This article goes over exporting a database in phpMyAdmin.

 

  1. Log into Control Panel.
  2. Once logged in, go to your domain \ databases
  3. Select the database
  4. Click on WebAdmin
  5. Click the Export tab at the top of the page for the selected database.
  6. The options to export are shown. By default, the export will create a .sql file which can be reimported into any database server. Additionally, the Save as File option at the bottom of the page is checked and you can choose to compress the database file if it is a database with a large amount of data.

Overview

Sender Policy Framework (SPF) is a method of fighting spam. As more time passes, this protocol will be used as one of the standard methods of fighting spam on the Internet. An SPF record is a TXT record that is part of a domain's DNS zone file. The TXT record specifies a list of authorized host names/IP addresses that mail can originate from for a given domain name. Once this entry is placed within the DNS zone, no further configuration is necessary to take advantage of servers that incorporate SPF checking into their anti-spam systems. This SPF record is added the same way as a regular A, MX, or CNAME record.

The authoritative source for this information can be found here: http://www.openspf.net/SPF_Record_Syntax.

Requirements

Your domain must be using DNN4Less name servers:

  • NS1.DNN4Less.com
  • NS2.DNN4Less.com

Instructions

  1. Log into Control Panel.
  2. Select your domain name
  3. Edit DNS Settings
  4. Click + Add a record to create a new record. Set the type to TXT and enter your SPF record in the right column.
  5. Click OK to Save the changes.

 

MIMEtype is a set of query that let the server knows how to deal with different file type.

To add a new MIME type in Parallels Plesk Panel, Follow steps below:

  1. Login to your Plesk Panel, click on “Virtual Directories”
  2. Click on “MIME Types”
  3. Click on “Add MIME Type”
  4. Insert the MIME type extension, and select the content from the drop down list, Click OK to save after you have done adding.
  5. In case you need a custom content to handle the file, simply add in the custom content in this box, and click save

Example, to add in a .swf MIME:

AddType application/x-shockwave-flash swf


Append below with the list of MIME type list for reference:

http://www.webmaster-toolkit.com/mime-types.shtml

  • Log in to your Plesk control panel.
  • Click on Tools & Settings on the right hand side.
  • Click on Server Settings, under General.
  • Where it says "Full hostname" is where you would want to put your servers new hostname, typically it is set up as something like server.DNN4Less.com or mail.DNN4Less.com and is normally always the same as what is set up as the primary reverse DNS.
  • Once you have set it click OK.
  • Note: When you will delete the website in plesk 10 or 11, then the all data associated with the user account will be deleted from the server. One thing more, the first website which is created for your account can not be deleted; however you can rename the account.

    Follow below steps to delete a website from the Plesk 10 / 11.

    Step 1: Login in to plesk with correct user name and the password.

    Step 2: Go to the subscription menu.

    Step 3: Now click on the “WebSites & Domain” Tab.

    Step 4: Now tick the domain which you want to remove.

    Step 5: Confirm the removal and now click OK.

    APPLIES TO:
    • Parallels Plesk Panel for Windows

    Answer

    To determine database provider it is necessary to run regedit.exe and go to

    for x86

    HKEY_LOCAL_MACHINE\SOFTWARE\PLESK\PSA Config\Config

    for x64

    HKEY_LOCAL_MACHINE\SOFTWARE\wow6432node\PLESK\
    PSA Config\Config

    The value of key "PLESK_DATABASE_PROVIDER_NAME" is the database provider which Plesk uses for database storage.

    The database providers that could be listed here are:

    - Jet
    - MySQL
    - MSSQL
     
    Source: http://kb.parallels.com/en/3453
    1. Login to Control Panel https://control.DNN4Less.com/cp
    2. Under your subscription/domain go to “Databases”
    3. Click database name
    4. Click “Webadmin”
    5. Click “Import”
    6. Click “Browse” to select the database then click “Go”

    If you have a production website and are planning major site changes, consider setting up a staging site — a separate location on the server where you can conveniently update and test a copy of the site before putting it into production.

    We recommend that you work with a staging site in the following way:

    1. Decide where you want to host the development copy and prepare the development environment. You can choose to host it in the same webspace, in a separate webspace on the same server, or upload it to an FTP account on another server.

      If you choose the same webspace, then you first need to set up a new website by adding a domain or a subdomain.

    2. (Optional step.) If you set up your development environment under your account in the Panel and your production site has APS applications installed via the Panel (at the Applicationstab), install the desired site applications in your development environment in the same subdirectory as you have on your production site. This step is optional; however, it will help you avoid changing manually database connection settings in the application scripts.
    3. Make a copy of the website and place it in the staging environment.
    4. Make copies of the databases used by the site and deploy them in the staging environment.
    5. Change database connection settings in the scripts to point at the databases in the staging environment.
    6. (Optional step.) Complete APS applications setup. Go to the Applications tab for your development site, locate the application in the list of installed applications, open its Settingsscreen and re-save the parameters. With this operation, the APS scripts should stop pointing at the production database and reconnect the application to the database copy. This step is needed if your production site has APS apps installed via the Panel and you performed Step 2 of the current instruction.
    7. Make the required changes to the site copy in the staging environment, and test them to make sure everything works as intended.
    8. Publish the updated site. This is done by pointing the document root of the production site to the staging site location.

    To set up a site for staging purposes:

    1. Go to the Websites & Domains tab.
    2. Click either Add New Domain or Add New Subdomain.

      We recommend that you use a subdomain for staging purposes.

    3. Proceed as described in Adding More Websites or Adding Subdomains.

    If you do not want your staging site to be accessible to the Internet users, do not register the newly added domain or subdomain name with a domain name registrar, or use an .htaccessfile (on Linux hosting) to restrict access to it.

    To make a copy of website files:

    1. Go to the Websites & Domains tab.
    2. Click Website Copying (in the Advanced Operations group).
    3. If you have several websites, select the one you need and click Manage.
    4. To copy website files to the document root of an existing site:
      1. Select the option Website in the Panel.
      2. Select the destination site from the Site name menu.
      3. Specify what to do with the files that might already be present in the destination directory.
    5. To copy website files to an FTP account on this or another server:
      1. Select the option FTP storage.
      2. Specify the server's host name and credentials for connecting to the FTP account.
      3. In the FTP connection method field, leave the Active mode option selected. If the Panel fails to connect to the external FTP account, select the Passive mode option here.
    6. Click OK.

    If the site uses scripts that work with a database, copy the database to the staging environment:

    • If the database is hosted on the same server managed by Panel 10, use the procedure below to copy it.
    • If the database is hosted on a server which is not managed by Panel 10, use the mysqldump utility to export the database, move the resulting data dump file to the staging environment and deploy it there. Modify the site's scripts in the staging environment so that they connect to the copied database.

    To make a copy of a database from the Panel-managed server:

    1. Go to the Websites & Domains tab > Databases > database name.
    2. Click Make a Copy.
    3. Specify the following:
      • Destination database server. You can select the same Panel-managed database server, or a database server located elsewhere. For an external database server, specify the host name or IP address, and access credentials: the username and password of a database management system user authorized to create new databases and database tables.
      • Destination database. You can choose to create a new database or copy the data to an existing database.
      • Create a full copy. Leave this option selected to copy the database structure and all data.
    4. Click OK.

      The copy of the database will be deployed on the destination server.

    5. Modify the site's scripts in the staging environment so that they connect to the copied database.

    When the site copy in the staging environment is updated and ready to go live, publish it as described in the following steps.

    To publish the updated site to the production environment:

    1. Go to the Websites & Domains tab.
    2. In the list of domain names, locate the address of your production site and click it.
    3. In the Document root box, specify the document root directory of the staging site.
    4. Click OK.

    This will make the updated site copy in the staging site location accessible to visitors of your production site address.

    Applies to Plesk 10.x.x & Plesk 11.x.x

    To rename domain name in Plesk, Please follow the following settings:

    1. Login to Plesk control panel.
    2. Click on "Websites and Domains"
    3. Click on the "Domain Name" under whom you want to rename domain name.
    4. Type New Domain name
    5. Click on "Ok".

    Renaming the domain name will rename DNS Settings, email addresses and all other settings related to the domain name.

    In Plesk panel go to Domains page, mark required domains and click on Check permissions button. Then uncheck Check-only mode checkbox and click OK.


    If it is necessary to repair permissions for all domains, you can launch Plesk Reconfigurator ( Start, Programs, SWsoft , Plesk, Plesk Reconfigurator ), when it is run,  choose Repair Plesk installation , then toggle on Plesk virtual hosts security and click on Check button.


    Note:
    Please be aware that any custom permissions which might be configured by customers will be replaced with default ones after this action.

    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.

     

    This article will explain how you can create an SPF record on your server using Plesk 11.

     

    If you have not already done so you will need to generate an SPF record first this can be done at Microsoft's SPF record wizard

     

     

    1. Login to your Control Panel https://Control.DNN4Less.com/cp
    2. Select your domain
    3. Click on the Open in Control Panel link for the relevant domain name.
    4. Click on the Website & Domains tab.
    5. Click on the DNS settings link.
    6. Click on the Add Record icon.
    7. Select TXT From the drop down list.
    8. Leave the Domain name field blank and enter the generated SPF record in theTXT record field.
    9. Press the OK button to add the record.
    10. To apply the SPF record to the DNS zone press the Update button.

     

    You need to connect to the server with remote desktop. 
    Once logged in open a terminal window. Start>Run> then type in CMD A black window will appear.


    You need to change to the Plesk install directory. cd\ %plesk_bin%\


    The %plesk_bin% here commonly stands for c:\program files\parallels\plesk\admin\bin folder in case of 'by default' installation. 


    Once there type in plesksrvclient -get


    This will print your password

    You can import your backup .sql files through phpMyAdmin.

    Importing:

    1. Log in to your MySQL database server via phpMyAdmin
    2. Select your database name on the left
    3. Click on the "Import" tab on top
    4. Click the "Browse" button and locate your .sql file
    5. Click the "Go" button on the bottom of the page to import the backup
    APPLIES TO:
    • Parallels Plesk Panel

    Resolution:

    This article describes how to install Plesk hotfixes that are provided in KB articles. Please familiarize yourself with the article carefully.

    To install a Plesk hotfix that has been provided in KB article the following steps need to be completed:

    1. Download the file to the server in binary format. Save it in any folder but not in the destination one.
    2. Backup or rename the original file.
    3. Important: Copy the saved file to the destination location. It is important that file inherits correct ACL permissions from the parent folder otherwise Plesk will not be able to access the file, displaying the following error message:

    Warning: failed to open stream: No such file or directory

    Symptoms

    Domain creation failed for some reason and was rolled back. The next time the domain is re-created, the following error message is displayed:

    Failed domain creation: Unable to update domain data: Failed mail post-configuration: Can't create mail domain service: mailManager->addDomain() failed: mailmng failed: Can't create domain.

    In Plesk 10.x error message differs:

    Failed mail post-configuration: Can't create mail domain servie: mail_Facade->createDomain() failed: mailmng failed: MEAOPO.PostOffice.AddPostOffice failed for name domain.tld [domain.tld]

    Cause

    The most possible cause is that the domain that you are trying to create already exists in mail server settings and this record was not removed during the rollback of unsuccessful domain creation.

    Resolution

    Remove mail domain from mail server manually as it was not removed due to incorrect rollback.

    Applies to:

    • Plesk 10.x.x & 11.x.x with MySQL Database
    • Windows Server 2008 & Windows Server 2008 R2

    Overview:

    When you try to change an email address password from a subscription (for example yourdomain.com) you receive an error:

    Error: The user account was not found. This could happen if the user account was removed by someone else while you were changing its settings and you cannot change the mail password.

    Solution:

    Login to your Server via RDP

    Open Command Prompt

    Login to MySQL Database (usually in %Plesk_admin%\MySQL\bin)

    Run the following command:

     

    UPDATE smb_users SET ownerId=(SELECT id FROM clients WHERE login='yourdomain.com') WHERE email like '%yourdomain.com';

     

    Replace "yourdomain.com" with your actual domain name.

    Applies to Plesk for Windows.

    You cannot connect to 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

    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.

    Plesk DNS named.conf Issue - Zone file and corresponding record in named.conf are missed for particular domain.

    Symptoms:

    Bind DNS server is used. There is no entry in named.conf for some domains, there also no zone file for it in the %plesk_bin%dns\var folder. If records are created manually they will be removed the next time Plesk updates named.conf.


    The following tutorial will guide you through the cause and resolution for solving Plesk DNS issues with any domain accounts that are not resolving properly.
     
    Cause:

    When the DNS zone for a domain is managed via Plesk, the status for this domain in the dns_zone table of the database is temporarily set to a value of 2 (to lock it for any further changes) and is then set back to a value of 0 value when the changes are processed. If for some reason the process is interrupted (Plesk restarts for example) the status field value may not get changed back to 0 and stays as 2. Therefore any changes are no longer recorded until the status is changed back to 0.

    Resolution: Editing the Plesk DNS zone database
     

    Please note: to isolate database issues with Plesk and your own web services (MySQL or MS SQL), we recommend and setup Plesk to use MS Access databases. If you have setup Plesk to use MySQL or MS SQL databases you will need to use your preferred database viewer to find the necessary DNS zone table. You can view MS SQL instructions below.
    1. To view and edit the Plesk DNS zone database you will need to use an MS Access database viewer such as MDBPlus, and then open up the pleskmain.db located at:

      C:\Program Files (x86)\Parallels\Plesk\admin\db - Note: password is the same as Plesk admin login.
    2. Check dns_zone records for the problem domain's entry (domain.com for example):
      1. if there are multiple entries for the same domain; remove the entry that has the incorrect setting of 2;
      2. if there is only one entry for the domain, adjust the value in the "status" column from 2 back to 0.
    3. Save the database.
    4. Go back into Plesk and navigate to the DNS zone settings tab for the affected domain.
    5. Select "Restore Defaults" to rebuild the appropriate entries for the domain

    You should now be able to resolve the domain correctly.


    For Plesk installations setup to use MS SQL as the default Plesk database:

    1. Login via MSSQL Server Management Studio Express or your preferred MS SQL management tool.
    2. Expand the Plesk database.
    3. Expand the "tables" section.
    4. Scroll down to "dbo.dns_zone", right-click on this and choose "open table"
    5. Delete or modify the erroneous entry as in Step 2. above.

    Overview

    Creating and using strong passwords is an important part of your server/website security.

    With Plesk 11, a strong password is required with your initial setup. These passwords are at least 8 characters long. Along with upper and lower-case characters, they require multiple occurrences of digits and special symbols. Such passwords provide strong protection from brute-force attacks.

    Things to include

    1. At least eight characters.
    2. One or more of each of the following:
      • lower-case letter
      • upper-case letter
      • number
      • punctuation mark
    3. Lookalike characters to protect against password glimpses. Examples:
      • O as in Oscar and the number 0.
      • Lower-case l and upper-case I.
      • The letter S and the $ sign.

    Things to avoid

    1. Words you can find in the dictionary.
    2. Passwords shown as "example strong passwords."
    3. Personal information, such as names and birth dates.
    4. Keyboard patterns, like qwerty or 12345. Particularly avoid sequences of numbers in order.
    5. Common acronyms.
    6. All one type of character - such as all numbers, all upper-case letters, all lower-case letters, etc.
    7. Repeating characters, such as mmmm3333.
    8. The same password you use for another application.

    Memorable password tips

    While passwords that are easy for you to remember are also less secure than a completely random password, following these tips can help you find the right balance between convenience for you and difficulty for hackers.

    1. Create a unique acronym for a sentence or phrase you like.
    2. Include phonetic replacements, such as 'Luv 2 Laf' for 'Love to Laugh.'
    3. Jumble together some pronounceable syllables, such as 'iv,mockRek9.'

    Keep your password secret

    1. Never tell your password to anyone (this includes significant others, roommates, coworkers, etc.). If you need to grant someone access to your server, set up a separate username and password for that person.
    2. Never write your password down, especially not anywhere near your computer.
    3. Do not store your password in a plain text file on your computer.
    4. Never send your password over an unecrypted connection - including unencrypted email.
    5. Periodically test your current password.
    6. Update your password every six months.
    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

    Symptoms

    When I open File Manager I am getting the following error:

    FileList::init() failed: ls_dir_wrapper() failed: Unable to logon user (PLESK900W2K3\USER1): (1326) Logon failure: unknown user name or bad password.
    ---------------------- Debug Info -------------------------------
    0: plib\ui_common\FileManagerUIPointer.php:709
        FileManagerUIPointer->accessItem(string 'GET', NULL null)
    1: plib\ui\client.domain.hosting.file-manager.php:86
        plesk__client__domain__hosting__file_manager->accessItem(string 'GET', NULL null)
    2: plib\UIPointer.php:599
        UIPointer->access(string 'GET')
    3: htdocs\plesk.php:42

        

    Resolution

    Make sure that the account associated with the domain is active on the server. If it is disabled, you need to enable it by modifying properties of the account. 

    If account is enabled, the most possible reason of the issue is that the password of domain owner account is not synchronized with corresponding record in Parallels Panel database.
    To fix that take the following steps:

    1. Retrieve the password of the domain owner from Parallels Panel database with the command below (where USER1 is an owner of the domain, it can be taken from the error):

    C:\> "%plesk_bin%"\dbclient --direct-sql --sql="select su.login, a.password from accounts a, sys_users su  where a.id=su.account_id and su.login='USER1'"

    login       password
    USER1  p@ssw0rd


    2. Synchronize system password with accordance of retrieved one as follow:

    C:\> net user USER1  p@ssw0rd