Troubleshooting CheckWriter Issues Additional Issues

Issue

Solution

Initialization error (in box at top)

“2147220999: method ‘~’ of object ‘~’ failed

If this error message continues to appear, please contact customer support.

 
Error not supported. Caused by AS400 software. Software FIX: Uninstall AS400 and reboot. CW should resume function. You may also contact AS400 regarding this error.
CREP7 - caused by using some other crystal reports based programs like “metronome” Occurs when printing.

Exact Error Message

“CREP7 20536: E - Aborting”

 
FIX: In this reported case the customer called metronome support where their metronome software had put in an older dll file on their NT machine. They helped to “replace” the “obstinate” file (crpe32.dll in the WINNTdirectory). 
Error 380 - caused by corrupting the database. Corruption can be caused because a computer is shut down without first closing an active session of CheckWriter. Normal use with improper installation on one terminal with the NETWORK edition can cause this error as well. Occurs when opening CheckWriter.

Exact Error Message:

Run-time Error ‘380’: Invalid property value.

 

 
FIX: To fix, back up your database following the Backing Up Your Database directions in this manual. Replace the db with a fresh new db from the CD and then restart each computer BEFORE mapping CheckWriter database drive on each client. This is a 99% fix. To get the data back is a different process. Usually importing the data as if the software was an upgrade will work.  After import, run JetComp.
Zero length string - typically caused when a field is empty but should not be, or when improper data is entered into some fields. The offending field seems to be listed between Tchecks.____________Cannot be… Occurs when printing

Exact Error Message:

Check Error

(CC) NW11:Error-2147217887:field’Tchecks.SigLine’cannot be a zero string length

 
FIX: Ether delete the record and start over, or find where you put the wrong characters and correct your mistake. TIP. The offending field is NAMED in the error message between “Tchecks." and “cannot”. Can also happen when inappropriately changing the signature options in the options menu.
Error saving options to database - caused by installing CW on your “D” drive or any drive other than C without having your network admin alter the drive paths. Occurs when opening CheckWriter or trying to save.

Exact Error Message:

Error 2147286781 saving options to database

 

 

FIX: Install CheckWriter on the C drive in the Program Files directory.  If you cannot do this, you can purchase the Network Edition where you can change the data file path to a custom setting.  If you have the Network Edition, go to the Options menu and alter the file path to reflect the location of your cw50.mdb file.
Bad file name or number - Caused by installing on D:\ or U:\ or other drive instead of C drive with the Single User Version.

Exact Error Message:

Initialization Error

52: Bad file name or number. If this error message continues to appear, please contact cust support.

 

 
FIX: Purchase the Network Edition of CheckWriter or Install the Single User Version on C:\ 

[ or, Have your network admin log in with administrative credentials and alter all of the file path names on your own machine, a process we do not support.]

 
Invalid database path - Caused by installing on D:\ or U:\ or other drive instead of C drive with the Single User Version.

Exact Error Message:

Invalid Database Path. (need CW50.mdb Rev cw5013.)

 

 
FIX: Purchase the Network Edition of CheckWriter or Install the Single User Version on C:\ 

[or, Have your network admin log in with administrative credentials and alter all of the file path names on your own machine, a process we do not support.]

Disappearing text - First time using, when trying to enter text it disappears when I switch fields - this is caused by trying to write to record 0 of 0.

 

 
FIX: Follow the instructions on the hard installation card that came with the software.  It should say, "Please Read Before Installation" at the top of this card.  See, "Entering your first check".  Create a new record by clicking the "Create New Check" button on the CheckWriter tool bar. You will notice you cannot type into record 0 of 0, but once you create a new entry, you will be able to type into record 1 of 1.
PCLXL Error when trying to print

 

 
Fix: HP print driver error, call HP at 208-323-2551 and tell them you have PCLXL error. They will walk through print drive adjustment or update to support the MICR font. Comments: Super easy.
Run Time Error 430

Exact Error Message:

Run Time Error 430: Class does not support automation.

 

 

FIX: Run MDAC file from “support” folder on CD or online support page "troubleshooting" in manual download and install MDAC.

ERRORS BELOW ARE VIRUS 
OR SPYWARE RELATED
DISCLAIMER: This resolution is for information only, and the removal and targeting of spybot and virus related errors is not supported by phone or email.

Installation of the CheckWriter software requires a virus free, and spyware free environment.

http://www.spybot.info/en/download/index.html

VIRUS AND SPYWARE ISSUES

Error 429 active x cannot create object

 

 

 

 

 

 

 

Cause: This issue has been confirmed to be caused by spyware and/or virus infection. Key registry files have been damaged or deleted.

Fix: Remove the spy ware with a spy bot search and destroy application, as found at http://spybot.info and remove any virus using a virus removal software like Norton. Alternatively, you can use another computer and the software will function normally.

DISCLAIMER: This resolution is for information only, and the removal and targeting of spybot and virus related errors is not supported by phone or email.

Installation of the CheckWriter software requires a virus free, and spyware free environment.

http://www.spybot.info/en/download/index.html

After your have removed all spyware and virus problems from your machine, if you still get the same error and your registry entries were not fixed, Microsoft has published an article on how to solve the issue available at the following link ERROR 429 MICROSOFT LINK.
Cannot initialize OLE Engine

 

 

 

 

 

 

 

Cause: This issue has been confirmed to be caused by spyware and/or virus infection. Your p2bdao.dll and/or p2irdao.dll and/or p2ctdao.dll   file or files have been damaged or deleted. Fix: Remove the spy ware with a spy bot search and destroy application, as found at http://spybot.info and remove any virus using a virus removal software like Norton. Alternatively, you can use another computer and the software will function normally.

If your virus and spyware programs remove the problem files but do not repair the damage, you must replace the damaged files.  

Check the version of these 3 files in your \windows\system directory:  Check the versions and integrity of the p2bdao.dll and/or p2irdao.dll and/or p2ctdao.dll files.  Clean copies of these files are available in zip file here.   Use or replacement of these files is at your own risk.  Simply copy the files in ole.zip to your windows\system directory to replace the files there now.  After this, CheckWriter should install normally.
Attempt to install CheckWriter, error message says:

"C:/WINDOWS/SYSTEM32/AUTOEXEC.NT
The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose
'Close' to terminate the application." 

It pops up in a window titled "16 Bit Windows Subsystem".

 

 

 

--------------------------------------->

New Information:  If removal and repair by your virus and spybot programs still do not allow installation of CheckWriter and you get:
 
16 bit Windows Subsystem Error
16-bit MS-DOS Subsystem
path to the program that you are trying to start or install
C:\Windows\System32\Autoexec.nt The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose 'Close' to terminate the application.

 

Cause: This issue has been confirmed to be caused by spyware and/or virus infection. Your autoexec.nt file has been damaged or deleted. Fix: Remove the spy ware with a spy bot search and destroy application, as found at http://spybot.info and remove any virus using a virus removal software like Norton. Alternatively, you can use another computer and the software will function normally.

DISCLAIMER: This resolution is for information only, and the removal and targeting of spybot and virus related errors is not supported by phone or email.

Installation of the CheckWriter software requires a virus free, and spyware free environment.

http://www.spybot.info/en/download/index.html

-----------------------------------

Solution provided by a customer who wrote:  "After spending time running a virus scan (no viruses were found) and running Spybot S&D (11 found). CheckWriter would still not install. The spyware was removed, but the damage was not repaired.

The final fix was to copy 'autoexec.nt' form the windows/repair folder to the windows/system32 folder. After that CheckWriter installed and ran.".