Error after upgrade CB 1.9 to CB 2.0.13

Hi,

on a website after upgrade to CB 2.0.13 I play the tolls and I have this message

Core CB database structure differences:
Table #__comprofiler_plugin Rows element = cbarticles : Field id = 40 instead of 17
Table #__comprofiler_plugin Rows element = cbforums : Field id = 34 instead of 18, Field iscore = 0 instead of 1
Table #__comprofiler_plugin Rows element = cbblogs : Field id = 33 instead of 19, Field iscore = 0 instead of 1
Table #__comprofiler_tabs Column cssclass does not exist
Table #__comprofiler_tabs Column useraccessgroupid exists but should not exist
Table #__comprofiler_tabs Index pluginclass does not exist
Table #__comprofiler_tabs Rows pluginclass = cbblogsTab : Field pluginid = 33 instead of 19
Table #__comprofiler_tabs Rows pluginclass = cbforumsTab : Field pluginid = 34 instead of 18
Table #__comprofiler_tabs Rows pluginclass = cbarticlesTab : Field pluginid = 40 instead of 17
Table #__comprofiler_ratings does not exist

and if I click to fix I have this message
Duplicate entry '17' for key 'PRIMARY' SQL=UPDATE `ag251_comprofiler_plugin` SET `id` = 17 WHERE (`element` = 'cbarticles')

Any idea to fix the problem ?

CB 2.0.13, Joomla 2.5.28, Cbsubs 4.0.1

Your database auto increment is broken. This happened with Akeeba usages or direct export and import usage without auto increment being kept. This causes reserved plugin ids to accidentally be used by installed plugins. It could also happen if you started from a really really old CB 1.x release (mambo days) and kept the same install.

Only way to fix it is to manually fix the table. See my reply below regarding this.

www.joomlapolis.com/forum/255-developer-members-support/231648-duplicate-plugin-upgrading-cb191-to-2011#272684

if I understand all core plugin should have a ID less than others plugins, right ?

Here is the #_comprofiler_plugin's table

Yes, plugin ids 1-500 are reserved. If anything other than a core CB plugin is using one of those ids then your tables auto increment was broken by something. This typically is from a direct database export/import or an older release of akeeba backup (they've since fixed the issue). See the linked topic where 2 other topics are provided for further explanation and solutions. You will need to manually fix the ids.