While every effort has been made to insure Sanction II performs flawlessly, there are some issues you might encounter during the initial installation, or after installing another program which may cause Sanction II to work incorrectly. Typically these issues are caused by mismatched system files which can occur when an installation program fails to correctly check file versions. This can also occur if files are "locked" during the installation and the program is unable to fully update all of the necessary files.
Sanction II relies on relatively few system DLLs, however the issues noted below can normally be fixed by downloading and installing the appropriate update.
Sanction II launches, but does not load case databases.
This is usually caused by the DLLs used by Microsoft’s JET /DAO. In most cases, this problem can be fixed by running the Jet 3.5 update located at: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q172733.
If the problem still exists after running this update, there may also be problems with the installed data access components. These additional MDAC files can be updated from http://microsoft.com/data/download_21242023.htm.
Sanction II is unable to play back media files.
This problem is typically caused by an outdated installation of Microsoft Media Player. Sanction II requires Media Player 6.4 or higher. The current version of Media Player can be downloaded from http://www.microsoft.com/windows/windowsmedia/download/default.asp.
Important – The Media Player program must be installed. A plug-in will not work with Sanction II. Some browsers or other programs may install Media Player as a component, not as the full product installation. Regardless of the version indicated by the plug-in, Sanction II will not be a able to properly play back files until the full version has been installed.
Setup continues to prompt with the message: "Setup cannot continue because some system files are out of date…" even after selecting OK to update the files and re-booting.
This is a rather complex issue that requires several steps to overcome. A final step may also be necessary which involves extracting system files directly.
It is strongly recommended that the user read the following Microsoft Knowledgebase Articles regarding this issue prior to attempting the solutions documented. Microsoft Knowledgebase Articles can be accessed from www.support.microsoft.com and entering the Article ID.
Also check the Verdict Systems WEB site for additional resources.
Knowledgebase Articles
Q191096 - PRB: Multiple 'System Files Are Out of Date' Errors
Q140570 - HOWTO: Move Files That Are Currently in Use
Q279764 - PRB: Multiple "System Files Are Out of Date" … on Windows 2000 Computer
Solution #1
Download the VBRun60sp5.exe file and run it. After it completes, run the Sanction II setup program again. This file can be downloaded from Knowledgebase Article Q290887.
Step 1
1. Using Windows Explorer, browse to the Windows subdirectory.
2. If either setup1.exe or Sanctionii.cab file exists in this directory, delete them.
3. Delete all files from the Windows\Temp subdirectory.
Step 2
1. Create a subdirectory off of the root drive called "TempInst" and copy the Sanction II installation files into this directory. If you are running the install from a DEMO CD, copy only the files in the root of the CD. Do not copy any subdirectories.
2. Re-boot the computer and enter windows in Safe Mode. To boot in Safe Mode, hit the F8 function key periodically during the boot up until the Windows DOS menu appears. Select option 3 from this screen. If you do not launch Windows in Safe Mode, you must re-boot and try again.
3. If you are part of a local area network, DO NOT LOG ON. Cancel any log on dialogs. If you on a restricted system which requires that you must log on, log on locally. (You may need to contact your system administrator to allow you to install the program if network DLLs are not allowing an update).
4. Browse to the TempInst subdirectory and launch the Setup.exe program.
5. If the install completes successfully, you may delete the TempInst subdirectory.
If the installation still fails, then you must install the OLE DLLi manually. Follow these steps EXACTLY!
Warning – if you are NOT an experienced windows, it is strongly recommended that you have an experienced user do these steps for you. Failing to backup system files properly can result in an un-bootable system.
Manually updating files is at your own risk - Verdict Systems cannot be responsible for loss of information caused by manually changing system files.
1. Re-boot the computer and again hit the F8 key to bring up the Windows DOS options.
2. Select the Command Prompt only option.
3. Type cd\ to change to the root subdirectory.
4. Type cd windows to change to the windows subdirectory (note if you have installed windows to a different subdirectory, type this name instead).
5. Type cd system to change to the windows system subdirectory.
6. Type ren olepro32.dll olepro32.001 to rename the ole file.
7. Type ren oleaut32.dll oleaut32.001 to rename the ole file.
8. Type extract C:\TempInst\Sanctionii.cab olepro32.dll to extract the ole file.
9. Type extract C:\TempInst\Sanctionii.cab oleaut32.dll to extract the ole file.
10. Type copy C:\TempInst\oleaut32.dll C:\windows\system\oleaut32.dll to copy the file to the windows system directory. (If you have installed Windows in different subdirectory, be sure to indicate the correct path in the destination).
11. Type copy C:\TempInst\olepro32.dll C:\windows\system\olepro32.dll to copy the file to the windows system directory. (If you have installed Windows in different subdirectory, be sure to indicate the correct path in the destination).
12. Re-boot the computer and run the setup program again.
Important – after doing the above, if you experience problems with other programs, rename the backed up files following steps 1 through 5 and then:
6. Type del olepro32.dll
7. Type del oleaut32..dll
8. Type ren oleaut32.001 oleaut32.dll to restore the original ole file.
9. Type ren oleaut32.001 oleaut32.dll to rename the original ole file.
10. Re-boot the computer.