Msg 515, Level 16, State 2, Line 27

Cannot insert the value NULL into column 'RoleID', table 'kb2.dbo.instantKB_CategoryRoles'; column does not allow nulls. Insert fails.

I have a lot of the above lines repeated over and over in the output of the 1.3 > 2.0 upgrade

In Instantkb_treeroles I have 0 Null values

In instantkb_treeroles I have 1474 records

In Instantkb_categoryroles I end up with 1235 so unless some truncation takes place I lose 239 records.

I can't find any NULL values anywhere except the blank line for inserting a new record.

Anyone any ideas?

Exception Type:        System.Data.SqlClient.SqlException
Exception Message:     Invalid object name 'InstantKB_Articles'.
Exception Source:      .Net SqlClient Data Provider
Exception Target Site: OnError

Sorry to hear your having some problems. We don't accommodate for nulls there as RoleID in the old InstantKB_TreeRoles table should never be bull. Categories will always need a valid role identity to determine who has access to the content within that category.

The only thing i can suggest for the moment Rob is to run a query similar to the following before running our update script.

DELETE FROM InstantKB_TreeRoles WHERE RoleID IS NULL

I've made a note of this Rob and will be looking to see if there is any reason RoleID would be null in the 1.3 InstantKB_TreeRoles table. Please let me know if this helps Rob,



Kindest Regards,

Ryan Healey
Director / Developer

Explore our products...
http://demos.instantasp.co.uk/

Hi Martin,

Hope your well .Nice to hear from you again I'm sorry to hear your having problems. The error messages indicates your installation of InstantKB.NET cannot find our main InstantKB_Articles database table. .

If you check the connection string within the InstantKB.NET 2.0 web.config file this should point a InstantKB.NET 2.0 database. If you open your database in management studio do you see the InstantKB_Articles table. I'm assuming you've received this error after attempting to update an existing 1.3 database. Did you receive any error message whilst running the upgrade script? Does it appear the database updated? Do you now see a number of new tables and stored procedures within your database?

Sorry to ask so many questions Martin. Any additional information you can provide will certainly help me determine what's causing this error. Looking forward to your response,


Kindest Regards,

Ryan Healey
Director / Developer

Explore our products...
http://demos.instantasp.co.uk/

Nice to hear from you and great to see v2.0 out! Hopefully we can get past these issues fairly easily.

I started again just so I could document the process.

1. Restored my existing, working 1.3 db into a new database (SQL2005)

2. Ran the upgrade script - see results attached

3. The Article table is not present in the upgraded DB

Let me know if you need more information to diagnose the problem.

Regards

Martin

	Post Attachments
	Bentley Upgrade Errors.txt (53 views, 77.16 KB)

Hi Martin,

Hope your well. Many thanks for your response. IT appears your running the ugrade script against a database that already contains a version of InstantKB.NET 2.0...

There is already an object named 'InstantASP_Emails' in the database.

When you run the script within management studio ensure you selected your restored 1.3 database from the drop down list. Please see attached screen grab.

Please let me know if this helps,


Kindest Regards,

Ryan Healey
Director / Developer

Explore our products...
http://demos.instantasp.co.uk/

	Post Attachments
	SelectingTheDatabaseToUpgra.gif (40 views, 73.46 KB)

Please excuse my stupidity! Yes you were correct, I was using a Database from one of the beta tests of KB2 - I restored the correct live KB1.3 database and the script ran just fine.

Thanks for your help and apologies for not concentrating!!

Cheers

Martin

Hi Martin,

Hope your very well. It's no problem honestly we are all only human unfortunately

I'm delighted to hear my suggestion helped. We are here to help and please don't hesitate to post any future problems. It's more than likely we've seen the problem dozens of times before and can hopefully point you in the right direction.

I just wanted to also say thanks Martin for your feedback and especially your time during the 2.0 release. I know your a busy chap and it's sincerely appreciated.

We do have a further update available today (more fun