[sims] SIMS.NET Broken User Homepage.

[tech_guy]

We can't find anything on SupportNet about this and Capita have yet to respond.

 

We have a user who has broken her home page and gets an error message on logging in to Sims.Net:

 

 

They can't reset their homepage to default either:

 

 

Help much appreciated.

[LosOjos]

Can you set it to default settings as admin? Might be worth a try...

 

Routines > Home Page > Home Page Group Configuration

 

[On a side note - I wish Capita would sort out the Routines/Tools menus, there's no logic whatsoever as to where to find things]

[Rawns]

We had this issue, not really sure how we fixed it to be honest but it was to do with SIMS permissions. We removed the user form all assigned system manager groups, re-added and saved. It initially did nothing but it seemed to kick in overnight as the following morning, the user no longer got the error.

[ass17]

Best way is to remove permissions for on user, re-add the permissions, test the user account. You will find resetting permissions within sums fixes most issues.

[vikpaw]

Didn't this or similar occur after one upgrade and affected all who had the detentions widget?

[SovietRussia]

We removed and readded the permissions like was mentioned, and nothing - Still not working

[vikpaw]

Try giving all permissions to see if having extra allows the widgets to do what they want.

prob worth changing password for a bit and taking control of account while you do that.

[Rawns]

@SovietRussia Did you get anywhere with this problem?

 

Re my post above, the user user I helped is getting the same error come up again! No permissions changes that I can see. Odd how it 'fixed' overnight and now is broken again!

[SovietRussia]

@SovietRussia Did you get anywhere with this problem?

 

Re my post above, the user user I helped is getting the same error come up again! No permissions changes that I can see. Odd how it 'fixed' overnight and now is broken again!

 

We sent our DB off to capita, who fixed it and returned it

[Rawns]

We sent our DB off to capita, who fixed it and returned it

 

Cheers for the info.

 

I logged it with Capita in the end who came back and said this is caused by a corrupt widget configuration setting in the SIMS database. Capita connected through remotely, ran a SQL Management Studio script to delete the corrupt entry it and we tested it successfully after.