An Error Occurred for different tiles

Home Forums Callisto as a Service An Error Occurred for different tiles

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #332
    Giovanni Myles
    Participant

    The new update dropped for Callisto Community. This resolved the majority of the issues I had. Namely, the different tiles simply said “An error occurred. Sorry but we couldn’t load this section.”. Now the only tile that shows this is the Update Compliance, Critical and Security Updates tile. What should I look at when trying to correct this? My user has dbo permissions in SQL and on the databases for SCCM. I also have local admin on the server in question hosting the controller service. Any ideas around what I should be checking? Thanks

    #333
    CallistoAdmin
    Keymaster

    Hi Giovanni, thanks for getting in touch!

    Can you confirm the version of ConfigMgr and the version of SQL you have please.
    Many thanks

    #334
    Jason Marves
    Participant

    Apologies for piggybacking of Giovanni’s post but I’m getting the same thing on the Update Compliance tile and getting it on the OS Deployment tile. In addition the Required Updates tile is just a blue bar which just says more details…

    I’m on ConfigMgr 1906 and SQL is 2016 SP1-CU5 (13.0.4451.0)

    #335
    CallistoAdmin
    Keymaster

    Thanks Jason,
    Does the account you’re logging in with have an email address set in AD that matches an account in the ConfigMgr console for an RBAC role? I.e. if you opened the console with that account would you see a limited set of stuff or would you see everything?

    How long does it take for the dashboard to render, we’re wondering if it’s timing out. If you could send us a screenshot to callisto@callisto.co that’d be handy.

    And if you press F12, go to the Console tab, reload the page and see if any errors appear, do the same for the Network tab, and send us anything interesting in there. The last XHR Content Type request on the network type would be interesting to see if you can send us the output of that. We’re keen to get this fixed for both of you.

    Alternative to all of the above, if you’re able to do a screenshare with one of the dev guys here that might be a lot easier! So please let me know.

    #338
    Jason Marves
    Participant

    Does the account you’re logging in with have an email address set in AD that matches an account in the ConfigMgr console for an RBAC role? I.e. if you opened the console with that account would you see a limited set of stuff or would you see everything?

    It does have a matching email address and it has access to see everything.

    How long does it take for the dashboard to render, we’re wondering if it’s timing out. If you could send us a screenshot to callisto@callisto.co that’d be handy.

    It takes about 30-35s to render the dashboard.

    And if you press F12, go to the Console tab, reload the page and see if any errors appear, do the same for the Network tab, and send us anything interesting in there. The last XHR Content Type request on the network type would be interesting to see if you can send us the output of that. We’re keen to get this fixed for both of you.

    I’m not seeing any errors in the console on reload. Just 16 instances of the below warning.
    10.23b8257571c1cb03ddbd.js:1 ag-Grid: tried to call sizeColumnsToFit() but the grid is coming back with zero width, maybe the grid is not visible yet on the screen?

    For the XHR output I assume you are looking for the response? If so it’s a lot to post here so I can send it via email if needed. The generic info though is it’s showing 200 OK 568.5 KB and 32.29s

    Alternative to all of the above, if you’re able to do a screenshare with one of the dev guys here that might be a lot easier! So please let me know.

    I can be available to do a screenshare.

    #339
    CallistoAdmin
    Keymaster

    Thanks Jason, we’ll drop you an email to arrange a quick screenshare.

    #340
    CallistoAdmin
    Keymaster

    Just to close this off, we made some modifications to the SQL back end for these problems and for Jason at least, this fixed the problem, if anyone else has this issue please let us know but it looks like it was a timeout issue. The dataset for software updates in particular is very large, so we have to be careful in how we select against this stuff.

Viewing 7 posts - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.