Hello
I have a problem with my eCconect access.
I create a new account(only read for safety) to access GP via eConnect.
But it is denied to access GP.
I really do not know what else to do.
I hope someone helps me.
Thanks!
Hello
I have a problem with my eCconect access.
I create a new account(only read for safety) to access GP via eConnect.
But it is denied to access GP.
I really do not know what else to do.
I hope someone helps me.
Thanks!
Hi
Thanks your help!
I have gave the access as Read Only to 8 companies in DB.
But error message is same of before.
Could you help me to find problem?
Thanks again!
Thanks your help!
There is a 'eConnectOut' stored procedure in both the system and company databases for Dynamics GP.
If you run this script against your GP databases, is it present in the database?
Select * from sysobjects where name = 'eConnectOut'
If not, you can re-create it from the Database Maintenance Utility to re-create stored procedures.
Thanks
Thanks for reply.
I encountered a problem as follows,please help me to check again.Thanks!
Log Name: Application
Source: Microsoft.Dynamics.GP.eConnect12
Date: 4/14/2020 9:43:37 AM
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: wms.ziyong.local
Description:
Action:
Get
Current User Name:
My\ziji
Input parameters:
Exception type:
System.InvalidOperationException
Exception message:
The stored procedure 'eConnectOut' doesn't exist.
I'm not quite following, but for eConnect, more times than not, it is going to use the service account you specified during the install of eConnect as the 'eConnect COM User', which is also the account that will be running the eConnect service.
This user account will be used to access the eConnect business objects, Incoming Service, outgoing Service and COM+ application. This account must be a member of the DYNGRP database role in the Microsoft Dynamics GP system and company databases on your SQL Server.
If you made a change to the eConnect service account and/or the account doesn't have access to Dynamics GP, try adding it to the DYNGRP database role under all GP databases, in SQL Server and see if that doesn't resolve the issue you're seeing with access being denied for Dynamics GP.
Thanks,