Timeslips 2016 hanging (not responding) when Bills, Reprint Bills is selected.

Timeslips 2016 (completely up to date) is hanging (not responding) when Bills, Reprint Bills is selected, but only for one user.  We are on Windows 10, not using a terminal server, just database on the network and standalone software installation on the individual workstations. This is the second problem in two days on a single workstation.  No one else is having problems.

The first problem was discovered yesterday, and is the same problem described here: 

http://sagecity.na.sage.com/support_communities/sage_timeslips/f/51/p/94048/267903#267903

This was the fix:

https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=68193&sliceId=1&cmd=&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl

 However, before the fix was applied, the new problem cropped up (TS handing when attempting to access the Reprint Bills dialogue box).  I have searched the forum and knowledge base and haven't found this problem described except in an older version of TS running on a terminal server. 

I have uninstalled and reinstalled TS 2016.  I have switched printers and updated printer and display drivers.  I have changed the compatibility settings in various ways.  The result of changing the compatibility settings is that the first problem crops up again, but it doesn't resolve the second problem.

Anyone have any solutions or even ideas?

  • 0
    Are you reprinting to screen or printer? What else is open on workstation? How much memory on workstation?
  • 0
    We have no found that if one is willing to wait 15 minutes or more, the Reprint Bills dialogue will eventually appear. However, this is unacceptable. Further, this problem has spread to some (but not all) of the other Timeslips users' workstations. No idea what the correlation is. Any suggestions welcome
  • 0 in reply to Mary R
    First, please reconfirm that this is Timeslips v2016, as I am only familiar with the Reprint Bills taking a long time in v2017, so it doing so in v2016 would be new and unusual.

    Second, please check your build number for the version you are running. Under Help, About Timeslips. Let us know specifically what build you are running.

    Third, what is the history with this install? Was it running correctly in the past? What, if anything, was changed recently? Were any Windows updates loaded?

    Fourth, make a backup and run a File | Data Verfication | with ONLY the Look for Errors option checked.

    Fifth, as a work around, if you know the client you are interested in reprinting, use this route to get to the images. (From the topmost menus) Bills | Billing Assistant | Pull up the Client you want to see | Click on Billing Details in the upper left | Click on the bottom menu running down the left - Advanced | Click on Billing History to see that client's images. With v2017, where we have seen the reprints take a while to pull up, this method seems to be able to pull them up quickly.

    Hope this helps.
  • 0 in reply to Nancy Duhon
    1. Yes, Timeslips v2016.
    2. Build 24.0.3.20
    3. The install was running correctly only the morning before the problem was discovered. The first machine on which the problem was identified is used almost exclusively for billing in Timeslips (all day, every day) and reprint bills is a frequently used function. There is another machine (mine) on which the problem also appears, but it is used infrequently to run Timeslips and I never reprint bills, so I cannot say with certaintly that it's a new problem for me. A third machine runs Timeslips constantly, and reprints bills often, and it is unaffected by this problem. I suspected Windows updates, but no new Windows updates were installed in the two days prior to the problem's commencement. Nothing else was installed or changed, unless it was an automatic update performed by one of the myriad programs we run. But it was not Windows and not Microsoft Office, that was easy to determine. As mentioned in my post, there was a problem the day before with printing bills to display, but that was resolved by changing the compatibility settings as suggested in a Sage post (see my original post). Before that problem was corrected, this current problem was discovered, so I don't believe it was the change to the compatibility settings that caused it, and in fact I have changed the back as a test with no change in outcome. HOWEVER, I DID uninstall and reinstall Timeslips during the process of trying to resolve the first problem, and that may have been where this second problem cropped up, I just don't know for sure. I also changed the default printer (and later changed it back) to see if that might have an effect.
    4. We will do this tonight and report back.
    5. I have tried this and it seems to be working. Too bad it's so many steps, but it's faster than waiting 15 minutes.

    I will report back to you on item 4, above. Many thanks!!!!
  • 0 in reply to Caren2
    Screen, but don't get to that point for 15 minutes to it's irrelevant. Timeslips was working perfectly only a few minutes before the problems started, and nothing untoward happened in the interim, not even an update, but only Outlook is open on the workstation (or nothing else at all, in numerous tests), unless you mean background processes, like Kaspersky, printer drivers, etc. One affected workstation has 16 GB of memory, the other has 8 GB.
  • 0 in reply to Mary R
    One thing to try on the problem machine - disable Kaspersky. See if it makes a difference.
  • 0 in reply to Caren2
    Caren, disabling Kaspersky had no effect.
  • 0 in reply to Mary R
    Data verification results will be the next thing.
    If that shows no problems, might suggest uninstall and reinstall BDE. Let me know your email address and I can send you instructions. Uninstalling Timeslips does not uninstall BDE. Do you run Word Perfect?
  • 0 in reply to Caren2
    We will run data verification tonight. Meanwhile, I can uninstall and reinstall BDE on my non-production machine and see if it helps. My email address is [email protected]. Thanks!