I believe the correct translation for the error is "The conversion of a varchar data type to a datetime data type resulted in an out-of-range value."
Other languages may expect a DD/MM/YYYY format. SQL Server generates this error when there is a mismatch between what is provided and what the SQL Server is expecting.
The Free Tools are normally tested with US default settings and time zones. Given your location and language, try following the advice in the link and see if that resolves the issue.
SQL Data Profiler has been tested with SQL Server 2017 and it does work, so this should not be the problem.
So, I must change my server date and time defaults to MM/DD/YYYY? I can't 'because all the other programs won't work properly. It' s a pity 'cause I just needed this tool ..
I think you misinterpreted my suggestion. I was merely trying to figure out what the actual issue was given your initial post. Let me explain a couple of things.
No where in the profiling step does it presume a US datetime format but instead using the ISO format.
If the problem is related to data stored related date time, there could be a number of explanations. Such as, possible the datetime values being shortened to YYMMDD, in which case that could present problems handling them when comparing ranges using the ISO format. Just a guess.
I believe the Idera resource that monitors the Send To address may be out of vacation. If you could send the logs to richard.giles@idera.com, I'd be happy to look them over.