Microsoft Dynamics GP 2018 Logging in to a company slow

(0) Share

Report

Posted on by Community Member

Hello,

We have recently upgraded to GP 2018 and are experiencing really slow login times after choosing a company. Once a user is logged in, it can take anywhere from 30 to 120 seconds for the home page to load. Once everything is loaded, everything moves just fine. Since we have over 150 databases, some users log into multiple companies in a single session, and this slowdown can impede their work day.

The set up:

Two RDS workstations, 4 cores, 16GB of RAM, Windows Server 2016

GP Client Application

One DB server, 8 cores, 64GB of RAM, Windows Server 2016.

I followed the Microsoft Whitepaper recommendations and I don't see any physical hardware limitations, but am not sure where to look further.

Thanks in advance

*This post is locked for comments

I have the same question (0)

All responses (16)

Answers (0)

Richard Wheeler 75,850 Moderator on at

Like (0)

Report

I would start eliminating things off their home page until you find what is running slowly.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Actually, I have already tried this and forgot to put it in my note. First thought it was the connect window trying to get out to the internet, but even after eliminating all windows I still have the same issue.

Was this reply helpful? Yes No
Richard Wheeler 75,850 Moderator on at

Like (0)

Report

I would suggest at a time when no one is in GP to run SQL Profiler and then have one user log in and see what is executing. Perhaps this is isolated to only certain users?

Was this reply helpful? Yes No
RRcharles 37 on at

Like (0)

Report

We are seeing some of the same issues with all users after out upgrade to GP 2018. It is 'snappy' up to the login page, once you select the company it seems to take some time. I turned on the DexSQL messages and am seeing some errors that are not making sense. We have Mekorma for check printing.

We are seeing several error messages that do not make sense..

LSTATE:(37000) Native Err:(102) stmt(144653176):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Incorrect syntax near 'USE'.*/
/*
/* Date: 11/06/2018 Time: 20:57:27
SQLSTATE:(37000) Native Err:(102) stmt(144648656):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Incorrect syntax near 'USE'.*/
/*
/* Date: 11/06/2018 Time: 20:57:28
SQLSTATE:(S0002) Native Err:(208) stmt(144675896):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid object name 'CPY20100'.*/
/*
/* Date: 11/06/2018 Time: 20:57:31
SQLSTATE:(08004) Native Err:(911) stmt(144668664):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Database 'DYNAMICSselect' does not exist. Make sure that the name is entered correctly.*/
/*
/* Date: 11/06/2018 Time: 20:57:31
SQLSTATE:(37000) Native Err:(102) stmt(144695120):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Incorrect syntax near 'USE'.*/
/*
/* Date: 11/06/2018 Time: 20:57:31
SQLSTATE:(37000) Native Err:(102) stmt(144702352):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Incorrect syntax near 'USE'.*/
/*
/* Date: 11/06/2018 Time: 20:57:31
SQLSTATE:(37000) Native Err:(102) stmt(144705064):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Incorrect syntax near 'USE'.*/
/*
/* Date: 11/06/2018 Time: 20:57:31
SQLSTATE:(37000) Native Err:(102) stmt(144705968):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Incorrect syntax near 'USE'.*/
/*
/* Date: 11/06/2018 Time: 20:57:31
SQLSTATE:(37000) Native Err:(102) stmt(144694216):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Incorrect syntax near 'USE'.*/
/*
/* Date: 11/06/2018 Time: 20:57:31
SQLSTATE:(37000) Native Err:(102) stmt(144705968):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Incorrect syntax near 'USE'.*/
/*
/* Date: 11/06/2018 Time: 20:57:41
SQLSTATE:(S0022) Native Err:(207) stmt(144701448):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name 'RM'.*/
/*
/* Date: 11/06/2018 Time: 20:57:41
SQLSTATE:(S0022) Native Err:(207) stmt(144701448):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name 'PM'.*/
/*
/* Date: 11/06/2018 Time: 20:57:41
SQLSTATE:(S0022) Native Err:(207) stmt(144701448):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name 'Include_Opening_Balance'.*/
/*
/* Date: 11/06/2018 Time: 20:57:41
SQLSTATE:(S0022) Native Err:(207) stmt(144701448):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name 'Opening_Balance_Type'.*/
/*
/* Date: 11/06/2018 Time: 20:57:41
SQLSTATE:(S0022) Native Err:(207) stmt(144701448):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid column name 'CHEKBKID'.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(3701) stmt(144655888):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure '##zDP_1904457S_1', because it does not exist or you do not have permission.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(3701) stmt(144655888):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure '##zDP_1904457UN_1', because it does not exist or you do not have permission.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(3701) stmt(144655888):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure '##zDP_1904457N_1', because it does not exist or you do not have permission.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(3701) stmt(144655888):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure '##zDP_1904457F_1', because it does not exist or you do not have permission.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(3701) stmt(144655888):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure '##zDP_1904457L_1', because it does not exist or you do not have permission.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(3701) stmt(144655888):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure '##zDP_1904457S_2', because it does not exist or you do not have permission.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(3701) stmt(144655888):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure '##zDP_1904457N_2', because it does not exist or you do not have permission.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(3701) stmt(144655888):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure '##zDP_1904457F_2', because it does not exist or you do not have permission.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(3701) stmt(144655888):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure '##zDP_1904457L_2', because it does not exist or you do not have permission.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(3701) stmt(144655888):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure '##zDP_1904457SI', because it does not exist or you do not have permission.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(3701) stmt(144655888):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure '##zDP_1904457SD', because it does not exist or you do not have permission.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(208) stmt(144646848):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid object name 'CPY20100'.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(3701) stmt(144652272):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure '##zDP_0274457S_1', because it does not exist or you do not have permission.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(3701) stmt(144652272):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure '##zDP_0274457UN_1', because it does not exist or you do not have permission.*/
/*
/* Date: 11/06/2018 Time: 20:57:44
SQLSTATE:(S0002) Native Err:(3701) stmt(144652272):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot drop the procedure '##zDP_0274457N_1', because it does not exist or you do not have permission.*/
/*

Was this reply helpful? Yes No
Richard Wheeler 75,850 Moderator on at

Like (0)

Report

When you installed GP, which country did you choose? US or Canada? I am wondering if you have a difference between the company in the databases vs the country on the client.

Was this reply helpful? Yes No
Dan Peltier on at

Like (0)

Report

One thing that I've seen cause slow logins are an excessive number of records in the SY07140 table. This table will have a dozen or so records with a blank userid, these are the 'default' records. Each user should have one of each of those defaults. Customizations or modifications to menus and shortcuts can bloat this table. Run a select statement against that table for the userid having the issue, and see how many records there are. If there's a lot, delete them all for the user account and during their next login, the records will be recreated from those 'default' records.

Was this reply helpful? Yes No
RRcharles 37 on at

Like (0)

Report

Thanks! I deleted the additional records in the SY07140. It is still slow loading.

Not sure why I am getting these messages in the log..

Cannot drop the procedure '##zDP_0274457N_1', because it does not exist or you do not have permission...

Was this reply helpful? Yes No
Dan Peltier on at

Like (0)

Report

Those just mean the Dex engine is finishing up whatever it was doing. Anything we work with temp tables, temp Dex procs are used to manipulate the data, and when the process finishes, we run the drop/delete statements twice, to be sure they're gone. These are just the second of the two, saying the proc IS gone.

The only thing I see, is references to Canadian Payroll, so Richard's question is more relevant.

Try a clean install of GP, no third parties, directly on the SQL server. Rule out Mekorma. If you have shared dictionaries over the network, move them local. Reset homepage role, check for/remove reminders.

Was this reply helpful? Yes No
MG-16101311-0 26,225 on at

Like (0)

Report

Can you try the following:

Open Group Policy on your SQL Server. Under Local Computer Policy, select Computer Configuration > Windows Settings > Local Policies > Security Options. Locate "Network Access: Named Pipes that can be accessed anonymously". Double-click to open the policy setting window and type SQL\QUERY. Click OK to save the change and close the Local Group Policy Editor window. Have the user or users attempt to log into the system to see if performance is improved. Please post back and let me know if this worked. I will explain in more detail if it did.

NOTE: This change does not require the SQL Server server to be rebooted.

Was this reply helpful? Yes No
RRcharles 37 on at

Like (0)

Report

Mariano, I was going to reach out to you...Unfortunately, this did not make a difference. I see Mekorma for Canadian Payroll also installed...is this installed by default?

Also, the login and company selection screens come up really fast. It is after we select the company and you get the message 'applying personal settings' that the Dynamics window goes blank for about 15 seconds before the side navigation bar within Dynamics comes up. Thanks!

Was this reply helpful? Yes No