I ran across an odd eConnect issue a while back that I thought I’d share today. In this case, the customer had recently updated to GP 2010 and updated their application to eConnect 2010 from the previous version that worked fine.
Following the release of Build 16 of the Support Debugging Tool , I want to take you through how to configure the SQL Profile Tracing functionality so you can gain the benefits of this awesome feature. The Support Debugging Tool has always been able to capture a DEXSQL.LOG of the communication between the Dynamics GP Application and the SQL Server, but when a Stored Procedure is called on the SQL Server, we lose visibility of what is actually happening at the SQL Server. Now with SQL Profile Tracing we can see exactly what is happening at the server as well and match this information with other logs we have at the user interface, Dexterity application and SQL Server levels.
There has been a lot of talk lately about the year end close Payables and Receivables. I feel like I have spent the last week or two justifying my reasoning for not needing to perform the year end close for Payables and Receivables to many of my customers and blog readers. (For more on this, please see my Year end close in Dynamics GP blog post .) My main reasoning has always been that the only thing accomplished by the year end close is updating the ‘amounts since last close’ year-to-date and last-year totals and since that can be easily (and maybe even better?) accomplished by a custom report, why waste time on the year end close for these modules in GP
One Response to Error Code 2337 When Installing Microsoft SQL Server Into A Virtual Machine. Pingback: Error Code 2337 When Installing Microsoft SQL Server Into A Virtual Machine | azurecurve – DynamicAccounting.net ..
As a follow on from yesterday’s post, Quick Tip: Passing Variables to SQL Server , I wanted to discuss the related topic about passing of date and time variables.