Replies: 15 comments
-
might be an issue of the "Blank Website" template, or do you experience the same with "Default Website" template? |
Beta Was this translation helpful? Give feedback.
-
A few questions on this, as I've seen this before in Azure a few times.
Azure PaaS offerings have a hard-set timeout of 230 seconds of inactivity, which can translate to longer given the DNN status updates, but often if installing on low-grade stuff (S1 AppService or S0 DB) it is possible to have issues. |
Beta Was this translation helpful? Give feedback.
-
Install was a bit slow indeed, though it went trough in the end without any errors... |
Beta Was this translation helpful? Give feedback.
-
Well, looks like that was the issue, on my local installation it went trough fine. |
Beta Was this translation helpful? Give feedback.
-
For DNN 10.x we are looking to "roll forward' the schema script, until we do that it isn't exactly possible. I'm curious, what scaling configuration were you using in Azure? (We have done 30+ installs in Azure in the last month without any issues, so just trying to find the scale point that is an issue so we can possibly document) |
Beta Was this translation helpful? Give feedback.
-
I think I did the install using: |
Beta Was this translation helpful? Give feedback.
-
+1 for this issue and the solution above. |
Beta Was this translation helpful? Give feedback.
-
We have detected this issue has not had any activity during the last 90 days. That could mean this issue is no longer relevant and/or nobody has found the necessary time to address the issue. We are trying to keep the list of open issues limited to those issues that are relevant to the majority and to close the ones that have become 'stale' (inactive). If no further activity is detected within the next 14 days, the issue will be closed automatically. |
Beta Was this translation helpful? Give feedback.
-
A few discussions regarding this topic on the forums. |
Beta Was this translation helpful? Give feedback.
-
I have the same issue. Controls are missing in my installation folder. Tried downloading some of them from GitHub but Admin/Skins/ControlBar.ascx does not exist anywhere. Not sure what could be the resolution. |
Beta Was this translation helpful? Give feedback.
-
This just happened to me with 9.10.0 on a clean install in my local testing environment. Had to do this:
I'm going to run through the process again to confirm. I may have done something wrong. Was in a hurry, as usual |
Beta Was this translation helpful? Give feedback.
-
@patrickryan79 |
Beta Was this translation helpful? Give feedback.
-
Yes, I think it was ... Admin/ControlBar.ascx or something like that. |
Beta Was this translation helpful? Give feedback.
-
thank you, I'll try to verify. |
Beta Was this translation helpful? Give feedback.
-
I am moving this issue to a discussion until it becomes actionable. |
Beta Was this translation helpful? Give feedback.
-
Description of bug
I installed a clean DNN 9.9.0 installation on Azure with:
After installtion I clicked on go to the site and got a 500 error.
In the log file it said something like:
The file '/Admin/ControlPanel/ControlBar.ascx' does not exist.
So I checked the hostsettings table for the controlpanel entry and indeed it showed
'/Admin/ControlPanel/ControlBar.ascx'
After I changed it to
'DesktopModules/admin/Dnn.PersonaBar/UserControls/PersonaBarContainer.ascx'
I was back in business...
Steps to reproduce
List the precise steps to reproduce the bug:
Current behavior
Installation went ok, but the site gave a 500 error
Expected behavior
Well....you know, a working site might be nice...
Error information
2021-03-02 14:27:35.520+00:00 [dw0sdwk00009R][D:17][T:21][FATAL] DotNetNuke.Framework.PageBase - An error has occurred while loading page.
System.Web.HttpException (0x80004005): The file '/Admin/ControlPanel/ControlBar.ascx' does not exist.
at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath)
at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath)
at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc)
at DotNetNuke.UI.Skins.Skin.InjectControlPanel()
at DotNetNuke.UI.Skins.Skin.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.AddedControl(Control control, Int32 index)
at System.Web.UI.ControlCollection.Add(Control child)
at DotNetNuke.Framework.DefaultPage.OnInit(EventArgs e)
at System.Web.UI.Control.d__225.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Web.Util.WithinCancellableCallbackTaskAwaitable.WithinCancellableCallbackTaskAwaiter.GetResult()
at System.Web.UI.Page.d__523.MoveNext()
Affected version
Beta Was this translation helpful? Give feedback.
All reactions