SMS 2.0 Memory problems

[AMcCarroll]

I've installed sms 2 and sql 7 on my server and i seem to be getting what looks like a memory leak, the memory usage keeps going up and up until I get an out of virtual memory error. I used the express setup option.<br>
<br>
<br>
Any ideas?<br>
<br>
Adrian McCarroll<br>
a.mccarroll@uk.insight.com

 

[Trunk]

Our SMS 2.0 site ran fine for 4 months, then we started experiencing exactly the same problem.....memory usage goes up until we run out of virtual memory. With Microsoft's help, we tracked the problem down to the processing of client hardware inventory MIF's. The problem still exists and there is still an open ticket with Microsoft. To stop the problem for now, they had us rename the dll that handles hardware inventory MIF's. The file is in the SMS/BIN/I386 folder on the site server and is called invproc.dll. They had us rename it to oldinvproc.dll for now to stop the processing of these MIF's. SMS now runs fine with the downside that the hardware inventory of our clients is not getting updated at the moment. The client software inventory is still functional.

 

[Guest_imported]

I submitted a question regarding lock ups and memory errors but your advice is great, so thank you.&nbsp;&nbsp;Secondly, it seems as though we have the same problem here at my company as you describe.&nbsp;&nbsp;I will put in a call to Microsoft as well so they will look into this further.&nbsp;&nbsp;<br><br>Thanks again<br>GScala

 

[danoh]

It could be MDAC.&nbsp;&nbsp;I don't know what SP you are using, but there is a bug with MDAC 2.0 sp1 that causes a memory leak.&nbsp;&nbsp;If you are using this, try upgrading to sp2.

 

[Trunk]

Actually, this problem has not repeated itself since we upgraded SMS to SP1 and SQL 7 to SP1.&nbsp;&nbsp;We are now back to processing hardware inventory MIFs as normal. <p>Tom Thaden<br><a href=mailto:thadents@usano.ksc.nasa.gov>thadents@usano.ksc.nasa.gov</a><br><a href= > </a><br>

 

[danoh]

Hi all again, I ment to say MDAC 2.1 SP1 has the memory leak, my other response stated MDAC 2.0 incorrectly.