Security - You do not have permission.......

headley27
headley27 Member Posts: 188
edited 2009-04-08 in SQL General
Good day,

I am curious what is forcing me to re-synchronize permissions.
I am using NAV 5.0 on SQL 2000.

I have been making some changes to custom functions that affect the side panel of Sales Quotes and Sales Orders.
I think it revolves around custom flowfields and the need to add/modify keys.

Amongst other changes, I modified a custom flowfield in the item table which forced me to modify a key in the Sales Line table. I believe that this was the change that brings up the message....
'You do not have permission to read the Sales Line table. Contact your system manager......'

The user previously had access to the Sales Line table.

When I add/modify/delete a key do I have to re-synchronize permissions with the SQL Server everytime?
I don't recall having to do so in the past.

Any insight would be greatly appreciated.

Thank you.

Answers

  • garak
    garak Member Posts: 3,263
    if you have the enhanced security model (File -> Database > Alter) then yes. If you drop / add / change some fields or keys then u must resynchronizise.
    If you have the standard security model, then u need not to sysnch.
    Do you make it right, it works too!
  • bbrown
    bbrown Member Posts: 3,268
    I have found no good reason to use the "enhanced" security mode. Has anyone?
    There are no bugs - only undocumented features.
  • headley27
    headley27 Member Posts: 188
    Interesting......

    I checked and the Advanced Tab shows Security Model = Advanced.

    I never had to resynch in 3.70 A. In fact, I can't even find this option (there is no Advanced Tab).

    I remember having to resynchronize a number of times...around the time of our conversion to 5.0, but I thought this just part of the conversion process. My Microsoft Partner was surprised that I previously never had to synchronize.
    Now this makes sense, it looks like Enhanced Security was implemented in 4.0.

    I found this when I started investigating further.
    http://dynamicsuser.net/forums/t/19622.aspx

    I am going to switch 'back' to Standard.

    Thanks again.
  • bbrown
    bbrown Member Posts: 3,268
    Enhanced was introduced in 4.0 but many sites complained so they put back Standard as an option in 4.0 (SP2 or SP3 - don't recall).
    There are no bugs - only undocumented features.
  • amarnath
    amarnath Member Posts: 51
    Hi guys one small question on permission do u think in standard mode option in database only one user can login at a time/ does it become a single user mode. I have a system setting of 3 user a sa,windows,test and all these three login can access together and do changes also . but if i move to standard will this work.


    The objective is we need all windows mode login working and for this i need to move to standard login.

    Thanks
    AMARNATH SRINATH
  • DenSter
    DenSter Member Posts: 8,307
    Setting the security model to standard will not set it to single user mode.

    You should really start a new thread when you have a new question instead of piggybacking on someone else's.
    Daniel Rimmelzwaan
    RIS Plus, LLC
  • james
    james Member Posts: 56
    I have a slightly different issue, which sounds like it might be because of the enhanced security model (it's on V4.0 SP0).

    I've added new tables to the database and then added the permissions to a users role. However NAV still thinks that they do not have permission and I suppose a synchronisation will sort this out.

    The thing that has thrown me though, is that I've tried to replicate this problem on the test system (it's configured the same) and I've added these permissions to my user account on there (previously SUPER, but replaced it with a sales persons permissions) and I don't have the issue - it allows me access after logging in with the lower permission level. Could it be that because I was previously a super user that has meant this problem is not occuring.

    It seems really strange, but I'm sure there's a reason for it. Is it possible that the user could be setup wrong on SQL or is it more down to the enhanced security model?
  • headley27
    headley27 Member Posts: 188
    My guess is that you haven't synchronized either scenario....if I read this right?

    New Tables, then New Permissions added for New Tables, No Synch = No Access

    Super User, then Permissions changed to Limited User, No Synch = Super User Access

    In both situations, access rights have not changed because synchronization has not taken place.

    Is this correct?

    Note:
    I have changed from Enhanced to Standard and everything is working wonderfully again. No more headaches.
    I should add that I needed to recreate some Windows Login Permissions that were assigned to SQL Server Tables and Views after I made the change.
    Navision requires you to run the 'Synchronize All Logins' function to finalize the change.
    We use SQL Permissions exclusively within Navision; however, I have created a number of reporting tools outside of Navision using Windows Security.
    Since these Windows Users did not 'exist' with Navision, the 'Synchronize All Logins' function decided to delete all permissions associated with the Windows User Accounts.
    Navision asks if you would like to delete the Windows Users or not, but deletes the permissions regardless of what you choose.
    I simply restored a copy of the database prior to the change and used a few SQL Scripts to transfer the missing permissions to the production database.

Categories