Re: Changing "Failed" Error Code
- From: "Bill Bradley" <wdbradley3@xxxxxxxxxxx>
- Date: Thu, 6 Apr 2006 01:31:19 -0600
I actually found the solution at MyItForum.
A two line batch file:
(NOTE: This is for SuperDAT (both Engine and DAT), for XDAT (just DAT) use
xdat.exe--both instances have had version removed, so that batch never has
to be edited. Also, for xdat, change number in second line from 44 to 49).
sdat.exe /SILENT /PROMPT
if errorlevel 44 exit /B 0
Works GREAT!
But...probably ought to have some kind of error translation built-in to
SMS...
Thanks.
"Kim Oppalfens <MVP>" <Kim dot Oppalfens@google mail.com> wrote in message
news:ehg7SyOWGHA.2376@xxxxxxxxxxxxxxxxxxxxxxx
Was your original advertisement a mandatory one?
--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"Bill Bradley" <wdbradley3@xxxxxxxxxxx> wrote in message
news:O9eW%23HeVGHA.1728@xxxxxxxxxxxxxxxxxxxxxxx
I'm trying to deploy the McAfee SuperDAT file on a recurring basis, and,
once the program has run on a computer and updated the McAfee Engine and
DAT, the next time it runs, it does nothing (since the files are already
updated), and generates an Error Code of 44, meaning "Files are already
updated", but, SMS interprets this as a Failure in the Log.
Is it possible to intercept this, so that the Error Code of 44 is not
reported as a Failure?
Thanks.
.
- References:
- Changing "Failed" Error Code
- From: Bill Bradley
- Changing "Failed" Error Code
- Prev by Date: Re: Assigned but not a client
- Next by Date: Re: Configuring multiple DPT servers at a large site
- Previous by thread: Changing "Failed" Error Code
- Next by thread: Console opens slowly after w2k3 srv service pack 1
- Index(es):
Relevant Pages
|
