Goals and Symptoms

This article applies to ION Enterprise 4.5 WebReach and greater.

The charting improvements made to Webreach that were introduced in ION Enterprise 4.5 make use of an ActiveX component called 'teechart5.ocx' or 'teechart7.ocx'.  This component is installed on the ION Enterprise Primary server at install time.  However, if charting is to be used on a client machine, this component must be installed on the client.  What typically happens is the first time a chart is viewed on a client machine, a dialog appears informing the user that an ActiveX component needs to be installed.  This component is downloaded from the Primary machine, installed and from this point on, charting is enabled on the client.

Facts and Changes

Facts

Category: Properties

Component: WebReach

Product: ION Enterprise

Causes and Fixes

There are two known scenarios where client PC's do not get prompted to install the ActiveX component

1) If a user is logged onto the client machine using a non-administrator account, the teechart5 or teechart7 install dialog will not appear, and charting will not function. Solution is to manually copy the teechart5.ocx or teechart7.ocx file from the ION Enterprise server and then register it on the client PC. Place the file into the C:\WINDOWS\system32 folder. To register the ocx (enter the following from command prompt):
''regsvr32 teechart5.ocx''
or
"regsvr32 teechart7.ocx"

2) If the MS security lockdown tool is setup on the ION Enterprise Server, the teechart5 or teechart7 install dialog will not appear on the Client machines, and charting will not function. The URLScan program(part of the MS Lockdown tool) blocks the download.

The solution is to modify the urlscan.ini file located in the c:\\WINNT\\system32\\inetsrv\\urlscan folder. Specifically, allow the extension .cab to pass through. After making the modification restart the web server.

An alternate solution is to manually copy over the teechart5.ocx or teechart7.ocx file from the ION Enterprise server and then register it on all client machines. Place the file into the C:\WINDOWS\system32 folder.