0x0000190D

Brad Johnson

unread,

Feb 10, 2010, 5:33:13 PM2/10/10

to

Hello,

In deploying C - Novell ZENworks Patch Management Agent Upgrade for Windows
from 6.0 or higher to 6.4.2.420 (QFE) (x86) (2K/XP/2K3) I am getting a
status of Failed (0x0000190D) for about 20% of the workstations. The
deployment detatils shows, "CRC failed during File copy Unable to download
file module: A489F868-2AB6-4302-B539-5267AFB04DCD". How do I go about
troubleshooting this problem?

Thank you,

Brad Johnson

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4855 (20100210) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

Shaun Pond

unread,

Feb 10, 2010, 11:37:35 PM2/10/10

to

Brad,

what patch level is your server at? There was an issue with CRC
previously, but fixed in 6.4SP1 Update 2 - hopefully you're at 6.4
SP*2* - I would re-cache the vulnerability as a first step

--

Shaun Pond

Brad Johnson

unread,

Feb 11, 2010, 10:06:46 AM2/11/10

to

I just recently applied B - Novell ZENworks Patch Management Server 6.4
Service Pack 2 Update 2 (QFE) (Manual Install) (See Notes). B - Novell
ZENworks Patch Management Server 6.4 Service Pack 2 Update 2 (QFE) (Manual
Install) (See Notes) was probably already cached before I did the server
update. I will re-cache. Some of the affected workstations access the
patches through distribution points, do I need to do something to have the
distribution points re-cache as well?

Brad Johnson

"Shaun Pond" <sp...@no-mx.forums.novell.com> wrote in message
news:VA.0000d30...@no-mx.forums.novell.com...

> __________ Information from ESET NOD32 Antivirus, version of virus

> signature database 4858 (20100211) __________

>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4858 (20100211) __________

Shaun Pond

unread,

Feb 11, 2010, 12:05:10 PM2/11/10

to

Brad,

they should see that the timestamp on the file is newer, and recache

--

Shaun Pond

Brad Johnson

unread,

Feb 11, 2010, 4:29:37 PM2/11/10

to

I did a re-cache by selecting the package and choosing Update Cache. I then
redeployed to the workstations that previously failed. They all failed
again. All the workstations with failed deployments are in remote offices
with distribution points. We do have some remote offices with distribution
points where the deployment of this package was successful. It appears that
the deployment is a success or failure on an office by office basis, i.e. if
one fails they all fail, or if one succeeds they all succeed. Even at the
offices with deployment fialures for this package we have successful
distribution of other packages.

Brad Johnson

"Shaun Pond" <sp...@no-mx.forums.novell.com> wrote in message

news:VA.0000d32...@no-mx.forums.novell.com...

> __________ Information from ESET NOD32 Antivirus, version of virus

> signature database 4859 (20100211) __________

>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4859 (20100211) __________

Shaun Pond

unread,

Feb 12, 2010, 6:24:55 AM2/12/10

to

Brad,

now that's interesting - I think it's quickest here if I throw this
into Lumension's lap... Ticket 100212-000008

--

Shaun Pond

Brad Johnson

unread,

Feb 12, 2010, 11:14:09 AM2/12/10

to

Thank you.

On one of the remote workstations I disabled the proxy setting, then
attempted the deployment again. It failed with the same error.

Brad Johnson

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4861 (20100212) __________

Shaun Pond

unread,

Feb 13, 2010, 4:10:41 AM2/13/10

to

Brad,

well the first answer I got back isn't exactly user-friendly, they
suggest clearing the cache in the distribution point...

--

Shaun Pond

Brad Johnson

unread,

Feb 14, 2010, 11:23:32 PM2/14/10

to

While it may not be user friendly, I am very willing to give it a try. Is
it possible to clear only the offending package or will I need to clear the
entire cache? Where would I find instructions for this procedure?

Brad Johnson

"Shaun Pond" <sp...@no-mx.forums.novell.com> wrote in message

news:VA.0000d33...@no-mx.forums.novell.com...

> __________ Information from ESET NOD32 Antivirus, version of virus

> signature database 4865 (20100214) __________

>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4866 (20100214) __________

Shaun Pond

unread,

Feb 15, 2010, 6:15:57 AM2/15/10

to

Brad,

it's hard to work out what the correct file is, since they're all
renamed. In the past, for an apache cache, I just shut down apache,
deleted all the files and directories under the cache, and restarted,
but there are other ways that I can find
http://httpd.apache.org/docs/2.2/caching.html for example.

--

Shaun Pond

Brad Johnson

unread,

Feb 16, 2010, 11:33:00 PM2/16/10

to

Shaun;

I cleared the cache of one of the distribution points and then redeployed

C - Novell ZENworks Patch Management Agent Upgrade for Windows from 6.0 or

higher to 6.4.2.420 (QFE) (See Notes) to one of the workstations in that
office. The deployment failed with the same error. Interestingly while a
new set of directories was added to the distribution point cache, \R\K\t, no
files were placed in the cache. After this failure I then deployed MS10-006
and MS10-005 to this same workstation. These packages were deployed
successfully. On the distribution point two new sets of directories were
created each containing a .data and a .header file.

Brad Johnson

"Shaun Pond" <sp...@no-mx.forums.novell.com> wrote in message
news:VA.0000d33...@no-mx.forums.novell.com...

> __________ Information from ESET NOD32 Antivirus, version of virus

> signature database 4868 (20100215) __________

>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4872 (20100216) __________

Brad Johnson

unread,

Feb 16, 2010, 11:56:31 PM2/16/10

to

I resolved the problem. I should have thought of this sooner. Our branch
offices are connected via VPN/firewall devices which also run AV software.
Due to a configuration error some of these devices do not have current AV
databases. The C - Novell ZENworks Patch Management Agent Upgrade for
Windows from 6.0 or higher to 6.4.2.420 (QFE) (See Notes) package is being
detected as a Hide.A trojan and is being blocked by these dveices. Once I
resolved the AV issue the patch is delivered just fine.

Thank you for all your help.

Brad Johnson

"Shaun Pond" <sp...@no-mx.forums.novell.com> wrote in message
news:VA.0000d33...@no-mx.forums.novell.com...

> __________ Information from ESET NOD32 Antivirus, version of virus

> signature database 4868 (20100215) __________

>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4872 (20100216) __________

Shaun Pond

unread,

Feb 17, 2010, 8:12:51 AM2/17/10

to

Brad,

d'oh! Thanks for the report

--

Shaun Pond

Delon Weuve

unread,

Feb 17, 2010, 11:26:28 AM2/17/10

to

Brad,

What AV software are you running and do you have details?

That way, I and others like myself don't have to reinvent the wheel.

Thanks.

>>> Brad Johnson<Br...@notrealaddress.com> 2/16/2010 10:56 PM >>>