Jump to content

Recommended Posts

Posted

Hi

Anybody had an issue where you try to put a leaving date in for a student and it whirls and whirls then freezes up, but won't ever save?

I have it now :( It even affected other users and froze their machines.

 

I've tried manually altering the year membership date to sooner. Using a date in the past / future, but no joy. No luck, even on some really old data from early last academic year on my test server.

 

Something must be wrong and it's failing part of the validation or getting caught in a loop. It's the same for two siblings, so i'm guessing it's related to the parents.

They have no outstanding fees.

 

I'm about to try on the server and then start unlinking contacts to see if that makes any difference, but thought i'd check in case it rings a bell with anyone.

cheers

Posted

Check the parent email addresses.

 

I've had a similar issue and it's where one of the contacts email addresses didn't have a type.

  • Thanks 1
Posted

No joy.

One has a type, the other no email, but i did go and make changes to both parents and save was fine. I have also changed the preferred forename of student and it saves fine. So not a validation that is obvious.

 

I'll have to do some more trial and error tomorrow.

Posted

Same but with phone numbers perhaps?

Otherwise don't know sorry!

 

That's my goto for pupils, with the goto for staff being absences :)

Posted

Meh, our data is pretty good and you can't have a number with no location.

I'll leave it overnight, see if it's just really really slow.

Posted

After running overnight - it eventually timed out, and gave me a useable fault code. This can be common and advice is to run the re-index patch, and / follow other tips for speeding up the system and checking resources.

One tip is to add command-timeout=600 to the connect.ini , mine is already set to 10000 - which explains why i had to wait overnight to get the error message - lesson to be learned there! :o

 

Meanwhile on the test server i deleted all contacts and was able to mark the student as leaver.

 

So, today i did the same on the live server and it's still not playing ball. Haven't had a chance to run re-index, but i can't imagine it will do a great deal. Other students have been marked as leavers fine, i don't see what is tying the system in knots for these two siblings.

  • 1 month later...
Posted

Had to revisit this as two more sibling leavers causing the same issue.

 

Validation didn't work, and database diagnostics brought up nothing either.

 

Finally, took the plunge got users out and ran the re-index patch, after which it worked. Yay :o)

 

Really worth checking what the commandtimeout is set to in connect.ini as if it's too large, you'll give up and restart the server or kill the offending client without seeing the error. I reckon 600 i.e. 10 mins is sufficient for most things. I can't imagine why at times the advice was to ramp it up to 10,000 or 100,000 and then never to bring it back down again.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...