Hey I got your PM sorry was slow respond putting it in forum is always what you should do. It looks like something is wrong with the name of it.
1 Like
I swear we saw this same error not too long ago.
Conversion failed when converting the nvarchar value '40167EECA364_A666_' to data type int.``My guess is the _ characters are causing it.
Ok so do you have SambaConnect on that computer? For Metrik? From what I read updating SambaConnect to newest version fixes it.
No worries @Jesse , I thought you might be busy 
I did notice this in the error log and was wondering where is it pulling that value from. Looks like a Hexadecimal value and yeah I thought of that too. Its “polluted” by the underlines.
Can you try updating sambaconnect? Just click to install it again and let it upgrade.
I just made a full re-installation of it. Should I try creating the document now?
Yes try now and see if it fixed it.
Unfortunately, it didnt.
Try closing Sambapos restarting it then try. Is it the same error?
Try also removing SambaConnect completely and then try.
That error was created by metrik connect. It should resolve by updating to latest version. But I would try deleting it completely.
Which reminds of 
Wait, Ill go uninstall it and remove all the %appdata% and %programdata% too. Ill let you know soon.
That is a specific error and it has been proven that Sambaconnect is the culprit… specifically an older version. That would explain why it works elsewhere.
Deleting just the SambaPOS Connect and reinstalling it didnt solve it but reinstalling after deleting %appdata% and %programdata% did. Not entirely sure which one of those was keeping the dodgy value.
I guess I can continue with my work as it saved the document properly.
Thanks @Jesse this was really helpful.
1 Like
@Jesse I wanted to ask you but I dont want to open a new topic for this but do you know why is the database that has been wiped of all transactions 900MBs in size? Even if it wipes the transaction from it, does it still keep it somewhere and if so, where?
I think that is more of a Microsoft SQL Question honestly. I will look at some information and get back to you on that.
Remember that it stores a lot of stuff in Database not just transactional data.
Looking at dbo._MigrationHistory table, database was created back in 2015 so it makes sense that it has a lot of stuff inside but almost 900MB of stuff?
I am really curious as to what exactly is it saving and does it make sense in keeping it, because its making it bulky and even when its compressed with the internet speed my client uses its very slow when it comes to syncing it with cloud.
You can use mssms to see how big each table is. Right click table press properties then look at storage.
1 Like