The table definition is invalid and cannot be validated.

tinoruijs · 2013-10-10

I've opened an NAV 2013 database in an NAV 2013 R2 and it was succesfully converted.
Now I'm trying to import the R2-objects in the converted database.
I'm receiving the following message "The table definition is invalid and cannot be validated.".

Anybody else encountered this?

tinoruijs · 2013-10-10

Strange. Compiling in DEMO-database doesn't return an error.
Compiling the objects in the converted database returns the error "he table definition is invalid and cannot be validated."
I'm gonna test why.

ringert · 2013-10-10

we have the same problem...

EVWeje · 2013-10-10

We have the same problem with a brand new installation (NAV2013R2 7.1.35473)
Installed SQL on a seperate box
Retored the Demo DB from Media
New instance on NAV server.
selected the correct DB.
NAV Works perfectly, but if we try to compile: "The table definition is invalid..."

Installed NAV on local machine (With SQL Express as backend) no problems in compiling...??
Have no idea, what is going on.

jjbravo · 2013-10-10

I have the same issue when trying to add custom fields to a standard table.
Adding my own tables/fields works fine.

My workaround for this, until MS gets back to me, is to set the Option "Prevent data loss from table changes" to No. This can be found under Tools->Options...

John

tinoruijs · 2013-10-11

jjbravo wrote:

I have the same issue when trying to add custom fields to a standard table.
Adding my own tables/fields works fine.

My workaround for this, until MS gets back to me, is to set the Option "Prevent data loss from table changes" to No. This can be found under Tools->Options...

John

Thanks for the workaround John!

tinoruijs · 2013-10-11

Just 1 kind of error I'm getting when compiling the objects in the converted R2 database.
"The 'Record2000000009' type is obsolete." and "The 'Record2000000009Handle' type is obsolete."

Only for objects table 11414, report 11405, 11406, 11407, 11408, 11411.
Has something to do with tabel 2000000009 Session which is not there anymore. Objects are compiled, so no problem for me now, but just wanted to let you know.

Marije_Brummel · 2013-10-11

That is Dutch localisation. User Certificates.

It does something with the session table.

Guess that does no longer work with a technical upgrade only.

jjbravo · 2013-10-11

According to MS, this is an issue with all the localized versions and they have sent it to Development in DK. Hopefully they will have it fixed soon.

I heard the Sessions table is obsolete, but that it does populate from the Windows Client, but not from the Web Client, so it's probably not a good idea to use it.

connamics · 2013-10-16

Hello together,

i have the same Problem. Is this Problem solved from MS?

I need a fast Solution.

Thanks

Jocafe · 2013-10-17

I have the exact same problem.
I exported some objects I had on NAV2013 std and wanted to add our customized code to the same object on R2 (by merging them manually) and now when I try to compile I get that error.

For now I'm using the workaround commented on this topic.

tpbrophy · 2013-10-24

I have experienced this as well. Has anyone heard anything more from Microsoft on this issue? Apparently we must go through an upgrade to get from NAV 7.0 to NAV 7.1. Also, it seems we cannot just do an executable upgrade even with a 7.0 database.

daves · 2013-10-24

An FYI and hope for notification of a fix:
I just got the subject error message while trying to make a trivial change to a table included in the North American localization. I then cloned (opened in Design mode and saved without change to a different number) the table from the local number series into the 50000 range. I can't make any modification to that copy of the table either. However, when I manually, line by line, create a new table that is a replica of the failing table, the compiler is perfectly happy with it. So the problem lies in something left by the process of moving the table from NAV 2013 RTM to NAV 2013 R2. BTW: This particular table was created as part of the US localization for NAV V3.60. The database I am using is an unmodified NA CRONUS (unmodified until I hit this problem :-) ).

Shedman · 2013-10-25

I have the same problem in two databases that I'm trying to upgrade. Both Dutch localisation, both giving the error in table 27, while there aren't even any customizations in it. Opened and converted from 2013 to 2013 R2, and it's broken

daves · 2013-10-28

Since I created a new copy of my problem table that worked, I exported both the working copy and the problem copy to text files and ran a file compare. The only difference that showed up in the file compare was the multiple language captions that were part of the problem copy. I wonder if that's a hint as to the problem cause.

jjbravo · 2013-10-28

Dave,
I've noticed that the setting "Prevent data loss from table changes" sometimes resets itself or if you don't click ok, it doesn't persist.
After setting it to "No" I've had no issues customizing or upgrading tables.

I'm still waiting for an answer back from MS. According to support, it's still in development in DK.

John

soya · 2013-10-28

Hi,
The same problem.
We tried to import translations. The problem was caused by an accented character in option field.

Warbridge · 2013-11-12

I am getting this same error on a database I just converted from 2013 to 2013 R2. This is the second time I've done this upgrade on the same database, and the first time I didn't have this problem on the same tables. Since I went through this once already, I thought I could export the tables, then import them into the second converted database. No such luck. The same objects which compile fine in 2013 R2 on one workstation receive the table definition is invalid error when I try to compile them in the second database. I cannot even import them in fob format.

Thus far R2 is proving to be a giant pain.

-- Scott

Gil · 2013-11-20

Upping this post. Does anyone have any solution for this? Thanks

Gil

nav_student · 2013-11-21

Same problem here.

It happens when try to compile the table 290 Sales Line.

I try to configure Prevent data loss from table changes to NO but i cwhen open again Tools > Options it changes automatically to Yes.

tedl30 · 2013-11-21

Hy

There are two methods to get around this error.

--> Start a Server Instance on your Developement machine using domain user account
--> Start a Server Instance on your SQL server using Network Service

See page: http://www.dynamics.is/?p=1619

I think this is bug in NAV 2013 R2

:(:( or we don't know something

ThomasHej_MSFT · 2013-11-21

Unable to validate table changes...

If turning validation off works, it indicates that you have trouble getting authenticated on the NST or that the NST can't be found.

Could you try the following:

A) Setup manually in Tools/Options the address/port etc of the NST and see if that makes any change.

Make sure that you are using Windows authentication AND that you are created as a NAV-user in the database.

Thanks,

Thomas

jjbravo · 2013-11-23

I was told by support that Dev in DK has fixed this issue, but they don't have a release date yet.

john

jjbravo · 2013-11-25

MS released a hotfix for this:
https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?scid=kb;en-us;2901564

John

tedl30 · 2013-11-26

jjbravo wrote:

MS released a hotfix for this:
https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?scid=kb;en-us;2901564

John

But erorr is still exist.

TomH_DK · 2013-11-27

Upgraded to NAV 2013 R2 build 35664, but the error "The table definition is invalid...." still occur ](*,)

Anyone with another solution ?

tedl30 · 2013-11-27

TomH_DK wrote:

Upgraded to NAV 2013 R2 build 35664, but the error "The table definition is invalid...." still occur ](*,)

Anyone with another solution ?

Hy I also upgrade but error still occur.

Teming · 2013-12-06

Tools/options/Prevent data loss from table changes - change to no and save it.

tedl30 · 2013-12-06

Teming wrote:

Tools/options/Prevent data loss from table changes - change to no and save it.

And lose all data in table ;(

Alex_Chow · 2013-12-19

Having same issue as well... This is not specific to the DK localization.

FDP · 2013-12-19

I have this issue, when I try to import the danish Cumulative Update 1 to a danish demo database

The workaround worked for me

Howdy, Stranger!

Quick Links

Categories

The table definition is invalid and cannot be validated.

Comments