Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Donate Today!

Do you enjoy these
technical forums?
Donate Today! Click Here

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

helpoutwithmcafee (TechnicalUser) (OP)
19 Mar 07 10:17
Hello guys,

I have an EPO Server 3.6.1 and have deployed the latest CMA. PC's are running VS8.0 with patch 14. Only 1 major issue:
DAT files are not being updated. I have created a task to deploy immediately, but no luck - any suggestions?

Helpful Member!  VictorySabre (TechnicalUser)
20 Mar 07 18:16
Did the DAT updates ever work before or is this a clean install/deployment? If this is an existing deployment, do you recall if the clients all stopped doing DATs around the same time?
helpoutwithmcafee (TechnicalUser) (OP)
22 Mar 07 2:13
Hi, thanks for the reply,

The DAT file updates did work before, I upgraded to EPO Server 3.6.1 and CMA 3.6.0.453. The deployment of the latest CMA works fine but the task for the DAT updates are not working, I have 5 or more DAT files out of date. If I change the task to run immediately and do an agent wake up call and set randomization to +/- 45 mins, nothing happens. I have checked policies, have the Virus Scan 8.0i NAP checked in, etc. I have permissions to the workstations as the deployment task works. What could it be....
helpoutwithmcafee (TechnicalUser) (OP)
22 Mar 07 2:23
Here is an extract of the log file:
Strange thing is that is says the update is succesful but the reports on the EPO server show they are out of date

Added a new task Updates to Scheduler's task list
20070320130038    i    #3832    Script    Backing up file(s) Engine DAT
20070320130038    i    #3252    Script    Pre-notifying for DAT update.
20070320130038    i    #1720    Script    Copying DAT.
20070320130039    i    #3252    Script    Update succeeded to version 4.0.4987.
20070320130039    i    #1720    Script    Post-notifying for DAT update.
20070320130043    i    #3252    Script    Update Finished
20070320130043    i    #3252    Script    Closing the update session.
helpoutwithmcafee (TechnicalUser) (OP)
22 Mar 07 2:59
Only other thing I can think of is the use of NT authentication rather the SQL authentication - do you think that is the issue
VictorySabre (TechnicalUser)
22 Mar 07 22:03
So it appears your clients are updating, but they are not reporting back to the ePO Server. This is very similar to what I've experienced on my end after I upgraded some of my ePO Agents to CMA 3.6.0.453. Those PCs that upgraded to CMA 3.6.0.453 no longer took any policy changes I made on the ePO Server and DAT updates also never appeared to be reported correctly.

Not sure if the condition I'm seeing is the same as what you have, but it can be an easy check to test on one of your PCs.

On one of your PCs, locate the Agent_PCNAME.log file. (Substitute PCNAME with one of the PCs not reporting correctly) On my PC, it was located at C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Db.

See if that log file has any indication of a "SignIt Error -2147483640". (Leave out the double quotes when searching) When I was going through the logs on my PCs that were having these problems, this is what I found on my PC.

Doing a search on McAfee's web site came up with the following web page (KB article #5803947):

https://knowledge.mcafee.com/article/86/5803947_f.SAL_Public.html

When I used the workaround suggested in that KB article on my client PCs and deleted the registry keys mentioned and restarted the service, the agents were able to communicate with my ePO Server and policies were able to be downloaded and applied successfully and DAT updates were reported successfully as well.

Let see if you have the same problem.
helpoutwithmcafee (TechnicalUser) (OP)
23 Mar 07 2:14
Thanks for that, it seems to be the same issue. I have tried the resolution and it fixes the issue. Any idea when mcafee will release a fix for this issue.
VictorySabre (TechnicalUser)
23 Mar 07 12:22
No idea when/if the fix will come out. Based on that article, they are still investigating the issue. I've basically held off on the deployment of the new agent on my end until I get a good solution/workaround to correct the problem as I deploy the agent.

What I did do was use SMS to roll out the registry deletion and service restart on all the PCs with CMA 3.6.0.453 and that at least got my existing PCs working.

I may have to stick to that solution for the rest of my PCs until the next agent version is released, whenever it is.
jeffatemc (Programmer)
26 Mar 07 9:59
Thanks for that tip Victory, I was able to correct many,many units that were not reporting. Have a star!
VictorySabre (TechnicalUser)
2 Apr 07 21:51
Woo-hoo! Thanks for the star!

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Back To Forum

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close