Has any one ever run into this one?
Re-Rite is installed on a Windows 2003 R2 Standard server that only runs Re-Rite. I have upgraded from Re-Rite v6.2.0.2x to v6.2.0.43 then to v6.2.0.44 but the service is still running hot. I have tried uninstalling completely, restarting the server and then re-installing Re-Rite after deleting the Re-Rite folder and then restarting some more, but no dice. I have also tried cutting out all InPaths and restarting the service but it still runs hot. There doesn't seem be anything in the event logs about the Re-Rite service.
I can get the CPU Usage to drop by restarting the e-Bridge Re-Rite service, but after 30 - 60 secs, the CPU Usage goes through the roof again. The extremely weird thing is that you would think that the server itself would run very slow, but the server actually seems to be running at a more than acceptable speed.
I currently have Toshiba looking into the issue, but I'm kind of hoping that I can beat them to the punch with info from someone that has experienced this themselves already.
Cheers,
Owl
Re-Rite is installed on a Windows 2003 R2 Standard server that only runs Re-Rite. I have upgraded from Re-Rite v6.2.0.2x to v6.2.0.43 then to v6.2.0.44 but the service is still running hot. I have tried uninstalling completely, restarting the server and then re-installing Re-Rite after deleting the Re-Rite folder and then restarting some more, but no dice. I have also tried cutting out all InPaths and restarting the service but it still runs hot. There doesn't seem be anything in the event logs about the Re-Rite service.
I can get the CPU Usage to drop by restarting the e-Bridge Re-Rite service, but after 30 - 60 secs, the CPU Usage goes through the roof again. The extremely weird thing is that you would think that the server itself would run very slow, but the server actually seems to be running at a more than acceptable speed.
I currently have Toshiba looking into the issue, but I'm kind of hoping that I can beat them to the punch with info from someone that has experienced this themselves already.
Cheers,
Owl
Comment