Sage Client 6.3 100% CPU after wakeup from Hibernation

[snipeman]

Everything was fine with my client before upgrading to v6.3, now when I turn it on after it has hibernated, Sage Client hangs at 99 or 100% CPU usage. If I go into the task manager and kill the Sage Client process and restart Sage, all is well. If I try to do anything in Sage Client before restarting I get the spinning circle icon forever.

I'm running WinXP Pro on my server and clients with wired gigabit Ethernet.

I am running no add ons to Sage Client or server, just plain 6.3.10.166 straight out of the box.

Again all was well for years with 6.2, I can't think of anything else that changed on the client. With 6.2 and earlier Sage when I would resume from hibernation it would take 15 or 20 seconds to sync back up with the Sage server, but it would always work. Now, no go.

Network card drivers are up to date, and I have not allowed Windows to turn power off to the network card during sleep modes. Note I"m not sleeping the computer though, I'm hibernating it, so this shouldn't matter. I suspect networking issues, but I don't know where to look.

Anyone have an idea?

Thanks!

[m0ng00se30]

not really a fix, but an idea... Java updates with Sage. If you haven't been updating to new version when they come out.. the Java would have changed. Now if that the problem or part of the solution I'm not sure... but want to put that in your head.. maybe it would get you going do the right road.

--Mike

[snipeman]

I was running java 1.6.0_03, I tried updating to version_05 but it didn't change anything.

I could set the computer to just shut down rather than hibernate, I was just trying to shave time off the restart. It is quicken to come out of hibernation that to boot up from scratch. Up until this incident hibernation has always been more reliable for me than S3 sleep modes on computers.

Perhaps this isn't a networking issue but it is a Sage issue after all?