Forums (Obsolete)

Member

trint99 - 4/18/2007 1:10:27 AM

Staging problems

I must be doing something wrong, but I can't figure out what.

Using 1.9.2579, we've set up multiple instances of our Kentico web site on virtual machines. Two sites, two database servers. The configuration on both servers is the same. One server is the the source, the other is the destination. For testing, I am using the admin username and password for staging. (Same account on both servers.)

I was (after much trial and error) able to get one page to stage correctly from the source to the destination. That page already existed on both servers and all I did was a small text change. This worked fine.

Then I tried deleting a file from the source and staging that change. It failed with the following error:

Failed to delete the document: Kentico.CMS.DataEngine.GeneralConnection.RunQueryObject: Query: update cms_versionhistory set NodeID = @NodeID, NodeNamePath = @NodeNamePath, NodeXML = @NodeXML, ModifiedByUserID = @ModifiedByUserID, VersionNumber = @VersionNumber, VersionComment = @VersionComment, ToBePublished = @ToBePublished, ModifiedWhen = @ModifiedWhen, PublishFrom = @PublishFrom, PublishTo = @PublishTo, WasPublishedFrom = @WasPublishedFrom, WasPublishedTo = @WasPublishedTo where versionhistoryid = @versionhistoryid caused exception: Kentico.CMS.DataProviderSQL.ExecuteQuery: Query: update cms_versionhistory set NodeID = @NodeID, NodeNamePath = @NodeNamePath, NodeXML = @NodeXML, ModifiedByUserID = @ModifiedByUserID, VersionNumber = @VersionNumber, VersionComment = @VersionComment, ToBePublished = @ToBePublished, ModifiedWhen = @ModifiedWhen, PublishFrom = @PublishFrom, PublishTo = @PublishTo, WasPublishedFrom = @WasPublishedFrom, WasPublishedTo = @WasPublishedTo where versionhistoryid = @versionhistoryid: caused exception: The UPDATE statement conflicted with the FOREIGN KEY constraint "FK_CMS_VersionHistory_CMS_User". The conflict occurred in database "Kenticocms_www", table "dbo.CMS_User", column 'UserID'. The statement has been terminated.

Next I tried to create a new file on the source server and stage it to the destination. That did not give an error message, but when I look at the new server, I can not navigate to the new page (404 error). The page shows up in the content list, but has no history and does not seem to be published.

I also tried to do "run complete synchronization" from the Manage Servers view and that causes an error:

System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.NullReferenceException: Object reference not set to an instance of an object. at Kentico.CMS.DataEngine.GeneralConnection.RunQueryObject(MetadataQuery query, Object[,] paramsIdent) at Kentico.CMS.DataEngine.GeneralConnection.RunQuery(String queryName, Object[,] paramsIdent) at Kentico.CMS.DataEngine.GeneralConnection.ExecuteQuery(String queryName, Object[,] paramsIdent) at Kentico.CMS.TreeEngine.CommonMethods.LogSynchronization(TreeProvider tree, TreeNode node, String eventCode, String nodePath) at Kentico.CMS.TreeEngine.SyncTaskManager.PrepareCompleteSync(String startingAliasPath) at Kentico.CMS.TreeEngine.SyncTaskManager.PrepareCompleteSync() at Kentico.CMS.CMSDesk.ManageServers.CompleteSynchronization(Object sender, DataGridCommandEventArgs e) at System.Web.UI.WebControls.DataGrid.OnUpdateCommand(DataGridCommandEventArgs e) at System.Web.UI.WebControls.DataGrid.OnBubbleEvent(Object source, EventArgs e) at System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) at System.Web.UI.WebControls.DataGridItem.OnBubbleEvent(Object source, EventArgs e) at System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) at System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace --- at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP.cmsdesk_tools_contentstaging_manageservers_aspx.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)


Member	trint.ladd@altn.com - 4/24/2007 5:48:31 PM Bump Anyone? Bump bump.


Member	martinh_kentico - 5/3/2007 11:44:08 AM RE:Bump Hi Trint, I sent you the anwer from the Helpdesk. Sorry about the delay. It is probably caused by inconsistency between CMSDefaultUserID web.config parameter and you database.

Member

trint.ladd@altn.com - 5/30/2007 10:29:55 PM

RE:Staging problems

I've been side tracked on another project for several weeks (naturally) and now I'm back working on staging.

I've got two new servers to test with. I double checked that both have the same user name and password for the staging user.

I created a page on the source server and was able to stage it to the target server. I modified it and staged it. I deleted it and staged the deletion. That's all good news.

I noticed that on the target server, the page I created never got a document history or workflow history. That that makes me a little nervous. I'd like to have the history go to the target server too.

That made me wonder. I created a page on the source server and staged it. Then I modified the page on the TARGET server. Then I modifed the page on the source server and staged the change.

On the target web site, the last edit (performed on the source server) is displayed correctly. But on the CMS desk of the target server, the edit made on the target server is still there. I couldn't get the source edit to show up in the CMS desk.

Then I destroyed the history on the target server and the source edit showed up.

This seems really odd, but if that is the expected behavior, then I guess I'll just have to make sure no one has access to edit the target server.

The last thing I tried was to do a complete synch of the target server. ("Run complete synchronization" button) That still caused an error.

System.Web.HttpUnhandledException: Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Kentico.CMS.DataEngine.GeneralConnection.RunQueryObject(MetadataQuery query, Object[,] paramsIdent)
at Kentico.CMS.DataEngine.GeneralConnection.RunQuery(String queryName, Object[,] paramsIdent)
at Kentico.CMS.DataEngine.GeneralConnection.ExecuteQuery(String queryName, Object[,] paramsIdent)
at Kentico.CMS.TreeEngine.CommonMethods.LogSynchronization(TreeProvider tree, TreeNode node, String eventCode, String nodePath)
at Kentico.CMS.TreeEngine.SyncTaskManager.PrepareCompleteSync(String startingAliasPath)
at Kentico.CMS.TreeEngine.SyncTaskManager.PrepareCompleteSync()
at Kentico.CMS.CMSDesk.ManageServers.CompleteSynchronization(Object sender, DataGridCommandEventArgs e)

Perhaps I have some page or object on my source server that's cause this. I don't know.

Any help would be appreciated.


Member	kentico_petrpa - 6/5/2007 5:14:17 PM RE:Staging problems Try to upgrade at least to the version 1.9a - where one known bug following full synchronization was covered.