Installation Failed on new deployment

Hi ,

I having issue have deploy BESCLient to servers. among 50 servers, only 22 has completed successfully.

  1. In Some server, the installation does not take place at all. Well Altiris guy told me my job push 100% succesfully. The server is Windows Server 2008 R2 , Bigfix Client is BigFix-BES-Client-9.5.2.56 .
    upon the deployment, i found the installation is not in
    C:\Program Files (x86)\BigFix Enterprise\BES Client
    C:\Program Files\BigFix Enterprise\BES Client
    or it actually never installed.

Where can i find the logs if the installation failed in halfway. (thats what i suspect)

  1. And some having issue report to Bigfix server. upon checking
    -the installation is completed
    -the masthead file is in correct path. (with a similar masthead file, some server work and som are not)
    -the port 52311 is open between client and server
    -client has enough disk space.
    -below is the logs in C:\Program Files (x86)\BigFix Enterprise\BES Client__BESData__Global\Logs

Current Date: November 1, 2016
Client version 9.2.8.74 built for Windows 5.1 i386 running on WinVer 6.3.9600
Current Balance Settings: Use CPU: True Entitlement: 0 WorkIdle: 10 SleepIdle: 480
ICU data directory: ‘c:\Program Files (x86)\BigFix Enterprise\BES Client’
ICU init status: SUCCESS
ICU report character set: windows-1252
ICU fxf character set: windows-1252
ICU local character set: windows-1252
ICU transcoding between fxf and local character sets: DISABLED
ICU transcoding between report and local character sets: DISABLED
At 00:00:02 +0100 -
Starting client version 9.2.8.74
Unhandled error: class NotASignedMessage
Client shutdown (Unexpected error)

Anyone here has similar issue or solution for me :slight_smile:??

Hi @JimmyEu,

  1. You mentioned you deployed BES Client version 9.5.2, the log snippet you provided was 9.2.8. Where was the client log taken?
  2. How did you perform the client deployment? What tool did you use? Did you use the .exe or the MSI installer? Your issue might be related to: http://www-01.ibm.com/support/docview.wss?uid=swg21505889
  3. Also, can you check if the actionsite.afxm located at C:\Program Files (x86)\BigFix Enterprise\BES Server\ matches the one the client has? The client actionsite.afxm is located by default at: C:\Program Files (x86)\BigFix Enterprise\BES Client

You might want to check this as well:

Error on starting BES Client service on Windows endpoint (masthead problem)
http://www-01.ibm.com/support/docview.wss?uid=swg21984704

1 Like

Unhandled error: class NotASignedMessage

Seems to be a problem related to masthead file.
Probably when the package were copied to remote machines it could got corrupted or missed.

1 Like

thanks. ur sharing is helpful. the problem is on the Masthead file. i retrieve a new and replace. it fixed.

1 Like

Yes u are right!. havent look into the logs details. but it did fixed it