Just deploying a site from local to SQL Azure. Everything looks fine however when I login to the back office and try and view any node that has a hostname set, I am getting an exception. DB name redacted. I am unable to view the hostname dialog for the the nodes either. Is this a bug in Umbraco or am I just doing something wrong? I updated my site to v7.0.4 this morning via NuGet but doubt that has to do with it. Also any node under the node that has the hostname set is also throwing the same sort of error. Anyone know what I might be doing wrong or is this a one for Issues.umbraco.org
Failed to retreive data for content id 1062
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_cmsPropertyData_cmsPropertyType_id". The conflict occurred in database "*****", table "dbo.cmsPropertyType", column 'id'.
The statement has been terminated.
Not sure why you would get an exception around "sql inserts" when you are just viewing the node, but are you sure you migrated the database properly? Maybe something in the schema got messed up which in turn corrupted the data when inserted into the database.
@Seb... Datatypes are all pretty standard nothing that would do DB interactions on load. Nodes outside that particular tree are fine. Only thing that is different about that tree is that it has a Hostname set in the Culture and Hostnames. The Tree looks like this
Site (this is fine can veiw this node)
-Home (hostname set here cant view this node or any of its children)
-- Pages from this point on are throwing the error also
-Widgets (fine can view this and all its children)
-Tiles (fine can view this and all its children)
Site Settings (this is fine can view all its children)
Deployment of the DB was done with SQL Management Tools using the Generate Scripts with the Script for SQL Azure options. This configuration works fine on my localhost and dev servers.
Not sure I mentioned this is all in the back office. I cant get the sie published because I cant view the start node of the tree as every action that i try on that node causes that DB insert error (all actions publish, hostnames and cultures, sort etc)
Wierd. Figured it out. For some reason a property that I had deleted 2 days ago all of a sudden was still there. Figured that out by creating a new document of the same type. So re-saving the document type fixed it.
v7.0.4 SQL Azure Fails to load nodes which have hostname set
Just deploying a site from local to SQL Azure. Everything looks fine however when I login to the back office and try and view any node that has a hostname set, I am getting an exception. DB name redacted. I am unable to view the hostname dialog for the the nodes either. Is this a bug in Umbraco or am I just doing something wrong? I updated my site to v7.0.4 this morning via NuGet but doubt that has to do with it. Also any node under the node that has the hostname set is also throwing the same sort of error. Anyone know what I might be doing wrong or is this a one for Issues.umbraco.org
Failed to retreive data for content id 1062
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_cmsPropertyData_cmsPropertyType_id". The conflict occurred in database "*****", table "dbo.cmsPropertyType", column 'id'. The statement has been terminated.
What datatypes do you have on these nodes?
This help? http://stackoverflow.com/questions/15502201/umbraco-content-tab-error-mixed-up-document-types
Not sure why you would get an exception around "sql inserts" when you are just viewing the node, but are you sure you migrated the database properly? Maybe something in the schema got messed up which in turn corrupted the data when inserted into the database.
Have you seen this blog post about moving a database to sql azure?
http://blog.iqit.dk/2014/01/move-your-db-to-azure
- Morten
Dunno how you moved the database from production to azure but i would recommend you using this tool when ever you migrate to Azure SQL
http://sqlazuremw.codeplex.com/
@Seb... Datatypes are all pretty standard nothing that would do DB interactions on load. Nodes outside that particular tree are fine. Only thing that is different about that tree is that it has a Hostname set in the Culture and Hostnames. The Tree looks like this
Deployment of the DB was done with SQL Management Tools using the Generate Scripts with the Script for SQL Azure options. This configuration works fine on my localhost and dev servers.
Not sure I mentioned this is all in the back office. I cant get the sie published because I cant view the start node of the tree as every action that i try on that node causes that DB insert error (all actions publish, hostnames and cultures, sort etc)
Nodes that dont have hostnames are fine.
Wierd. Figured it out. For some reason a property that I had deleted 2 days ago all of a sudden was still there. Figured that out by creating a new document of the same type. So re-saving the document type fixed it.
is working on a reply...