/build/static/layout/Breadcrumb_cap_w.png

Upgraded server to KACE SMA 13.0.383; trying to use "View By:" labels under Managed Installations throws "There was an error retrieving the data for this page"

We recently upgraded both a development VM and our production VM from 12.1.169 to 13.0.383, and the upgrade proceeded without error in both cases. However, today we noticed that both servers are having the following problem:

We have a few hundred Managed Installations, and about as many labels to which those MIs are attached, in various combinations. In the Managed Installations screen, if you click on the View By popup and select any label under the Deploy To Label submenu, no MIs are displayed and the system throws the following error in a pink banner across the top of the page: "There was an error retrieving the data for this page. Please refresh the page. If the error persists, try resetting the default page layout." Needless to say, refreshing the page does nothing helpful, nor does resetting to the Default Page Layout, nor any combination of column visibility that I can find. The labels are still properly attached to the MIs (and/or vice versa), which can be confirmed by going into the Labels pane, choosing a label, and clicking its Managed Installs to reveal all MIs attached. 

Hopefully there's a quick and easy resolution to this, as this is functionality that we use many dozens of times every day. Thanks in advance for any suggestions.


1 Comment   [ + ] Show comment
  • You may want to review the labels themselves to ensure that they still work. In previous upgrades when errors like this occured it was because of a modification to the SQL tables as part of the install. I would start with checking any Smart Labels that are based on things like custom SQL statements or have criteria based on custom software or fields.

    Do they all fail, or just some? Do you have any examples of the labels that are not working? - JordanNolan 1 year ago

Answers (2)

Posted by: Hobbsy 1 year ago
Red Belt
0

Log a call with support or update to v13.1

Posted by: Machead 1 year ago
Yellow Belt
0

Thanks, I've done both now. The 13.1 upgrade failed to complete, multiple times, so I'm holding off on that for now; thank goodness for snapshots. Had better luck with the support call. They confirmed this is a bug in both 13.0 and 13.1, and it's now been assigned a defect number.


Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ