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
5.2.0 SendAsDeniedException error when using smtp.office365.com for emails
The "5.2.0 SendAsDeniedException" error message that can occur when using Microsoft's SMTP server is due to the techniques Microsoft uses to fight spam. Please note that this error comes from the mail server and is simply forwarded to you through the TM Master v2 interface. If you encounter this error message either in your TM Exchange logs or when trying to send emails from TM Master v2 (including RFQs and POs in the procurement process), then you or your IT department need to explicitly allow the email account you have set up for SMTP in TM Master v2 to send emails as the relevant user email accounts. You can find step by step instructions from Microsoft on how to this here:
Please note that due to the "Test SMTP" and "Test settings" functions using a hardcoded dummy email address, these tests will continue to trigger the error even after you have made the changes described above. For this particular issue you should disregard the SMTP test result and instead test by sending an email from TM Master v2. We suggest for example that you try sending a report or an RFQ to your own email address. If this succeeds then your settings are working.
If the error occurs when sending emails from TM Master v2 (including RFQs and POs in the procurement process) do the following:
The account set up for sending such emails in your database can be found under [System -> Settings -> Mail settings -> SMTP login name]
Make sure that the "SMTP login name" account is allowed to send as all relevant user email accounts using the instructions from Microsoft linked above.
If the error is found in the TM Exchange logs do the following:
Go to [System -> TM Exchange settings -> Settings] and make sure that [Sender address] is the same as [User name], or if you want them to be different use the instructions from Microsoft linked above to allow the [User name] to send as [Sender address].
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