Forum / Remote Desktop Manager Mac - Support

Invalid object name 'UserRoamingSettings'

  • Create an Issue
  • Cancel

hello together, I updated my RDM today (file from the website) and since then get this error:

A.c80ba12e4d0dcd22500b279e220e08230: Invalid object name 'UserRoamingSettings'.
at Devolutions.RemoteDesktopManager.Business.DataSources.SQLServerConnectionDataSource.c27bc2696e54a01b19073e7b8c7a31372[ceaa9d1a76410934033f88a1b7444f6db] (System.String c0543ca550f15febd1b069e16fd4b95e1, System.Data.IDbDataParameter[] c91084b2aae54f62d01e2a4664a847bd7) [0x000af] in <9b7155c91894495b8816a38798bde195>:0
at A.c1b7e8caf3fa8e5fb77cc57c00e8d5e1c.c297adc0d5df00bd9460db73f36eb01d0 (Devolutions.RemoteDesktopManager.UserRoamingSettingType ce09e369ebbef4f4b21c32b05541864bf, System.String c6e94516697ee7619e178544cd71183ad) [0x000e2] in <9b7155c91894495b8816a38798bde195>:0
at A.c8e90713531c57022813e92202711dbd5.c69614dbe2365de08f4a9ef1a974c69f9 (Devolutions.RemoteDesktopManager.Business.FavoriteFolderContainer c5e8e1b9c8b180bffc4ef853fdf5f4bf2) [0x0002e] in <9b7155c91894495b8816a38798bde195>:0
at A.c8e90713531c57022813e92202711dbd5.c34c7aad8f3ba72762bbeed1be3bace04 (A.c323b374042cd3040715f1835f9a00a5c cf92249fb171d54e031580709bdd89675) [0x0006d] in <9b7155c91894495b8816a38798bde195>:0
at A.cbbb560bfd0154564f3a0626f8038689f.c30df0c3c041b3f873986da0d50525d49 (A.c323b374042cd3040715f1835f9a00a5c cf92249fb171d54e031580709bdd89675) [0x00472] in <9b7155c91894495b8816a38798bde195>:0
at A.cbbb560bfd0154564f3a0626f8038689f.c077dd37237eaa481d92c8d5146b3a4df () [0x00029] in <9b7155c91894495b8816a38798bde195>:0
at A.c38222ca4c7726912417aaf2b844619a2.c73b0a6ec93bdf5cb21397ffa5eec223e (System.Boolean c9803eeca9e1f49872d3e83fc93c3edbd, System.Boolean cd5cb57b8432dc11a0cfb6135c32c553f) [0x0001e] in <6edae96ed0f145a396477517f239eae8>:0
at A.c38222ca4c7726912417aaf2b844619a2.c08958c8e40d88f3f6d4bf4e248b06263 (System.Boolean cd5cb57b8432dc11a0cfb6135c32c553f) [0x00115] in <6edae96ed0f145a396477517f239eae8>:0
at A.c38222ca4c7726912417aaf2b844619a2.c5bfb9e4a1ca2bb96dbad42292cd27346 () [0x00000] in <6edae96ed0f145a396477517f239eae8>:0
at A.c38222ca4c7726912417aaf2b844619a2.c8f2e6a7f53848d0262f2bdc864661f6e () [0x0000c] in <6edae96ed0f145a396477517f239eae8>:0
--- End of stack trace from previous location where exception was thrown ---
at (wrapper managed-to-native) AppKit.NSApplication:NSApplicationMain (int,string[])
at AppKit.NSApplication.Main (System.String[] args) [0x0003d] in <87136c6c6f2e41eea18d0a86c05d1f2e>:0
at A.cf7391eac3051280550fc2b95b031ac78.cf0dc1cfd9b511309d6fbd24be6ac2187 () [0x0000b] in <6fdf43e0cbdc48e48506fdfc8a4d5845>:0
at A.cf7391eac3051280550fc2b95b031ac78.cf80ac4075cce562eb8254151c47d3e24 () [0x0000a] in <6fdf43e0cbdc48e48506fdfc8a4d5845>:0
at A.cf7391eac3051280550fc2b95b031ac78.cf80ac4075cce562eb8254151c47d3e24[ceaa9d1a76410934033f88a1b7444f6db] () [0x00039] in <6fdf43e0cbdc48e48506fdfc8a4d5845>:0
at A.cf7391eac3051280550fc2b95b031ac78.cf80ac4075cce562eb8254151c47d3e24[ceaa9d1a76410934033f88a1b7444f6db] (System.String[] cbf612d2839f2a4d8fdc49b2c83b19051) [0x00006] in <6fdf43e0cbdc48e48506fdfc8a4d5845>:0
at A.cdd520c65dd8e922550634a1652d62e71.cd00ca868e3a2e07e1a60509ada71b4d9 (System.String[] c35db0c6ba23194a1143852629dee5eb1) [0x0017e] in <6edae96ed0f145a396477517f239eae8>:0

Best regards
Christof

Clock2 yrs

Hello,

Using SQL Server as your data source, you are probably not the only one using RDM in your organization.

Is there some RDM Windows users in your organization? If yes, which version are they using? Is it possible for one of them to go in File -> My Data Source Information and send me a print screen of that report?

Best regards,



David Grandolfo

signaturesignature

Clock2 yrs

Hi,
We have the same problem using RDM Enterprise with Windows and Mac clients as well.
Windows client ver: 12.0.8.0
Mac client ver: 4.6.0
One of us updated the his mac client to RDM ver 4.6.1 and have the same error. Other win and mac users with above versions can access the database.
Thanks in advance!
Regards,
Peter

Clock2 yrs

Hello David,

send you PM

Clock2 yrs

Hi,

We've found the issue.

While RDM Mac 4.6.1.0 came with changes for the SQL Server data base, it didn't come with the upgrade script for said data base. We'll release a new version this week with the missing data base upgrade.

In the meantime, the workaround would be for one user to update to RDM Windows 13.x and install the data base update, which should solve the issue for other users.

Best regards,

Xavier Fortin

signaturesignature

Clock2 yrs

Hello,

thank you for your help!

BR Christof

Clock2 yrs

Thank you for your quick help!
Regards, Peter

Clock2 yrs