W2K Advance Server - COM problem
#1
![Default](https://www.scoobynet.com/images/icons/icon1.gif)
Error in event log showing:
"
COM+ has determined that your machine is running very low on available memory. In order to ensure proper system behavior, the activation of the component has been refused. If this problem continues, either install more memory or increase the size of your paging file.
"
The server has 1gb of ram, 192mb page file. Runs fine all other times do not think this is a lack of memory or too small a page file problem. It is causing problems with IIS which I then have to re-boot the server to resolve this.
Anyone with any ideas as to establish exactly which app is hitting COM and thereby causing the memory problem?
Any S/W that can be used to monitor this?
The rest of the message in the event viewer does not give the game away!
TIA
Buck
"
COM+ has determined that your machine is running very low on available memory. In order to ensure proper system behavior, the activation of the component has been refused. If this problem continues, either install more memory or increase the size of your paging file.
"
The server has 1gb of ram, 192mb page file. Runs fine all other times do not think this is a lack of memory or too small a page file problem. It is causing problems with IIS which I then have to re-boot the server to resolve this.
Anyone with any ideas as to establish exactly which app is hitting COM and thereby causing the memory problem?
Any S/W that can be used to monitor this?
The rest of the message in the event viewer does not give the game away!
TIA
Buck
#2
Scooby Regular
Join Date: Sep 1999
Location: Bedfordshire
Posts: 4,037
Likes: 0
Received 0 Likes
on
0 Posts
![Default](https://www.scoobynet.com/images/icons/icon1.gif)
Hmmm,
A tricky one, you first call would be to look in component services and try and identify any thrid party COM objects that have been installed, specifically look for any where in the activation specifies a server activation which means that object can run out of process (i.e. not invoked by an executable) and also see the advanced tab to see if it is set to leave running when idle, most of the objects packaged with Win2k will have these set (there wont be many 4 or 5) so you should be able to identify any 3rd party ones, in component services you can also look at the transaction list to see if that sheds any light on things. It definately sounds like a rogue (and poorly written) COM/COM+ object!
good luck
Gary
A tricky one, you first call would be to look in component services and try and identify any thrid party COM objects that have been installed, specifically look for any where in the activation specifies a server activation which means that object can run out of process (i.e. not invoked by an executable) and also see the advanced tab to see if it is set to leave running when idle, most of the objects packaged with Win2k will have these set (there wont be many 4 or 5) so you should be able to identify any 3rd party ones, in component services you can also look at the transaction list to see if that sheds any light on things. It definately sounds like a rogue (and poorly written) COM/COM+ object!
good luck
Gary
Thread
Thread Starter
Forum
Replies
Last Post