You’re offline. This is a read only version of the page.
Announcements
9
Hello ,
We recently acquired 10 new Limited User Type licenses along with our current Full licenses. Entered new Registration keys and created new user with Limited license type but user is unable to login in spite of having just Inquiry access in GP. When user logs in first user is getting "don't have security privilages..." error, when click ok Company login window is displaying and when click ok user is getting below SQL error. I ran Dex Log but i couldn't find any thing substantially. Interesting part is, when same user has been changed to Full license then user is able to login successfully and i also checked SQL Server with both Full and Limited user has same access to Dynamics and Company db. Not sure what's going on, please help if anyone have seen this behavior before ? FYI, i also ran Grant SQL. Attached Security tasks which are configured for Inquiry role. We are using GP 2018 R2.
Check this post
community.dynamics.com/.../dynamics-gp-limited-license-type-help
As previously noted, GP Limited User Licenses work very well for users who need inquiry/reporting access but should not be altering data.
You can set up a Full-License User who is only assigned the LIMITED USER roles.
Please check this blog post , this gives you details of what Limited users can do along with roles.
Limited licenses do NOT be able to perform all A/P duties. They can be assigned to security that allows for inquiring/reporting on data but they won't be able to do things like enter or post transactions. [They will be able to enter self-service transactions like their own payroll time and purchase requisitions.]
We often recommend Limited licenses for management-level positions where the user needs to inquire on data but not enter/modify data.
Thanks David and Lisa for your response, issue was related to one of GP customizations.
Also as Lisa mentioned. Using GP Power Tools will help you identify the security issues on login.
David
To fix the SQL error. Restore the default regional settings.
Using dots/periods in the date format does not work for the code that is failing. I have seen dots in AM/PM cause time to fail.
It is caused by code that uses STR() rather than sqlDate() and sqlTime() functions.
Using STR() will also means the code will fail in countries that use dd/mm/yyyy date formats.
Bad code that needs fixing.
David
The following statement is the issue.
/* Date: 04/08/2022 Time: 17:26:06
stmt(146554056):*/
BEGIN DECLARE @stored_proc_name char(41) DECLARE @retstat int DECLARE @param5 int set nocount on SELECT @param5 = 0 SELECT @stored_proc_name = 'IAA.dbo.uprBuildHomepageDataGridTempTable' EXEC @retstat = @stored_proc_name '', '1900.01.01', '-4714.11.30', '##2070626', @param5 OUT SELECT @retstat, @param5 set nocount on END
/*
Update:
When i checked closely Dex SQL log i noticed this statement which is giving SQL Date to string conversion error. Looks like UPR10501 is Payroll module table and we don't even use this module.
/* Date: 04/08/2022 Time: 17:26:06
SQLSTATE:(01000) Native Err:(0) stmt(146554056):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]insert into ##2070626 select distinct TimeCard.PayCode, TimeCard.UNTSTOPY, TimeCard.TRXDATE from UPR10501 as TimeCard where TimeCard.EMPLOYID = '' and TimeCard.TRXDATE >= '1900.01.01' and TimeCard.T*/
/*
/* Date: 04/08/2022 Time: 17:26:06
SQLSTATE:(22008) Native Err:(241) stmt(146554056):*/
[Microsoft][SQL Server Native Client 11.0][SQL Server]Conversion failed when converting date and/or time from character string.*/
Do you have add-in products that may need to be added to the security? Run a GP/SQL log to see what items are having an issue.
[If you have access to GP PowerTools, it can help troubleshooting this as well.]
#1
André Arnaud de Cal...
291,359
Super User 2024 Season 2
#2
Martin Dráb
230,370
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
