4.0 Roles and Permissions

jag333
jag333 Member Posts: 27
edited 2006-01-27 in NAV/Navision Classic Client
We are experiencing a problem when we assign a company to a specific database login in the Role screen. When the users try to log in with an ID that has a role with a company restriction, they get the following message:
'You do not have permission to read the Object table.'

We did not have this problem in 3.7, and, in 4.0, if we take the company out of the role, they do not get the error but can open any company. Any ideas?

:-k
Jen

Comments

  • jag333
    jag333 Member Posts: 27
    Does anyone have any ideas or has anyone else seen this before? We are wondering if it is a Navision issue or if it has something to do with our add-on...
    Jen
  • kai
    kai Member Posts: 9
    I had the same problem just yesterday.

    Solution: Create a new role with just read permission on the object table and maybe 'Member Of' table. I called this role LOGIN.
    Do not assign a company to this role.

    Make every user member of this role.
  • sblot
    sblot Member Posts: 21
    did the user have the ALL role assigned??

    the ALL role have permission on the system table.
  • jag333
    jag333 Member Posts: 27
    I took the company name out of the "All" role and I was able to get into the software, however, the list of company names came up even though I only gave the login permission to one company with the rest of the role ID's I used.
    Jen
  • jag333
    jag333 Member Posts: 27
    I also tried creating the LOGIN role and that didn't help. Also, I looked at the setup for the ALL login and it has read permission to both the Object table and the Member Of table... Any other ideas? Am I doing something wrong?
    Jen
  • neilgf
    neilgf Member Posts: 148
    ](*,)

    Having exactly the same problem as Jen with version 4 Navision (Swiss version) database ('You do not have permission to read the Object table') so if anyone has any ideas, please let me know. ALL permission certainly seems to cover these permissions so I don't understand!

    Needless to say user id SA does not have the same issue!

    Neil
  • ara3n
    ara3n Member Posts: 9,258
    Have you synchronized after changing permissions? In 4.0 you have to synchronize everytime you make changes to permissions
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • jemmy
    jemmy Member Posts: 247
    If you are using SQL option, the login id should be exist in the Microsoft SQL Server, if not you can't use synchronize functionality.
    What I did are:
    1) create the login ID in the SQL Server
    2) assign them to Navision
    3) set the role
    4) set each specific permission

    Hope this helps...

    Jemmy
  • neilgf
    neilgf Member Posts: 148
    Thanks for the advice. Synchronisation fixed the problem but I now have another!

    I can now log in using the user id. I then have the select the company and when I do I get the standard windows crash screen (send / don't send) and Navision then restarts. Tried a number of times but same result!

    Any ideas what I am doing wrong?

    Neil
  • zarryn
    zarryn Member Posts: 29
    Are you using Update 1 for 4.0? There were some security updates.

    Read more about it here: http://www.mbsonline.org/forum/topic.asp?TOPIC_ID=13228
    Zarryn
  • jag333
    jag333 Member Posts: 27
    Synchronize? How do I synchronize? We don't use SQL so maybe that's not an option? I'm not sure since we have our own add-on and it's possible that the form for database logins might have been copied over from 3.7 inadvertantly...
    Jen
  • neilgf
    neilgf Member Posts: 148
    Tried update 1 and no impact. Same problem. Found out SP1 is due out September - apparently.

    Anyway, tried various other suggestions re making user database owner (not a good idea) and they all did not work. ](*,)

    Then our IT guy changed login from database server authentication to authentication login. All gone away! \:D/

    Also had another problem re date not valid. Suggested fix to switch off time logging on users and in GL set up. Again worked.

    Thought this may be of interest!

    Neil
  • siriporn
    siriporn Member Posts: 2
    Dear

    I have problem to assign company to user. the above error occurred.

    I using Native Database, not SQL. :-k

    Could you please suggest how to exactly solve the problem.

    Thank you so much !!!

    Siriporn
  • Tim81
    Tim81 Member Posts: 68
    siriporn wrote:
    I have problem to assign company to user. the above error occurred.

    You can solve this problem very easy. There are two possibilites. First you create a new role, second you extend the role "ALL".

    Second is easier. Assign the role ALL (alternatively the new role) to the user WITHOUT ASSIGNING A COMPANY.

    Extend the ALL-role with (or insert in the new role) this Permissions:

    1. TableData - 2000000001 - Object (NOT AllObject) - Read
    2. TableData - 2000000003 - Member Of - Read
    3. TableData - 2000000061 - User Menu Level - Read, Insert, Modify, Delete

    This should work.
  • ningnongjin
    ningnongjin Member Posts: 42
    hi all,

    i'm also facing the same situation, no permission to read objects table. i didn't have this problem when assigning user to specific companies using SQL database, but with the proprietary one it's really bugging me.
  • jag333
    jag333 Member Posts: 27
    I looked at my permissions again for the ALL role and see that the permissions recommended for tables: Object, Member Of and User Menu Level are all set as they should be. I still can't assign a company to a login without getting the Object table error. Using Native Navision.
    Jen
  • Forester
    Forester Member Posts: 8
    Good day !

    Enybody solve this problem to asociate Role with Company

    I cann't .

    I use Navision database.
    I tryed to give permissions to table 'Objects', but this don't work.

    Help me
  • Forester
    Forester Member Posts: 8
    Does Enybody can solve this problem?

    Please help who can!

Categories