We have been getting multiple timeout errors throughout the day for the past two weeks. The background processing service also dies on us multiple times a day.
Is there anyway to fix these timeout errors?
What's happening is when somebody is doing an action and it times out.. there is no way for us to complete the action.
For example: I reassign a change task and it times out (usually all users will start getting the "operation timed out" error) .. but when everything clears up .. that specific task that I got an error on can no longer be reassigned regardless if everything else is running fine. All it does is give me a timeout error and crashes the app.
I was able to clear one by logging into the console on the app server with the SA account.
I haven't had luck with any others. They are basically stuck and anytime I try to complete or reassign for the user it crashes on me.
This is only happening to Change Tasks currently.
EDIT: I was able to get it reassigned through webdesk. Unfortunately our CR windows look horrible in webdesk so it's just a workaround. Would still like to know if there is anything else I can do to alleviate the issue.Thanks!
If the Problem is just with Change Tasks I'd bet you've got an unbounded collection on the object. Stu's article should help you understand if you have and how to get rid of it: The effect of unbounded collections on system performance. Failing that I'd recommend working through the suggestions in the performance manual (Service Desk 7.4 Performance Guide), it will at least help you narrow down the cause of the issue.