Tuesday, September 02, 2014

Tech Tuesday: SmartList Builder needs to Finish Installing at Every Login

We hope you had a restful Labor Day weekend! To start the week off we have a Tech Tuesday article from our SmartList Builder guru, Jared Dux, who is addressing an error that some users have been experiencing when upgrading SmartList Builder. 

 


Some users will experience this message even after performing their current upgrade correctly. This happens because SmartList Builder is looking for a specific table structure and if it is incorrect this message will appear at every login. The most likely cause was during a previous upgrade going to GP 2010 R2 some tables were not updated by GP Utilities. More specifically in this instance a field called Blank_Field_CB was supposed to be added during the upgrade process. At this point checking the dexsql.log file will show which tables have invalid columns and verify that Blank_Field_CB is missing.

If you do not have a dexsql.log you will need to switch the following three lines in the Dex.ini to equal TRUE:
 

SQLLogSQLStmt=TRUE
SQLLogODBCMessages=TRUE
SQLLogAllODBCMessages=TRUE


Once you are sure this is causing the message you can download the script here and execute against the DYNAMICS database. Make sure to back up the database before running the script.

If you have any questions regarding SmartList Builder please email us at sales@eonesolutions.com!

Thursday, August 28, 2014

eOne Labor Day Hours

It's official - summer is winding down, classes are starting up and eOne is getting ready for a fun and busy fall season. We'll be sharing the events we're participating in and some of the new training options with you in the coming weeks. In the meantime though, we'll be joining in with many in the US to take a break for Labor Day. If you're in the US, we hope you have time on Labor Day to rest and enjoy time relaxing with friends and family. 


With that in mind, our office will be closed on Monday, September 1st and will reopen on Tuesday, September 2nd. In the meantime, feel free to utilize our website to order products and services, obtain reg keys, view renewals, download products and get access to all sorts of information. 

If you are not able to find the answers you need, please reach out to our team: 

Tech support requests: support@eonesolutions.com 
Sales inquiries: sales@eonesolutions.com 
Marketing inquiries: marketing@eonesolutions.com
Renewal inquiries: renewals@eonesolutions.com 

Enjoy the holiday and we look forward to talking with you on Tuesday!

Tuesday, August 26, 2014

Tech Tuesday: How to Perform a SQL Trace to Debug eConnect Errors


This week's Tech Tuesday article is from our Support Guru, David Youngquist, who will walk you through how to perform a SQL trace to debug eConnect errors. 

1. Find out what user the eConnect service is running under. Press the Windows + R key on your keyboard to bring up the Run command. Type in “services.msc” and hit enter. This will open the services window. Find the “eConnect for Microsoft Dynamics GP 20XX Integration Service”


2. Once you find the service, right click on it, go to Properties, and go to the Log On tab.  Write down the user that is used there. In my screenshot the user is eonedemo\Administrator:
 

3. Open SQL server management studio and connect to the SQL server that is storing your GP databases. Once in management studio, go to Tools – SQL Server Profiler. This will open the profiler window. It should automatically open a Trace Properties window. If it does not, just go to File – New Trace.  

4. In the Trace Properties window, change to the Events Selection tab and uncheck the top three events. (see screenshot)


5. Click on the Column Filters button (shown above) and highlight Login Name. Then click on the Like button and put in the name you found in step 2. In my case it was eonedemo\administrator


6. Click OK and then click Run on the Trace Window. 

7. Go into SmartConnect and run the map you are getting the error on. Once you get the error, stop the trace by clicking on the stop button at the top of the window. Then go to Edit - Find and type in the procedure name you are trying to trace, in this case it’s the taUpdateCreateCustomerRcd procedure. Once you find where the error occurred copy the data from the bottom part of the window. 


8. Run the query in Query Analyzer and see what result you get. In my case I got an error 251, which is an eConnect error code.  


9. To find the eConnect error, run the following query. Select * from Dynamics..taErrorCode where ErrorCode=XXX. In my case, the error was 251, so I replaced XXX with 251.


10. My error is telling me that the Customer ID already exists and the Update If Exists flag is set to not allow updates.

If you have further questions regarding eConnect errors please search our Knowledge Base articles or email support@eonesolutions.com for more information.