Troubleshooting
Troubleshooting
I have accidentally started printing a long report, but need to end it immediately
Cancel the print job in Simple Accounting, then go to the Windows Control Panel, select Printers. You should see the job in the Print Manager. Select Purge to end the job. If the printer continues to print, clear its internal print buffer by turning it off, then back on, according to the manufacturer’s instructions.
Posted In: TroubleshootingReports print unnecessary blank pages
Check to see that you have selected the correct printer driver in the Windows Control Panel. Also, check that there is not already some left over garbage in your printers internal buffer.
Posted In: TroubleshootingReports print in the wrong typeface, or with strange characters on each page
Check to see that you have selected the correct printer driver installed in the Windows Control Panel.
Posted In: TroubleshootingUnknown Error Posted: 755:WSLSTG
While running Simple Accounting I receive the following error message in a dialog box which shuts down the program: Unknown Error Posted: 755:WSLSTG This error is posted when the system detects a shortage of memory (system resources). To remedy this situation, increase the size of your permanent swap file to allow for more memory usage…. Read more.
Posted In: TroubleshootingInternal Error WSLDIAL
While running Simple Accounting I receive the following error message in a dialog box which shuts down the program: "Internal Error: WSLDIAL – 02" This can occur if you are using an outdated Simple Accounting DLL. DLLs contain program code which supports the main software. Each DLL version must match the main EXE version in… Read more.
Posted In: TroubleshootingInvalid Data Path
When I start Simple Accounting I immediately see a dialog box which says that my data path is invalid and I need to edit the SIMPLE.INI file on this workstation. You have entered an invalid path to data in the users SIMPLE.INI file. Each user of Simple Accounting may have their own personal SIMPLE.INI file… Read more.
Posted In: Troubleshooting