Getting the following when trying to install DNN. A similar thing also happened when trying to install WordPress.
Error: Installation of DotNetNuke at http://domain.com/dnn failed. Non-zero exit status returned by script. Output stream: 'Error during MSSQL version checking [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. '. Error stream: 'Error during MSSQL version checking [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. '.
When it happened with WordPress, I tried the install again and it worked the second time. However, with DNN it does not seem to be working after a second try. Yes, the MS SQL server does exist and is ready to provide.
I am working on a new install of PPA, and after installation on the management node Im trying to add the other nodes. Ive tried to add a Apache, Postfix, DNS & DB node, and they all have the same issue. The installation task fails with the following error:
Destination host 'node.domain.com' (#3), IP '192.168.1.*' : The operation can not be completed because the following component is missing or is not running: pleskd (sc_name '', sc_id #45)
(domain and IP are removed here, correct in the original error. The IP is a backchannel IP, and the public IP was properly set in the management node).
I've verified that pleskd was installed and is running on each node:
24710 ? S 0:00 /usr/local/pem/sbin/pleskd --props-file /usr/local/pem/etc/pleskd.props --send-signal 24712 ? S 0:00 /usr/local/pem/sbin/pleskd --props-file /usr/local/pem/etc/pleskd.props --send-signal 24714 ? S 0:00 /usr/local/pem/sbin/pleskd --props-file /usr/local/pem/etc/pleskd.props --send-signal ...
I've verified that my management node can connect to the nodes in question via 8532:
Code: ]# telnet 192.168.1.* 8352 Trying 192.168.1.*.. Connected to 192.168.1.*. Escape character is '^]'. ^] telnet> quit Connection closed.
So there shouldn't be any firewall or other networking issues.
Installing Plesk Panel with Spamassassin on Ubuntu 14.04 LTS gives a significant error:
Restarting SpamAssassin Mail Filter Daemon: No /usr/bin/perl found running; none killed. server socket setup failed, retry 1: spamd: could not create IO::Socket::INET6 socket on [::1]:783: Cannot assign requested address server socket setup failed, retry 2: spamd: could not create IO::Socket::INET6 socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 9: spamd: could not create IO::Socket::INET6 socket on [127.0.0.1]:783: Address already in use spamd: could not create IO::Socket::INET6 socket on [127.0.0.1]:783: Address already in use invoke-rc.d: initscript spamassassin, action "restart" failed. dpkg: error processing package sa-compile (--configure):
even though spamassassin (i.e. spamd) is not running. The usual suspects for the before mentioned error, being
a) differences in the name of the PIDFILE variable in /etc/default/spamassassin and /etc/init.d/spamassassin b) directory and/or file location are not readable/writable
are not causing this specific installation bug. The work-arounds:
1 - not installing spamassassin (not an option) 2 - installing spamassassin and (afterwards)
change /etc/default/spamassassin, add the option "-4" to the line OPTIONS, resulting in the line: OPTIONS="--nouser-config -4 --username=popuser --daemonize --helper-home-dir=/var/qmail --virtual-config-dir=/var/qmail/mailnames/%d/%l/.spamassassin --create-prefs --max-children=5" run plesk-installer or autoinstaller again ..Work-around 2 works fine, after reinstallation the /etc/default/spamassassin is as it should be (note that the added "-4" is not present anymore).
The before mentioned work-around suggests some error in the installation process, very likely to be an issue with the chronological order of installation of the various components. In theory, it can be excluded that this bug/issue is caused by psa-spamassassin and/or spamassassin (version 3.3.x) packages, even though some current spamassassin bugs are known: URL....I sincerely hope that Parallels Team can investigate and patch both of the bugs/issues.
Windows setup: Plesk Panel 11.5 - Server 2012r2 - IIS 8.5 - PHP 5.3/5.4/5.5 - mySQL/MSSQL. Server runs behind firewall (NAT). Setup with local DNS pointing all A records towards public IP.
Situation: Installed Wordpress through Plesk applications. (mysql). URL....Installs themes in WP console. Everything ok. Installs theme from file, site gets an 500 error. Sometimes installation of theme goes fine, but once activated or previewed it shows 500 error.
Error: Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.Please contact the server administrator to inform of the time the error occurred and of anything you might have done that may have caused the error.
on my Ubuntu 14.04 LTS server, I have ran the install script. This process stopped with the message: ERROR while trying to establish test connection. If you are installing Plesk on an already configured MySQL server, you need to specify the administrator's credentials to succeed with the installation.
To do this, you need to create a file - /root/.my.cnf with the 'client' section where you need to provide user and its password ("user = $admin_name" and "password = $admin_pass").
After installation is finished, the file /root/.my.cnf will be renamed to /root/.my.cnf.bak
Check the error reason(see log file: /var/log/plesk/install/plesk_12.0.18_installation.log), fix and try again
Accordingly, I have the existing my.conf copied to the ROOT directory and added the two missing lines in the client area. After that I started the plesk-installer.sh again. The process stopped at a line
"Installed product components are determined" and nothing still happend. The log files says nothing but the last information at the previous try.
I tried to install open-xchange from application vault.
I got the following error message: Fehler: Die Installation von Open-Xchange ist fehlgeschlagen. Non-zero exit status returned by script. Output stream: 'Creating OX context user_30 Not Found Failed to create OX context user_30: Not Found '. Error stream: 'Creating OX context user_30 Not Found Failed to create OX context user_30: Not Found '.
the following properties I made: public ox website: http://ox.mydomain.de ox installation server: myip
After migrating our existing client base from legacy Plesk 9.x servers and Expand to PPA, clients phoned in with mail sending problems. These clients are using submission port 587 because their ISPs intercept port 25.
Existing client, Outlook error message:
"None of the authentication methods supported by this client are supported by your server"
Testing with Thunderbird, error message:
"An error occurred while sending mail. The mail server responded: 5.7.0 Must issue a STARTTLS command first. Please verify that your email address is correct in your Mail preferences and try again."
It seems a "fresh" PPA requires STARTTLS on e-mail clients. It is furthermore confirmed that Thunderbird detects the e-mail server settings as dependant on TLS.
The problem is that TLS doesn't seem to work properly by default.
In order to preserve our existing customer base, we follow: [URL] ....
Bottom line, in your /etc/postfix/master.cf, change the line that says "submission" from this:
Today i setup a test environment. I have all fresh OS installs today. Management node is Centos 6.5 with PPA 11.5 update 2
I go to servers > add > choose IIS role. The Server is Windows 2012 R2, I have disabled Windows Firewall and disabled UAC, and rebooted it before trying to setup on PPA.
Enter IP and i get the following error.
Code: Automated WinRM Enabling Failed Error during WinRM enabling on '192.168.1.101'. Script exit code is 1. Script output (stdout/stderr): ERROR: Cannot open control pipe - NT_STATUS_INVALID_PARAMETER Failed to install winexesvc /
Repair Connectivity To make automated deployment possible please try to check network communications between Management and target nodes. Ensure that WMI is not blocked on a target node. Or copy, paste and invoke the following script on a target node.
How can i migrate best multiple confixx server to a PPA environment?
I have read migration confixx to ppa is not directly supported, is that right? Can i first migrate all confixx server to one plesk server and migrate in a next step all to ppa or should i migrate step by step each confixx server to a plesk server and after this migrate to ppa?
Who can handle plesk/PPA the multipe username? (server1 with user: web1 | server2 with user: web1) ?
Due to data center limitations, I am restricted to 100GB on my primary disk but can have up to 2TB on a second disk.Is it possible to have the backup node use the second disk instead of the primary disk?Also is it possible to have multiple to have multiple backup nodes?