logmon probes does not run with vs2017_redist on Windows 2008 R2 SP1

Products

• NIMSOFT PROBES
• DX Infrastructure Management

Issue/Introduction

The logmon probe does not run with vs2017_redist on Windows 2008 R2 SP1, we get the following error:

 

Robot  is not able to start the logmon probe:

 

Aug 28 08:47:53:858 [2592] Controller: Probe 'logmon' FAILED to start (command = logmon.exe) error = (14001) The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail.  

 

The same error is also in the controller.log file.

 

If i install the vs2008_redist package, logmon works but i understand there are security concerns with  vs2008_redist. I had a webex with Nitin and showed him the issue and he suggest that i created this case to get logmon certified with vs2017_redist as soon as possible.

 

 

Environment

Release : 9.1.0

Component : UIM LOGMON

Resolution

The “side by side configuration is incorrect” error may occur because of the Visual C++ Runtime  is corrupted on the computer.

We can remove side by side error configuration error by following these steps

1.Open the regedit  HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > CurrentVersion > SideBySide > Winners >

Under this search for the key  1fc8b3b9a1e18e3b or 9.0  and under 9.0 replace the default value with the highest value of the version number  appeared ,as shown in the attached screenshot.

 

2.Restart the system .This will remove the side by side error configuration.The logmon is runnning with VS2017_redistpackage only.

for example like HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows > CurrentVersion > SideBySide > Winners > x86_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_none_02d0010672fd8219 > 9.0

 

For more information please refer to the like https://www.majorgeeks.com/content/page/solved_the_application_has_failed_to_start_because_its_side_by_side_configuration_is_incorrect_error.html

I already tested in my system and worked fine .Can you please test this in your setup environment before providing this solution.