TM Master Common Errors
- 5.2.0 SendAsDeniedException error when using smtp.office365.com for emails
- A connection was successfully established with the server, but then an error occurred during the login process
- Attaching files to component - Error: Object reference not set to an instance of an object.
- Data at the root level is invalid. Line 1, position 1
- Error Moving File From Temp Folder COMM Folder
- Error when opening Inventory -> Spare parts
- Error when TM Master upgraded to higher version
- Failure Sending Mail - Possible Fixes
- Language Compatibility Issues Turkish, Portuguese & Spanish
- Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
- Object reference not set to an instance of an object - SetSparePartImage
- OutOfMemory
- Printer does not support A4 papersize
- Rebuilding / Reorganisation of Indexes
- Report Header Name is Shorter Than 3 Characters
- System.ArgumentException: Parameter is not valid.
- System.Exception: RelatedDataView is Disposed
- System.NotImplementedException Module rights for Batch Job App
- System.Runtime.InteropServices.COMException
- System.Runtime.InteropServices.COMException. The remote procedure call failed
- System.Xml.XmlException: Invalid character in the given encoding. Line 1, position 1.
- The conversion of a varchar data type to a datetime data type resulted in an out-of-range value (Norwegian format)
- The conversion of the varchar data type into datetime produced an out of range value Spanish/Portugese Date Format
- The process cannot access the file because it is being used by another process.
- The specified string is not in the form required for an e-mail address
- The timeout period elapsed prior to completion of the operation or the server is not responding
- Transport level error - The semaphore timeout period has expired
- Transport level error - The specified network name is no longer available
- Unable to add SRF report (System.Runtime.InteropServices.COMException. The remote procedure call failed.)
- Visual Styles-related operation resulted in an error because visual styles are currently disabled in the client area
Error when TM Master upgraded to higher version
Error when TM Master upgraded to higher version
System.ArgumentException: These columns don't currently have unique values.
at System.Data.ConstraintCollection.AddUniqueConstraint(UniqueConstraint constraint)
at System.Data.ConstraintCollection.Add(Constraint constraint, Boolean addUniqueWhenAddingForeign)
at System.Data.DataTable.set_PrimaryKey(DataColumn[] value)
at TmMv2.Version20662.UpdateConsumablesUserRights()
at TmMv2.Version20662.UpdateDbData()
at TmMv2.DbVersionCheck.UpdateDbData(Int32 currDataVersion)
at TmMv2.TmMv2Startup.StartNext(Boolean SkipUserCheck)
at TmMv2.TmMv2Startup.Start(Boolean SkipUserCheck)
at TmMv2.My.MyApplication.MyApplication_Startup(Object sender, StartupEventArgs e)
- When upgrade the TM master from lower version (2.661) to higher version (2.665) mostly this error message will prompt while launch the TM Master for login.
- IT will require to check in the ‘tmsystem’ table in the SQL, whether the ‘DataVersion’ column has been upgraded to higher version (2.665)
Run this query in SQL to check : - select * from tmsystem;
- Here ‘DataVersion’ column has not been upgrade as per ‘DBVersion’ column, which should be same to run the TM master with upgraded version.
Run the below SQL query to make the DataVersion same as DBVersion :-
update tmsystem set dataversion = 20665;
- Once the query executed successfully, TM Master will allow to login with upgraded version (2.665)
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article