Sage 100

 View Only
  • 1.  I have a client running 4.4 getting Error 65 Windo

    Posted 01-15-2015 07:35
    I have a client running 4.4 getting Error 65 Window element does not exist or already exists when they attempt to either print or preview the SO Sales Journal. The message points to either BT_Preview or BT_Print. I've run the customizer utility to update panels to the current level to no avail. Since this screen is even ""customizable"" not sure what to try next. This issue only applies to one of four companies. No problem for the other three. They are unable to update the year-end invoices and finish inventory adjustments so the heat is on to resolve this. Any ideas are appreciated.


  • 2.  RE: I have a client running 4.4 getting Error 65 Windo

    Posted 01-15-2015 07:48
    WAG: Check that the printer is valid, rebuild data


  • 3.  RE: I have a client running 4.4 getting Error 65 Windo

    Posted 01-15-2015 08:09
    Is this happenning on other PC's as well? I seem to recall soemthing with dual monitors and having to center the Print screen on the main monitor before you press Print. I could be totally off here but worth a try..


  • 4.  RE: I have a client running 4.4 getting Error 65 Windo

    Posted 01-15-2015 08:57
    I'm getting the error when using a Remote Desktop connection so it's not PC specific. That rules out printers too as I attempted to print to my local printer.


  • 5.  RE: I have a client running 4.4 getting Error 65 Windo

    Posted 01-15-2015 12:12
    Reset panel possible?


  • 6.  RE: I have a client running 4.4 getting Error 65 Windo

    Posted 01-15-2015 12:39
    In Customizer: Are either of those buttons (preview and print) off the edges of the screen? Is the main screen large enough to cover the tab screens?


  • 7.  RE: I have a client running 4.4 getting Error 65 Windo

    Posted 01-15-2015 13:09
    Well, turns out the Master Developer (do we still use this term?) that provides EDI interface had modified the program the day after client last updated this Journal in this company. I spotted the program date being so much newer than the other programs, plus a zipped up copy of the program with the developers name on it. They have resolved their error so all is well - except for my tail chasing of the past two days.