{{tag>category:"OpenInsight 32-Bit" author:"Clare Robinson" author:"Bob Carten"}} [[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]] ==== OECGI2 Debugging Under 64-bit Windows 7 (OpenInsight 32-Bit) ==== === At 11 JAN 2011 06:23:38PM Clare Robinson wrote: === I am attempting to write web services using OECGI2 and OpenInsight 8.0.8. I have followed the instructions to set up debgugging and under Windows XP it works perfectly - putting a Debug statement into a function correctly stops. If, however, I run under Windows 7 with the same configuration (except with the registry entries under Wow6432Node), the OESocketServer (running in debug mode from the command line) reports: "Engine creation FAILED, code *-38*" and the same code is returned to the client. If the OESocketServer is set up as a service, the code returned to the client is -1003. Once it has failed once, even if I take the debug statement out and recompile and restart the OESocketServer (but not the OI Engine, whether the application is running or not) it still fails. Shutting down the OI Engine and restarting it allows it to work properly. Also, just shutting down, whether or not the debug statement is taken out also allows it to work. Note that this also affects 9.2.0 in exactly the same way. I have tried: * running the OI Engine both in native Windows 7 and in XP SP3 compatibility mode. * running both the OI Engine and the OESocketServer as administrators. In addition: * UAC is off * The installation of 8.0.8 was a copy of the directory from Windows XP (via a zip file so as not to run foul of Windows 7 security issues that occur when copying directories across the network) so I know everything there is the same in both XP and Windows 7. My fall back is to continue development under Windows XP and then verify under Windows 7 but it would be nice not to have to run the XP virtual machine. There is probably some tiny thing I have overlooked. Any assistance would be greatly appreciated. ---- === At 11 JAN 2011 09:21PM Bob Carten wrote: === 38 is REV_ERR_ENGINE_EXISTS 1003 is REV_ERR_LOGON The messages could be a symptom that you are trying to start multiple engines with a single engine license, for example if you are running regular oinsight and trying to run the socket server too, or they could a symptom that you have instructed OECGI to start a named engine which is already running. Try a blank servername with StartupFlags and ShutdownFlags both equal 1, or specify a servername in the registry, set StartupFlags and ShutdownFlags both equal zero and manually start an oengine with the servername you have specified by using the /sn= parameter. ---- === At 12 JAN 2011 02:25PM Clare Robinson wrote: === Hi Bob, Thank you for your response. Changing the StartupFlags and ShutdownFlags values both to 0 did the trick in the Windows 7 64-bit environment (the Windows XP environment did not need this). In summary, the working solution for Windows 7 64-bit had registry settings of (in addition to the others in the oecgi2.reg file): EngineName: (same as /SN= setting) StartupFlags: 0 ShutdownFlags: 0 This worked for both 8.0.8 and 9.2.0. For those still on OI 8 and using Windows 7 64-bit, the registry keys need to be put at: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\RevSoft\OECGI2 (discovered by looking at the oecgi2_WOW6432.reg file in the 9.2.0 version of OI). For Windows XP I was using, successfully: EngineName: (same as /SN= setting) StartupFlags: 2 ShutdownFlags: 0 as per the OECGI2 debugging document (which I can't find now). Changing StartupFlags to 0 on Windows XP also worked. Thank you for your assistance. Regards Clare [[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=977DA780AF047C5E85257815008081A9|View this thread on the Works forum...]]