Back

Topic

[KB760]Troubleshooting PcVue Installation: VBA

Tags: Installation, VBA

PcVue installation
10 years ago
By RM
Options
Print
Applies to:

PcVue 10.0 and later
Summary:

Unexpected behavior during the PcVue VBA installation process.
Originator: JM
Details:

VBA is not installed after a reboot was requested during the installation process

Applies to
PcVue from versions 10 to
PcVue 11 (11.0.06037)
PcVue 11.1 (11.1.02031)
Also FrontVue until
FrontVue 11 (11.0.06019)
FrontVue 11.1 (11.1.02003)

The following explanation is only for the case that the installation process requested a reboot and VBA was not installed. This may occur even if you did not chose to reboot. The behavior is due to a Windows Installer restriction.

How to install VBA in such a case:

1 – Restart the computer
2 – Uninstall PcVue
3 – Reinstall PcVue

This solution will be sufficient most of the time.
The reboot is generally required by the installation of Sentinel driver, the second time you install PcVue, the Sentinel driver will be already installed, so the reboot will be no longer necessary, and VBA will be installed.

If it does not work, the only way is to launch PcVue installation using Sv\Setup.exe and the parameter REBOOT=ReallySuppress.

Note:
This behaviour happens only during first installation, when VBA is not already installed
To install a later version, it is strongly advised to ugrade the current installed version (without uninstalling it), to avoid to uninstall / reinstall VBA.

Note:
A “correction” has been integrated, the request for reboot has been postponed, from PcVue installation to installation start screen.
This correction will work only if you launch PcVue installation normally (via setup.exe located at the root of the installation package).

Registry database after the installation of VBA

When investigating problems with the installation of VBA it can be useful to check the Registry. The following is from a good installation.

  • HKLM\SOFTWARE\Microsoft\VBA    (On 32-bit platform)
  • HKLM\SOFTWARE\Wow6432Node\Microsoft\VBA      (On 64-bit platform)
    • Vbe6DllPath=C:\\PROGRA~1\\FICHIE~1\\MICROS~1\\VBA\\VBA6\\VBE6.DLL
    • Subkey VBA6.4
      • Installed=dword:00000001
    • Subkey VBA6.4\InstalledBy
      • {0C9AB2EC-EC33-408B-8CA6-B377B47BD6A5}=dword:00000000
      • …
      • {product guid n}=dword:00000000
    • Subkey VBA6.4\Locales
      • 1033=dword:00000000
      • …
      • <lang id n>=dword:00000000
  • HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\         (On 32-bit platform)
  • HKLMS\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\          (On 64-bit platform)
    • Subkey {FB97C283-1F3C-42D4-AE01-ADC1DC12F774}
      • DisplayName=Visual Basic for Applications SDK
      • DisplayVersion=6.05.1020
    • Subkey {A13D16C5-38A9-4D96-9647-59FCCAB12A85}
      • DisplayName=Visual Basic for Applications (R) Core – English
      • DisplayVersion=6.5.10.32

Version 10.0 marks the end of error 115 but there is a possibility of compatibility issues (during the uninstall process) with versions using VBA 6.4, according the order in which the products have been installed and removed. However this should only result in an error display and not cause any serious problems.

If there are problems with VBA please provide an export of the following registry keys

  •  On 32-bit platform:
    • HKLM\SOFTWARE\Microsoft\Vba
    • HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
  • On 64-bit platform:
    • HKLM\SOFTWARE\Wow6432Node\Microsoft\Vba
    • HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall

For your information (and if you want to check) here are the product codes corresponding to VBA 6.5 / 6.4

  • VBA 6.4 – Core : {90F50409-6000-11D3-8CFE-0150048383C9}
  • VBA 6.4 – English resources : {90F60409-6000-11D3-8CFE-0150048383C9}
  • VBA 6.5 – Core {FB97C283-1F3C-42D4-AE01-ADC1DC12F774}
  • VBA 6.5 – English resources : {A13D16C5-38A9-4D96-9647-59FCCAB12A85}

Created on: 14 Apr 2015 Last update: 04 Sep 2024