DB error for every attempt at saving content and document type changes
We are getting these errors when saving content data and document types.
System.Data.SqlClient.SqlException:
Cannot insert the value NULL into column 'id', table
'mydb.dbo.cmsPropertyData'; column does not allow nulls. INSERT
fails.
System.Data.SqlClient.SqlException:
Cannot insert the value NULL into column 'IsDefault', table
'mydb.dbo.cmsDocumentType'; column does not allow nulls. INSERT
fail
we are using umbraco version 4.7, and have ported the solution from one server to another and it have been working fine for a long time on new server.
we have tried to follow the guides for cleaning the db from the links here, but the error is not gone:
Seems that there's something wrong with your database, I assume that the 'id' field of cmsPropertyData (and the other table) need to be identity columns (ie thery need to generate their own id's)
We used the Import And Export Data wizard to move the database from one server to the other, and was not aware that no index, foreign keys, primary keys would be exported. So all that got lost in the process.
DB error for every attempt at saving content and document type changes
We are getting these errors when saving content data and document types.
we are using umbraco version 4.7, and have ported the solution from one server to another and it have been working fine for a long time on new server.
we have tried to follow the guides for cleaning the db from the links here, but the error is not gone:
http://borism.net/2008/12/16/fixing-a-large-cmspropertydata-table-in-umbraco/
http://our.umbraco.org/forum/using/ui-questions/7106-Database-full---now-I-have-problems-with-the-node-structure
We hope someone have an idea about how to fix the problem.
Hey Henrik,
Welcome to the forum!
Seems that there's something wrong with your database, I assume that the 'id' field of cmsPropertyData (and the other table) need to be identity columns (ie thery need to generate their own id's)
What db are you using?
Rich
Thanks for Rich for the tip, you are right.
We are using MS SQL server 2008 R2 database.
We used the Import And Export Data wizard to move the database from one server to the other, and was not aware that no index, foreign keys, primary keys would be exported. So all that got lost in the process.
Glad you got it sorted :)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.