Installing 9.1.1117 client on Win 2003 Failure

(imported topic written by ravi.k@techsa)

Hi all,

We are facing a tough time with a IEM deployment on RHEL and DB2.
The server infrastructure - IEM Server, DB, Console is up and running with 9.1.1117.
The setup has over 2000 Windows 2003 systems.

The client 9.1.x (tried two versions 9.1.1082 & version 9.1.1117). The client installation gets completed. However, we get an error on the Windows 2003 systems:

Client services fail to start
on Windows 2003

Windows
could not start the BES Client on Local Computer
. For more information, review the System Error Log. if this is a non-Microsoft service, contact the service vendor, and refer to
service-specific error code 32
.

Application Event Logs
show the following error

The description for Event ID ( 32 ) in Source ( BESClient) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event:
Failed to load libBEScrypto shared library: Dynamic library failed to load (C:\Program Files\BigFix Enterprise\BES Client/libBEScrypto.dll): LoadLibrary failed
.

It must be noted that the dll file is present in the folder.

  1. The client logs also indicate towards the same event log error

Client shutdown
(Failed to load libBEScrypto shared library: Dynamic library failed to load (C:\Program Files\BigFix Enterprise\BES Client/libBEScrypto.dll): LoadLibrary failed.)

Any indications as to what could be going wrong. We have a PMR open - but 15 days and we still dont have a clue as to what’s going wrong. A lower version 9.0.787 works fine.

Any pointers ??

(imported comment written by MattPeterson)

We’re you able to resolve this?

We have been using 9.1.1117 for a while now and all of a sudden one of our 700 some 2003 x86 servers stopped reporting in. I’m seeing the exact same behavior on this client as you’ve outlined.

We are experiencing the same type of issue on a custom coded project. We found if we completely reload the server OS the problem resolves itself.

Is there a AV run against the client installation directory? How about exclude the client directory from the AV list?

We have tried it with no AV installed.