16 Feb’17

BIODBC Error Scribe Insight

Error in Scribe Insight:
“Conversion failed when converting date and/or time from character string” when connected to SQL Adapter.

When do we get this error?
When we create a SQL connection using ODBC or OLEDB adapter in Scribe Insight and use the same either as Source or Target connection in Scribe DTS.

What is the root cause of this error/issue?
It’s the date-time format of the machine where the scribe Insight DTS is being run.

How can we reproduce the error?
In the windows, DateTime settings, change the format for time with separator as (.) instead of (:). Open the Scribe Workbench and create a sql connection using odbc\oledb connection, create a target connection, map some fields and run the DTS. You will get the error.

Simply change the time format to have the colon separator instead of (.)

Hope this helps. I have found that having the time format other than colon separator creates error while working with other ETL tools as well.

Written by

Team Member


Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.

Want to streamline your business processes?

  • This field is for validation purposes and should be left unchanged.

Recent Articles

  • How to hide the Delete button in a page in Microsoft Dynamics NAV

    21 March’ 2018

    Introduction: By default, Delete button is visible on every page in the Home tab but if we do not want the user to dele...

    Read more
  • Managing mailbox through Email Archiving

    20 March’ 2018

    Introduction: Email can fill your Outlook Inbox quickly – new messages, replies, and forwards. Before you know it, yo...

    Read more
  • Workaround to Report.SAVEASPDF in NAV 2018

    20 March’ 2018

    Objective: In NAV 2017 Emailing the PDF by running the report using Report.SAVEASPDF is now not allowed in NAV 2018. Th...

    Read more
  • Dynamics 365 Client Diagnostics

    15 March’ 2018

    Main cause of Performance Issues: Bandwidth and latency are the primary characteristics which affects the performance o...

    Read more
  • Closing Blind Shift in MPOS and CPOS in Dynamics 365 for Retail

    15 March’ 2018

    Manual For closing Blind shift in POS: Blind shifts terminate the currently ongoing shift and when logged in a new shif...

    Read more