Aloha EDC problem

[alohaakamai3]

v5.3.24

Everytime I try to run EDC reports, svchost.exe pushes CPU usage to about 70%, along with resources used by the EDC process itself, pushes CPU time to about 100%. It will take a really long time to show the transaction report, and if you chose multiple days to view at the same time, it may not work at all (hangs indefinitely).

There are supposedly a million and one things that cause svchost.exe to cause really high CPU time, like the Windows Update process, viruses etc. We were of the opinion that reloading XP Pro and installating the latest patches/XP2 would correct the problem, but it did not. During the rebuilding process (and before), this is the only problem this PC is having-it's not doing anything else flakey.

Anyone have an ideas what might be causing this?

Thanks

 

[alohaakamai3]

Forgot to mention, it's svchost.exe NETWORK SERVICE that's gobbling all the CPU time.

 

[posknowitall]

Check the quantity of edc settlement folders that are in the EDC folder for their processor. This will slow down Aloha manager when too many dated aloha folders accumulate?

 

[alohaakamai3]

POSknowitall-

Thanks for the reply. I suspected this originally too, but removing them didnt help.

I don't know if it's just some odd combination of hardware and software, or just that I've never had a client try to run that many EDC reports together-but it ended up being service pack 2 in XP.

After trying different things for hours, I figured it had to be SP2 or these printer drivers that had caused him grief previously, as well as other users (found this out searching online). So we built it yet another time, and this time after applying service pack 2, we were able to see this service run very high, and the EDC resources being given very low CPU time (would not allow us to change the priority for whatever reason).

I probably could have saved myself some time by just rolling back sp2 after the first rebuild, but I honestly didn't think that would be the issue since it's standard on every XP build. And I am not thrilled about leaving it off, but without it, the EDC reports are running within acceptable time limits when viewed together, and the client is satisfied.