Reckon Accounts Launcher has stopped working

  • 1
  • Problem
  • Updated 3 years ago

The above relates to PP2016 - Windows 7 Pro, 64 bit system, 32 gb Ram, and heaps of storage on the harddrive.

For quite a while (many months) I've been getting the above error message.   This is occurring after attaching files to register entries.   In the main, most of the attachments are PDF files. 

It is more an intermittent error as for 80% of the time I can attach files without any problems.

A further problem is that clicking 'Close Program' does NOT close the program, the mouse pointer changes to the animated circular thingo.   Doing an Alt-Tab-Del to access the Task Manager, no programs are listed so can't shut down PP2016 from there.

I'm left with shutting down completely, the whole damn computer.   This is only occurring for PP2016.   It does not occur with any of my other programs, such as Office, Adobe stuff etc.

Any clues or ideas?
Photo of st


  • 2,250 Points 2k badge 2x thumb

Posted 3 years ago

  • 1

What do you see recorded in the Windows Event Log at the time of these errors?

Photo of Rav

Rav, Community Manager

  • 94,150 Points 50k badge 2x thumb
Hi Steven,

Check out this related thread here in particular the suggestions from Reckon FAQ's on March 7 in regard to renaming the file and clean uninstallation.

Does your issue persist after completing the steps outlined in that post?

Let me know how you get on

Photo of st


  • 2,250 Points 2k badge 2x thumb
Thanks Gary and Rav.   

Gary - I had a look at the Windows Event Log but nothing stood out.   Is there something specific I could search for?

Rav - I'll try you suggestion later tonight.
Steven - long shot but often overlooked.  In EVENTS LOG there are sections for system as well as applications,  and if you can observe any failure messages being reported there at  the TIME of the incident,  then you may get a clue as to whether it is a resource issue or some conflict with some system library module or the application program itself.

Dive into the logs when the error has just happened,  to see if the operating system has helped report what is going on.  Not all issues are reported this way - but worth a try.