Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Symposium Processor at 100%
- Thread starter nurser
- Start date
Try clearing out your scheduler.... it might be full of reports trying to be pulsed out to bad locations. If its a slow build to failure this might be it...
Otherwise set up the Server Monitor software(Operating System Feature) to log those two services(processes) over the course of the two weeks. You should at least be able to verify if its a "persistent" or "spike" issue and if its a spike issue exactly when it happens.
Its at least a place to start....
Otherwise set up the Server Monitor software(Operating System Feature) to log those two services(processes) over the course of the two weeks. You should at least be able to verify if its a "persistent" or "spike" issue and if its a spike issue exactly when it happens.
Its at least a place to start....
- Thread starter
- #3
Scheduler free, only 1 report in.
System runs for either 2/3 days before services spike.
Pulled the perflogs, looks like memory is used during day, but at end of the day it never recovers to what it was before.
Nortel's recommended upgrading all client connections to SDK 4.2, currently Nice Recorder sitting on V3 so upgrading tonight.
Thanks, will keep you updated.
System runs for either 2/3 days before services spike.
Pulled the perflogs, looks like memory is used during day, but at end of the day it never recovers to what it was before.
Nortel's recommended upgrading all client connections to SDK 4.2, currently Nice Recorder sitting on V3 so upgrading tonight.
Thanks, will keep you updated.
Unless the "memory leak" was a symptom related to version 4.02 I don't think its going to do anygood to upgrade. Did they mention anything about problems with that happening relating to that version?
Try going into the PerMon and selecting Process under the Performance Object drop down box. Then select Private Bytes and each and every process listed to the right of that. You should be able to identify the exact process sucking up all the memory by the end of the day.
Try going into the PerMon and selecting Process under the Performance Object drop down box. Then select Private Bytes and each and every process listed to the right of that. You should be able to identify the exact process sucking up all the memory by the end of the day.
- Thread starter
- #6
Think we found the problem, one of the below errors:
* Moved Pagefile completely over to D:
* Was 128MB file on C, 1.5GB on D, removed 128MB file
* Updated SQL Server on all servers to SP3
* Reinstalled 3rd party wallboard server as W2K Server
* Biggest change was upgrading NiceCLS Server to latest service pack.
Since the above changes, perfmon showing stable memory level. Previous to the it was wildly variable.
* Moved Pagefile completely over to D:
* Was 128MB file on C, 1.5GB on D, removed 128MB file
* Updated SQL Server on all servers to SP3
* Reinstalled 3rd party wallboard server as W2K Server
* Biggest change was upgrading NiceCLS Server to latest service pack.
Since the above changes, perfmon showing stable memory level. Previous to the it was wildly variable.
- Status
Similar threads
- Locked
- Question
- Locked
- Question