|
Get Adobe ! |
.OCX Support
This page provides information for County and State technical staff responsible for supporting .ocx files for the eWiSACWIS application.
If you have any issues with the install please contact
Sue Zemke (608)
266 6712
·
"How to" fix OCX
Install error prompt - June 2011 (PDF)
·
Installing OCX on a Vista machine
·
Macro
message fix - July 2006
·
Manual
Installation instructions
.ocx Manual Installation Instructions
To access the files needed:
·
The most recent files were issued on May
11th 2011 (confirmed July 1st, 2011)
·
Please Note: The Install will
detect which version of word you have and if it is older than 2007, it will do
nothing.
OCX Install Files (in zip file)
·
Extract the contents of the zip file into a
folder or disk
·
Folder should contain these files:
o
ocx.cab is the signed file.
o
DeployOcx.HTM contains the object tag and
other tags needed to unzip and install ocx.
To install the OCX:
There is more than one method that can be used. Among the most commonly
used methods to manually install ocx files are:
Manual installation to each PC
·
Login to the workstation as the 'Administrator'
·
Extract the contents of the zip file into a
folder on the worker station's C:\ Drive, or use a disk that contain the
unzipped files
·
Double Click on the DeployOCX.html file
Network installation
·
Log in as Administrator to network
·
Copy the files to a common network drive and
double click on the DeployOcx.htm file from the user's PC, or send the end user
a link to open the DeployOcx.htm file
Intranet installation
·
Deploy the files to a local web server and send
the link to the DeployOcx.htm file to the user (some counties have done this by
adding the link to the County Message Area of eWiSACWIS).
Local software installation
·
Use NAL, SMS or any other locally used software
to distribute.
Citrix installation
·
Logon as administrator to the Citrix server.
·
Access the eWiSACWIS application and install the
files.
·
Once the installation is completed, publish IE to
all the user desktops.
·
Verify that the eWiSACWIS folder has full access
to all users.
·
Repeat this process for each Citrix server.
To verify the installation:
·
Open Internet Explorer
·
From the Tools menu select "Internet Options..."
·
On the General Tab click on the "Settings"
button
·
On the Settings pop-up click on the "View
Objects" button
·
Check that file
"SacwisDocumentAutomation.ocx" is present
.ocx Manual Removal Instructions
Download and run the following file to uninstall the OCX:
.ocx Macro Message Fix
Problem:
End user gets a popup message asking them to enable or disable macros when they
attempt to open an MS Word Template in eWiSACWIS.
The popup contains “Always trust macro from this source” checkbox, but
the end user is unable to check the checkbox.
They continue to get the popup message every time they use a template.
1.
The solution depends on saving a certificate file to the
PC. To do so, save zip file
Verisign-Class-3-Code-Signing-2004-CA.zip to the C drive of the PC that
needs to be fixed.
2.
Open the zip file; it will contain a single file,
Versign-Class-3-Code-Signing-2004-CA.cer.
Extract (save) the file to C
drive of the PC.
3.
Open the file from the C drive.
4.
Click on the "Install Certificate" button.
5.
The "Certificate Import Wizard" should open. In the
"Certificate Import Wizard" click on the "Next" button and keep clicking on the
"Next" button (leaving the default options selected) until you get to the step
where there is a "Finish" button (there are 3 screens in the "Certificate Import
Wizard"). After clicking on the "Finish" button you should see a message "The
import was successful"
6.
Now the user should be able to check the "Always trust
macro from this source" checkbox when a document is launched through eWiSACWIS
and not have to keep enabling the macro every time a document is launched
through eWiSACWIS.
Note:
For counties on Citrix and/or have many users, installing this certificate
manually on every user's workstation may not be a feasible option. For such
counties automating the certificate installation maybe a better option. For
counties using Microsoft OS based servers the following links gives some details
on automating this process:
Updated October 24, 2011
