You’re offline. This is a read only version of the page.
9,142
Hi David
This is necessarily an issue with the SDT but I thought I recalled seeing somewhere something about this.
One of my clients has quite an extensive security model. We chose not to use the Default User to grant access to all the system stuff as it had too much access in it.
The users are getting a non-access error message, which thanks to the security profiler we have been able to track. It is to resource ID 872.
The Security Information tells me it is excluded from security. Is there any way to grant the security?
Cheers
Heather
*This post is locked for comments
Hi Heather
No Problems.
If you double click (or right click) on a resource on the Security Profiler (after importing the xml), you can jump to the Resource Information window... so you don't have to re-enter or change modes.
You can also jump to Security Information from Security Profiler or Resource Information window using right click menu or Security button.
David
PS: Mummy Brain Syndrome (MBS) happened to my wife too. Don't worry it does go away.... eventually ..... just waiting for the kids to leave home.
Hi David
I had looked for the report in the security area before logging this and could not find it. Of course, I look again today and it is right in front of my eyes.
I didn't know about importing the xml file so thanks for that note. I have gotten to grips with lots of what you have made available in the SDT, but hadn't spotted that.
The other mistake I made was to not change the resource option to reports before putting the resource ID in when using the Resource Information window.
Let's just say mummy brain completely got in the way!
Thanks for your help with this.
Cheers
Heather
Hi Heather
Why are we reading the XML file? You should be using the Support Debugging Tool's user interface.
You can import an exported .log.xml file into the Security Profiler window on your system. This would have made it more obvious that the resource type (Restype) is 23 which has a resource description of Report.
The report with Resource Name (Resname): Purchase Receipts Update Detail by Document (resource id 872) can be found in the Security Task window and added to a Security Task as needed.
Hope this helps
David
Hi David
These are the details from the profiler:
-<Record Rec="14"><Field ID="Sequence Number">14</Field><Field ID="Date">2012/07/28</Field><Field ID="Time">12:45:05</Field><Field ID="Restype">23</Field><Field ID="DictID">0</Field><Field ID="Resid">872</Field><Field ID="Status Description">Denied</Field><Field ID="AltDictID">0</Field><Field ID="Alias">0</Field><Field ID="Intercompany ID">DSL</Field><Field ID="User ID">barb</Field><Field ID="Resource Description">Report</Field><Field ID="Product Name">Microsoft Dynamics GP</Field><Field ID="Resname">Purchase Receipts Update Detail by Document</Field><Field ID="Display Name">Purchase Receipts Update Detail by Document</Field><Field ID="Description"/><Field ID="String A 255">You don't have security privileges to open this window. Contact your system administrator for assistance.</Field><Field ID="IntegerValue">1</Field><Field ID="DictionaryAvailable">0</Field><Field ID="ResourceAvailable">0</Field><Field ID="ModifiedAvailable">0</Field></Record>
Am I reading it wrong?
Cheers
Heather
Hi Heather
You are correct that this is not specifically related to the Support Debugging Tool (SDT), but the tool does help to see what is happening and why the window cannot be found in the Security Task Maintenance window.
The Form with the resource ID 872 in the Dynamics dictionary is called pmStub and has no windows on it.
Forms with no windows, forms with only hidden windows and forms that are used for multiple purposes are usually excluded from security as denying access to them can cause issues.
Forms can be excluded from Security in 3 ways:
1) They have no windows.
2) The main window (first in the list) has a display name of ~internal~.
3) The developer has used the ExcludedFromSecurity() of form sySecurityTaskEntry function or a trigger on the this function to programmatically exclude the form.
A form that is excluded from security cannot cause access privilege errors as access is always allowed. It also cannot be seen in the Security Task Maintenance window.
Please use the Security Profiler to double check what resource is causing the error. I suspect that the pmStub form (resource ID 872) is not the issue.
Let us know how you go.
David
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,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (