GP2015 R2 Upgrade – “ASI_MSTR_Explorer_Favorites: Number of results columns doesn’t match table definition”

There were couple of exceptions related to GP2015 R2 that I wished to share here. One would be discussed here and other one on the next post.

After upgrading to GP2015 R2, while doing a routine testing, following error message was thrown while trying to open Smartlist:

Screen Shot 2015-07-31 at 6.53.32 PM

Full message as follows:

Unhandled database exception:
A get/change operation on table ‘ASI_MSTR_Explorer_Favorites’ failed accessing SQL data.

Number of results columns doesnt match table definition.

Number of results columns doesnt match table definition.


Debugging this error took me to the table Smartlist Favorites Master (ASIEXP81). Strange, however, that number of columns indeed matched.

I remembered this issue happening in GP 10 and GP 2010. Suggested solutions were to run GRANT.SQL on all databases and changing ODBC provider to SQL Native Client. However, in my case, both were already done and confirmed.

To avoid any further delay or issue(s), I decided to backup the records from ASIEXP81, recreate the table using GP SQL Maintenance and push the records back from the backup table.

Resolution: Drop and create the table Smartlist Favorites Master (ASI_MSTR_Explorer_Favorites, ASIEXP81) using GP SQL Maintenance.

Only that, I did not have to reinsert the records. When I opened the Smartlist after recreating the table, it automatically populated all records. Strange, again. But it worked.

Word of caution: Always take backup before you do anything with the data.


GP2015 R2 Upgrade – GP Utilities “SynchronizeTableData()” Error & Fix

This issue has already been reported and it’s also been addressed. I would like to post this still. To act more like a pointer. It’s quite crucial in nature.

I have been testing GP2015 R2 upgrade on my test environment when I faced the following error message:

Screen Shot 2015-07-27 at 6.10.32 PM

Quite evidently, upgrade didn’t go through after. I remembered this being posted on our GP Support & Services blog. Dug the post and got the solution.

Here’s the post: Known Upgrade Issues When Upgrading To Microsoft Dynamics GP 2015 R2

Please note that this has been fixed already and is available with June 2015 Update.


#GPPT Welcome to the GP Power Tools Public Beta

Vaidhyanathan Mohan:

#MSDYNGP #GPPT David has released GP Power Tools public beta. Fun time ahead.

Originally posted on David Musgrave's Winthrop Development Consultants Blog:

David Meego - Click for blog homepageToday, I am announcing a free public beta of GP Power Tools for Microsoft Dynamics GP versions 11.0 (GP 2010), 12.0 (GP 2013) and 14.0 (GP 2015).

As you know, I have been working extremely hard on getting GP Power Tools for Microsoft Dynamics GP ready for release and now it is time to get some feedback.

GP Power Tools is the next generation replacement for the Support Debugging Tool.

Read on for more details …

View original 294 more words

GP 2015 R2 Upgrade Issues & Possible Solutions

There is a GP community forum question that discuss about GP 2015 R2 upgrade errors. As always, contributors have poured in their thoughts and possible solutions to fix these issues.

Read the question here: GP 2015 R2 errors during update & Fixes

I recommend this post to everyone who are planning to upgrade to GP2015 R2 soon. This may save a lot of time.

Thank you GP community for being selfless, informative and helpful.


Positive Thoughts for Leslie Vail

Vaidhyanathan Mohan:

My thoughts and wishes for Leslie. Get well soon and guide us as usual.

Originally posted on David Musgrave's Winthrop Development Consultants Blog:

David Meego - Click for blog homepageThis is a shout out for my great friend Leslie Vail. Leslie is a Microsoft Most Valuable Professional (MVP) for Microsoft Dynamics GP and has been a stalwart of the Microsoft Dynamics GP community for many years. She also known as the Dynamics Confessor on her Dynamics Confessions Blogspot.

Between you and me, she does not like it when I mention that she worked with Great Plains Accounting before Great Plains Dynamics 1.0 was even released. So don’t mention it to anyone.

Well, Leslie needs our help.

View original 249 more words

Visual Studio Integration Toolkit replaces Menus for Visual Studio Tools

Vaidhyanathan Mohan:

Great news for Dynamics GP developers/consultants. Menus for Visual Studio Tools has reborn with a new name “Visual Studio Integration Toolkit”.

Originally posted on David Musgrave's Winthrop Development Consultants Blog:

David Meego - Click for blog homepageGreat news for Visual Studio developers.

Winthrop Development Consultants are pleased to announce the release of the Visual Studio Integration Toolkit for Microsoft Dynamics GP (VSIT).

The Visual Studio Integration Toolkit replaces Menus for Visual Studio Tools and is now available for Microsoft Dynamics GP 2010, Microsoft Dynamics GP 2013 (including GP 2013 R2) and also for Microsoft Dynamics GP 2015.

View original 218 more words

CBM Cash Receipt Customer GL Posting Account Error

A user reported this issue when he tried to enter a cash receipt in CBM module. Following error message prevented him from continuing further.

Screen Shot 2015-02-23 at 3.10.24 PM

This error was confirmed to be happening only for one particular customer record. For all other customers, it worked.

We basically do not have posting accounts setup for each customer or customer class. So it is absolutely no way due to missing posting accounts. Several minutes later, decided to compare customer records between this particular customer and one other customer that’s working.

REASON: Customer Class ID for this customer record was wrong and was not part of the list of customer classes that we have setup on our company. Because this class ID was wrong, posting accounts validation stopped right there and threw a message that was totally irrelevant to actual reason.

RESOLUTION: I changed the customer class ID for this customer with an existing one. User could then enter a cash receipt in CBM.

Troubleshooting issues successfully is probably the best way to end a business day!