Options

Session table problems after upgrade to 4.0SP3

Lieutenant_BobLieutenant_Bob Member Posts: 15
Hi there, and a happy new year to you all!

I have a problem, and was wondering if any of you have encountered something similar.

After an upgrade to 4.0SP3, i have what appears to be a rights management problems, but seems to dwelve deeper than that.

I have a custom form, where you can make a list of items below a head, a standard Navision way of doing things. It has been in production for a long time.

After the upgrade, when users tried to add an item, an error occurs:

"You do not have permission to read the Session table"

Well, I thought, easy breazy. I go to the users Roles, and add the "200000009 Session table" with read privileges. Didnt change a thing, even after restart of Navision.

Well, I thought again, a little less easy, but still managable. I try myself, and being of the "Super" role, no surprises, worked like a charm. I momentarily add the user as "Super", just to test, and I restart his client and: Same result. Error message.

This seems odd, so I try with other users, and all to the same result. They can't add new lines, and I can.

If it is not a rights management problem, what could id be? Any thoughts would be appreciated.

Thanks in advance!

Bob
Clothes make the man. Naked people have little or no influence on society.

Answers

  • ara3nara3n Member Posts: 9,258
    Are you on sql?
    which security model have you setup? regular or enhanced?

    If enhanced, did you synchronize security?
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • bestbest Member Posts: 1
    User role "super" is irrelevant for this problem. I discovered that
    you must have db_owner permission on sql server to get read permission for table "session".

    user 1 ("super" without db_owner) : can´t read table 2000000009
    user 2 ("super" with db_owner) : can read table 2000000009

    I also tested table 2000000010. The same problem occured.
    I guess that all "system" tables are affected by this behavior.


    We use the sql server option with regular security system.
  • kinekine Member Posts: 12,562
    You just need to grant select privileges for $ndo$shadow on view Session in your DB. You do not need to be DB_Owner.
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • Lieutenant_BobLieutenant_Bob Member Posts: 15
    Happy New Year Guys!

    Again I must bow to the wisdom of the allmighty forum.

    Kine's advice worked perfectly, and the post by "best" really narrowed my question down to the essentials.

    Thanks. You made my start of 2007 alot easier.

    Bob
    Clothes make the man. Naked people have little or no influence on society.
  • kinekine Member Posts: 12,562
    This solution was found by our customer and I am just using "their" knowledge... 8)

    Please, shall you add the [Solved] prefix into subject of your first post in this thread? Thanks...
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • Lieutenant_BobLieutenant_Bob Member Posts: 15
    Thanks, Kine.

    I have added the [Solved] to the subject.

    Bob
    Clothes make the man. Naked people have little or no influence on society.
Sign In or Register to comment.