• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1646
  • Last Modified:

Services.exe using excessive memory

Services.exe is using, on average, 150 Meg of memory.
This seems excessive.
I have searched the entire HDD to ensure it is not a virus/trogan.
I only found one copy in the system 32 folder (where it is supposed to be).
Also, no virus' found on a Norton scan.
I checked the MSCONFIG to see if it was in the start up, it is not.

This is a new phenomenon.  No updates or patches installed to cause it.
Confusing.

All appears normal on the server except the services.exe
I have also shutdown any unnessesary services.

Any help would be appreciated.
0
greetrufus
Asked:
greetrufus
  • 5
  • 4
1 Solution
 
mcsweenSr. Network AdministratorCommented:
Could be a cpl of different ones...have a look at this search and see if you can match any of em up

http://www.google.com/search?hl=en&q=site%3Aca.com+services.exe+trojan
0
 
greetrufusAuthor Commented:
Checked those.
From my knowledge and the sites referenced (unless I'm missing something), services.exe should be running in the system32 folder.
Typically, when it is a virus, it will install mulitple (or at least one) copies of services.exe (the infected one) in other locations (c:\windows for example).
A through search  of my HDD only indicates one services.exe file in the correct location, which Windows needs to run.
None of the articles I read indicate that the services.exe in system32 is replaced by th virus/trojan.

hmmmm...
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

 
mcsweenSr. Network AdministratorCommented:
On my most stressed W2k3 server (SQL) Services.exe is taking up only 37MB of RAM.  On one of my domain controllers it uses 2MB.

On my fully patched W2k3 Domain Controller Services.exe is

Version: 5.2.3790.1830
File Version: 5.2.3790.1830 (srv03_sp1_rtm.050324-1447)
Modified: Thursday, March 24, 2005, 6:13:36 PM
Size: 107 KB (110,080 bytes)


0
 
mcsweenSr. Network AdministratorCommented:
does this server have a high workload or a lot of applications/services installed on it?
0
 
greetrufusAuthor Commented:
I did notice when I shutdown or kill services the size of service.exe shrinks.  It's most notable when I shutdown different Quickbooks processes.
0
 
greetrufusAuthor Commented:
It is a DC and is only a file server.
It is running ADS and WINS, DNS as well, but only 20 users connected, maybe 10 with active files open.

Version: 5.2.3790.0
File Version: 5.2.3790.0 (srv03_rtm.030324-2048)
Modified: Thursday, March 29, 2003
Size: 102 KB (104,448 bytes)
0
 
mcsweenSr. Network AdministratorCommented:
Ahhh, I bet it's the Quickbooks services running away with it.  Might have a memory leak or just the services are hogs.
0
 
greetrufusAuthor Commented:
Qb service is normal
0
 
uncommonsCommented:
I just wanted to add that I had a W2K3 server that for 11 months has been rock steady, when the QB2007 Database service was added to this server it leaked memory until it crashed the server. Removing the database engine resolved the issue, it uses the services.exe for the majority of its processes and made it look like that file was the issue. We have virtualized a server just for the  QB database and it runs ok but requires a weekly re-boot.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now