Welcome Guest! You need to login or register to make posts.



Go to last post Go to first unread
#1 Posted : Thursday, November 25, 2004 6:00:00 AM(UTC)

Rank: Advanced Member

Groups: Member, Administration, Moderator
Joined: 7/28/2003(UTC)
Posts: 1,656

Thanks: 5 times
Was thanked: 75 time(s) in 73 post(s)
We are carefully testing Image Uploader at various Windows versions, but sometimes you may meet installation problems at some specific configurations. This topic provides guidelines how to gather necessary info that will help us to fix the problem.


Supporting all possible configurations of Windows and Internet Explorer is quite troublesome. We are carefully testing Image Uploader on various configurations, but it may appear that it just fails to work at some machine. The most unpleasant situation is when it just refuses to be installed at this computer. In this case you see a "broken image" icon (small red cross) instead of the control.

Why It May Occur?

The most possible reason for that is lacking of some system files required by Image Uploader. Normally (in 99% of conditions) these files should be available, at all configuration listed at System Requirements section. However during installation of some software or similar situations, some system files may be updated. This may break work of another software that depends on these files (so-called "dll hell" problem).

Typically it happens at Windows 98/ME. Modern versions of Windows does not allow update system files so easily.

How to Determine Whether You Have Depedency Problem?

Control may fail to be installed not only because of missing dependencies. There are a number of another possible reasons: wrong CLSID specified at <object> tag, missing CAB file, etc. So if you get "broken image" instead of control, try to open our online demo page and see if the problem will be reproduced there:


If Image Uploader works here, it means that it is a problem in your code, not in missing dependencies. Otherwise we should go further to get more details.

To establish whether it is a dependency problem or any other failure, try to extract .ocx file from .cab and register it manually. Follow these steps:
  1. Go inside of ImageUploader3.cab with Windows Explorer. You will see files packed at this cabinet file.
  2. Open right-click context menu at file ImageUploader3.ocx and select Copy item.
  3. Go outside of .cab file.
  4. Open right-click context menu and select Paste item.
  5. Open command line (Start -> Run...) and type regsvr32 <full path to ImageUploader3.ocx>\ImageUploader3.ocx.
Registration should fail and similar error message should appear (error code may vary):

LoadLibrary("ImageUploader3.ocx") failed. GetLastError returns 0x00000485. 

The error code displayed here will help us to identify the problem more exactly.

What to Do to Get It Fixed?

First of all, please make a screenshot for the error message displayed by regsvr32 utility. Besides of that, please provide additional information that will help us to determine what file is a reason of the problem.

To obtain additional details, please use Dependency Walker utility. It is a small application which analyzes executive file (such as .dll, .ocx, .exe), checks what external files it depends at, and if any of such files is not available at your machine, it indicates that. You should just load ImageUploader3.ocx into this software, save report file and send it to us. Besides, it may obtain some extra system details which may help us.

Follow these steps:
  1. Download Dependency Walker utility at this location: http://www.dependencywalker.com/depends21_x86.zip.
  2. Extract this archive and run file depends.exe. Dependency Walker window should appear.
  3. Go to menu File -> Open and open ImageUploader3.ocx.
  4. Go to menu File -> Save As... and save a report file (it will call it something like SSubTmr6.dwi) somewhere.
  5. To get extra system details, go to menu View -> System Information. Dialog that describes your system details will be displayed. Copy these details somewhere.
After that please submit case with these files:
  • Screenshot of regsvr32 error message.
  • Dependency Walker report file.
  • System Information obtained from Dependency Walker.
We will try to resolve the problem as soon as possible.

Edited by user Friday, May 23, 2008 3:49:43 PM(UTC)  | Reason: Not specified

Best regards,
Fedor Skvortsov
Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.