Hello,
I am trying to convert DB from Ver4 Sp2 to Ver.
I follow the processw which the vendor gave us, it seems straight forward but I get the message
" You donot have a permission to ‘tempblob’ table’. contact the system manager, if you need to have your permission change.
I run it using a sys admin sql server user ID.
according to them, it could be a licence problem and we need to ask one of them to do.
It means that we can’t do it ourselves.
any advice on this?
thanks,
Susan
I think I have seen something similar. I was upgrding a database from 3.70 to 5.0 and I got this on some tables that were in a “add-on” number range but were not in my developers license range (and were not in the customers license range). I didn’t know how these objects got there and why they weren’t in the license but I knew they were not needed.
I knew I wasn’t using the tables in question so I deleted them from the Object table in SQL. This is a dirty hack but it got me through the problem.
Be very careful if you try to do anything like this and always do it on a copy of live system first. If you decide to try it on the live system make sure you have a current backup. Deleting data directly from the Object table in the NAV database is almost certainly not supported and if you stuff it up you are likely to cause irreperable damage.
Thanks for that
The vendor keeps saying that we couldn’t do it ourselves we should ask them to do it.
the vendor said that they don’t have this message and everything goes well.
Do you have a developer licence when you are running this? and still get the similar message?
Thanks,
Susan
Yes I was using a developer’s license and got a similar message - but this was for a specific add-on with an ID in an add-on range. Maybe the problem you are having is different. If your vendor can do it with their developer’s license and you can’t this would suggest that it is a licensing issue. I do know that the upgrade guide recomends that you use a developers license for the process - but I seem to think people have managed to do this “technical upgrade” many times with just a normal license. Have you upgraded your license to v5.0? Can you track down this tempblob table you mentioned in the error message? What ID does it have? Is that ID in your license?
Hello,
I can’t find any ID for that.
I haven’t upgrade your licence to V5.
Vendor gives us the licence and my understanding that we will load that licence after we finish converting it.
but we stuck with converting DB.
I can’t see tempblob ID and by looking at my licence brieftly, I don’t see tempblob ID too.
also when I First convert the DB - there is another message ( below) so I deleted as requested then do converting till the second error msg ( tempblob table permission).
I don’t understand when I close it after 2nd message, when I open it, the 1st error message comes back again.
DO you think that we need to ask the vendor to do the converting?
Thanks,
Susan
SYMPTOMSWhen you try to convert a database to Update 3 for Microsoft Dynamics NAV 4.0 Service Pack 2 or to Microsoft Dynamics NAV 4.0 Service Pack 3, you receive the following error message: The following SQL Server error(s) occurred:
“Column names in each table must be unique. Column name ‘securityoption’ in table dbo.$dbo$dbproperty is specified more than once.
SQL: ALTER TABLE [dbo].[$ndo$dbproperty] ADD securityoption INTEGER NOT NULL DEFAULT 0” This problem occurs if you are using Microsoft SQL Server Option for Microsoft Dynamics NAV 4.0.CAUSEThis problem occurs if the $ndo$dbproperty SQL table contains a Securityoption column.RESOLUTIONTo resolve this problem, use SQL Server Management Studio or SQL Server Enterprise Manager to delete the Securityoption column from the $ndo$dbproperty SQL table. Then, convert the database.
Yes I think you should let your vendor do it. They say they can do the converesion with no problem so why not let them do it?
Yes you are right about the security option error message coming back - I was getting this as well and it’s a pain. The reason is that when NAV tries to convert the database to version 5.0 it adds the securityoption field to the $ndo$dbproperty SQL table. They it fails because it cannot convert the tempblob table (in my case it was a different table). It rolls back the changes it made to the tables but not to the $ndo$bdproperty table. This means that the next time you try it, it fails telling you it cannot add the securityoption field to the $ndo$dbproperty table (because it already exists).
Open the object designer (Shift+F12) and click on the tables button. Do a find on the Name field for a table called tempblob (since you have not copied the exact error message, I cannot guarantee this is correct - but you should look at the error message.) If there is a table there called tempblob - what is the ID number? You will probably find that it is in a 50000+ range that is not in your license (I believe in version 5.0 the range of table IDs have to be explicitly named). It will work for you vendor because they have a developers license.
You will probably find that even if you got past the tempblob problem, it will fail with the next 50000+ range issue.
Thanks for your advice.
I guess after we are fighting with the vendor…
one consultant said that with our licence we should be able to do it ourselves and another one ( account manager) we can’t do it.
Finally we get a result that they send us a hot fix.
we will try it.
hopefully everything is ok.
I will let you know what is the outcome
hello …
back yo this topic…apply the hot fix and still got the same error message
and now we are advised that we do differently as below
• Take a full backup of the NAV 4.x database.• Create a new database on the test environment using NAV 5.x.
• Restore the backup using the new NAV 5.x database.
right now I just restoring the DB…it takes so long…mind you our DB is about 54Gb…
4 hours reach only 52%…
the question is…why do we have to upgrade tpo ver 5 using the above process rather that using SQL - restoring which much quicker…
I don’t know yet whether the converting will work or not…
obviously my vendor doesn’t really know what they are doing… they always says… microsoft recommend blah…blah…
has anyone had a prob with converting to Nav5 ?
I really need some help…
thanks,
Susan
I think the advice offered by your vendor is good. If you are having problems converting the database, you can use the NAV backup/restore. Although this is slower, NAV will take care of business and you are pretty much guaranteed to get a result at the end of the day - and many would say a better database.
If you know what you are doing you can do the SQL restore and conversion which you first started. I did this and yes I had problems, but I fixed them and got past them. If you are struggling to do this then go for a simple method that works.
Thanks Woof…
I follow their instruction however during restoring - there is an error message appeared said:
" The following SQL Server error occured while acesssing the master wkhs entry table.
3958,42000,microsoft[]ODBC SQL Server Driver] [SQL Server] transaction aborted when accessing versioned row in table ‘dbo.inserted’ in database ‘NavTest5’ requested versioned row was not found.your tempdb is probably out of space.please refer to BOL on how to configure temppdb for versioning.
does this error message refer to additional module which attached to standard financial navision or tempdb out of space?
mind you that we have 3 additional modules attach to it ( rostering,client,residency module)
thanks,
Susan
The error message seems quite informative. Is it possible that you really have run out of space at the point of the error?