Click to see
all of our products!
Wieser Software

Payslips for RTI PAYE Tools

Version 2.27 released.

Print Payslips from HMRC's free RTI tools!
Works with 2017 PAYE Tools!

Works with Windows 7, 8, 8.1 and 10!

 

Crashes

When our software crashes, it writes a crash dump to your disk. This file is installed in the Program Data folder, which may be hidden on your computer. Normally, on a crash it would compose an email containing the file "C:\ProgramData\Wieser Software\Payslips for PAYE Tools\errorLog.txt", however if you are using a webmail service only for your email, that won't work successfully, and you'll have to send that file manually.

To confuse things even more, on XP, that file is located in
"C:\Documents and Settings\All Users\Application Data\Wieser Software\Payslips for PAYE Tools"


While a program should never crash, occasionally one slips through.
Here are the crashes we know about, and how to work around them:
Why do I get a NET Framework Intialization Error on first run?
I get a database cannot be opened error! Printing and Print Preview fails on my machine
Printing on a virtual machine crashes
Printing crashed with the message "Illegal characters in path."
Printing crashed with the message "PrintTicket provider failed to retrieve PrintCapabilities"
I manually edited your configuration files, and now the software doesn't work.


Why do I get a NET Framework Intialization Error on first run?

Some customers have reported that when the program is first run, it may display the following error message: Net Framework Initialization Error This can happen in several ways. Either the .NET Framework was removed from your system (you can check on the Programs and Features item in the Control Panel), or your system may need a reboot immediately after installation of the Framework. If you continue to have this error after a reboot, please contact us by email for further assistance.

Back to top


I get a database cannot be opened error!

Some customers have reported that when purchasing the full version, it may display the following error message: A null was returned after calling the 'GetService' method on a store provider instance of type 'System.Data.SQLite.SQLiteFactory'.

As far as we've been able to ascertain, this is caused by installing the full version while a trial version is running, and choosing not to close the running copy, and instead rebooting. What this does, if performed in this order is uninstalls a crucial piece of the software. The solution is simply to reinstall Payslips for PAYE Tools, and let it repair the installation.

Back to top


Problems printing

We have hundreds of installations of the program working correctly, but every now and then we get a report of printing just not working.

When this happens, we take the time to investigate what's gone wrong, but in every case we've investigated so far it's been a problem with something other than our program. In an attempt to help diagnose this, we recommend you follow the following steps, one at a time.

If the above steps fail to work, please contact us, as we're always interested to find out why things aren't working the way the should be.

Back to top


Printing on a virtual machine crashes

When you encounter an error, you will see this message: Tell Microsoft about this problem window In general, you should send the Error report, as we can get these and fix the problems. It also helps Microsoft find a repair bugs.

In this case, clicking show details gave this signature:

AppName: payslipsforpayetools.exe AppVer: 1.5.0.1 ModName: unknown
ModVer: 0.0.0.0 Offset: 0a06f876

This error turned out to be caused by using a virtual printer driver on my virtual machine. Installing the free Microsoft XML Paper Specification Essentials Pack from Microsoft fixes this.

Back to top


Printing crashed with the message "Illegal characters in path."

This is caused by some other software installed on your system that modified your registry.

The list of fonts on your machine are stored in the following hive in the registry:
HKEY_LOCAL_MACHINE/Software/Microsoft/Windows NT/Current Version/Fonts

If you examine this hive, you'll see names of the font as the Name, and the filename of the font as the value. The problem is that the filename has hidden characters appended to the end of it. To fix the error, all you need to do is rewrite the font entry by double clicking the name and then press OK. The problem is there are hundreds of potential entries and only some of them will be wrong.

To help find them, we've created a command line program that finds the entries that are broken. Keep running the program, and editing the entry until it no longer reports failure.

You can download it from this zip file

Technical details on our blog

From Version 1.06, if you find your system exhibits this problem, if you run the program as an administrator with the a command line argument as follows: PayslipsForPAYETools /fixfonts

Back to top


We've also had a report of getting a PrintTicket provider failed to retrieve PrintCapabilities.

Apparently, installing the Microsoft XML Paper Specification Essentials Pack from the Microsoft website may fix this problem, though we haven't managed to verify this. We did find on a machine that didn't print with this error (using a Kodak ESP C310) printer, that printing to the XPS printer driver did work, indicating a problem with the driver.

On the particular machine we found this problem on, changing the printing preferences to "print directly to printer" fixed the problem.

Back to top


I manually edited your configuration files, and now the software doesn't work.

The best way to fix this is to make copies of the original files before you do this, and copy them back. Of course, you probably didn't if this is your problem and you're reading this. In that case, uninstall and reinstall the software.

Back to top


"Windows is a registered trademark of Microsoft Corporation in the United States and other countries."

Read our privacy policy
Copyright © 2011-2017 by Wieser Software
All Rights Reserved