Open Forum

Expand all | Collapse all

Econnnect Error on GP2018

Jump to Best Answer
  • 1.  Econnnect Error on GP2018

    Posted 13 days ago
    Hi,

    We have just upgraded to GP2018 from GP2018.
    We are getting errors on Econnect integration.

    Dynamics GP Accounts Payable Exception: Microsoft.Dynamics.GP.eConnect.eConnectException:
    The EXECUTE permission was denied on the object 'taUpdateCreateVendorRcd', database 'XXXX', schema 'dbo'.

    Dynamics GP Accounts Payable Exception: Microsoft.Dynamics.GP.eConnect.eConnectException: '', hexadecimal value 0x02, is an invalid character. Line 1, position 481.
    at Microsoft.Dynamics.GP.eConnect.ServiceProxy.CreateTransactionEntity(String connectionString, String xml)

    Dynamics GP Accounts Payable Exception: OLE IDispatch exception code 0 from .Net SqlClient Data Provider: The SELECT permission was denied on the object 'PM30300', database 'XXXX', schema 'dbo'...

    Dynamics GP Accounts Payable Exception: Microsoft.Dynamics.GP.eConnect.eConnectException: The EXECUTE permission was denied on the object 'taUpdateCreateVendorRcd', database 'XXXX', schema 'dbo'.
    at Microsoft.Dynamics.GP.eConnect.ServiceProxy.HandleSqlException(FaultException`1 ex)

    I tried running Grant,sql on company database as well as DYNAMICS database but it didn't work.

    I appreciate all the help


    ------------------------------
    Umit Ciltas
    Applications Manager
    ------------------------------
    Academy - Online Interactive Learning from Experts


  • 2.  RE: Econnnect Error on GP2018

    TOP CONTRIBUTOR
    Posted 12 days ago
    Hello Umit,

    Did you do an in-place upgrade or did you migrate to a new server?

    If you are on a new server, the first thing I would do is verify all of the code in your integration points to the new server.  You may have something like a SQL stored procedure or view that has the old server name hardcoded.  Then I would verify the SQL permissions of all of the accounts that are associated to your integration (i.e. the logon for the service:  eConnect for Microsoft Dynamics GP 2018 Integration Service).

    Chris



    ------------------------------
    Chris Donnelly
    Sr Mgr of Info Systems and Financial Reporting
    Healthmark Industries
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 3.  RE: Econnnect Error on GP2018

    Posted 12 days ago
    HI Chris,

    We upgraded on a new server.  So we had to move the logins and restore the databases on the new SQL server.
    SQL 2017 on Win 2016 box.

    I will double check the integration connection again but connection is successful.
    Stored procedures are all original ones from system so we did not develop them.
    I have realized some of those stored procedures are encrypted.

    I have not checked the econnect service account but I will verify that

    Thank you

    Umit

    ------------------------------
    Umit Ciltas
    Kissimmee FL
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 4.  RE: Econnnect Error on GP2018

    TOP CONTRIBUTOR
    Posted 12 days ago
    Hi @Umit Ciltas,

    I agree with Mike.  When I've seen errors similar to yours it has been rooted in the SQL permissions of the user that is associated with the eConnect for ​​Microsoft Dynamics GP integration service.

    Running the grant script for that is a good start.  You'll also want to make sure that user has been granted the DYNGRP permissions on the relevant databases.

    Thanks,

    Samantha


    ------------------------------
    Samantha Higdon ,CPA,CGMA
    Consultant
    Lagom, LLC
    Carmel IN
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 5.  RE: Econnnect Error on GP2018

    Posted 12 days ago

    Yes, econnect user is in DYNGRP both in DYNAMICS and company database.

    Thank you
    Umit Ciltas

    ------------------------------
    Umit Ciltas
    Kissimmee FL
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 6.  RE: Econnnect Error on GP2018
    Best Answer

    TOP CONTRIBUTOR
    Posted 12 days ago
    Did your eConnect installer have sysadmin permissions to the SQL Server? Also make sure for the installation time that that person is also a local admin on the eConnect Server location. That way all eConnect pieces are put in place properly. Reinstall or repair the eConnect service if not.

    The other possibility is the eConnect integration code AD User doesn't have the needed GP/SQL access.

    Do your errors on the eConnect Server Event log have the Service account in the error or the Integration User AD account(Current User Name)?
    Event Viewer > Applications and Services Logs > eConnect

    ------------------------------
    David Morinello
    Senior Dynamics GP Systems Architect
    Ascend Learning, LLC
    Leawood KS
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 7.  RE: Econnnect Error on GP2018

    Posted 12 days ago

    Hi David,

    That was it.
    eConnect integration code AD User doesn't have the needed GP/SQL access.
    It was not in the company database DYNGRP role.
    It was in DYNAMICS database.

    Everyone was on point and were very helpful
    Thank you for quick response.

    Umit Ciltas
    Applications Manger

    ------------------------------
    Umit Ciltas
    Kissimmee FL
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 8.  RE: Econnnect Error on GP2018

    GPUG ALL STAR
    Posted 12 days ago
    @Umit Ciltas I agree with all of the above.​

    Basically, though, if you are upgrading from one version to the next some tables may change in the Stored Procedures.

    If you are on a new server, does it have a different 'sa' password, and if so, have you installed the right version of eConnect with the permissions for the new 'sa'.

    Is eConnect set to use the users credentials when writing to SQL? If so, you'll need to make sure the users' AD Accounts are all setup on the new/upgraded server.

    Is your eConnect pointing to the new instance, if there is a new instance?

    If you are using a front-end like SmartConnect, have you upgraded SmartConnect to the new version, etc.

    ------------------------------

    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 9.  RE: Econnnect Error on GP2018

    SILVER CONTRIBUTOR
    Posted 12 days ago
    One other thing that you need to note is that if you have any customized eConnect stored procedures (those usually have a name beginning with 'ta') you will need to re-create those after the upgrade as GP will update them with the out of the box stored procedures.

    ------------------------------
    Jeff Woodard
    Chief Technical Officer
    Transportation Financial Services, Inc.
    West Palm Beach FL
    ------------------------------

    Academy - Online Interactive Learning from Experts


If you've found this thread useful, dive deeper into User Group community content by role