When you upgrade from any previous versions of GP to 10 or 2010 you will find that security is the biggest thing to change. Many of my users panic when they see this message pop up.
I have found a quick way for me to decipher what permissions they are missing. First it does involved access to your SQL server for GP and access to run SQL Server Profiler. Profiler became my absolutely bff when I started doing heavy GP support. Because all of the users actually have their own SQL login it is easy to isolate SQL activity that is happening for just that user.
So the first thing I do is fire up Profiler and adjust the column filters for the Login of the user that I plan on watching. Then I tell them to hit the button or link or window or what ever keeps giving them the error message. But do not click the “ok” button. When that error dsiplays the last SQL message you see in Profiler should look like this
With that information I run this query in SQL:
select * from SY10700 where DICTID = 0 and SECURITYID = 123
This will give me a list like this
In this case I could choose from either the Admin_company_001 task or the Admin_payrl_001 task to give the appropriate access. This is security so you can also just use this as a guide to find the actual item you are missing. Sometimes I will find they just need access to the task or I will find it just helps me find the particular permission they are missing and I can add that to a task they currently have.
There is a ton of information about security out there. You can find queries that will tell you everything that each user has access to. You will find once you fill the SY09400 with data you can get a ton of information from there as well, but for me when time is of the essence and I need to get that user the correct permissions I have found this is the fastest way for me.