GPPT – GP Power Tools

A remove range operation on table ‘SY_Current_Activity’ failed accessing SQL data

error1

You’ve probably encounter this error message on rare occasions in Dynamics GP, but be prepared for seing an increase with GP 2015 & up.

Recently I was working on a case with a customer that upgraded last fall (2016) from GP 2010 to GP 2015, and ever since the upgrade, the users who access GP over Citrix exclusively (no local GP clients) had randomly issues with pop-ups denying them access to some of the 50 GP companies.. The corporation has office mainly on the east-coast and also over in Asia, thus making the maintenance more difficult with the 13-hours timeshift, as the system is busy most of the 24h in a day.

error2

However, as they also use tons of 3rd-party ISV products and some customization, it was hard to pinpoint the culprit / faulty module. At some point we thought that it was the “inactivity” timer of the Rockton Toolbox that was causing this, but it made no sense to me, especially as the companies were not in the user’s access list.. Disabling the feature in RSTB was only a temporary solution, as you can guess that with so many companies, comes also a lot of users and more than often they don’t exit GP properly, leaving their session run on the Citrix server.. doubled down with the fact that there was no timeout set for inactive sessions, it wasn’t helping either. On top of that, the company is using FastPath for SSO and as I discovered later, FP does also have a feature for ‘inactivity’ timeoout.. As both were enabled (FP & RSTB), it becomes really though to diagnose the source of the problem.
We tried to enable the DexSQL tracing with the help of GP Power Tools, but as it occured only randomly, it was not a solution, since all users accessed GP thru 2 Citrix servers, the logs were growing fast (because enabled to all users) and it was slowing down the system.

By early 2017, we had a confirmation from Rockton that it might have been a bug related to the Toolbox ‘inactivity’ timeout feature, and thus applied the latest build with big hopes. Alas, only a few days later, the problem was back again with some users out of Asia reporting the pop-ups.. Strangely it occured mostly at Asia’s business hours (during night on east-coast) or very early in the morning on Eastern Time. My suspiscion started towards some maintenance job that would kill user sessions without further validation, but couldn’t find any tangible hints. I tried also by all kinds of back-end manipulation of the ACTIVITY table to reproduce the behavior and get the error message, as I suspeced the shared DEX.ini  to be causing this (DEX.ini stores the last company ID when a user exits GP).

At the end, as I had a conversion with my good friend & fellow MVP David Musgrave on how I could potentially enable single user tracing, without implementing indivual user DEX.ini config files, he suggested to have a look at the ACTIVITY table from the DYNAMICS DB, and check for potential triggers that could fire up at a bad time. Low & behold, it turned out that starting with GP 2015, Microsoft implemented new feature in GP that required a trigger on the ACTIVITY table to proceed with some clean-up work on company DB tables, which whne happening under a context when users were logged into another company at the same time to which they didn’t had access, would cause the infamous pop-up to show on screen.. confusing the users about the company they didn’t access to.

Read the details in David’s blog post about the underlying details and a (temporary) resolution. For now, the trigger was simply disabled on the ACTIVITY table, to confirm the source of the problem. Further action is required to resolve the issue on a long term basis with Microsoft and/or 3rd-party providers.

https://winthropdc.wordpress.com/2017/03/08/delete-or-remove-range-errors-on-sy_current_activity-table-after-gp-2015-r2/

 

Categories: Citrix - TS, Dynamics GP, GPPT - GP Power Tools | Leave a comment

The All-New-GPPT finally released… in BETA.

It was worth the waiting … on July 7th, David Musgrave finally announced the long waited successor of the Support Debugging Tool (aka #SDT), under the new name GP PowerTools (#GPPT).

Soon as I got the link to the download area, I went to pick up the firt built of the new package and the next day installed it.. and there is when I ran into troubles.. I had previously applied on my GP2015 test bed system upgrades to go from GP2010R2 to GP2013R2, and 2015 RTM, so I was coming from a previous release of SDT that was running fine under GP2013R2, and still had all the references in 2015.. Since I couldn’t survive without the SDT very long, Dave was kind enough to provide me a pre-build for 2015 of the actual SDT, so I could test properly the new GP.

That being said, the new setup of the GPPT comes with a few tricks if you already have an old SDT installed… and you need to be careful the way you apply the update.  I don’t wanna repeat what David already wrote, so for more details about what to care for to install the new #GPPT, go and have a look at today’s blog post about the public BETA setup.

The current BETA release has a time-bomb built-in that will expire the product on August 15th, 2015. By that time David will either have released another BETA with an extended expiration date, or feel confident enough that #GPPT is ready for prime-time release on the commercial level. Yes.. the new #GPPT will no longer be available for free since David doesn’t work anymore for Microsoft and has to work hard to get the bread on the table too :-).. But  the inital launch price should be very affordable at 365$/yr and everyone should get a license to support that super tool that took years of development to reach this level of quality (that’s less than a coffee cup a day !). Just the current BETA release required several hundred hours of work to add in new features and functionality that will make you fall in love again with GP’s administration (in case you just divorced from it 🙂 )..

Here are a few ones just to show you.

  • The Company selection screen. David included some of it’s VBA code that he wrote in the past to allow to enlarge the company selection list from the login screen, because sometimes it was very hard to figure out which company to select when they all started with the same or similar names.. To enable this feature you have to navigate into the GPPT Administrator Settings > Company tab, and in the middle of the screen, check the box called ‘Add extra width to company name drop down list…’
GP widen Login screen

GP widen Login screen

  • Another one I love is the all new Security Log enabler.. in the old #SDT when a user had security issues, you would walk up (or connect) to the end-user and start the security profiler to track what’s causing the issue, then export the log to XML by file or e-mail, re-import it with your POWERUSER role user and load the profiler trace to figure out what’s not working.  The new Security Log allows you to enable all this directly from your workstation on the product level itself. To enable this, you navigate again to the Administrator Settings > General tab, and at the bottom check the box “Enable Security Activity Tracking”.

    Centralized Security tracking log

    Centralized Security tracking log

  • Finally another nugget is the fact that you can now setup a different password for the GPPT administrator and for the System protected area password. This way you can delegate or share some of the powerful functions of GPPT without revealing the system password.

    Image 2015-07-08_134943

    Dedicated GPPT Admin password

Lots of new functions to still discover, so stay tuned as I’m going to report more about my findings on the new #GPPT.

Until next post, have a great time.

@GP_Beat

Categories: Dynamics GP, GPPT - GP Power Tools, SDT - Support Debugging Tool, System Administration | Leave a comment

Create a free website or blog at WordPress.com.