DBSync Cloud Workflow (iPaaS)

2022

Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Installation & Troubleshooting

Setting up SQL Server Database Permissions

When the Connector runs in two server mode, the eConnect COM+ application uses SQL Server integrated security to connect to the eConnect business objects. During the installation of eConnect, you need to supply a domain user account for the COM+ application. This domain user account need be put in the DYNGRP in SQL Server. To set up the user account, complete the following procedure:

  1. Launch "SQL Server Enterprise Manager" and go to the DYNAMICS database.
  2. Right click User under the database DYNAMICS and choose New Database User.
  3. Add the domain user account to the DYNGRP database role.

FAQ

1. What are the pre-requisite software requirement for DBSync integration with Microsoft Dynamics GP?

The eConnect libraries must be installed (eConnect Documentation) however the full eConnect Runtime module does not need to be installed.

2. Does Dbsync need to be installed on the same machine as that of Microsoft Dynamcs GP?

DBSync Microsoft Dynamics GP (GreatPlains) adapter can be either configured on the same instance GP is installed or on a remote machine which can access GreatPlains database.

3. What are the limitations of DBSync integration with Microsoft Dynamics GP?

The eConnect interfaces do not support every object and interaction available within Microsoft Dynamics GP (Great Plains). If your integration scenario requires working with objects from other modules or more sophisticated queries, you will need to use our Database Adapter for Microsoft SQL Server to connect to backend database tables directly. While this is an option, it is recommended to avoid accessing Microsoft Dynamics GP (GreatPlains) database directly to maintain data integrity and business rule executions.Skip navigation| | http://help.boomi.com/display/BOD

http://help.boomi.com/display/BASDASH/Boomi+AtomSphere+Dashboard Dashboard > Boomi AtomSphere > ...Boomi AtomSphere Help > 3 - Build > 3.2 - Building Connectors > Available Connectors > Great Plains Connector > Great Plains Connector Install and Troubleshooting Guide

 

View

  1. Launch "SQL Server Enterprise Manager" and go to the DYNAMICS database.
  2. Right click User under the database DYNAMICS and choose New Database User....
  3. Add the domain user account to the DYNGRP database role.

    Make sure DTC is running

  4. Launch the Services console by going to Start >> Run and type services.msc. Verify the Distributed Transaction Coordinator service is running.

    Setup Functional Currency in MS-Dynamics GP

    eConnect requires a functional currency to be set up for Microsoft Dynamics GP, even if multicurrency is not being used. To set up a functional currency, do the following:
  5. Open the Multicurrency Setup window in Microsoft Dynamics GP.
    From the menu bar, choose Tools >> Setup >> Financial >> Multicurrency. This example designates US dollars as the functional currency.
  6. Complete check links when needed.
    If a message prompts you to run check links for the multicurrency table, you should do so. To run checklinks, go to File >> Maintenance >> Check Links. Select the series and tables to check. Click OK.

    Common Connection Issues and Troubleshooting

    Error: The partner transaction manager has disabled its support for remote/network transactions

    When making a request to eConnect, you may get exception as below:cli.System.Transactions.TransactionException: The partner transaction manager has disabled its support for remote/network transactions. (Exception from HRESULT: 0x8004D025)
    at cli.System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(Unknown Source)
    at cli.System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(Unknown Source)
    at cli.Microsoft.Dynamics.GP.eConnect.eConnectMethods.eConnect_Requester(Unknown Source)
    at server.eConnect.request(eConnect.java:38)
    at java.lang.reflect.Method.invoke(Method.java:434)
    at gnu.java.rmi.server.UnicastServerRef.incomingMessageCall(UnicastServerRef.java:394)
    at gnu.java.rmi.server.UnicastServer.incomingMessageCall(UnicastServer.java:279)
    at gnu.java.rmi.server.UnicastServer.dispatch(UnicastServer.java:235)
    at gnu.java.rmi.server.UnicastConnection.run(UnicastConnection.java:219)
    at java.lang.Thread.run(Thread.java:744)
    at java.lang.VMThread.run(VMThread.java:76)
    at java.lang.VMThread$1.Invoke(VMThread.java:334)
    at cli.System.Threading.ThreadHelper.ThreadStart_Context(Unknown Source)
    at cli.System.Threading.ExecutionContext.Run(Unknown Source)
    at cli.System.Threading.ThreadHelper.ThreadStart(Unknown Source)
    Caused by: cli.System.Runtime.InteropServices.COMException: The partner transaction manager has disabled its support for remote/network transactions. (Exception from HRESULT: 0x8004D025)
    ... 12 more
    Solution:
    First verify the "Distribute Transaction Coordinator" Service is running on both database server computer and client computers.
  7. Go to Start >> Administrative Tools >> Services.
  8. Turn on the "Distribute Transaction Coordinator" Service if it is not runningIf it is running and Atom is not on the same computer as the database server, on the computer running database server
  9. Go to Start >> Administrative Tools > Component Services.
  10. On the left navigation tree, go to Component Services >> Computers >> My Computer (you may need to double click and wait as some nodes need time to expand).
  11. Right click My Computer select Properties.
  12. Go to the MSDTC tab
  13. Click Security Configuration
  14. Make sure you check "Network DTC Access", "Allow Remote Client", "Allow Inbound/Outbound", "Enable TIP" (Some option may not be necessary, have a try to get your configuration)
  15. The service will restart.
  16. Try to connect from Boomi AtomSphere.
  17. YOU MAY NEED TO ALSO REBOOT YOUR SERVER IF IT STILL DOES NOT WORKOn your client computer use the same above procedure to open the "Security Configuration" setting, make sure you check "Network DTC Access", "Allow Inbound/Outbound" option, restart service and computer if necessary.
    On you SQL server service manager, click "Service" dropdown, select "Distribute Transaction Coordinator", it should be also running on your server computer.

    Error: The transaction has already been implicitly or explicitly committed or aborted.

    When change IP in the local client machine you may get exception as below:Starting call eConnect....cli.System.Transactions.TransactionException: The transaction has already been implicitly or explicitly committed or aborted.
    at cli.System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(Unknown Source)
    at cli.System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(Unknown Source)
    at cli.Microsoft.Dynamics.GP.eConnect.eConnectMethods.eConnect_Requester(Unknown Source)
    at server.eConnect.request(eConnect.java:78)
    at java.lang.reflect.Method.invoke(Method.java:434)
    at gnu.java.rmi.server.UnicastServerRef.incomingMessageCall(UnicastServerRef.java:394)
    at gnu.java.rmi.server.UnicastServer.incomingMessageCall(UnicastServer.java:279)
    at gnu.java.rmi.server.UnicastServer.dispatch(UnicastServer.java:235)
    at gnu.java.rmi.server.UnicastConnection.run(UnicastConnection.java:219)
    at java.lang.Thread.run(Thread.java:744)
    at java.lang.VMThread.run(VMThread.java:76)
    at java.lang.VMThread$1.Invoke(VMThread.java:334)
    at cli.System.Threading.ThreadHelper.ThreadStart_Context(Unknown Source)
    at cli.System.Threading.ExecutionContext.Run(Unknown Source)
    at cli.System.Threading.ThreadHelper.ThreadStart(Unknown Source)
    Caused by: cli.System.Runtime.InteropServices.COMException: The transaction has already been implicitly or explicitly committed or aborted (Exception from HRESULT: 0x8004D00E)
    ... 12 more
    Solution:
    This is because the MSDTC cannot correctly use the DNS server to resolve a new IP address for the local host name after the IP address changing. Restore your old IP or check the DNS settings to make sure the GP DB server can correctly resolve the client host name via DNS server.

    Troubleshooting

    Because the Great Plains application consists of many different modules including eConnect, .NET, Microsoft SQL server, DCOM, MSDTC, etc. initial configuration and troubleshooting can be more involved than with other applications and connectors.
    Most Great Plains connection issues are related to permissions: user permissions and database permissions.
    High-level diagnostic steps:
  18. Verify Boomi Connection configuration
  19. Verify database port
  20. Check the user has the right password and permission
  21. Check the database has the right permissionsUser Permission: eConnect need configure a user (domain user) to have right permission to connect to Great Plains. Below are the details steps to check and make sure the user permission is correct.
  22. Login to the Windows machine installed Boomi Atom.
  23. Go to Start >> Run and type services.msc and click OK to launch the Services console.
  24. Verify the "Distributed Transaction Coordinator" service is started.
  25. Go to Start >> Run and type dcomcnfg and click OK to launch the Component Services console.
  26. Go to Console Root >> Component Services >> Computers >> My Computer.
  27. Right click My Computer and choose Properties...
  28. Go to the Default Properties tab and verify Enable Distributed COM on this computer is checked.
  29. Go to the MSDTC tab and click Security Configuration. Verify "Network DTC Access", "Allow Remote Clients", "Allow Inbound", "Allow Outbound" and "Enable Transaction Internet Protocol (TIP) Transaction" are checked.
  30. Under My Computer folder, right click COM+ Applications and choose Properties...
  31. Click Identifyand verify the user and password are correct and have not been expired or locked from Windows user management tools. The user configured here should be the same user configured in the Boomi Great Plains Connection. To make sure the password and the user account is right, you can retype the password and click Apply. If it is incorrect, it will display an error.
  32. After resetting the Identity, you may need "Shut Down" and "Start" the eConnect COM+ application by clicking the mouse right button as below:Database permission: eConnect need connect to the MS SQL server with the user configured in the above "Identity" tab. The correct permissions are also needed on the database side.
  33. Log into the MS SQL server (this guide illustrates SQL Server 2005).
  34. Start the "SQL Server Configuration Manager" and go to SQL Server 2005 Network Configuration >> Protocols for <server name> >> TCP/IP*. Right click TCP/IP and choose Properties.
  35. On the Protocol tab, verify Enabled is set to "Yes". On the IP Addresses tab, in the IPAll section, verify the port is specified in either the TCP Dynamic Ports or TCP port.
  36. Start "Microsoft SQL Server Management Studio Express", right click your database instance, and choose Properties.
  37. Go to Security and verify "SQL Server and Windows Authentication mode" is checked.
  38. Setup the necessary database permissions for the user. Please refer to the above section "Setup COM+ account DB permission" for details. | | |

     

    Do you have suggestions to improve our documentation? We'd love to hear about them in our Feedback Forums

     

    Adaptavist Theme Builder Powered by Atlassian Confluence

 

This page

 

 

Other pages

 

 

 

Account

 

 

Normal view

 

 

Printable view

 

 

Home page

 

 

Dashboard

 

 

 

News

 

 

Recent updates

 

 

RSS feed builder

 

 

 

Index

 

 

Site map

 

 

Labels

 

 

 

Attachments index (13)

 

 

People directory

 

 

Space activity

 

 

Log in

 

 

 

History

 
  • No labels