Field number 27 is not defined in the Object Metadata table

WoodMan

Hi there Mibuso,

First of all thanks to Mibuso for being an invaluable resource to me over the last few years. I hope this email is formatted correctly and doesn't offend anyone (official disclaimer!)

We have just upgraded to Nav 2009 R2 and I am working on getting the web services running. I am using build 33494.

The server service is running and I have confirmed this in the application log:

Service:
Microsoft Dynamics NAV Business Web Services are available at [url=http://]http://[/url]<server_address>:7047/DynamicsNAV/WS/Services.

When I load the address given in the event, I get the following message:

The <name of database> database on the <server_address> server is not enabled for Microsoft Dynamics NAV Classic. You must enable Microsoft Dynamics NAV Server with Microsoft Dynamics NAV Classic. On the File menu, click Database, and then click Alter. Choose the Options tab and select Microsoft Dynamics NAV Server.

When I put the database into single user mode, and then tick the option 'Enable for Microsoft Dynamics Nav Server', I get the following Navision error:

'Field number 27 is not defined in the Object Metadata table'.

When i look at the object metadata table, there are 6 fields in there, but no field 27:

Enabled Field No. Field Name
Yes 3 Object Type
Yes 6 Object ID Integer
Yes 9 Metadata BLOB
Yes 12 Version List
Yes 15 User Code
Yes 24 Object Key

I have searched on Mibuso and what seems like the whole of that internet , and my partner seems a bit stuck too. They have suggested a new build which hasn't made any difference.

Can anyone help?

Many thanks,
Bill.

thegunzo

Hi

This field in new in NAV and is introduced in a KB package last Februray if I recall this correctly.
If you are using a RTC build newer than this you will also need to use a classic client newer than this. If you open the database with the same build classic client it will ask to a database upgrade that will add this field to the Object Metadata table. After that you will not be able to open the database with an older client.

Good luck.

WoodMan

Hi Gunnar,

Thanks for the response.

I managed to find this information regarding that field:

1. KB 2678831 RTC disconnects with RecordRef
1. ****See above for the new field titled “Metadata Version” number. This can be useful when deciding if needs to recompile objects after applying a hotfix. The following fun facts relate to this information:
2. • The current build number determines the Metadata Version number
• When applying a hotfix, if the Metadata Version for the old build is different to the Metadata Version for the hotfix build being applied then the MS partner should include a step to recompile all objects in the database after applying the hotfix.
• If you compile any object in the Classic Client the current Metadata Version number will be applied to the record for that object in the “Object Metadata” table (ID 2000000071).
• If the “Object Metadata” table does not have a column called “Metadata Version” then the build number must be earlier than 32942 which was the build where this new column was added. When any hotfix build >= 32942 is applied the database conversion process will add this new column to the “Object Metadata” table.



I have another problem in that the updated client is not prompting me for a database conversion, but I've gone back to the partner to help with that.

I've marked this topic as solved,
Cheers!
Bill.

thegunzo

Great.

You can use another database that has the updated table 2000000070 and export it as a fob and import into your database. Then you recompile all objects and they will update the Metadata Version field.