OLE ERRORS

OLE ERRORS

Scrap Dragon OLE Errors

OLE errors are usually generated by either a missing or unregistered file on a particular workstation. Scrap Dragon is trying to execute an external program or Active X control that Windows can’t find. Running local setup while signed in as an administrator should copy and register all of the needed files. Be sure to select the option to ‘Install OCX DLL registry tool’ during local setup. If the OLE errors continue, try one or all of these solutions:

Missing JPEGger Viewer

If the OLE error occurs when you are trying to view pictures in JPEGger, then it is possible that Scrap Dragon has not been properly configured to launch the JPEGger viewer. In Scrap Dragon; Back Office; Maintenance; Setup; Local Computer Options; Imaging Tab, check that the JPEGger viewer is pointing to an existing file. The easiest way to do this is to click on the button with the 3 dots to the right of the space to enter the JPEGger viewer program and browse to the viewer program, usually C:\program files (x86)\jpegger\multiviewer.exe. 

Missing JpeggerClient

If the OLE error occurs at a point that a picture is normally taken, eg. when reading the scale, or paying a customer, then it is possible that Scrap Dragon has not been properly configured to launch the JPEGger client. In Scrap Dragon; Back Office; Maintenance; Setup; Local Computer Options; Imaging Tab, check that the jpegger client is pointing to an existing file. The easiest way to do this is to click on the button with the 3 dots to the right of the space to enter the JPEGger capture program and browse to the C:\program files(x86)\jpegger\jpeggerclient.exe file. 

Unregistered Calendar Control

If the OLE error occurs before displaying a screen with a place to enter a date and the calendar does not display when entering the date, then the calendar Active X control is not registered. Use the Manually Unregister and Reregister a control procedure below on the following files:
msacal70.ocx
mscomct2.ocx
mscomm32.ocx

Unregistered Image Control

If the OLE error occurs before displaying a screen with a picture and the picture does not display, then the Imaging Active X control is not registered. The solution is to manually unregister and re-register the Imaging control. Use the Manually Unregister and Reregister a control procedure below on the following file:
ImageEnXLibrary.ocx.

Unregistered Windows Socket Control

If the OLE error occurs when communicating with TCP/IP to EZCash or other devices, then the Windows Socket control is not registered. The solution is to manually unregister and re-register the Windows Socket control. Use the Manually Unregister and Reregister a control procedure below on the following file:
mswinsck.ocx

Unregistered Secure FTP Control

If the OLE error occurs when communicating via Secure FTP, then the We Only Do Software FTP control is not registered. The solution is to manually unregister and re-register the We Only Do Software FTP control. Use the Manually Unregister and Reregister a control procedure below on the following file:

wodsftp.ocx

Manually Unregister And Reregister A Control using the OCX DLL registry tool

Often, the solution is to manually unregister and re-register a control file. You must be logged into the computer as an administrator for this procedure to succeed. Browse to the c:\windows\system32 folder or the location of the control to register.  Repeat this procedure for each of the unregistered files. Highlight the file, right click to display a menu and then left click Unregister. Do this 3 times. Each time the system will respond with ‘unregister successful’. Then right click to display a menu and then left click Register. The system will respond with ‘Register successful’. This technique will only work if you selected the option to ‘Install OCX DLL registry tool’ during local setup.

Manually Register A Control using the regsvr32 utility

Often, the solution is to manually register a control file. At an elevated CMD prompt (run as administrator) enter the command:

regsvr32 filename

the filename must include the complete UNC path and can reference a file on the server.  when issued with the -/u parameter the command will unregister the control.  complete documentation for this command can be found at this link: