ACT 5.5: "procedure entry point LoggerStart in logger.dll not foun

[MN]

I deployed the ACT 5.5-DCPs an several clients and after a reboot some
clients showed an error message. The message reads "ALMON.EXE - procudre
entry point LoggerStart not found in logger.dll". I believe it has something
to do with the installed Sophos anti-Virus, but would like to hear, if
anybody else had that problem and how it can be solved.

Thanks for any help,

Martin Nothnagel
(I submitted a bug report in MS-Connect, too.)

[Ajith Alexander [MSFT]]

I believe you're right in your diagnosis that it is an interaction with
Sophos. We'll investigate the bug you filed and see how we can work around
it. In general (as described in our step by step guides), some antivirus
applications don't work well with ACT's data collection mechanism. Several
antiviruses can be modified to set a custom rule that allows signatures of
these data collection packages to get through. This is an option worth
exploring.

Another thing to try in order to temporarily unblock you is to just run the
inventory agent (which does not interact significantly with applications on
your machine) and use that inventory and the compatibility data you get from
ACT's compatibility exchange to help with your compatibility assessment.

-Ajith Alexander [MSFT]

[MN]

Hi Ajith,

thank you for your reply. Whitelisting the ACT is a good advice, I will
check if
this solves the problem. We also opened a case at Sophos, maybe they will
adjust their software to work side-by-side with ACT.

Thank you,

Martin Nothnagel

[Wynne@discussions.microsoft.com Mark Wynne]

Guys,

The issue is that Logger.dll is an actual component of the Sophos Antivirus.

When you install the Collector on a machine running Sophos, when Sophos
tries to call a function in Logger.dll it is finding the Logger.dll
installaed by the collector and thus the Entry Point is invalid as this is
not Sophos' Logger.dll file.

Is there a way we can specify that the logger.dll file is not dployed in the
collector or is it a Key Part of the collector.

I have altered %ProgramFiles%\Microsoft Application Compatibility Toolkit
5\Agent Framework Install\Agents\UACCE\UACCEAgent.XML and removed the File
Node for Logger.dll which works in so much as logger.dll is not deployed. But
the collection agent fails to start as it is obviously looking for
functionality within that dll.

Any help Greatly appreciated.

[Anders_R]

Any news on this? I am experiencing the exact same thing. The logger.dll from
the ACT 5.5 DCP is installed and most likely registered in system32, but
there is no way to isolate it in the DCP .msi file, since that msi is just a
wrapper for a binary stream exe installer. My hope lies with Sophos coming up
with a smart solution, since I doubt that the DCP.msi will be possible to
edit in a manner that enables issolation of that logger.dll. It don't think
that unregistering the MS dll file will be a good idea either, but I will
give it a shot.

Looking forward to any update on this.