This topic contains answers for the frequently asked questions related to the problems with Image Uploader installation. Be sure to read this topic before creating support case.
In this topic:
There can be several reasons:
Internet Explorer can be configured to prohibit installation of ActiveX controls. Typically this configuration is default on server editions of Windows (like Windows 2003). Also, in some corporate networks it can be defined with the security policy.
Default security settings on workstations (like Windows XP) allows installing signed ActiveX controls.
To check whether security settings are ok, follow these steps:
You should be an administrator to install ActiveX controls in Internet Explorer 7 and 8 on Windows XP. However, on Windows Vista/7 administrator permissions are not required.
Some firewall software may be configured to block any ActiveX controls met on the page the user loads. If you have some firewall installed, check out its settings or contact your system administrator regarding this problem.
To install Image Uploader on client machine, Internet Explorer downloads the ImageUploader37.cab file. You should provide a correct URL to this file, otherwise, Internet Explorer will fail to download and install it.
URL to this file is specified in the codebase of the control. If the Image Uploader embedding scripts library is used, this is configured with the activeXControlCodeBase property. It can be both absolute and relative URLs. Make sure that ImageUploader37.cab is accessible from this URL. To do it, type this URL in the Address bar of your browser and click Enter. Note, if you use an absolute path type it as is; otherwise, if the path is relative, type it relatively to the page which hosts Image Uploader. If the browser starts downloading ImageUploader37.cab file, the specified path is correct.
For example, if you host Image Uploader on the http://domain.com/ImageUploader/default.aspx
page and set activeXControlCodeBase to the "../Scripts/ImageUploader6.cab" value, type
http://domain.com/Scripts/ImageUploader6.cab in your browser's Address bar to check the path.
ActiveX controls should be signed with a digital certificate to be interpreted as safe by Internet Explorer. In theory it is possible to enable unsafe ActiveX controls, however, it is not recommended as it may compromise security.
Image Uploader is already signed with Aurigma's digital certificate (speaking more precisely, the ImageUploader37.cab file). However, if you modify this file anyhow, e.g. rename or re-assemble it, the digital signature will not be valid. This way Internet Explorer will interpret this file as unsafe and reject to load it.
Several reasons can cause this problem:
Java version of Image Uploader requires Java Runtime Environment (JRE) version 1.5 or later. If it is not installed, no Java applet will run.
Most browsers allow users to disable Java applets. Make sure whether Java applets are enabled in your browser settings (varies from browser to browser).
If you experience problems with Java version installation on Mac, keep in mind, that some Mac browsers do not support JRE 1.5 by default. To have these browsers to work with JRE 1.5, it is necessary to install Java Embedding Plug-in.
The following Mac browsers already have built-in JRE 1.5 support:
When a user opens the page which hosts Image Uploader in one of the supported browsers, ImageUploader37.jar is automatically downloaded and installed. If the URL to the directory with this file is incorrect, the installation will fail and java.lang.ClassNotFoundException will be thrown.
URL to the directory where ImageUploader37.jar file is located is specified in the javaAppletCodeBase property of the Image Uploader embedding scripts library. It can be both absolute and relative URLs. Make sure that the correct directory is accessible from this URL. To do it, type this URL and ImageUploader37.jar filename in the Address bar of your browser and click Enter. Note, if you use an absolute path type it as is; otherwise, if the path is relative, type it relatively to the page which hosts Image Uploader. If the browser starts downloading ImageUploader37.jar file, the specified path is correct.
For example, if you host Image Uploader on the http://domain.com/ImageUploader/default.aspx
page and set javaAppletCodeBase to the "../Scripts/" value, type
http://domain.com/Scripts/ImageUploader6.jar in your browser's Address bar to check the path.
Yes. The only browser that supports ActiveX technology is Internet Explorer on Windows. No other browsers can work with ActiveX controls (including Internet Explorer for Mac). Use Java version of Image Uploader with these browsers. If you are using Image Uploader embedding scripts library to work with Image Uploader, it will automatically detect the user's browser and load appropriate version.
Yes. Java version of Image Uploader does not support Internet Explorer for Mac.
See a list of supported browsers for more details.
Yes. You can download standalone installer at this location:
http://www.aurigma.com/Products/DownloadFile.aspx?ID=107
Although standalone installer allows users to install Image Uploader regardless to Internet Explorer settings, the user still needs administrator privileges.
Most likely the problem is in incorrect codebase.
This situation has the following explanation. ActiveX controls are cached by the browser. Once it is downloaded and installed, stored on client computer. If on the first computer you visit online demo of Image Uploader or load it anywhere else, Image Uploader gets into the browser's cache. Internet Explorer will not try to download it and therefore incorrect codebase will not cause any problems.
However, as soon as you try to open the page from another computer, which never downloaded Image Uploader, Internet Explorer will try to download it from the codebase, and of course it will fail.
See the Updating Image Uploader on the Client Side topic.
You need to order a private-label version of Image Uploader. Contact our sales department for more details.
If you get this message when updating Image Uploader in the browser, it means that you have another browser instance with Image Uploader opened. In this case it locks the old version of Image Uploader. That is why old version fails to be uninstalled and the browser prompts to restart computer to complete installation.
To avoid this problem, it is recommended to close all the browsers that host Image Uploader before updating it.
Most likely you have modified the ImageUploader37.cab anyhow (e.g. renamed it or changed some files inside it), or it was corrupted. It has made the digital signature invalid. That is why the browser interprets this CAB file as unsigned.
So if you encounter this problem, download Image Uploader Aurigma website again and update the ImageUploader37.cab file on the server.
Although Image Uploader has been built as backward-compatible as possible, if you are using Image Uploader of previous generations, you should make certain changes in your code. They are described in the Upgrading from Previous Versions section.
Also, keep in mind that license keys for previous major versions are not compatible with new version. You should purchase an upgrade. Feel free to contact our sales department if you have any questions regarding this matter.