Forum / Remote Desktop Manager Mac - Support

Can't assign Roles

  • Create an Issue
  • Cancel

Hi,

everything in the new DB works fine but if i try to assign roles to a user i get the following Error:

Unable to save the user in database!

Field 'CreationDate' doesn't have a default value

Greetings

Clock13 days

Hi,

I can't reproduce this.


Could you provide you Application Log (Help -> Application Logs -> Open)? There might be additional info in it that might help.

Best regards,

Xavier Fortin

signaturesignature

Clock13 days

sure:


[07.11.2018 14:47:44 - 6.0.1.0 64-bit]ERROR MySql.Data.MySqlClient.MySqlException (0x80004005): Field 'CreationDate' doesn't have a default value
at MySql.Data.MySqlClient.MySqlStream.ReadPacket () [0x00096] in <1add403c719d4eeeae437db5aa8f6c1a>:0
at MySql.Data.MySqlClient.NativeDriver.GetResult (System.Int32& affectedRow, System.Int32& insertedId) [0x0001e] in <1add403c719d4eeeae437db5aa8f6c1a>:0
at MySql.Data.MySqlClient.Driver.GetResult (System.Int32 statementId, System.Int32& affectedRows, System.Int32& insertedId) [0x00000] in <1add403c719d4eeeae437db5aa8f6c1a>:0
at MySql.Data.MySqlClient.Driver.NextResult (System.Int32 statementId, System.Boolean force) [0x00022] in <1add403c719d4eeeae437db5aa8f6c1a>:0
at MySql.Data.MySqlClient.MySqlDataReader.NextResult () [0x00205] in <1add403c719d4eeeae437db5aa8f6c1a>:0
at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader (System.Data.CommandBehavior behavior) [0x002ad] in <1add403c719d4eeeae437db5aa8f6c1a>:0
at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader () [0x00000] in <1add403c719d4eeeae437db5aa8f6c1a>:0
at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery () [0x00033] in <1add403c719d4eeeae437db5aa8f6c1a>:0
at A.c62151df7d13ceddef73b4c42194d331e.c3dea6f32f6a4c2f28ec22f618fe1c67f (Devolutions.RemoteDesktopManager.Business.Entities.UserEntity c03a060829e6ffb23a02a911a6c7f9354, System.Data.IDbTransaction cb0e84463dceab1dc0c9748e2f11fdfc1) [0x0041f] in <b81932db67c44bb4a9944935865c675b>:0
at A.c1386f0c36ceb87c848f150120d1ce698.c273918d0a77199f99e4ccbadcbe5b91f (Devolutions.RemoteDesktopManager.Business.Entities.UserEntity c03a060829e6ffb23a02a911a6c7f9354, System.Boolean c58958e21b2557e9fded09d64ed2f0da7, System.String c20a45f64caf6be3bb404afc7e28da849, A.cc920622727084c42f744018197caa94b+ca7828b2254254d519b31a1653896889d c4272a7a2a87934de86e05f41660dd2a6, System.Guid[] c65b4a5d45794dc5ff1b454aef988e35e) [0x001a9] in <b81932db67c44bb4a9944935865c675b>:0

Clock13 days

Hi,

This looks like a schema error.


Could you send us you data source schema? You can do this in the data source configuration window, under the Upgrade tab. The button is Email Schema to Support. Just mention my email in the message (xfortin@devolutions.net) so the support forward it to me.

Best regards,

Xavier Fortin

signaturesignature

Clock13 days

done!

thank you!

Greetings

Clock13 days

hi,

any updates?

Greetings

Clock8 days

Hi,

I've sent you a private message (through the forum) with something I'd like you to try. Have you perhaps not received it?

Best regards,

Xavier Fortin

signaturesignature

Clock8 days

Hi,

oh sorry, i didn't saw it.

Every Statement works except:

ALTER TABLE rdm.LoginHistory MODIFY COLUMN CreationDate datetime null; ERROR 1171 (42000): All parts of a PRIMARY KEY must be NOT NULL; if you need NULL in a key, use UNIQUE instead


------------
But: Roles are are working now!


Thank you very much!
--------------
Are there some additional steps or is everything ok now?


Greetings

Clock8 days

Hi,

It should be OK, but it is hard to be sure. Especially as this was already a particularly weird issue. If you get any other issues, just come back to us with it and we'll work it out.

Best regards,

Xavier Fortin

signaturesignature

Clock8 days

Hi,

It was a completely new database. Should i clear it and recreate everything or is there currently a problem with the initializing script? (I also could try to initialize the DB with a windows client)

Thank you very much for your help!

Greetings

Clock8 days

Hi,

I'm not the most savvy SQL user, but if I remember correctly, this was an issue of some (or all) triggers not triggering. This issue as been observed with other users and is probably server specific. We do not know why as of yet though. I doubt you'll see any benefit in recreating and you'll probably end up having to do the script I've sent you regardless.

Best regards,

Xavier Fortin

signaturesignature

Clock8 days

Hi,

ok, thats fine, just wanted to know if i can optimize the situation because we needed the new DB.

(maybe also a container db problem)

Thank you for your time and excellent support!

Greetings

Clock7 days