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) / Integrations with job ...
Microsoft Dynamics GP (Archived)

Integrations with job SQL and eConnect 11.0

(0) ShareShare
ReportReport
Posted on by Community Member

I am trying integrations with eConnect 11 (Dynamics GP 2010 R2) throught a  SQL Server 2008 R2 Job execution, this Job on Step 1 (just one) run as Proxy, the proxy has a Credential, this Credential has a Local Windows User with Administrator policies and Group. Job executes an windows application it contains the eConnect logic.

When I try to run Job, this raise a process and finish it, but I checked it, an error was registered ""

When I try to run application as "Run as Administrator" without Job, the application work perfectly without any errors.

Why? What should I do?

*This post is locked for comments

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

    Sorry, here the full post with the error message...

    I am trying integrations with eConnect 11 (Dynamics GP 2010 R2) throught a  SQL Server 2008 R2 Job execution, this Job on Step 1 (just one) run as Proxy, the proxy has a Credential, this Credential has a Local Windows User with Administrator policies and Group. Job executes an windows application it contains the eConnect logic.

    When I try to run Job, this raise a process and finish it, but I checked it, an error was registered "There was no endpoint listening at net.pipe://localhost/Microsoft/Dynamics/GP/eConnect/EntityOperations that could accept the message. This is often caused by an incorrect address or SOAP action."

    When I try to run application as "Run as Administrator" without Job, the application work perfectly without any errors.

    Why? What should I do?

  • Verified answer
    Community Member Profile Picture
    Community Member on at

    Hi,

    As a test I would check and see what account SQL Server Agent Service is running under.

    I would try updating this account to be a user with Admin privliges and then try and run the job again.

    Hope this helps,

    Adam

  • Community Member Profile Picture
    Community Member on at

    Hi Adam.

    thanks you a lot....your answer worked it!!!

    In Fact, the Account SQL Server Agent Service was running under Local System / Network Service, I Chenged it to an Domain User with Admin Privilegies also I changed the Job Step 1 had a proxy by SQL Server Agent Service account and everything worked perfectly..

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