Forum / Remote Desktop Manager Mac - Support

SQL command connection erorr: Invalid column name 'RepositoryType'

  • Create an Issue
  • Cancel

Hi, I'm David Nicolas.

Since this week, when I open RDM Mac 5.4.0.0 I obtain a connection error to Data Source in SQL Server 2016.
Error: Invalid column name 'RepositoryType'

I use Macos 10.14.3


I've no changed Data Source parameters.
What's wrong?


This is the log error detail:


System.Data.SqlClient.SqlException (0x80131904): Invalid column name 'RepositoryType'. at System.Data.SqlClient.SqlConnection.ErrorHandler (System.Object sender, Mono.Data.Tds.Protocol.TdsInternalErrorMessageEventArgs e) [0x00057] in <423017a70d134d2e8fc7ceeb76602e53>:0 at Mono.Data.Tds.Protocol.Tds.OnTdsErrorMessage (Mono.Data.Tds.Protocol.TdsInternalErrorMessageEventArgs e) [0x00008] in <3919aff23b4a47dcb072a0d9b6a2e3e7>:0 at Mono.Data.Tds.Protocol.Tds.ProcessMessage (Mono.Data.Tds.Protocol.TdsPacketSubType subType) [0x000f9] in <3919aff23b4a47dcb072a0d9b6a2e3e7>:0 at Mono.Data.Tds.Protocol.Tds.ProcessSubPacket () [0x00134] in <3919aff23b4a47dcb072a0d9b6a2e3e7>:0 at Mono.Data.Tds.Protocol.Tds.NextResult () [0x00039] in <3919aff23b4a47dcb072a0d9b6a2e3e7>:0 at System.Data.SqlClient.SqlDataReader.NextResult () [0x00042] in <423017a70d134d2e8fc7ceeb76602e53>:0 at System.Data.SqlClient.SqlDataReader..ctor (System.Data.SqlClient.SqlCommand command) [0x00019] in <423017a70d134d2e8fc7ceeb76602e53>:0 at (wrapper remoting-invoke-with-check) System.Data.SqlClient.SqlDataReader..ctor(System.Data.SqlClient.SqlCommand) at System.Data.SqlClient.SqlCommand.ExecuteReader (System.Data.CommandBehavior behavior) [0x00068] in <423017a70d134d2e8fc7ceeb76602e53>:0 at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader (System.Data.CommandBehavior behavior) [0x00000] in <423017a70d134d2e8fc7ceeb76602e53>:0 at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader (System.Data.CommandBehavior behavior) [0x00000] in <423017a70d134d2e8fc7ceeb76602e53>:0 at System.Data.Common.DbDataAdapter.FillInternal (System.Data.DataSet dataset, System.Data.DataTable[] datatables, System.Int32 startRecord, System.Int32 maxRecords, System.String srcTable, System.Data.IDbCommand command, System.Data.CommandBehavior behavior) [0x0003f] in <423017a70d134d2e8fc7ceeb76602e53>:0 at System.Data.Common.DbDataAdapter.Fill (System.Data.DataSet dataSet, System.Int32 startRecord, System.Int32 maxRecords, System.String srcTable, System.Data.IDbCommand command, System.Data.CommandBehavior behavior) [0x00069] in <423017a70d134d2e8fc7ceeb76602e53>:0 at System.Data.Common.DbDataAdapter.Fill (System.Data.DataSet dataSet) [0x00029] in <423017a70d134d2e8fc7ceeb76602e53>:0 at A.c1b7e8caf3fa8e5fb77cc57c00e8d5e1c.cf7143f4d0ccb8590178f208ae12c1b10 (System.String c0543ca550f15febd1b069e16fd4b95e1, System.Data.IDbDataParameter[] c91084b2aae54f62d01e2a4664a847bd7, System.Data.IDbConnection c411a53bd0524b604aa9ce68084b23ced) [0x00051] in <3fa88bf73282476fa410611b6384968d>:0 at A.c62151df7d13ceddef73b4c42194d331e.c604a5f69d4f5f8ac5373f547ffecf2ff (System.String ccd9ff22aaef233bc8822e47c926bac53) [0x0011c] in <3fa88bf73282476fa410611b6384968d>:0 at A.c62151df7d13ceddef73b4c42194d331e.c604a5f69d4f5f8ac5373f547ffecf2ff (System.Boolean c2dc10ccb40e1e4ec89fa5cbd7d21ef0b) [0x00033] in <3fa88bf73282476fa410611b6384968d>:0 at A.c127aba5e51116d712eb16ce5dc0eb1db.ca3cd3392b75ef3702153d6b07329f4c2 (System.Boolean c52ca1685d4c50ae48235af70f2e0c5fa) [0x00085] in <de2cb21792024f5ea905393b25aa380e>:0 at A.c414ad574f35f8f32a3a27421e4e7552c.c7c141a063e95b24850d0eb2932f23c53 (A.c323b374042cd3040715f1835f9a00a5c cf92249fb171d54e031580709bdd89675) [0x0038a] in <de2cb21792024f5ea905393b25aa380e>:0 at A.cbbb560bfd0154564f3a0626f8038689f.cc215c098d9d30db01ad4833019a25cf4 (A.c323b374042cd3040715f1835f9a00a5c c6001ae751a83ae74954d848ad5dee7b4, System.Boolean c96a7bc363d8d2129b9f77a24d058260b) [0x001ef] in <3fa88bf73282476fa410611b6384968d>:0 at A.cbbb560bfd0154564f3a0626f8038689f+c16953690314bbbd399cd15fee6ab1c86.ceb009fb61eced9c3d9497ff5369331be () [0x000eb] in <3fa88bf73282476fa410611b6384968d>:0 at A.cbbb560bfd0154564f3a0626f8038689f.c30df0c3c041b3f873986da0d50525d49 (A.c323b374042cd3040715f1835f9a00a5c cf92249fb171d54e031580709bdd89675) [0x00372] in <3fa88bf73282476fa410611b6384968d>:0


Thank you all.

Clock8 mths

Hello David,

This error normally occurs when the database has been updated. Could you confirm with the database administrator if they install RDM 6.2.1 and they update it.

If so, please download the latest version at https://mac.remotedesktopmanager.com/home/download .

Best regards,



David Grandolfo

OFFICE CLOSURE!
Although our various support queues will be monitored for emergencies, Devolutions' offices will be closed on October 14th 2019.

signaturesignature

Clock8 mths

Hello David, Thanks for your answer.

The Database was updated, security updates. yes. Is a usual operation.
Sadly, I can't update RDM Mac to 6.x because Integrated Security issue with SQL Server doesn't work with RDM mac 5.5+ ( https://forum.devolutions.net/topic30175-integrated-security-on-sql-server-data-source-doesnt-work-with-rdm-mac-.aspx )

Clock8 mths

Hello,

I'm afraid that as of now, the workaround would be to use database User to authenticate on the data source or roll back to RDM 5.4.0.0.

We understand that updating software for security update could be necessary, I suggest looking at the release notes of RDM Mac if you can stay at RDM 5.4.0.

That being said, if other users' works well, is there a way to use the same authentication type?

Best regards,



David Grandolfo

OFFICE CLOSURE!
Although our various support queues will be monitored for emergencies, Devolutions' offices will be closed on October 14th 2019.

signaturesignature

Clock8 mths

Hi David,

My colleagues are using Windows. No problems that. I'm 'that other guy' in my company wink


Wating for Mono/Xamarin future release smile

Best regards,

David Nicolas

Clock8 mths

I just re-added the missing Column since it seems innocuous so I could continue to limp my Mac folks along.... We have not seen any issues simply adding the column to the dbo.Repository table. Does your team see an issue with this? Also, if it pleases the court, could your DBA add it back in and keep 5.4 testing in mind until the mono framework issue is addressed.

Clock5 mths

Hi,

The biggest job of SQL Server database modification was done last Fall. If editing the column was sufficient for it to continue working, it shouldn't become much more of a problem later. That being said, I've emphasized "shouldn't" for a good reason. This is not something I can really guarantee.

If anything, I'd suggest holding up on updating your RDM Windows versions to conform to the older version of RDM Mac. This is the best way to ensure cross-platform support (though I can easily understand how this could be an issue).

Best regards,

Xavier Fortin

signaturesignature

Clock5 mths