Hi Billy,
Is this happening in local development environment and not DXP?
One thing I have noticed before is tblBigTable and tblBigReference are large is size. See here on how to check the largest tables.
If these tables are the largest then it might be possible that on initialization, you are getting a timeout warning, however sql is still running the scripts in the background to process.
I would let it run for some time, possibly overnight and then come back.
There is a way to safely clear down these tables, i'll dig out the info.
Thanks
Paul
This issue is happening in both my local and DXP. I am not sure if your approach (I would let it run for some time, possibly overnight and then come back) will work in DXP, the app has been running for days now and the issue persists. Though, I could be wrong here.
I do see the tblBigTable at the top of the file size list.
dbo.tblActivityLog | 15,736,582 | 12,419,032 | 9,127,936 | 3,046,608 | 244,488 |
dbo.tblNotificationSubscription | 4,797,676 | 1,565,168 | 697,104 | 817,904 | 50,160 |
dbo.BVN.NotFoundRequests | 5,350,197 | 948,040 | 933,472 | 3,480 | 11,088 |
dbo.tblWorkContentProperty | 244,138 | 240,592 | 174,584 | 58,856 | 7,152 |
dbo.tblScheduledItemLog | 23,703 | 152,792 | 150,320 | 1,128 | 1,344 |
dbo.tblBigTable | 27,546 | 119,992 | 95,768 | 20,912 | 3,312 |
dbo.tblContentProperty | 78,484 | 89,992 | 66,432 | 20,224 | 3,336 |
dbo.tblWorkContent | 81,846 | 67,848 | 33,176 | 30,768 | 3,904 |
dbo.tblContentLanguage | 58,747 | 48,000 | 24,464 | 20,352 | 3,184 |
dbo.tblActivityArchive | 65,968 | 28,776 | 28,312 | 192 | 272 |
dbo.tblContent | 54,257 | 25,464 | 10,672 | 12,712 | 2,080 |
dbo.tblTree | 270,946 | 17,880 | 8,880 | 7,976 | 1,024 |
dbo.tblBigTableReference | 16,112 | 15,184 | 13,592 | 1,192 | 400 |
Optimizely support got back and It seems that this was a bug with EPiServer.CMS.UI 12.8.0. Upgrading to the latest version will resolve the issue. https://world.optimizely.com/support/bug-list/bug/CMS-24819
I am running into initialization issues when migrating from CMS 11.15.0 -> CMS 12.8. It seems CMS is having a hard time running a specific SQL script. I have verified the tblBigTable does exist in my CMS Database. If I open SSMS and run the SQL against CMS DB it executes fine, if I try to run it against Commerce DB (it obviously does not work) but does provide the error "Invalid object name 'tblBigTable'"; which leads me to believe something might be configured wrong on my end to where the application is trying to update the Commerce DB.
Error Summary
Attempts to fix
The only way I can get the error to go away (but introduce a new one) is to comment out my AddCmsAspNetIdentity line in Startup. I am using a custom Identity user called SiteUser, which inherits ApplicationUser.
I have also tried running dotnet-episerver update-database.
Full Error Stack
Startup.cs File
CMS Package List