We have had problems since upgrading to k2 with CPU. It was at 100% utilization for hours, and of course the interface was slow. I configured SQL to only use the second core, and it was ok for at least the last few days. We upgraded a couple of weeks ago. Beginning Thursday evening through Saturday morning CPU
core 1 (SQL) has been holding steady at 100% and the interface hasn't
worked. It was extremely slow, but we could still manage to maneuver
enough to configure a few things. At this point we only get the error
below after logging in.
RequestTimeOut Queue:: User IP:: 127.0.0.1 Seconds::30
I've narrowed it down to the kaseya messagesys service. It stops after 5
minutes or so and CPU drops, but when it's running CPU is completely
So at this point I'm configured another server to move SQL to. The only
question I have now is how do I move SQL to another server when i can't
get into the kaseya interface? Is there a way to do it on the backend or
do I have to reinstall.
My ticket number is CS011639, but now it's Saturday and support has
limited off-hours coverage. I need to get my system back up before
Has anyone else seen this error and have any suggestions?Legacy Forum Name: requestTimeOut Queue error - need to move sql, Legacy Posted By Username: runnetworks