Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

eConnect error when running from SQL Server Agent job

(0) ShareShare
ReportReport
Posted on by 65

Hi all new to the forum. I am getting a troublesome eConnect error.   

I am getting this error:

 

Description: Microsoft.Dynamics.GP.eConnect.eConnectException: 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.

 

Here is some background on my implementation:

 

I am using eConnect 12.0.

I have written a SSIS destination component that uses eConnect to load GL Journal entries. (this all works fine)

I have implemented this with the .net references in the C# code. I basically serialize the data and submit to eConnect.

 

This runs on one server which has SQL and eConnect installed all in one place (I have also done this in a distributed environment).

 

I integrate this SSIS destination component in a SSIS package, which I can successfully run with the correct credentials from these environment and configurations:

BIDS

command prompt (dtexec)

Windows scheduled job

 

Whenever I try to get to configure this as a SQL Server Agent job I run into issues.

 

I have set up a job to run as the appropriate credential.

I refer to a package from the SQL Server package source.

All seems fine.

 

I run and when it gets to the eConnect submission portion it fails with the error abouve. Log follows.

 

I just have a feeling something is not configured or set up correctly to allow me to run in this fashion?

 

 

Microsoft (R) SQL Server Execute Package Utility

Version 10.50.4000.0 for 32-bit

Copyright (C) Microsoft Corporation 2010. All rights reserved.

 

Started:  1:07:11 PM

Progress: 2013-02-07 13:07:12.70

.

.

.

Progress: 2013-02-07 13:07:24.17

   Source: Data Flow Task - Process eConnect GP Journal entries

   Validating: 0% complete

End Progress

Progress: 2013-02-07 13:07:24.23

   Source: Data Flow Task - Process eConnect GP Journal entries

   Validating: 33% complete

End Progress

Progress: 2013-02-07 13:07:24.23

   Source: Data Flow Task - Process eConnect GP Journal entries

   Validating: 66% complete

End Progress

Progress: 2013-02-07 13:07:24.24

   Source: Data Flow Task - Process eConnect GP Journal entries

   Validating: 100% complete

End Progress

Progress: 2013-02-07 13:07:24.24

   Source: Data Flow Task - Process eConnect GP Journal entries

   Prepare for Execute: 0% complete

End Progress

Progress: 2013-02-07 13:07:24.24

   Source: Data Flow Task - Process eConnect GP Journal entries

   Prepare for Execute: 33% complete

End Progress

Progress: 2013-02-07 13:07:24.24

   Source: Data Flow Task - Process eConnect GP Journal entries

   Prepare for Execute: 66% complete

End Progress

Progress: 2013-02-07 13:07:24.24

   Source: Data Flow Task - Process eConnect GP Journal entries

   Prepare for Execute: 100% complete

End Progress

Progress: 2013-02-07 13:07:24.26

   Source: Data Flow Task - Process eConnect GP Journal entries

   Pre-Execute: 0% complete

End Progress

Progress: 2013-02-07 13:07:24.35

   Source: Data Flow Task - Process eConnect GP Journal entries

   Pre-Execute: 33% complete

End Progress

Progress: 2013-02-07 13:07:24.35

  Source: Data Flow Task - Process eConnect GP Journal entries

   Pre-Execute: 66% complete

End Progress

Progress: 2013-02-07 13:07:24.36

   Source: Data Flow Task - Process eConnect GP Journal entries

   Pre-Execute: 100% complete

End Progress

Error: 2013-02-07 13:07:25.03

   Code: 0x00000000

   Source: Data Flow Task - Process eConnect GP Journal entries HBS GP Journal Entries Destination Adapter

   Description: Microsoft.Dynamics.GP.eConnect.eConnectException: 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. See InnerException, if present, for more details. ---> System.ServiceModel.EndpointNotFoundException: 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. See InnerException, if present, for more details. ---> System.ServiceModel.AddressAccessDeniedException: The pipe name could not be obtained for net.pipe://localhost/Microsoft/Dynamics/GP/eConnect/EntityOperations. ---> System.IO.PipeException: The pipe name could not be obtained for the pipe URI: Access is denied. (5, 0x5)

   --- End of inner exception stack trace ---

   at System.ServiceModel.Channels.PipeSharedMemory.Open(String sharedMemoryName, Uri pipeUri)

   at System.ServiceModel.Channels.PipeConnectionInitiator.GetPipeName(Uri uri)

   --- End of inner exception stack trace ---

 

Server stack trace:

   at System.ServiceModel.Channels.PipeConnectionInitiator.GetPipeName(Uri uri)

   at System.ServiceModel.Channels.NamedPipeConnectionPoolRegistry.NamedPipeConnectionPool.GetPoolKey(EndpointAddress address, Uri via)

   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)

   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)

   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)

   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)

   at System.ServiceModel.Channels.CommunicationObject.Open()

 

Exception rethrown at [0]:

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

   at System.ServiceModel.ICommunicationObject.Open()

   at Microsoft.Dynamics.GP.eConnect.ServiceProxy.CreateServiceChannel(ChannelFactory`1 svcChannelFactory)

   at Microsoft.Dynamics.GP.eConnect.ServiceProxy.InitializeServiceProxy()

   --- End of inner exception stack trace ---

   at Microsoft.Dynamics.GP.eConnect.ServiceProxy.InitializeServiceProxy()

   at Microsoft.Dynamics.GP.eConnect.ServiceProxy.GetInstance()

   at Microsoft.Dynamics.GP.eConnect.GetNextDocNumbers.GetNextGLJournalEntryNumber(IncrementDecrement incdec, String BackOfficeConnString)

   at HBSGPJournalEntriesDestAdapter.HBSGPJournalEntriesDestAdapter.GetNextJournalEntry()

   at HBSGPJournalEntriesDestAdapter.HBSGPJournalEntriesDestAdapter.SerializeInvoiceObject(String filename, PipelineBuffer buffer)

End Error

.

.

.

DTExec: The package execution returned DTSER_FAILURE (1).

Started:  1:07:11 PM

Finished: 1:07:25 PM

Elapsed:  13.618 seconds

  

Thanks

*This post is locked for comments

  • Patrick Duffner Profile Picture
    65 on at
    Re: eConnect error when running from SQL Server Agent job

    Dave,

    Thanks for the post. I will be getting back to this issue tomorrow and I will try this suggestion. I will post back findings.

    I could totaly see this working it explains why the Destination Component I have in the package doesn't see eConnect Service running, it isn't allowed to see them........

    Thanks,

    Duff

  • Dave Dusek Profile Picture
    on at
    Re: eConnect error when running from SQL Server Agent job

    Duff,  

    I believe your issue is this:  The pipe name could not be obtained for the pipe URI: Access is denied.

    I was looking at this and it sounded familiar with a case we had a while back.  I wasn't the engineer on it but the error was the same as yours.  The problem was due to the Proxy being used by SQL Server Agent (SSMS | SQL Server Agent | Proxies) not having the correct permissions.

    The Proxy did have SQL Server Integration Services Package permissions however did not have "Operating system (CmdExec)" subsystem permissions.  

    In that case, once they did that, things started to work.  

  • Patrick Duffner Profile Picture
    65 on at
    Re: eConnect error when running from SQL Server Agent job

    Sandip.

    Thanks for the reply. I checked the service and it is running. This particular implementation is using eConnect for Microsoft Dynamics GP 2013 Integration Service I might have said an earlier version on my initial post, sorry. I have the same issue on the earlier versions of eConnect also however.

    The package can run fine on this machine as a Windows scheduled job, from VS, from command prompt.

    This error always happens when I try to run via a SQL Agent Job and configure it as a SQL Service Integration Services Package with run as credentials, these credentials are the same ones I use to run successfully the other ways.

    I agree the error appears as if the service is not running. Wouldn't the service still be running? It's just a different way of running the job, that's why I wonder if I have it configured correctly or there are permissions I still need to grant.

    Thanks,

    Duff

  • sandipdjadhav Profile Picture
    18,297 on at
    Re: eConnect error when running from SQL Server Agent job

    Duff,

    Can you check your eConnect Services are running on the server or not? Make sure 'eConnect for Microsoft dynamics GP 2010 Integration Service' is running.

    Thanks

    Sandip

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

Jainam Kothari – Community Spotlight

We are honored to recognize Jainam Kothari as our June 2025 Community…

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Almas Mahfooz Profile Picture

Almas Mahfooz 3 User Group Leader

Featured topics

Product updates

Dynamics 365 release plans