Discussion Locked

Mcafee Locks up With Drwatson

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I was wondering if anyone else has seen this. We use E-policy Orchestrator from NAI to manage our Anti Virus infrastructure. All of our servers run NT 4.0 with SP6A. We are running Net shield 4.5 with SP1.

Net shield start generating DR. Watson?s and the epolicy tries to fire it right back up. In seconds my systems have run out of virtual memory and the only recourse is a hard system reboot.

NAI suggestion was to check the service pack level and Engine revision. All of these are up to date. Anyone else seen this? Anyone have a suggestion?

6 replies

by maxwell edison

KNOWN INSTALLATION ISSUES:
1. If you plan to use Microsoft SQL Server 7 for your Anti- Virus Informant reports database and you install the software on a clean server rather than update an
existing installation, you must install the MDAC utilityon the ePolicy Orchestrator server before beginning the ePolicy Orchestrator installation. To do this, locate the \MDAC directory on the ePolicy
Orchestrator CD-ROM and run MDAC_TYP.EXE.

If you do not install MDAC, and you do not have an ODBC SQL driver present prior to installing the ePolicy Orchestrator software, you can only select (local) as your reports database location and you
can only run MSDE as your database.

2. For this release, a username and a password for
Windows NT user accounts during ePolicy Orchestrator
server installation must meet certain requirements.
You may not use a blank username or password. You may
use alpha characters "A" through "Z", numeric
characters "0" through "9", and/or special characters
"#", "@", or "$", although neither a username or
password can begin with a numeric character. The
username or password must begin with an alpha
character or one of the special characters
listed above.

3. Setup works only with pathnames of a limited length.
You must log in for ePolicy Orchestrator services to
start. If you copy the ePolicy Orchestrator program
files to your Windows NT desktop, then runSetup from
this location, your installation might fail because
the path to your desktop folder is too long. McAfee
recommends that you use a short directory name in the
root directory to install this product.

4. The ePolicy Orchestrator software is not supported
if installed on a Windows NT Backup Domain Controller
(BDC).

5. The computer name and the DNS name must be the same.

by maxwell edison

KNOWN UPGRADE ISSUES:

1. If you are upgrading from the ePolicy Orchestrator
v1.0 software, you must import the AVI_UPDATE.REG file
into the registry of your upgraded ePolicy Orchestrator
server. This file can be found in:

\AVI\AVI_UPDATE.REG

To import the file, start Windows Explorer in this
directory and double-click the file. This action adds a
number of additional alert types to the registry for the
GroupShield Dominosoftware and ePolicy Orchestrator
agent. This allows you to filter the alerts with the
alert filter, and produce reports and queries based
on those alerts.

2. McAfee recommends that you install all available
security patches, hot fixes, or service packs for
the Microsoft SQL Server 7 software.

3. NetToolsDB110 is left as an entry in ODBC connections
after an upgrade from the ePolicy Orchestrator v1.0
software. This link is not required forthe v1.1
software.

4. McAfee recommends that you stop the following service
before upgrading the server to v1.1:

NAI ePolicy Orchestrator server service

If you do not stop this service, you can experience
a Dr. Watson error message.

continued in next comments....

by maxwell edison

.
.
KNOWN UPGRADE ISSUES (cont...)

5. If you are running Seagate Crystal Reports tools while
installing Anti-Virus Informant, the install may fail or
require an additional reboot. McAfee recommends closing all
Crystal Reports tools before beginning the installation.

6. If you are upgrading the ePolicy Orchestrator v1.0
software to the v1.1 software, be aware that you must
convert your v1.0 report database to a v1.1 database
if you want to use it: - With the v1.1 software.

- As a source database, when using the Merge tool to
create a merged database.

The database must be converted because the v1.1 software
uses an enhanced database schema to provide additional
reporting functionality.

To convert your v1.0 database, install and open the
v1.1 software, then import the contents of the v1.0
database into the software's new v1.1 database. To do
this, follow the steps outlined in the "Importing
alerts from a report database" section of the
Administrator's Guide. The name of the v1.0 database
is NAIEvents, if you have not changed it.

NOTE:
On an average machine, the import function can
process 40000 alerts an hour. If your report
database is very large, you might want to leave the
import running overnight as it can take a long time.

7. When upgrading from v1.0 to v1.1, the upgrade will
succeed but theePolicy Orchestrator server service
may not start if you have changed the password that
was used to install the v1.0 ePolicy Orchestrator server.
To correct this, go to the Control Panel services,
double-click on the ePolicy Orchestrator server service
and ensure the password is correctly entered.

by mbartholomew

The problem is not the Epolicy server. It is all of the Servers that it manages. AS the remote client (Servers) DR watson out. Epolicy fires the Netshield service backup. I want to stop the Dr Watson's from happening in the first place.

by mikel~t

I've seen signs of this issue....I believe you need to increase the amount of time that Netshield can use to scan large objects. It is a registry edit, and as of now, I don't have the key you need to adjust....but NAI's website should have the listing of the key on their website in the tech support section. Just do a search for Dr. Watson (if you haven't already)....I have a feeling that the Dr. Watson error is repeating because the Netshield App hits a large file type, and errors out again.
Hope this helps.

Mike

This discussion is closed to new replies.