rsp probe 5.57 / 5.58 crashes when discovering: conf_rsp.exe / MSVBVM60.DLL / Exception code: 0xc0000005

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

The RSP probe crashes whenever we discover any device.

Remote System Probe Configuration Tool has stopped working
A problem caused the program to stop working correctly. 
windows will close the program and notify you if a solution is available 
 

In the Windows Event log the following is observed: 

Faulting application name: conf_rsp.exe, version: 1.17.0.37, time stamp: 0x666abf07
Faulting module name: MSVBVM60.DLL, version: 6.0.98.15, time stamp: 0x49b01fc3
Exception code: 0xc0000005
Fault offset: 0x000c9bee
Faulting process id: 0xcc4
Faulting application start time: 0x01db0359dadf1a39
Faulting application path: C:\Users\<user>\AppData\Local\Temp\2\util\conf_rsp.exe
Faulting module path: C:\Windows\SYSTEM32\MSVBVM60.DLL
Report Id: e9e45f94-af8f-485d-96f7-29791f6e88e4
Faulting package full name: 
Faulting package-relative application ID: 

 

 

Environment

• DX UIM 20.4.* / 23.4.*
• rsp probe versions affected: 5.57 / 5.58
• vs2017 upgrade 

Cause

The issue is related to the last 2 versions of the RSP probe 5.57 and 5.58 which have issues with the GUI vs2017 upgrade. Only when discovering, when running these versions, (or when only any of these 2 versions are present in the archive), the GUI crashes.

Resolution

• The issue will be fixed in the upcoming release of RSP probe which will be included in the Release of DX UIM 23.4CU3. The new GA probe version will also be available on support.nimsoft.com archive on the day of the release of DX UIM 23.4CU3. [ETA for release of CU3 is some time in January 2025].

 

• In the meanwhile, there is a workaround:
  
  
  •   The version 5.56 is not affected. Direct download link: http://support.nimsoft.com/Files/Archive/00120/rsp-5.56.zip  
    
    
  •   For the workaround to be effective you must remove rsp version 5.57 and 5.58 from the archive, downgrade rsp to 5.56 and the discovery will succeed. 

NOTE: You can upgrade later on to 5.57/5.58 as the probe will be fully functional, except for the Discovery operations. For that, you need 5.56 and NO 5.57/5.58 in the archive. The reason for NOT having 5.57/5.58 in the archive is because the IM will always try to fetch the latest version GUI from the archive. So, if it fetches the 5.57/5.58 GUI, it will crash due to the vs2017 issue.