If there are no errors and the upgrade completed with the persona bar icons missing, then I'd suggest again following my advice from Oct 24 in this forum thread (deleting the resources file).  To confirm, there is likely some sort of 500 or 404 error related to Get in the web developer console. This happens occasionally after an upgrade or after moving a website from one place to another.  

Thank you. We Will try that.

We did face another issue after the upgrade. There was page load exception due to the Get Javascript libries exception.

We cleared that table then the website loaded. Do we need data in that table?

What exactly does the data in that table does and why it failed?

Thanks

Posted By SDas on 1/17/2023 8:35 AM

Thank you. We Will try that.

We did face another issue after the upgrade. There was page load exception due to the Get Javascript libries exception.

We cleared that table then the website loaded. Do we need data in that table?

What exactly does the data in that table does and why it failed?

Thanks

I'm not sure what the actual details about the error and what you deleted are, but if my suggestion is the issue, nothing else is required to be deleted. 

In general, deleting data will only be necessary on DNN instances where people have been experimenting with updates directly to the database, including schema changes.  These kinds of things are often considered a core code change, and not a best practice.  

Thank you for the response.

We tried the oct 24 forum suggestion. But didnt help. We see that Main.css has changes that are resposible for the icons. Those upgrade chages are not reflecting on site.

Below is the error we see on website after the upgrade. The site was not loading .We cleared the table dbo.JavascriptLibraries to check if that will work. It did. But, as you said we should not be clearing any. Is this error due to version mismatch?

   at DotNetNuke.Framework.JavaScriptLibraries.JavaScript.GetScriptVersions()     at DotNetNuke.Framework.JavaScriptLibraries.JavaScript.Register(Page page)     at DotNetNuke.Framework.DefaultPage.b__15_0(Object sender, EventArgs args)     at System.Web.UI.Control.OnPreRender(EventArgs e)     at ClientDependency.Core.Controls.ClientDependencyLoader.OnPreRender(EventArgs e)     at DotNetNuke.Web.Client.ClientResourceManagement.ClientResourceLoader.OnPreRender(EventArgs e)     at System.Web.UI.Control.d__249.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.UI.Control.d__249.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.UI.Control.d__249.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()

If you've ever at any point - including now - had a partially complete DNN upgrade and then kept the site alive without restoring it and starting over, then you're in a fairly precarious situation.  

First, I'd try to upgrade past the version giving you the issue, namely 9.11 right now.  However, 9.11.1 isn't yet released.  Once we get the point of having a 9.12 or 10.0 release, you could get lucky and upgrade through the issues.  Though, it's something that is not likely, and you'll need to live with the broken persona bar for quite a while using this approach.  

What would be a faster and yet far more time-consuming suggestion is to rebuild the website on 9.11.0 today.  You'd need to migrate all of the extensions, content, and users.  This is by no means easy or fast to do, but it would resolve all unknown issues you're running into right now - and most importantly, it will get rid of any orphaned data, invalid schema updates, mismatched files/DLLs, etc.  

missing jQuery was issue on mine.  the following did not exist:

E:\www\DNN_Platform_9.9.1\Resources\Libraries\jQuery\03_07_01

I had 03_05_01; but the upgrade did not add 03_07_01.  I manually copied that directory from another web site and the persona bar works now.
I can't say if clearing DesktopModules\Admin\Dnn.PersonaBar\Resources\ directory was required or not.  I did that first (without success); the resource file did not re-create.  After fixing jQuery the resource file did get recreated, and the persona bar started working.

Root cause was my own fault.  I upgraded from 9.9 to 9.13 directly.  The 9.13 upgrade did not include the new jQuery... probably because earlier upgrades would have done that.

Posted By Mike of NZ on 5/9/2024 5:31 PM

missing jQuery was issue on mine.  the following did not exist:

E:\www\DNN_Platform_9.9.1\Resources\Libraries\jQuery\03_07_01

I had 03_05_01; but the upgrade did not add 03_07_01.  I manually copied that directory from another web site and the persona bar works now.
I can't say if clearing DesktopModules\Admin\Dnn.PersonaBar\Resources\ directory was required or not.  I did that first (without success); the resource file did not re-create.  After fixing jQuery the resource file did get recreated, and the persona bar started working.

Unfortunately, I can't say I've run into any instances in the past when the jQuery files weren't updated. Though, I rarely change anything about the configuration of that.  If I remember correctly, once you change that setting, the upgrade process may be ignoring it, making the assumption that your configuration change needs to be persisted.  This would be true of most other features as well.  However, the file should actually be there.  The configuration of it shouldn't change, if a change was made prior.  

Regarding the missing icons, the three most common reasons I see them go away are, in order of the frequency I see them: 

1. Some corruption of the file in the resources folder, as you noted.  Deleting it and reloading the page generally fixes this every time.  I usually only see this after some big event on the server, or after restoring the site.  
2. A JavaScript conflict.  I've seen a lot of poorly written JS get in the way.  
3. Corrupt cache.  This is most common when you're using a CDN/WAF, like CloudFlare.  This isn't to say there's something wrong with CloudFlare. Cache just gets corrupted every once in a while.  Clearing it will resolve the issue, when it's the cause.