{{tag>category:"OpenInsight 64-bit" author:"Gerry Van Niekerk" author:"bshumsky"}} [[https://www.revelation.com/the-works|Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community]] ==== Printing (OpenInsight 64-bit) ==== === At 14 MAR 2024 07:21:01PM Gerry Van Niekerk wrote: === Hi Everyone Have an issue with printing... Running OI 10.2.1 on a workstation (Windows 10 Pro) Connected to a server 2018 When starting my app in runtime mode the first time I print it says I need to run the client setup When starting in dev mode no issues Have redone client setup 3 times and still the same, and restarted the workstation. Installed from server using \\server\oi..... to install from No difference if running OI on the workstation itself ie copied the system to thew local pc. Any suggestions? Thanks, Gerry ---- === At 15 MAR 2024 09:31AM bshumsky wrote: === Hi, Gerry. OIPI "classic" or OIPI.Net (VSPRINTER1 or VSPRINTER2)? Can you capture the exact text that you're seeing? Can you look at the shortcuts that you're using for the runtime vs dev mode - are there any differences? Is one set to "run as administrator", and the other isn't, for example? Thanks, - Bryan Shumsky [url=https://www.revelation.com]Revelation Software, Inc.[/url] ---- === At 17 MAR 2024 07:02PM Gerry Van Niekerk wrote: === Hi Bryan. Oipi.net - VSPRINTER2 logins are as follows: \\csb_server\clients\Strata\Strata10\OpenInsight.exe /AP=STRATA /un=STRATA /pw=.... /DV=0 \\csb_server\clients\Strata\Strata10\OpenInsight.exe /AP=STRATA /PW=.... /un=STRATA /DV=1 message as follows: Please run the client installation process (clientsetup.exe) to install OIPNet on this workstation same message if I run manually from a mapped drive Thanks.. Gerry ---- === At 18 MAR 2024 08:10AM bshumsky wrote: === Hi, Gerry. That message is displayed when we're unable to communicate with the OIPI.Net control. The fact that you see it in one case, and not the other, suggests that you are running one shortcut as admin, and the other not - unless you use the two different shortcuts as two different users on the desktop? Try to run the runtime (non-dev) shortcut by right-clicking on it, then choose "Run as Administrator" - does printing work then? If it still doesn't, then start up the dev shortcut the same way (right click, run as administrator), and see if the printing error now appears there? One other question - it seemed from your initial post that maybe you're saying the error appears the first time you try to run OIPI.Net in "runtime" mode, but does that mean that when you run OIPI.Net again subsequently in the same session it now works? Or in runtime mode, it is always failing? Thanks, - Bryan Shumsky [url=https://www.revelation.com]Revelation Software, Inc.[/url] ---- === At 18 MAR 2024 06:31PM Gerry Van Niekerk wrote: === Hi Bryan, Run as admin didn't make a difference. Will do more testing and let you know. Gerry ---- === At 19 MAR 2024 08:06PM Gerry Van Niekerk wrote: === I solved the Mystery... When testing I used one particular report. When I printed a different report the error didn't appear and printing was fine. So what was the difference. In this report we call a procedure that in return call a form to tell me to print to Screen, Printer etc. In the code (legacy code) it calls the procedure again with certain paramaters, from a Button. Then the code said end_window(@window) when I changed it to send_event(@window,'CLOSE') NO MORE ERROR.. and only happens when in Runtime mode. So it's now working correctly. Gerry ---- === At 20 MAR 2024 05:02AM bshumsky wrote: === Hi, Gerry. Glad you solved it. - Bryan Shumsky [url=https://www.revelation.com]Revelation Software, Inc.[/url] [[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=E2B0A59AC5E66E4D90BD238D8C1D2CFE|View this thread on the Works forum...]]