Printing email invoice along with hard copies in BV2013 crashes BV randomly

There is no specific trigger - different customers, no one particular line item on the invoice, no specific email address. All of the latest patches to Windows 7, BV and Outlook 2007 have been applied. The only common factor is that the crash always occurs on the initial print (email & hard copies) and always prints with no problem when called up from Sales Analysis.

  • 0

    Does this problem occur on more than one workstation? It could be related to a resource or memory issue - if the workstation is rebooted, does the problem go away? Does the user shut down the computer at the end of each work day?

  • 0 in reply to JimmyL

    Only one person does invoices so don't know if it would occur on others. The computer is shut down every night. The problem is very random, maybe 1 invoice in every 75 or so does it. This happened on her old xp machine and continues on the new win7 machine. The network has been replaced and the server as well.

  • 0 in reply to JOYHUT

    I can understand why this would be difficult to troubleshoot and duplicate for that matter since it only happens once every 75 or so. At this point it's probably best over the next while to get the end-user to pay attention to any patterns or common factors when the freeze occurs. For example, what other modules are opened in BusinessVision? What other third-party applications are opened? Perhaps it could be clicking the mouse somewere that is triggering it. Determining the exact events or circumstances will help to get to the bottom of this problem. Hope that helps and all the best!

  • 0 in reply to JimmyL

    Are you getting an error code when it kicks you out.  We were having a similar problem when printing invoices and got error 114 - we finally figured out that BV didn't like the printer driver for our Xerox machine so we print to screen.

  • 0 in reply to Donmar

    no error message - just hangs the system, then boots the user out. Had the same thing start up with another client on Monday. I think we have figured her problem to have been a missing java update. Won't know for probably a day or two but as of this morning getting the latest update SEEMS to have fixed it.