Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
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.
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.
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?
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.
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.
Business Applications communities