Update:
Now have access to my server (RDP) & Port 80 is open and responding.
My 2nd IP is installed.
However:-
My website reporting in IE - "Error displaying the error page: Application Instantiation Error: Could not connect to MySQL."
Backend access is fine, so logged into Plesk and looks like MySQL is down - "Host: localhost:3306 (MySQL) The server is unavailable."
phpMyAdmin won't give me access -
MySQL said:
#2002 - No connection could be made because the target machine actively refused it.
— The server is not responding (or the local server's socket is not correctly configured).
mysqli_real_connect(): (HY000/2002): No connection could be made because the target machine actively refused it.
The Plesk MySQL server is running fine, it's the client one that is dead. Looking at SERVICES MySQL56 - STOPPED and won't restart manually, it just stops right away.
Looking in the log file (being careful to look into the client one) I see:
2017-02-11 13:59:30 3160 [Note] Plugin 'FEDERATED' is disabled.
2017-02-11 13:59:30 458 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2017-02-11 13:59:30 3160 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-02-11 13:59:30 3160 [Note] InnoDB: The InnoDB memory heap is disabled
2017-02-11 13:59:30 3160 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-02-11 13:59:30 3160 [Note] InnoDB: Memory barrier is not used
2017-02-11 13:59:30 3160 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-02-11 13:59:31 3160 [Note] InnoDB: Not using CPU crc32 instructions
2017-02-11 13:59:31 3160 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-02-11 13:59:31 3160 [Note] InnoDB: Completed initialization of buffer pool
2017-02-11 13:59:31 3160 [Note] InnoDB: Highest supported file format is Barracuda.
2017-02-11 13:59:31 3160 [Note] InnoDB: The log sequence numbers 8767211683 and 8767211683 in ibdata files do not match the log sequence number 14687657615 in the ib_logfiles!
2017-02-11 13:59:31 3160 [Note] InnoDB: Database was not shutdown normally!
2017-02-11 13:59:31 3160 [Note] InnoDB: Starting crash recovery.
2017-02-11 13:59:31 3160 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-02-11 13:59:31 3160 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace joomla_9_old/jos_jcomments uses space ID: 197 at filepath: .\joomla_9_old\jos_jcomments.ibd. Cannot open tablespace joomla_a/jos_jcomments which uses space ID: 197 at filepath: .\joomla_a\jos_jcomments.ibd
InnoDB: Error: could not open single-table tablespace file .\joomla_a\jos_jcomments.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
So, what caught my eye was "Cannot open tablespace joomla_a/jos_jcomments"
This is an old database long since not used........so I deleted it, along with another couple........then tried to start MySQL56 service and it works!
My website
www.ianjohnston.com is alive again.......subject to some testing.
Gawd knows why those old databases were a problem, have never been in the past!
Phew!
PS. No wonder Dave hires a tech guy to look after his website.......far too stressful!
Ian.
[complete newbie at IIS and MySQL but got there!]