You do not have permission to run the XXX table.

thetallbloke

Hi all,

I have a rather odd permission issue..

The error I'm getting is :
You do not have permission to run the G/L Entry - GST Entry link table.
Contact your system administrator to have your permissions changed.

Ok, seems like an easy permission problem right..?!??

So I had a look at my permissions, and I have SUPER... I also have full control of the database in SQL Server...

We also have a number of other roles that have specific read/write/modify access to that specific table (253).. I even tried adding in one of those roles to my login... still no joy..

Does anyone have any idea what could be causing this issue for me..????

I had someone remove all my access, synchronise all logins and add my access back and do another synch... still no joy...

I'm at a loss... Any suggestions, no matter how odd would be greatly appreciated...


Thanks

Karenh

It is probably because your license does not include permission for that table. Check your license to be sure that you are using the correct one.

I do not have that table in version 5 SP1. What version are you using?

thetallbloke

Hi Karen,

I'm using Nav 6.0 SP1...

I thought it might be a license issue too, so I reloaded our license in and still no joy...

We have other databases that use the same license file without a problem... this is a dev database that I'm having issues in..

I can't even design the object...
I get a :
"You do not have permission to read the 'G/L Entry - VAT Entry Link' table."

It is very frustrating...

AdamRoue

It means that you have "a" license with access, this has been used and now you have an entry in the table. Using another license has no rights, you cannot open it, design it or anything, but because the table contains data the error is called. This used to happen with partners building a database for a client using the partner license not the clients license. I would guess if you look at it in SQL you will see data in the table.

thetallbloke

Thanks Adam for your post...

But how do you suggest that I go about fixing this problem...???
Delete the data out of that table..???

rdebath

thetallbloke wrote:

I thought it might be a license issue too, so I reloaded our license in and still no joy...

Sorry, I can't think of anything that would give the symptoms you describe except PEBCAK (Thinks that make you go Doh! ); Thought you may be being imprecise here, so, Question 1; which button did you use to the "reload" the license.

Try checking the "Permission range" table (unlisted virtual table; make a form) what permissions does that have on the 'table' and tabledata for that table number. Are system permissions 9010 and 9015 in there too?

Two standard questions just to be sure.
Does the user you're logged in as (to the database) have sysadmin or dbowner access for that database?
Is the database using the Standard or Enhanced security model?

One last thing to note, however, is that the VAT link table is relatively recent, are you sure you're using the most recent version of your DEV license; does it need a refresh?

thetallbloke

G'day Robert,

Ok.. I've done some digging to answer your questions... Since I'm not all that experienced in Nav, I'm fully aware where the problem probably exists...

Ok..
To load in the license I'll give a bit more info.. I have a beefy laptop that is running Nav locally on it.. as in Nav client (classic and RTC), service tier and full SQL 2008 R2 Standard.. It's running 64bit windows 7...
So when I loaded the license file on I went to tools=>License Information=>upload..
I selected my license file and the client told me something like "license file loaded successfully"...

My login in SQL has DBO privs..

On this machine and Nav setup, I'm using Standard security model.

With the permission range table, I created a form to access this and found something weird, but not surprising... really..
Ok, on my machine, I have the following records:

Object Type Index From To Read Permission Insert Permission Modify Permission Delete Permission Execute Permission
Table 22 250 252 Yes Yes Yes Yes
Table 23 254 269 Yes Yes Yes Yes

Ok, so even I can look at this and see that I don't have permission to the 253 table..

However, I did the same thing in another database that apparently is using the same license and I get the following record.

Object Type Index From To Read Permission Insert Permission Modify Permission Delete Permission Execute Permission
Table 22 250 269 Yes Yes Yes Yes

Obviously, in that database I have no problem with the 253 table...

So something seems to be screwed up with either the license file or when the license went in... maybe I need to just remove the current license and load it in again..

Is that possible...??? I believe I have a cronus license here somewhere... maybe I can upload that one and then upload my proper license over the top again...

thetallbloke

I just loaded the cronus license in and then our dev license back in and still the same problem..

I didn't check the Permission Range table, but I'm guessing it'll be the same..

ARGH..!!!

rdebath

Look at it this way; it's a good thing you discovered this missing license file now rather than after the hard disks died on the live machine, isn't it.

Easiest should be to get a new copy of your license file from Microsoft...

But another possibility to get the license file is to extract the license file from the other database. It's normally stored as a blob in the $ndo$srvproperty table in the master database; it's the only thing in there. The blob is unencoded and uncompressed so you just have to extract it to a file.

If it's not there there's a similar license column on the $ndo$dbproperty table in the database itself.

vaprog

Rdebath assumes, your current license is defective or outdated. But there is still another possibility.

There are two places where a NAV license can be stored on an SQL server, the server or the database. License | Upload sends it to the server. However, if there is a license loaded into the database, this database license is used rather than the uploaded (server stored) one. So, please check the Database Alter... dialog, Integration tab, whether Save license in database is ticked and untick it. You should only upload the license to the database if you have databases on the same server instance that need to use different licenses.

thetallbloke

vaprog,

You got my hopes up..!!!! only to snatch them away again..

hahahahah

I checked the screen you suggested.. however the "Save license in database" is unticked...
Does this mean that the license file is corrupted or out of date as Robert seems to be suggesting..???


How do I clear out all licenses (database and server) and start again...????

Thanks

Sog

You can quickly check if your license is in order.
With the license information try change. This changes the license to the one you selected and this one will be used for how long NAV is open. When you close NAV it will revert to either the DB license or the server license.
If that doesn't work, then you should export the license from another working db and try it with that one.

kitik

AdamRoue wrote:

It means that you have "a" license with access, this has been used and now you have an entry in the table. Using another license has no rights, you cannot open it, design it or anything, but because the table contains data the error is called. This used to happen with partners building a database for a client using the partner license not the clients license. I would guess if you look at it in SQL you will see data in the table.

Have you read this post? I belive AdamRoue is right. You need to remove data from that table and won't have the issue anymore.
But... you need to load a license with permision on the table to remove it... so I suggest you to contact your partner.

Salut!

rdebath

Okay, put this in a .cmd file and it should extract the Nav License from the master database of the default instance on this machine into the C:\TEMP directory.

echo> c:\temp\bcp.fmt 8.0
echo>> c:\temp\bcp.fmt 1
echo>> c:\temp\bcp.fmt 1       SQLIMAGE      0       0       ""                        1     license     ""
bcp "Select top 1 license FROM master..[$ndo$srvproperty]" queryout C:\TEMP\FIN.FLF -f bcp.fmt -T

thetallbloke

Hi Kitik,

I did see Adam's post... my next posted asked if I should delete the data out of that table...

Without waiting for a confirmation that I should actually delete all the data from that table, I did it anyway...
This is a dev system after all, so if it breaks I can just get another copy of a database again..

Anyway... that fixed my current problem.. I can now post my Sales Orders without getting that original error...

However, what I don't get is how this happened... what would I do if this was a production database restored from a backup that this happened to...???

I can't go and delete the data.... my accountant buddy in the office just about fell off his chair when I told him I truncated the table..

rdebath

vaprog wrote:

Rdebath assumes, your current license is defective or outdated. But there is still another possibility.

Not really, the license without table 253 is a V5 license the one with Table 253 is a V6 license. It's a new addition for the V6 objects and seems to have records inserted for all G/L postings with VAT (GST). I'm not sure why they made it a distinct table though, it could easily be just a single field on the VAT Entries table.

AdamRoue

thetallbloke wrote:

Hi Kitik,

I did see Adam's post... my next posted asked if I should delete the data out of that table...

Without waiting for a confirmation that I should actually delete all the data from that table, I did it anyway...
This is a dev system after all, so if it breaks I can just get another copy of a database again..

Anyway... that fixed my current problem.. I can now post my Sales Orders without getting that original error...

However, what I don't get is how this happened... what would I do if this was a production database restored from a backup that this happened to...???

I can't go and delete the data.... my accountant buddy in the office just about fell off his chair when I told him I truncated the table..

The issue is not with the data deletion, the issue is with the poor process controls in place. In my opinion a different license was loaded, mistake 1, then a table was opened and populated, mistake 2, then someone noticed the license was wrong and imported the correct license, thereby causing the issue. Access control and procedures are paramount when handling this sort of data.

5 years ago or so this was a pretty common occurence in partners with poor control procedures - delivering databases to customers that had been configured with a partner license and delivered untested with a customer license.

The standard fix is to load the partner license and open the table and delete it. Do it through NAV, not SQL. Then apply the correct license and start trouble shooting further permission issues.

vaprog

This post bothered me, so I returned to it.

AdamRoue and kitik, you seem to know something about security in NAV that I don't. So please enlighten me:

AdamRoue wrote:

It means that you have "a" license with access,

What makes you conclude this?

AdamRoue wrote:

this has been used and now you have an entry in the table.

dito

AdamRoue wrote:

Using another license has no rights, you cannot open it, design it or anything, but because the table contains data the error is called.

This last part, "but because... " startles me. Why and how does it make any difference, whether the table contains any data?

rdebath wrote:

vaprog wrote:

Rdebath assumes, your current license is defective or outdated. But there is still another possibility.

Not really, the license without table 253 is a V5 license the one with Table 253 is a V6 license. It's a new addition for the V6 objects and seems to have records inserted for all G/L postings with VAT (GST). I'm not sure why they made it a distinct table though, it could easily be just a single field on the VAT Entries table.

Aniway, I'd call using a V6 (SP1) db with an V5 license working with an outdated license. So, thetallbloke, you need to get a license that allows you to access table 253, or you need to use objects that do not require that table (i.e. V6 without SP1 or prior). So, nonregarding my questions to AdamRoue and kitik, deleting data from that table wont help you.

thetallbloke

Hi vaprog,

Deleting the data DID help though... for a while at least...

I truncated the table from within SQL management studio (I can hear the tuts from people already ), and was then able to, without changing licenses or anything, was then able to modify the table and post my SO's which is how I discovered the problem to start with..

I AM CONFUSED..!!!!

Theres a whole heap of chat on here in this thread about me having the wrong this and the wrong that... but clearly I have the correct license if I can now design the table...

What happens later after processing a few SO's, my Nav client goes back to saying the original error... "You do not have permission to blah blah blah..."

vaprog

thetallbloke wrote:

I truncated the table from within SQL management studio (I can hear the tuts from people already ), and was then able to, without changing licenses or anything, was then able to modify the table and post my SO's which is how I discovered the problem to start with..

I doubt this is an effect of truncating the table because ...

thetallbloke wrote:

I AM CONFUSED..!!!!

Theres a whole heap of chat on here in this thread about me having the wrong this and the wrong that... but clearly I have the correct license if I can now design the table...

This would imply NAV does not honour license permissions correctly, given your statement was correct:

thetallbloke wrote:

With the permission range table, I created a form to access this and found something weird, but not surprising... really..
Ok, on my machine, I have the following records:

Object Type Index From To Read Permission Insert Permission Modify Permission Delete Permission Execute Permission
Table 22 250 252 Yes Yes Yes Yes
Table 23 254 269 Yes Yes Yes Yes

Ok, so even I can look at this and see that I don't have permission to the 253 table..

However, I did the same thing in another database that apparently is using the same license and I get the following record.

Object Type Index From To Read Permission Insert Permission Modify Permission Delete Permission Execute Permission
Table 22 250 269 Yes Yes Yes Yes

Obviously, in that database I have no problem with the 253 table...

Somehow, the information we have so far does not match up

rdebath

thetallbloke wrote:

clearly I have the correct license if I can now design the table...

What happens later after processing a few SO's, my Nav client goes back to saying the original error... "You do not have permission to blah blah blah..."

The Table and TableData permission are distinct, it should be physically possible to be able to design a table but not insert data into it. That's one of the reasons I asked for both Table and TableData permissions. It would be a serious breach of process at Microsoft though.

It's also, in theory, possible that the RTC isn't checking the license properly, it is new code, but again this is quite unlikely. The chance of the classic client having a bug is very very low.

Clearly you do have two licenses. The Permission Range table directly shows the permissions of the currently loaded license, if you do a Tools->License->Change that client's Permission Range table will change no other client's will.

The license is loaded into a client when the client starts. For the RTC this is when the Server Tier is started. These two licenses will have the same serial number and text description as they are for the same customer; the only ways to distinguish them will be a binary compare of the files or a compare of the Permission Range table. (NB: There's nothing to stop you creating a Permission Range PAGE if you need it)

I just checked a Cronus V6 No SP and it doesn't have Table 253 either so I suspect the licenses are V6sp1 and V6 not V5 as I suggested earlier. That solves the problem as to why you weren't complaining about the service tier not working.

One last thing, if Nav loads a license file it is NOT corrupted. There is a fairly strong checksum on the license file that means it's very unlikely for a corrupted file to be accepted by Navision.

So did you extract the license file from the live master DB yet?

thetallbloke

G'day Robert,

I am having issues with exporting the license file from a production database... I keep getting the error:

---------------------------
Microsoft Dynamics NAV Classic
---------------------------
The operating system cannot find the file C:\Program Files (x86)\Microsoft Dynamics NAV\60\Classic\fin.flf .

Verify that the drive, directory, and file names are correct.
---------------------------
OK   
---------------------------

As for what you said here:

I just checked a Cronus V6 No SP and it doesn't have Table 253 either so I suspect the licenses are V6sp1 and V6 not V5 as I suggested earlier. That solves the problem as to why you weren't complaining about the service tier not working.

Thats not quite true, I was getting the same error in Classic and RTC... actually slightly different error message... one said VAT the other said GST.. I'm guessing the language setting takes care of that...

I'm almost at the point where I just give up on this issue..

My workaround for it is to keep working and just delete all the entries from table 253 when the error comes up.. it works for a while and then fails.. since its only a dev database I can do this...
I realise that this isn't a solution, but it will get me out of trouble until my objects have been developed and can be moved into another "working" database installation...

rdebath

thetallbloke wrote:

I am having issues with exporting the license file from a production database... I keep getting the error:

---------------------------
Microsoft Dynamics NAV Classic
---------------------------
The operating system cannot find the file C:\Program Files (x86)\Microsoft Dynamics NAV\60\Classic\fin.flf .

Ahh, I said extract, like I described in an earlier message...

rdebath wrote:

Okay, put this in a .cmd file and it should extract the Nav License from the master database of the default instance on this machine into the C:\TEMP directory.

echo> c:\temp\bcp.fmt 8.0
echo>> c:\temp\bcp.fmt 1
echo>> c:\temp\bcp.fmt 1       SQLIMAGE      0       0       ""                        1     license     ""
bcp "Select top 1 license FROM master..[$ndo$srvproperty]" queryout C:\TEMP\FIN.FLF -f bcp.fmt -T

and mentioned in an even earlier message. Export is not the opposite of upload.

thetallbloke wrote:

As for what you said here:

I just checked a Cronus V6 No SP and it doesn't have Table 253 either so I suspect the licenses are V6sp1 and V6 not V5 as I suggested earlier. That solves the problem as to why you weren't complaining about the service tier not working.

Thats not quite true, I was getting the same error in Classic and RTC... actually slightly different error message... one said VAT the other said GST.. I'm guessing the language setting takes care of that...

A V5 license would mean the service tier would not even start.

Actually, now you mention it, the RTC does seem to have a very nasty tendency to keep switching to American. If it can't even keep the language straight does that mean it's probably all crap?

AdamRoue

Hi Vaprog

I concluded that the partner had a license to access the table with no permission and that it has been applied and used BECAUSE there is data in a table the license now being used has no access to. How else would the data get into the table?

It depends upon the code and where it is. My memory tells me that if a partner creates responsibility centres in a database and delivers it to a customer and the customer license is applied and they have no access to responsibility centres then they will receive an error message on the responsibility centre table.

This certainly happened in 4.0. I was only trying to suggest possible reasons for the error message and from my experience the above situation causes it. It does not mean it is the cause in this case, but certainly applying a license with rights and deleting the data then applying the customer license would resolve the issue.

thetallbloke

Hi Robert..

I've run the script that you provided and managed to get an flf file out of a working system...

When do you suggest I load this extracted license file...??? now or after I get the error again...???

The only problem is that I haven't had the error posting sales orders for a little while now... I could post a dozen orders and see if it surfaces again.. but should I load the license in before or after...???

If I do it before, obviously I won't know really if its fixed anything... :-D

SRishi

Hi All,

I faced the same kind of issue, I have given the super permission to user still it was showing the read permission relatated error. Solution in NAV 2009 R2 is Synchronize the login which you are facing the error. If it is NAV 2013 or higher version check the credential and Re-start the navision services.