Upgrading cdm probe to version 5.70 or later may cause a server reboot.

Document ID : KB000045870
Last Modified Date : 14/02/2018
Show Technical Document Details

Updated

Issue: 

 
- "We were upgrading CDM probe to the latest version (5.71) in our production environment and we received
      server reboot alerts. We checked and found that the servers were rebooted."
 

 

Environment: 

 

 

- This is happening regardless of the UIM or O.S. version. The issue is seen when upgrading
    to cdm 5.70 or higher.

 

 

Cause:

 

- The reason for the reboot is that, when upgrading to cdm 5.70 or higher,
    the vs2010sp1_vcredist_x64(x86) package is needed.
- When installing this package, the server may get rebooted.
- When it does, the following events are seen from the Windows Event Log:
 
- Event ID: 1033, Source: MsiInstaller: 
 
Windows Installer installed the product. Product Name: Microsoft Visual C++ 2010 x64 Redistributable
  - 10.0.40219. Product Version: 10.0.40219. Product Language: 0. Manufacturer: Microsoft Corporation.
  Installation success or error status: 0. 
 
- Event ID: 1038, Source: MsiInstaller: 
 
Windows Installer requires a system restart. Product Name: Microsoft Visual C++ 2010 x64 Redistributable
  - 10.0.40219. Product Version: 10.0.40219. Product Language: 0. Manufacturer: Microsoft Corporation.
  Type of System Restart: 2. Reason for Restart: 1. 
 
- Event ID: 1029, Source: MsiInstaller: 
 
Product: Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219. Restart required. The installation or
  update for the product required a restart for all changes to take effect. The restart was deferred to a
  later time. 
 
- Event ID: 1042, Source: MsiInstaller: 
 
Ending a Windows Installer transaction: p:\14656662de7b6e61370c4b987a\vc_red.msi. Client Process Id: 14952. 
 
 
Solution:

 

 Version 1.01 of the vs2010sp1_vcredist_x64 and vs2010sp1_vcredist_x86 packages have been updated to include

   the /norestart option. The updated packages are available in the Web Archive and should be downloaded to the

   local archive so that they will be used when deploying the cdm probe or any other probes which may require the

   vs2010sp1 packages as a prerequisite.

 

 

 

Workaround

 

- So far, there is no permanent fix but a workaround that goes as follows:
 
1) Create a superpackage from the vs2010sp1_vcredist_x64 (or x86, or both, depending on your end machines)
     and, in the "Miscellaneous" tab, under "Post install command", add "/norestart". 
 
2) This "/norestart" has been provided by Microsoft and it will avoid the restart of the server.
 
3) Screenshot summarizing step 1:
 
vs2010sp1.jpg
 

 

Additional Information:  

 

- Info on this behavior in the cdm's release notes: