You’re offline. This is a read only version of the page.
220
Hi,
We have a newly upgraded GP 2013 environment. I have two users who are coming across the following issue: when they go to transactions they see the following message: "You don't have security privileges to open this window error message. Contact your system administrator." I have looked at previous posts and have the role and security settings as they are described. It does not prevent a user from actually completing the intended action; they just click 'ok' and continue, but it does appear.
Any assistance appreciated.
Thank you.
*This post is locked for comments
I had a similar issue for a user with restricted access to Payables Transaction Entry. When they closed the Payables Transaction Entry Distribution window, an error popped with 'You don't have security privileges to open this window. Contact your system administrator' etc. They were able to continue after selecting Ok in the error message.
As per the earlier responses from Bill, Kirk, Leslie, etc, it seemed likely that there was an issue with an unseen window or report. I started SQL Profiler immediately before selecting the Distributions Ok button again. It referred to 'aaWinWasOpen from AAG20001' and 'exec DYNAMICS.dbo.zDP_SY10000SS_1 'user1',-1,3180,22103,2'. The references to an AA table and dictionary 3180 (Analytical Accounting) made it likely that an AA security issue was the problem. After some testing, I created a new Security Task ID 'TRX_AA_001_02' (copied from TRX_AA_001*) which I restricted to two Operations (both called Analytical Payables Transaction Entry. As I couldn't tell them apart, I included both). In Security Task Setup, Category = Financial, Product = Analytical Accounting, Type = Windows, Series = Sales (strangely, they were listed under Sales and not Purchasing), and the two Operations were named 'Analytical Payables Transaction Entry'.
I then allocated the new Task ID to one of the user's custom Security Roles. After that, the error no longer occurred when the user selected the Ok button from the Distribution window.
Andy Cashman
Seqola Australia
Hi,
I would install the Support Debugging Tool (FREE). When this kind of error presents itself, you will get information about exactly which resource cannot be accessed as well as the dictionary that contains that resource.
Installing this tool really makes these kinds of issues a breeze to manage.
Kind regards,
Leslie
Did you import all the customization to all your client machine after the upgrade?.
Have you attempted to change users right after the upgrade?
Did you export logins from previous version before the upgrade and import the same logins from the new version so as to ensure that the same users have the corresponding logins and privileges in the new version?.
which window is giving an error?
RomRyan
Here is the window that we came across this issue with.
In your dexsql log you are looking for something that looks like this.
{CALL DYNAMICS.dbo.zDP_SY10000SS_1 ('User Name' , 'Company ID','Module', 'Security ID', 'Object Type')}
In my environment this is what it looks like for this report.
{CALL DYNAMICS.dbo.zDP_SY10000SS_1 ('KIRK', 1, 346, 22492, 2)}
Let us know if you got this resolved.
Kirk
Just following up to see if this has been resolved - with what Kirk has posted, wondering if you have solved this, if you would post the solution for the rest of the community.
Thanks.
It sounds like their is a dummy report being called. When we upgraded to GP 2013 I had this happen with a Manufacturing report and if I recall correctly it was the sales transaction entry window the user was actually going to. I believe the name of the report contained the word dummy but I don't recall the exact name. In the end I had to create a desql log to find out which report it was and then update the user security to allow them access to the report (even though there isn't an actual report in this case).
Let me know if you want the exact report name. I can look it up in the morning.
Regards,
Kirk
I just went to a user, and it occurs in the payables Transaction Entry after she clicks the 'Distribution' button. She clicks 'ok'. Then the Distribution screen opens. When she clicks on the 'Distribution Reference' line, it pops up again.
Please send a screen clip if you can.
It never fails. If you click ok, it goes away, and the user may proceed to do whatever they had intended.
To read more into this - you have 2 of 4 users getting the errors - all users have the same security rights?
Can you post a sample of one user screen that works and one example where it fails.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (