web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / eConnect Failed to con...
Microsoft Dynamics GP (Archived)

eConnect Failed to convert parameter value from a String to a Date/Time

(0) ShareShare
ReportReport
Posted on by Accounting Department 1,552

community.dynamics.com/.../97625.aspx

I am also having this error.  The problem is, this integration works fine from user workstations, but we get the error when trying to run the integration in GP2010 on terminal server.

When I remotely connect to the Terminal Server, I can see the date/time format is the same as on my workstation (m/dd/yy).  Yet, I get the error on TS.

The user logs into TS using an rdp file and also gets this error.

Seeing as it works on my workstation, it is not a problem with the data source.

 

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Have you logged in to the TS server using the user who runs the eConnect and configured the date format? Setting the date format for the logged in user is not enough.

  • Accounting Department Profile Picture
    Accounting Department 1,552 on at

    I have logged into the TS remotely as myself and tried running the integration.  I also get the error, yet it works from my local client. I made sure they both had the same Regional Settings and Date settings.

    The data source is a View I created in the GP database.  I even tried using Convert(date,[DOCDATE) instead of just the DOCDATE.  Is there another conversion I should be trying?

  • Accounting Department Profile Picture
    Accounting Department 1,552 on at

    Sorry I misread your reply - I thought I had to change the date format for the user running the Integration.

    This time I logged in as the user that was configured to run eConnect when eConnect was installed... I changed the regional settings and restarted the service.

    I logged back in as the user running the Integration and it ran successfully for me and another user.

  • Community Member Profile Picture
    Community Member on at

    I had a similar error using smartConnect a third party tool which was built around the econnect framework. I solved it by making sure that the date formats were the same and the integration ran smoothly. Thanks to this discussion it helped me get my stuff working.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans