Before investigating any DataShare Connect error validate that the SME can access the data through their Accounting Package.
This is the best way to double check the SME is using the correct credentials and has the correct access permissions for the data they are trying to upload.
If the user is unable to access the data using the credentials in their possession then it follows that DataShare Connect will be unable to access the data using the same credentials.
For DataShare Connect to access the Microsoft Dynamics GP data the you will need to know;
- Which version of Microsoft Dynamics GP you wish to upload data from.
- The SQL Server Instance Name.
- The SQL Server User ID and Password that can access the Microsoft Dynamics data.
- Which Company you want to upload data from.
If DataShare Connect does not detect Microsoft Dynamics GP correctly.
If DataShare Connect does not detect the Microsoft Dynamics GP package correctly on an SME's desktop check;
- Registry key "SOFTWARE\Microsoft\Business Solutions\Great Plains" exists with a subkey for each version of the Microsoft Dynamics GP that is installed. (Check the WOW6432Node key on x64 machines). If this key is not found it is most likely that the accounting package installation is in some way corrupted - get the SME to logon to the accounting package and check for correct operation.
Errors will be reported in the log file in the %appdata%\validis\logs folder.
This is the file that will be used by support to investigate and fix your issue. Visit this page for more information.
If DataShare Connect refuses the Microsoft Dynamics GP credentials.
If the credentials the SME is supplying to DataShare Connect are refused you need to check that the SME actually has access to the SQL Server where the dynamics database exists. Use Microsoft SQL Management Studio to try to connect to the database and login to the database using the credentials supplied. Type the credentials in rather than use credentials cached in SQL Management Studio or the SME's password manager.