The DAU deployment is failing on most of our machines, with the error,
"Failed to process action: Information for id
794bb54fe527e4f96b9b24cfbed566a5 has not been cached." This is happening
for both our XP and Win7 machines.

This all started the beginning of the week when I was getting a lot of
"Analyze failed to launch.{}" errors. I found TID 7009187. I followed the
instructions: added a file named dummy.txt to each of the agents folders,
ran a patch subscription "update now", deleted the dummy.txt files, and
reran the "update now". After this my problems with the DAU deployment
started. In the last few days I have added some new machines to ZCM, they
are not experiencing any problems with the DAU. Only those machines which
were in ZCM at the time I did the TID 7009187 procedure.

Working with Novell support we thought we had come up with a solution. On
two machines, one XP and one Win7, we manually deleted all the *.pls files
from the zpm directory, ran "zac cc", then "zac ref bypasscache". At this
point all the ZCM related icons on the desktop and in the ZEN Application
Window disappeared, so we ran "zac ref", this brought all the icons back.
At this point we were able to successfully start the DAU.

With this information I created a bundle with the following actions: Delete
the *.pls files in the zpm directory using a script, delay for 2 minutes,
run zac cc, run zac ref bypasscache, delay 2 minutes, run zac ref. I
deployed this bundle to all workstations (this includes the machines added
to ZCM in the past couple days and the two machines on which we did our
manual testing). The bundle ran successfully, however we are still getting
the error: "Failed to process action: Information for id
794bb54fe527e4f96b9b24cfbed566a5 has not been cached." when deploying the
DAU to all machines except those machines added to ZCM in the last couple of
days and the two machines on which we did our initial manual testing of this
procedure.

Working with Novell support we have tried numerous manual methods to get the
DAU to run without error on these machines and nothing has worked. I don't
understand how the bundle I deployed could make it so there now appears to
be no resolution to the DAU deployment error. As of the end of the day on
Friday (today) we are still stumped. Does anyone have any idea what I can
try to get the DAU to deploy successfully again?

Thank you,

Brad Johnson


__________ Information from ESET NOD32 Antivirus, version of virus signature database 6470 (20110916) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com