Analytical Accounting Installation Troubleshooting

Service Pack 5 affects Microsoft Dynamics GP 10.0 logon performance

From the archive. This post dates from the blog’s Dynamics GP and early Power Platform era. Products and screenshots may have changed since it was written.
No need to be alarmed, but if you currently use Analytical Accounting with Microsoft Dynamics GP 10 and have applied the recently released Service Pack 5, you may experience slow logon performance due to extra records being added to the dbo.syMenuMstr table each time a user logs into the system.

As a temporary fix and workaround, you can setup a SQL Server job to run once a day (more depending on the number of users in your environment) that will clear the offending records:



use DYNAMICS;
go
delete from SY07110 where CmdParentDictID = 3180;


Upon logon, the menu items for Analytical Accounting are automatically recreated.

For more information on creating a SQL Server job visit MSDN.

Until next post!

MG.-
Mariano Gomez, MVP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/
Analytical Accounting Installation Troubleshooting

Comments

GP User said…
thank you for this. i ran this query and it instantly fixed my problem!
September 22, 2010 at 1:34 PM
Anonymous said…
Does this just cause slowness in the logon process, or a general overall slowness in GP such as when switching from Area Page to Area Page? We have a client that is experiencing an overall slowness in GP since the SP5 install.
October 18, 2010 at 12:18 PM
Mariano Gomez said…
Since the area page is stored in the temp folder, you can try removing all files from the temp directory on the machine experiencing the issue.

Exit GP and close all applications running (including those in the system tray) and go to Start > Run, then type %temp%. Highlight all files then delete them.

Go back to GP and check to see if the problem persist. If you require further assistance I would suggest you contact Microsoft Dynamics GP support as I don't provide support via my blog.

MG.-
Mariano Gomez, MVP
October 20, 2010 at 11:26 AM
Unknown said…
I was able to identify this as being my problems as well with Analytical Accouting. The crazy part is my client does not use AA. How would I remove AA from the database so these references to the 3180 product do not load to the SY07110 table?

Thanks in advance!
October 21, 2010 at 9:49 AM
Mariano Gomez said…
Cogle23,
The simplest way to remove a product from your environment is by removing the dictionary from the DYNAMICS.SET file. There is a KB article available to help you with the steps to remove a product from the launch file.

MG.-
October 21, 2010 at 12:35 PM
Post a Comment