Error loading database (OpenInsight 64-bit)
At 13 JAN 2022 07:12:46PM Donald Bakke wrote:
A few, but not all, of us are seeing this problem:
This seems to only happen when gonig from a child app (including EXAMPLES) to SYSPROG, but never the other way around. I managed to create an engine log when this happened. Here is the last entry:
****************************************************************************** Begin processing time: 1/13/2022 15:45:34 RUN BCHECKLEGALUSER 'SYSPROG', 'SYSPROG', '𖜖•—Š‚', 0, 0 Stop processing time: 1/13/2022 15:45:34 Execution time: 15 milliseconds. Execution status: failed. Error code: SSP322. ******************************************************************************SSP322 means "invalid password". This is definitely a valid password because we can open SYPROG directly with that password. This makes me think the problem is a holdover from one of the earlier betas that seemed to corrupted existing users. Not all of us arrived to 10.1 using the same starting point and upgrade path. This might explain why some of us see the problem and some do not.
Is anybody else seeing this?
At 28 DEC 2022 07:50PM Joshua Goddard wrote:
yes
At 28 DEC 2022 08:15PM Barry Stevens wrote:
yes
Yes, BUT, if you stop the oengineserver it works, so, I assume there is some sort of corruption there in the oeserver.cfg file, not that I can see anything obvious.
At 28 DEC 2022 10:17PM Joshua Goddard wrote:
How is the oengnie serve related this? By oengine server do yoy mean that java program?
At 28 DEC 2022 11:33PM Barry Stevens wrote:
How is the oengnie serve related this? By oengine server do yoy mean that java program?
In Task Manager services I see - OEngineServer v10.0 (OpenJDK) which uses info in the eserver.cfg file that is in the OI root folder, which appears to have app logon info.
That is as far as my knowledge extends.
At 28 DEC 2022 11:35PM Donald Bakke wrote:
How is the oengnie serve related this? By oengine server do yoy mean that java program?
In Task Manager services I see - OEngineServer v10.0 (OpenJDK) which uses info in the eserver.cfg file that is in the OI root folder, which appears to have app logon info.
That is as far as my knowledge extends.
Barry - I think Joshua is pointing out that the problem that I originally reported and that he confirmed has nothing to do with the OEngineServer. This is happening when launching OI as a desktop application.
At 29 DEC 2022 02:14AM Barry Stevens wrote:
How is the oengnie serve related this? By oengine server do yoy mean that java program?
In Task Manager services I see - OEngineServer v10.0 (OpenJDK) which uses info in the eserver.cfg file that is in the OI root folder, which appears to have app logon info.
That is as far as my knowledge extends.
Barry - I think Joshua is pointing out that the problem that I originally reported and that he confirmed has nothing to do with the OEngineServer. This is happening when launching OI as a desktop application.
I know, but I was reporting that I can reproduce it, but, not when I stop the service.
At 29 DEC 2022 10:52AM bshumsky wrote:
Hi, everyone.
Barry, perhaps due to the intermittent nature of this bug, it _seems_ like it's related to the engine server begin stopped, but it may not be.
I know that all 3 of you guys are running the 10.2 beta - can you confirm that you're still seeing this problem with the latest beta?
Thanks!
- Bryan Shumsky
At 29 DEC 2022 06:08PM Barry Stevens wrote:
Hi, everyone.
Barry, perhaps due to the intermittent nature of this bug, it _seems_ like it's related to the engine server begin stopped, but it may not be.
I know that all 3 of you guys are running the 10.2 beta - can you confirm that you're still seeing this problem with the latest beta?
Thanks!
- Bryan Shumsky
Running beta 4
At 29 DEC 2022 07:31PM Joshua Goddard wrote:
I am running beta 2.
This error randomly stopped happening, so I think it's good now
At 31 DEC 2022 01:40AM Donald Bakke wrote:
Hi, everyone.
Barry, perhaps due to the intermittent nature of this bug, it _seems_ like it's related to the engine server begin stopped, but it may not be.
I know that all 3 of you guys are running the 10.2 beta - can you confirm that you're still seeing this problem with the latest beta?
Thanks!
- Bryan Shumsky
I cannot replicate this issue. I've tried several fresh installs of OI 10, from 10.0.1 through 10.2.0 Beta 4. I've tried upgrading from 10.0.1 through 10.1.0, and tested the issue during each upgrade along the way.