Cannot open data source (MySQL) after upgrade to 14.0, and cannot upgrade database schema either

Cannot open data source (MySQL) after upgrade to 14.0, and cannot upgrade database schema either

avatar
lucvdv
Disabled

After upgrading to 14.0, RDM can no longer open my (MySql localhost) data source because of a missing table 'rdm.repository'.

It didn't offer to upgrade it during installation.
When I open its properties now the "Update Schema" button is grayed / not accessible, and "Test Host" and "Test Schema" say everything is OK.


When I connect to MySQL and check the database, there really is no table called 'repository' in the rdm database.

And this says what database version I have:


mysql> select DatabaseVersion from databaseinfo;
+-----------------+
| DatabaseVersion |
+-----------------+
| 122 |
+-----------------+
1 row in set (0.00 sec)

All Comments (6)

avatar

I'm the only one in the company using MySQL as data source, my colleagues use SQL Server.
They got to update their database.

I created a ticket, but got no response yet, not even an auto-reply, which is why I came over to the forum.


Browsing around, I begin to think that my problem may be that I currently have the open (non-commerical) version of MySQL on this system.
The database was originally created on another workstation that may well have had the commecial version installed.
When I replaced my workstation, I just installed a recent MySQL download and copied the database (dump & restore).
Could that be it?

avatar

Hi,


I'm seeing this same issue... I have to double click on the data source in the sources window which opens a sepearate connection detail window that lets me do the update. But when I do, I get the following error anyway:

MySql.Data.MySqlClient.MySqlException (0x80004005): Can't create table 'RDMGR.ConnectionState' (errno: 150)
at MySql.Data.MySqlClient.MySqlStream.ReadPacket()
at MySql.Data.MySqlClient.NativeDriver.GetResult(Int32& affectedRow, Int64& insertedId)
at MySql.Data.MySqlClient.Driver.NextResult(Int32 statementId, Boolean force)
at MySql.Data.MySqlClient.MySqlDataReader.NextResult()
at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior)
at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
at MySql.Data.MySqlClient.MySqlScript.Execute()
at Devolutions.RemoteDesktopManager.Business.DataSources.MySQLConnectionDataSource.ExecuteScript(String script, IDbConnection dbConnection)
at Devolutions.RemoteDesktopManager.Business.DataSources.MySQLConnectionDataSource.ExecuteScript(String script, IDbTransaction dbTransaction)
at Devolutions.RemoteDesktopManager.Business.DatabaseUpgradeAction.Execute(DatabaseConnectionDataSource dataSource)
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.Upgrade(Boolean silent, LogMessageDelegate logMessage)


Any tips on what could be causing this?

I've tried to do the update as my own user (SYSDB global Privileges) as well as the DB root user account

avatar

Hello,

Before I start, we do no have an auto-responder in our support mailbox, the CEO finds them cold, artificial, and they dont provide real value.

As for the issue, we've had multiple reports of issues like yours, we are investigating and will provide a fix ASAP.

Best regards,

Maurice

avatar

Thanks for the status update, and sorry for being impatient.

I uninstalled MySQL 5.7.19.1 community and installed MySQL 5.7.21.0 commercial, but it doesn't change anything.
I gave the account used to connect to MySQL full permissions to be sure (all on *.* with grant option).

RDM finds the database, Test Host and Test Schema say it's OK, and the Create Schema and Update Schema buttons are both disabled.

avatar

Edit the data source and the upgrade button will be enabled. Upgrading the database should solve your issue.

We are investigating why the DB upgrade wasn't automatic.

Best regards,

Stéfane Lavergne

avatar

Thanks, that helped.

Maybe this can help determining why it wasn't automatic: I have 3 data sources, shown in this order.

1 - 'Local Data Source'
2 - 'MySQL Localhost'
3 - 'Wimionline'

#1 is completely empty
#2 is the default at startup.
#3 is a SQL Server. This database had already been updated before I installed the RDM update.