ActiveX Controls Fail to Load - Archive Services for Microsoft SharePoint - English - Foundation 22.1 - OnBase - Essential - Premier - Standard - external - Essential - Premier - Standard

Archive Services for Microsoft SharePoint

Platform
OnBase
Product
Archive Services for Microsoft SharePoint
Release
Foundation 22.1
License
Essential
Premier
Standard

ActiveX controls may fail to load on workstations running Internet Explorer. Depending on the workstation's Internet Explorer security settings, one of the following symptoms may occur:

  • The ActiveX control fails to load, and an icon with a red x is displayed in the ActiveX component's location.

  • The Information Bar is displayed, providing the option to Run or Don't Run the ActiveX control. When the user clicks Run, the ActiveX control fails to load.

  • Internet Explorer displays the error, Failed to load [control name] ActiveX control.

Cause

ActiveX controls may fail to load as a result of an ActiveX security setting in Internet Explorer. When enabled, the Only allow approved domains to use ActiveX without prompt setting can prevent ActiveX controls from loading properly in OnBase Web applications, including the OnBase Web Client, integrations for SharePoint and SAP, and the Medical Records Management Solution.

Solution

To ensure that ActiveX controls can load properly, preset the allowed OnBase ActiveX controls and the associated sites in the registry as described in “Per-Site ActiveX Controls,” available at the following location: http://msdn.microsoft.com/en-us/library/dd433050(VS.85).aspx#_itpro

This article describes how to allow specific ActiveX controls to run for specific sites. See the “Code Samples” topic for sample scripts to update the registry. These scripts use the CLSIDs of the ActiveX controls being enabled. The CLSIDs for the OnBase Web ActiveX controls are provided in the following table:

ActiveX Control

{CLSID}

OBXFileSvc

{D0745161-309E-4345-8301-A68166939648}

OBXPopup

{6354E6EF-4C10-440F-817C-AD43BED4C8DD}

OBXWebControls

{3E484757-6B33-488D-B415-7249146F68C6}

OBXWebDocumentSelect

{C685F130-98AD-4DF4-9245-B6FB7AC3EC11}

OBXWebPrint

{92D974D3-9056-44E5-BC47-D04439A52C0B}

OBXWebScan

{0DEC9D4B-2AF9-4170-BE55-A90FB55FAD32}

OBXWebViewer

{620C84F3-3947-4182-9A83-7AF7B2E05F51}

OBXWorkflowLoadBalance

{4F2F0EB0-F4A9-4817-86B4-70619B9C1441}

CAUTION:

Modify the registry at your own risk. Incorrectly editing the Windows registry can cause serious problems that may require you to reinstall your operating system. Be sure to back up the registry before making any changes to it. For more registry information, see the following Microsoft articles: http://support.microsoft.com/kb/256986 and http://technet.microsoft.com/en-us/library/cc725612.aspx

For example, a script that allows the ActiveX viewer (OBXWebViewer) to run on all domains may include the following:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Ext\Stats\{A8A7310D-814C-4695-AD02-235675E4BD60}\iexplore\AllowedDomains]
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Ext\Stats\{A8A7310D-814C-4695-AD02-235675E4BD60}\iexplore\AllowedDomains\*]

More information about writing registry scripts can be found at the following location: http://support.microsoft.com/kb/310516