<div>
A course of action could be the following:<br />
<br />
Configure Avast to skip the SQL directories where it usually finds viruses<br />
<br />
Then scan your system with a different virus scanner, e.g. Trend micro online virusscanner:<br />
<br />
<a href="http://housecall.trendmicro.com/" rel="ugc">http://housecall.trendmicro.com/</a>
</div>


A course of action could be the following:

Configure Avast to skip the SQL directories where it usually finds viruses

Then scan your system with a different virus scanner, e.g. Trend micro online virusscanner:

http://housecall.trendmicro.com/ [http://housecall.trendmicro.com/]

<div>
I hope all is well with this guy...MobilePCDR. However, I would like to know how it all turned out. I've been in his/her position and that's why I offered my comments.<br />
&nbsp;<br />
Naerwen<br />

</div>


I hope all is well with this guy...MobilePCDR. However, I would like to know how it all turned out. I've been in his/her position and that's why I offered my comments.
 
Naerwen


<div>
<div class="content wysiwyg-content">
Hello,<br />
<br />
I have a server running Server 2003 Standard that I manage. &nbsp;The company also has a person who handles their rental software. &nbsp;Ever since he took over, setup SQL on the server and has had login rights, the server has had two virus infections. &nbsp;Now it's happening again, and what usually tips me off is there will be tons of cmd.exe in the task manager, and a cmd.exe error followed by a cacls.exe error that appears repeatedly. &nbsp;Evertime I have done the clean, it pulls files out of the SQL directories. &nbsp;I am starting to have my doubts as to whether or not it's truly been infected, or if SQL is causing a bug and maybe the anti-virus (Avast) is seeing SQL files as being suspicious. &nbsp;Any help is greatly appreciated!<br />
<br />
Anthony
</div>
</div>


Hello,

I have a server running Server 2003 Standard that I manage.  The company also has a person who handles their rental software.  Ever since he took over, setup SQL on the server and has had login rights, the server has had two virus infections.  Now it's happening again, and what usually tips me off is there will be tons of cmd.exe in the task manager, and a cmd.exe error followed by a cacls.exe error that appears repeatedly.  Evertime I have done the clean, it pulls files out of the SQL directories.  I am starting to have my doubts as to whether or not it's truly been infected, or if SQL is causing a bug and maybe the anti-virus (Avast) is seeing SQL files as being suspicious.  Any help is greatly appreciated!

Anthony

Infection or Bug?

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).