search cancel

After PIM Windows installation finished successfully, but seosdb and services for PIM drivers were not created.


Article ID: 7249


Updated On:


CA Virtual Privilege Manager CA Privileged Identity Management Endpoint (PIM) CA Privileged Access Manager (PAM)


Installation of PIM 12.8 GA RO70543 (12.80.1587) Windows version on Windows 2012 R2 boxes finished successfully, but seosdb and services for PIM drivers were not created on some specific box, so after reboot the box PIM couldn't start.

The symptom has happened on some specific boxes.


PIM: 12.8 GA RO70543 (12.80.1587)OS: Windows 2012 R2


PIM installer uses InstallShield, and InstallShield has known issues of Handle leaks in some specific cases. This causes of skipping the actions of seosdb creation and PIM driver installation.


note: The "CA" in the title of URL page means "Custom Action".


For PIM 12.8 GA RO70543  (12.80.1587), test fix T4A7121 is released.

Also, the fix will be included in the product release next to PIM 12.8 SP1.

Additional Information

When the symptom has occurred, the following message patterns are identified in install log.

MSI (s) (1C:30) [05:06:16:070]: Note: 1: 2769 2: BuildPluginsProcFile 3: 1 
Info 2769.Custom Action BuildPluginsProcFile did not close 1 MSIHANDLEs.   <=== Handle leak symptom happens.

MSI (s) (F8:70) [06:38:04:505]: Executing op: ActionStart(Name=InstallDrivers,,)
Action 6:38:04: InstallDrivers.
MSI (s) (F8:70) [06:38:04:505]: Executing  op:CustomActionSchedule(Action=InstallDrivers,...f39,)
MSI (s) (F8:5C) [06:38:04:521]: Invoking remote custom action. DLL: C:\Windows\Installer\...tmp, Entrypoint: f39

InstallShield 6:38:04: Running InstallScript function f39
  <=== The messages from InstallShield are recorded in normal case.
  <=== But if those messages are not recorded, then it implies services of PIM driver are skipped.

If you see the similar message patterns in a PIM install log and your install version is not PIM 12.8 GA RO70543  (12.80.1587), please open a new case and add the technical document number in your case.