In August we installed a new server and, with SIMS Support help on-site, moved the SQL database and SIMS over to it. Before moving we did the Aug update.
Later one of our admin people noticed that when trying to edit the Father's details of a pupil (but OK with Mother's details) SIMS crashed. See attached screenshot. She could still enter a Father's details from scratch.
Eventually realised that crashing was the rule for most users, and that only one user COULD edit Father's details. A user wih many more permisson groups.
Worked With Capita Support but they were unable to reproduce the fault. Once they found that we had one custom permisions group they were unable to provide further answers.
By giving one of the admin users ALL the Group Permissions that the successful user had, then stripping them out one at a time, I found that we can now only do this particular type of edit with "Fees Manager" in permissions.
Anyone had an experience like this? No users had to have this permissions group to edit before the Aug Update/move.
I think I came accross this kb in my search for a match to the error. Superficially it has same message.
Not quite what I am getting. The user who can edit, gets to edit all and any Father's details. But all the users who can't, can't. No details of any Father of any pupil on the system can be edited until the illogical group is applied.
Work around is OK, as its mainly one person who does all the edits, but it's not right.
If you'd like to identify yourself to me, I will see what we can do to help you. User defined permission structures should not cause this issue. Try assigning one of our standard permissions to a person and see if it still occurs.
I heard about this exact problem, and it depended on the route taken to change the details.
So if you are in a students record and go to their contacts and try to edit, then it crashes out.
If you go via the link for contacts (little man in front of an envelope) and then search for the Father and then edit it is fine. Is that the workaround you are using?
Sometimes the route taken does make a difference, and i suppose different permissions apply.
It reminds me of the time when in order to see staff timetables you had to to have the next of kin permission. somehow, the system was drawing that data out even though it wasn't required and thus caused a crash.