Push of a package failes. But Logs say its good.. Well from what I see

Usage and Config Platform
1

(imported topic written by sid.lucas91)

OK,

So our company is new to the product. We had a scheduled meeting with a tech for training today. But it fell tough because the boss had an emergency to deal with.

As it stands. It looks like the install is working from the logs. But its is reporting back via the server that it has failed.

Tried a few things.

Cleaning the registry for Symantec.

Uninstalled BigFix

Nuked Program Dir files.

Reinstalled.

Install failed.

Action Script Execution Detail

Completed // action script to deploy CPM Endpoint application

Completed begin prefetch block

… Reduced

Completed endif

Logfile:

… Reduced

At 15:17:51 -0700 - Trend Core Protection Module (http://sync.bigfix.com/cgi-bin/bfgather/trendcpm)

Command succeeded (Exit Code=2) waithidden “C:\Program Files\Trend Micro\Core Protection Module\TMCPMCLI.exe” CONFIG -i “C:\Program Files\Trend Micro\Core Protection Module\global.ini” (fixlet 1211)

At 15:17:53 -0700 - Trend Core Protection Module (http://sync.bigfix.com/cgi-bin/bfgather/trendcpm)

Command succeeded regset "

HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\CPM

" “SetCPMGlobalSettingsActionID”=“1211” (fixlet 1211)

At 15:17:58 -0700 - Trend Core Protection Module (http://sync.bigfix.com/cgi-bin/bfgather/trendcpm)

Command succeeded regset "

HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\CPM\client

" “InstallTime”=“Fri, 02 Apr 2010 15:18:34 -0700” (fixlet 1211)

At 15:17:59 -0700 - Trend Core Protection Module (http://sync.bigfix.com/cgi-bin/bfgather/trendcpm)

Command succeeded (No pending restart) action may require restart {“CPM_DEPLOY”} (fixlet 1211)

At 15:18:01 -0700 -

ActionLogMessage: (action 1211 ) ending action

At 15:18:02 -0700 - actionsite (http://10.70.1.60:52311/cgi-bin/bfgather.exe/actionsite)

Not Relevant - Core Protection Module - Endpoint Deploy (fixlet:1211)

At 15:18:37 -0700 -

Report posted successfully.

Yet… I get this on the report…

Summary

The action failed.

This action has been applied 1 time and will not be applied again.

Status Failed

Start Time 4/2/2010 3:22:06 PM

End Time 4/2/2010 3:23:25 PM

And the system still shows up to be deployed, as it should.

I may not know what I’m looking for, but any hints would be appreciated.

2

(imported comment written by Ashwin.D91)

sid.lucas

Logfile:
… Reduced
At 15:17:51 -0700 - Trend Core Protection Module (http://sync.bigfix.com/cgi-bin/bfgather/trendcpm)
Command succeeded (Exit Code=2) waithidden “C:\Program Files\Trend Micro\Core Protection Module\TMCPMCLI.exe” CONFIG -i “C:\Program Files\Trend Micro\Core Protection Module\global.ini” (fixlet 1211)

Hi,

I think the problem is at this particular line

Exit Code = 0 means it executed successfully. 1 means it failed and 2 means the command is not recognized.

You might wanna check that line to see if there is any error in that line. From my experience, if a line executed with an exit code other than 0, the overall fixlet reports as failed because the success criteria is set as “All lines of the action execute successfully”.

Thanks

Ashwin

3

(imported comment written by sid.lucas91)

Thanks for the follow up. I guess I didn’t have a notice that anyone did.

But the fix is simple to answer my own question

  1. Execute the task to uninstall the CPM endpoint specifically targeting this computer. (Target > Change the radio button to specifically the computer, manually input the name in the field bellow). When you launch the Action change the relevance so that only the word true appears in the relevance of the action. This will force the action to execute against the targeted computer.

  2. Go to the user temp directory remove the temp files Normally set to %HOMEPATH%\AppData\Local\Temp

  3. Remove Remove the Trend files out of C:%PROGRAMFILES%\BigFix Enterprise\BES Client_BESData and C:%PROGRAMFILES%\BigFix Enterprise\BES ClientBESDataGlobal_Download\Trend Core Protection Module

  4. After the action completes, computer and search the registry for any Trend Micro key or values (Trend is a good search term. You will miss some of the keys if you don’t search for Trend for some reason.) and delete them.

  5. Reboot the machine

  6. Deploy the CPM endpoint to the machine.