Closed Safety1st closed 5 years ago
The sql migration code haven't been touched for many years and either works of give some useful feedback, so it's difficult to provide you steps to fix this. Probably the most effective way is you inject log / debug info into the migration code and see what you get out of it.
The sources for the sql migrator package can be found here - specifically the code doing the actual migration is here - you can update the code on your installation in the file /Composite/InstalledPackages/content/views/Composite.Tools.SqlServerDataProvider/SqlServerDataProvider.aspx.cs
You can log using Composite.Core.Log.
I don't understand how I can use your info since I'm not a programmer. Could you make an archive to replace existing files?
BTW I used verbose logging, it displays nothing too:
20181224 12:48:38.3723 5 262 Verbose TreeFacade Loading tree from file: D:\home\isotonic.ru\httpdocs\App_Data\Composite\TreeDefinitions\PageType.xml
20181224 12:48:38.4192 5 262 Verbose TreeFacade Time spend on loading the tree: 47ms, file: D:\home\isotonic.ru\httpdocs\App_Data\Composite\TreeDefinitions\PageType.xml
20181224 12:48:38.4192 5 262 Verbose TreeFacade Loading tree from file: D:\home\isotonic.ru\httpdocs\App_Data\Composite\TreeDefinitions\ServerLog.xml
20181224 12:48:38.4192 5 262 Verbose TreeFacade Loading tree from file: D:\home\isotonic.ru\httpdocs\App_Data\Composite\TreeDefinitions\UrlConfiguration.xml
20181224 12:48:38.4504 5 262 Verbose TreeFacade Finished: Initializing tree system (109 ms)
20181224 12:48:38.6379 5 262 Verbose ElementHookRegistratorFacade Time for VirtualElementProvider: 344 ms
20181224 12:48:38.6379 5 262 Verbose ElementHookRegistratorFacade Total time for: 375 ms
20181224 12:48:38.6379 5 262 Verbose HookingFacade RGB(194, 252, 131) Finished: Initializing Entity Hooks (391 ms)
20181224 12:48:39.1067 5 15 Verbose CodeGenerationManager New assembly already compiled by this application domain (5)
20181224 12:48:39.1224 5 15 Verbose GlobalInitializerFacade RGB(194, 252, 131) Writer Lock Acquired (Managed Thread ID: 15, Source: GlobalInitializerFacade.UninitializeTheSystem)
20181224 12:48:39.1224 5 15 Verbose GlobalInitializerFacade RGB(194, 252, 131) Starting: Uninitializing the system
20181224 12:48:39.1224 5 15 Verbose GlobalEventSystemFacade RGB(255, 128, 255) ----------========== Firing Shut Down Events ==========----------
20181224 12:48:39.1692 5 15 Verbose WorkflowFacade RGB(194, 252, 131) ----------========== Finalizing Workflows ==========----------
20181224 12:48:39.2005 5 181 Verbose WorkflowFacade RGB(194, 252, 131) System is shutting down, skipping delayed initialization
20181224 12:48:44.1662 5 15 Verbose WorkflowFacade RGB(194, 252, 131) ----------========== Done finalizing Workflows (5000 ms ) ==========----------
20181224 12:48:44.1662 5 15 Verbose GlobalEventSystemFacade RGB(255, 128, 255) ----------========== Done firing Shut Down Events (5047 ms ) ==========----------
20181224 12:48:44.1662 5 15 Verbose GlobalInitializerFacade RGB(194, 252, 131) Finished: Uninitializing the system (5047 ms)
20181224 12:48:44.1662 5 15 Verbose GlobalInitializerFacade RGB(194, 252, 131) Writer Lock Releasing (Managed Thread ID: 15, Source: GlobalInitializerFacade.UninitializeTheSystem)
20181224 12:48:44.1662 5 15 Verbose Global.asax --- Web Application End, 12:48:44 Id = 5---
20181224 12:49:13.6480 6 22 Verbose WorkflowFacade RGB(194, 252, 131) ----------========== Initializing Workflows (Delayed: 30079) ==========----------
20181224 12:49:13.6793 6 22 Verbose WorkflowFacade RGB(194, 252, 131) ----------========== Done initializing Workflows (31 ms ) ==========----------
20181224 12:49:13.7418 6 22 Verbose WorkflowFacade Workflow created, Activity = Composite.C1Console.Actions.Workflows.FlowInformationScavengerWorkflow, Id = d350492e-9c9a-4453-af33-d68e35a7025f, User = (system process)
20181224 12:49:13.7574 6 22 Verbose WorkflowFacade Workflow instance status changed to Idle. Id = d350492e-9c9a-4453-af33-d68e35a7025f, User = (system process)
20181224 12:49:13.7730 6 22 Verbose WorkflowFacade Workflow instance status changed to Running. Id = d350492e-9c9a-4453-af33-d68e35a7025f, User = (system process)
20181224 12:49:13.7730 6 22 Verbose FlowControllerFacade Starting scavenger run
20181224 12:49:13.7887 6 22 Verbose WorkflowFacade Workflow instance status changed to Idle. Id = d350492e-9c9a-4453-af33-d68e35a7025f, User = (system process)
20181224 12:49:13.7887 6 22 Verbose FlowControllerFacade Flow scavenger started
20181224 12:49:13.8199 6 22 Verbose WorkflowFacade Workflow created, Activity = Composite.C1Console.Events.Workflows.UserConsoleInformationScavengerWorkflow, Id = 547694cb-d7da-4160-b822-705a2b339752, User = (system process)
20181224 12:49:13.8199 6 22 Verbose WorkflowFacade Workflow instance status changed to Idle. Id = 547694cb-d7da-4160-b822-705a2b339752, User = (system process)
20181224 12:49:13.8199 6 22 Verbose WorkflowFacade Workflow instance status changed to Running. Id = 547694cb-d7da-4160-b822-705a2b339752, User = (system process)
20181224 12:49:13.8199 6 22 Verbose WorkflowFacade Workflow instance status changed to Idle. Id = 547694cb-d7da-4160-b822-705a2b339752, User = (system process)
20181224 12:49:14.8512 6 133 Verbose BuildManagerHelper Preloading ASP.NET controls
20181224 12:49:15.1069 6 133 Verbose BuildManagerHelper Preloading ASP.NET controls completed in 257 ms
20181224 12:49:15.1069 6 133 Verbose BuildManagerHelper Preloading ASP.NET pages and handlers
20181224 12:49:15.2476 6 133 Verbose BuildManagerHelper Preloading ASP.NET pages and handlers completed in 129 ms
20181224 12:54:13.8419 6 24 Verbose WorkflowFacade Workflow instance status changed to Idle. Id = 547694cb-d7da-4160-b822-705a2b339752, User = (system process)
So I was having an issue getting 6.6 to convert to SQL and the issue I found was a missing Xslt folder (nothing has to be in it, just a folder) within App_Data folder. After I put in the empty folder it worked like a charm. It was getting caught on the IXslt data type.
@toliphant thanks for sharing, much appreciated
Next attempt to use the CMS. Same hosting, recent version of C1. Migrating completed successfully with the message 'Data store migration completed'. Then site doesn't work anymore. You could see errors start page & console. Log is here.
Since Forum is unavailable I post issue here.
I use Venus starter site, website language − Russian. When I start migrating, indicator
Working... Please wait
appears. And thats's all. There are no error records in~/App_Data/Composite/Logfile/YYYYMMDD.txt
. Database also doesn't increase (tables 0). Things simply don't get changed. I tried migrate on 2 different hosting from 2 different countries with the same results. System requirements for 'C1 CMS running on Microsoft SQL Server' are met. Migrating guide is strictly followed.May be there is some debug version of SQL.Provider to monitor that happens? Sure I would give access to server panel & databases.